Disks connected to SAS expander/JBOD can't be connected/accessed

Bug #1977760 reported by Fabian Kurtz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When starting up drives connected by SAS expanders (e.g. inside JBOD cases), those disk do not show up and dmesgs notes the following error:
mpt3sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:6955/_scsih_expander_add()!

It seems there is some kind of limit in terms of expanders (attached to different HBA Ports) which didn't previously exist. This error occurs at least under Ubuntu 20.04 and 22.04.

Current config: Ubuntu 22.04 LTS (5.15.0-35-generic #36-Ubuntu SMP Sat May 21 02:24:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-35-generic 5.15.0-35.36
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
Uname: Linux 5.15.0-35-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
AlsaDevices:
 total 0
 drwxr-xr-x 2 root root 60 Jun 5 14:07 by-path
 crw-rw----+ 1 root audio 116, 2 Jun 5 14:07 controlC0
 crw-rw----+ 1 root audio 116, 1 Jun 5 14:07 seq
 crw-rw----+ 1 root audio 116, 33 Jun 5 14:07 timer
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-35-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
Date: Mon Jun 6 16:16:57 2022
HotplugNewDevices:

HotplugNewMounts:

InstallationDate: Installed on 2022-06-05 (1 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic root=UUID=0d9d27ee-535c-4da0-baec-ee3a6b4a7ba4 ro mpt3sas.max_queue_depth=10000
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-35-generic N/A
 linux-backports-modules-5.15.0-35-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 16:17:00.150: The udisks-daemon is running (name-owner :1.4).
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-6.2
dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-6.2
dmi.sys.vendor: QEMU

Revision history for this message
Fabian Kurtz (mr-goodcat) wrote :
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.