LSI-9201-16E Troubles

New JBOD(same model) arrived… SATA drives still do not detect. This time though, the orange LED that shows non official drives is actually turning on. This is different than the last JBOD in hindsight.

I’ve noticed on both JBODs, that the interposers for SATA, will quickly flash green, but then the lights turn off. This was behavior that only occurred on the SATA drives, as the SAS drives remained green. The SATA drives still seem to spin though. I’ll also try with the new SAS drives when they arrive. Any advice would be golden. Do you think it could be a compatibility issue with the MB? It seems odd as the device itself can be detected/lanes assigned.

Have these drives worked in any system of yours?
If not, the only remaining idea I have is that they are sensitive to 3.3V power (google “hdd 3.3v pin”, I personally fixed mine by using kapton tape).

The SATA drives indeed were working in my old system. I can also do a sanity check and connect them via regular SATA. I’ll do that within the hour. I’ll also look into the 3.3v thing. The new SAS drives should be arriving sometime today, so I’ll also report any updates regarding those.

Have yet to test the 3.3v thing for SATA, but the new SAS drives (512) are still not detecting. I’m pretty confident it’s either my motherboard itself, or some setting at this point. I’m at a loss though. I’ve found references about adding this into grub, mpt3sas.max_queue_depth=10000, yet it changes nothing.

lspci is showing the correct controller.
01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] (rev 02)

lspci -k|grep mpt3sas reveals this:
Kernel driver in use: mpt3sas
Kernel modules: mpt3sas

sas2flash -listall reveals
LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved

    Adapter Selected is a LSI SAS: SAS2116_1(B1) 

Num Ctlr FW Ver NVDATA x86-BIOS PCI Addr

0 SAS2116_1(B1) 20.00.07.00 14.01.00.07 07.39.02.00 00:01:00:00

Everything seems right. I literally just don’t know what to do now. I can go about attempting to connect it to another known good working Desktop. I do have an older one (LGA1151) but outside of that, I’m lost. I feel extremely defeated I fear.

Some more text for those who might be able to utilize it. Everything seems fine, but I might be blind.

sudo dmesg | grep -i sas

[ 0.000000] Command line: BOOT_IMAGE=/ROOT/24.04.1.1@/boot/vmlinuz-6.6.29-production+truenas root=ZFS=boot-pool/ROOT/24.04.1.1 ro libata.allow_tpm=1 amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 intel_iommu=on zfsforce=1 nvme_core.multipath=N mpt3sas.max_queue_depth=10000
[ 0.007979] Kernel command line: BOOT_IMAGE=/ROOT/24.04.1.1@/boot/vmlinuz-6.6.29-production+truenas root=ZFS=boot-pool/ROOT/24.04.1.1 ro libata.allow_tpm=1 amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 intel_iommu=on zfsforce=1 nvme_core.multipath=N mpt3sas.max_queue_depth=10000
[ 0.980144] mpt3sas version 43.100.00.00 loaded
[ 0.981035] mpt3sas 0000:01:00.0: enabling device (0000 → 0002)
[ 0.982260] mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (32054632 kB)
[ 1.009425] mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
[ 1.012739] mpt2sas_cm0: MSI-X vectors supported: 1
[ 1.014240] mpt2sas_cm0: 0 1 1
[ 1.019667] mpt2sas_cm0: High IOPs queues : disabled
[ 1.020543] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 49
[ 1.021189] mpt2sas_cm0: iomem(0x0000000082580000), mapped(0x0000000053b000be), size(16384)
[ 1.021860] mpt2sas_cm0: ioport(0x000000000000f000), size(256)
[ 1.070441] mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
[ 1.094383] mpt2sas_cm0: scatter gather: sge_in_main_msg(1), sge_per_chain(9), sge_per_io(128), chains_per_io(15)
[ 1.095546] mpt2sas_cm0: request pool(0x00000000552c9ece) - dma(0x100800000): depth(16991), frame_size(128), pool_size(2123 kB)
[ 1.102444] mpt2sas_cm0: sense pool(0x000000009ff74015) - dma(0x100b00000): depth(10000), element_size(96), pool_size (937 kB)
[ 1.104057] mpt2sas_cm0: reply pool(0x00000000b0cc0a10) - dma(0x100c00000): depth(17055), frame_size(128), pool_size(2131 kB)
[ 1.104905] mpt2sas_cm0: config page(0x00000000df647f55) - dma(0x12a71a000): size(512)
[ 1.105559] mpt2sas_cm0: Allocated physical memory: size(24276 kB)
[ 1.106214] mpt2sas_cm0: Current Controller Queue Depth(9997),Max Controller Queue Depth(29251)
[ 1.106877] mpt2sas_cm0: Scatter Gather Elements per IO(128)
[ 1.147658] mpt2sas_cm0: LSISAS2116: FWVersion(20.00.07.00), ChipRevision(0x02)
[ 1.149018] mpt2sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[ 1.151222] scsi host0: Fusion MPT SAS Host
[ 1.153385] mpt2sas_cm0: sending port enable !!
[ 1.822563] mpt2sas_cm0: hba_port entry: 00000000fee7c1e0, port: 255 is added to hba_port list
[ 1.826571] mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x5000d3100048771b), phys(16)
[ 1.956608] mpt2sas_cm0: port enable: SUCCESS

After forcing packages to install/run, here are the results of storcli show all

CLI Version = 007.2310.0000.0000 Nov 02, 2022
Operating system = Linux 6.6.29-production+truenas
Status Code = 0
Status = Success
Description = None

Number of Controllers = 0
Host Name = truenas
Operating System = Linux 6.6.29-production+truenas
StoreLib IT Version = 07.2400.0200.0100
StoreLib IR3 Version = 16.14-0

Here are also the results of sudo sas2ircu 0 display:

LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.

Read configuration has been initiated for controller 0

Controller information

Controller type : SAS2116_1
BIOS version : 7.39.02.00
Firmware version : 20.00.07.00
Channel description : 1 Serial Attached SCSI
Initiator ID : 0
Maximum physical devices : 839
Concurrent commands supported : 29251
Slot : Unknown
Segment : 0
Bus : 1
Device : 0
Function : 0
RAID Support : No

IR Volume information


Physical device information


Enclosure information

Enclosure# : 1
Logical ID : 5000d310:0048771b
Numslots : 16
StartSlot : 0

SAS2IRCU: Command DISPLAY Completed Successfully.
SAS2IRCU: Utility Completed Successfully.

The goat(?) chatgpt mentioned checking SAS addresses for a mismatch, and here is the result

sudo storcli /c0 show all

CLI Version = 007.1504.0000.0000 June 22, 2020
Operating system = Linux 6.6.29-production+truenas
Controller = 0
Status = Failure
Description = Controller 0 not found

I then followed it up with sudo lspci -nn | grep -i sas

01:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] [1000:0064] (rev 02)

okay, chatgpt is cooked, they are out of ideas, and are suggesting for me to rebuild the driver and the kernel. If you boys can’t help, I’ll be consulting the greybeards on gentoo or LFS at this rate. lmfao.

Installed the HBA into a 1151 machine, same issue. After a more detailed analysis, stickering is slightly different on the interposers. Just incase they’re counterfeit, I went about ordering a used caddy, as opposed to just the interposers. :confused: