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)
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.
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
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
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.
