Issues with 9207-8e and MD1200

[faring]

R430 with a SAS 9207-8e connected to a MD1200 (unified+redundant) with 3 14TB WD SATA drives.

 

I'm not seeing the 9207 show in BIOS or iDRAC, or during startup (BIOS or UEFI mode). Once Unraid is up, it's not showing the 9207 or MD1200 in system devices. I've tried single connection to each of the MD1200 controllers as well, and moving the 9207 to the other slot, still the same. Also not getting lights on the drives. What's really throwing me for a loop is that it IS being recognized and given a SCSI ID during the OS boot:

 

Mar  5 15:43:36 Tower kernel: mpt2sas_cm0: hba_port entry: 00000000696f4739, port: 255 is added to hba_port list
Mar  5 15:43:36 Tower kernel: mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x500605b009a8c070), phys(8)
Mar  5 15:43:36 Tower kernel: mpt2sas_cm0: expander_add: handle(0x0009), parent(0x0001), sas_addr(0x500c04f28aba8e3f), phys(38)
Mar  5 15:43:36 Tower kernel: expander-2:0: add: handle(0x0009), sas_addr(0x500c04f28aba8e3f)
Mar  5 15:43:36 Tower kernel: mpt2sas_cm0: handle(0xa) sas_address(0x500c04f28aba8e3d) port_type(0x1)
Mar  5 15:43:36 Tower kernel: scsi 2:0:0:0: Enclosure         DELL     MD1200           1.01 PQ: 0 ANSI: 5
Mar  5 15:43:36 Tower kernel: scsi 2:0:0:0: set ignore_delay_remove for handle(0x000a)
Mar  5 15:43:36 Tower kernel: scsi 2:0:0:0: SES: handle(0x000a), sas_addr(0x500c04f28aba8e3d), phy(36), device_name(0x0000000000000000)
Mar  5 15:43:36 Tower kernel: scsi 2:0:0:0: enclosure logical id (0x500c04f28aba8e00), slot(36) 
Mar  5 15:43:36 Tower kernel: scsi 2:0:0:0: qdepth(1), tagged(0), scsi_level(6), cmd_que(0)
Mar  5 15:43:36 Tower kernel: scsi 2:0:0:0: Power-on or device reset occurred
Mar  5 15:43:36 Tower kernel: sd 2:0:0:0: Attached scsi generic sg2 type 13
Mar  5 15:43:36 Tower kernel: end_device-2:0:0: add: handle(0x000a), sas_addr(0x500c04f28aba8e3d)
Mar  5 15:43:36 Tower kernel: ata7: SATA link down (SStatus 0 SControl 300)
Mar  5 15:43:36 Tower kernel: mpt2sas_cm0: expander_add: handle(0x000b), parent(0x0002), sas_addr(0x500c04f28aba8ebf), phys(38)
Mar  5 15:43:36 Tower kernel: expander-2:1: add: handle(0x000b), sas_addr(0x500c04f28aba8ebf)
Mar  5 15:43:36 Tower kernel: mpt2sas_cm0: handle(0xc) sas_address(0x500c04f28aba8ebd) port_type(0x1)
Mar  5 15:43:36 Tower kernel: scsi 2:0:1:0: Enclosure         DELL     MD1200           1.01 PQ: 0 ANSI: 5
Mar  5 15:43:36 Tower kernel: scsi 2:0:1:0: set ignore_delay_remove for handle(0x000c)
Mar  5 15:43:36 Tower kernel: scsi 2:0:1:0: SES: handle(0x000c), sas_addr(0x500c04f28aba8ebd), phy(36), device_name(0x0000000000000000)
Mar  5 15:43:36 Tower kernel: scsi 2:0:1:0: enclosure logical id (0x500c04f28aba8e00), slot(36) 
Mar  5 15:43:36 Tower kernel: scsi 2:0:1:0: qdepth(1), tagged(0), scsi_level(6), cmd_que(0)
Mar  5 15:43:36 Tower kernel: scsi 2:0:1:0: Power-on or device reset occurred
Mar  5 15:43:36 Tower kernel: scsi 2:0:1:0: Attached scsi generic sg3 type 13
Mar  5 15:43:36 Tower kernel: end_device-2:1:0: add: handle(0x000c), sas_addr(0x500c04f28aba8ebd)

 

 

[JorgeB]

Please post the diagnostics.

[faring]

Sure, attached.

tower-diagnostics-20230306-1001.zip

[JorgeB]

The HBA is being correctly initialized and the enclosure is being detected:

 

[2:0:0:0]    enclosu DELL     MD1200           1.01  -          /dev/sg2
  state=running queue_depth=1 scsi_level=6 type=13 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/2:0:0:0  [/sys/devices/pci0000:00/0000:00:03.0/0000:05:00.0/host2/port-2:0/expander-2:0/port-2:0:0/end_device-2:0:0/target2:0:0/2:0:0:0]
[2:0:1:0]    enclosu DELL     MD1200           1.01  -          /dev/sg3
  state=running queue_depth=1 scsi_level=6 type=13 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/2:0:1:0  [/sys/devices/pci0000:00/0000:00:03.0/0000:05:00.0/host2/port-2:1/expander-2:1/port-2:1:0/end_device-2:1:0/target2:0:1/2:0:1:0]

 

Note that Unraid does not support SAS multipath, so there should be a single cable form the HBA to the enclosure, though that's not why the devices are not being detected, but since the enclosure is it suggests the problem is between the drives and the enclosure.

 

 

[faring]

Thanks, that gives me a place to start.