SOLVED All SAS disks aren't displaying their serial number in the webui

[regnock]

Hi,

I'm running the current stable version of 9.10. Currently none of my SAS disks are displaying their serial numbers in the webui. My two SSD and two NVME devices are reporting them correctly. All the problem drives are hanging off a AVAGO MegaRAID SAS controller.

Also possibly related. I added descriptions to all of these disks and they didn't survive after my web session.

I have attached a screenshot, that shows the missing serial numbers. Those descriptions are now gone also.

Is this a known issue?

 

[Jailer]

All the problem drives are hanging off a AVAGO MegaRAID SAS controller

Which specific model and what firmware version?

 

[Arwen]

Maybe bad news. The MegaRAID is not a HBA, (Host Bus Adapter), if I recall this correctly.
Thus, you may not get SMART data from the drives either. And ZFS may not beable to cause
a SAS / SCSI block sparing.

But, as @Jailer asked, please supply the model of the Avago / LSI card.

 

[regnock]

Which specific model and what firmware version?

Hi,

Thanks for the replies.

The controller is a LSI MegaRAID 9361-8i SAS 12Gb/s PCIe 3.0 8-Port Controller with 1GB Cache

Here is the relevant snippet from dmesg which contains the firmware version:

Code:

mfi0: 359019 (533784522s/0x0020/info) - Shutdown command received from host

mfi0: 359020 (boot + 10s/0x0020/info) - Firmware initialization started (PCI ID 005d/1000/9361/1000)

mfi0: 359021 (boot + 10s/0x0020/info) - Firmware version 4.290.00-4536

mfi0: 359022 (boot + 13s/0x0008/info) - Battery Present

mfi0: 359023 (boot + 13s/0x0020/info) - Package version 24.9.0-0022

mfi0: 359024 (boot + 13s/0x0020/info) - Board Revision 11A

mfi0: 359025 (boot + 18s/0x0008/info) - Battery charge complete

mfi0: 359026 (boot + 18s/0x0008/info) - Battery temperature is normal

mfi0: 359027 (boot + 32s/0x0004/info) - Enclosure (SES) discovered on PD 23(c Port 0 - 3/p1)

mfi0: 359028 (boot + 32s/0x0004/info) - Enclosure (SES) discovered on PD 08(c Port 0 - 3/p2)

mfi0: 359029 (boot + 32s/0x0004/info) - Enclosure (SES) discovered on PD 2a(c Port 4 - 7/p1)

mfi0: 359030 (boot + 32s/0x0004/info) - Enclosure (SES) discovered on PD 09(c Port 4 - 7/p2)

mfi0: 359031 (boot + 32s/0x0004/info) - Enclosure PD 08(c Port 0 - 3/p2) communication restored

mfi0: 359032 (boot + 32s/0x0004/info) - Redundant enclosure EMM PD 09(c Port 4 - 7/p2) inserted for EMM PD 08(c Port 0 - 3/p2)

mfi0: 359033 (boot + 32s/0x0004/info) - Enclosure PD 09(c Port 4 - 7/p2) communication restored

mfi0: 359034 (boot + 32s/0x0004/info) - Enclosure PD 23(c Port 0 - 3/p1) communication restored

mfi0: 359035 (boot + 32s/0x0004/info) - Redundant enclosure EMM PD 2a(c Port 4 - 7/p1) inserted for EMM PD 23(c Port 0 - 3/p1)

mfi0: 359036 (boot + 32s/0x0004/info) - Enclosure PD 2a(c Port 4 - 7/p1) communication restored

mfi0: 359037 (boot + 32s/0x0002/info) - Inserted: Encl PD 08

ses0 at mfi0 bus 0 scbus0 target 8 lun 0

ses0: <LSI SAS2X28 0e12> Fixed Enclosure Services SPC-3 SCSI device

ses0: Serial Number 

ses0: 150.000MB/s transfers

ses0: Command Queueing enabled

ses0: SCSI-3 ENC Device

ses1 at mfi0 bus 0 scbus0 target 9 lun 0

ses1: <LSI SAS2X28 0e12> Fixed Enclosure Services SPC-3 SCSI device

ses1: Serial Number 

ses1: 150.000MB/s transfers

ses1: Command Queueing enabled

ses1: SCSI-3 ENC Device

ses2 at mfi0 bus 0 scbus0 target 35 lun 0

ses2: <LSI SAS2X36 0e12> Fixed Enclosure Services SPC-3 SCSI device

ses2: Serial Number 

ses2: 150.000MB/s transfers

ses2: Command Queueing enabled

ses2: SCSI-3 ENC Device

ses3 at mfi0 bus 0 scbus0 target 42 lun 0

ses3: <LSI SAS2X36 0e12> Fixed Enclosure Services SPC-3 SCSI device

ses3: Serial Number 

ses3: 150.000MB/s transfers

ses3: Command Queueing enabled

ses3: SCSI-3 ENC Device

 

[ItsValium]

Bummer, no real HBA like allready suggested, any chance you could exchange it for a real HBA?

 

[Ericloewe]

SAS3... Good news is that you may be able to use it with the new software stack, which replaces mfi and does support direct-attach disks. Search the forums for how to use mrsas instead of mfi.

 

[regnock]

SAS3... Good news is that you may be able to use it with the new software stack, which replaces mfi and does support direct-attach disks. Search the forums for how to use mrsas instead of mfi.

Switching the driver worked! I now see serial numbers and my custom descriptions appear to be sticking. Thanks for all the help.

 

[Arwen]

@Ericloewe, thanks for picking up that detail about the driver switch.

@regnock,
Please check to see if you can get SMART data from the drives. It should work now but there is a
saying, if you did not test it, it does not mean it will work.

 

[regnock]

@Ericloewe, thanks for picking up that detail about the driver switch.

@regnock,
Please check to see if you can get SMART data from the drives. It should work now but there is a
saying, if you did not test it, it does not mean it will work.

I am getting SMART data from the drives now :)

 

[Ericloewe]

@Ericloewe, thanks for picking up that detail about the driver switch.

FWIW, the new stack works with all LSI SAS3 controllers and with the SAS2308 - the latter might be interesting for vendor-locked cards with no IT firmware.