mtimk307

Thanks for the recommendation. I finally had a chance to update the HBA firmware. Unfortunately, this didn't fix the issue with the particular drive. I did test with another 2.5" drive (1TB Samsung) I had laying around and it initialized just fine so it must be some comparability issues with the particular drive (2TB Seagate Firecuda Compute - realizing now it's a hybrid drive. Wonder if that has anything to do with the compatibility issues....). For now, I've just swapped around some sata cables and have the troublesome drive directly connected to the motherboard. What's odd is that during the boot sequence the Avago/LSI boot utility initializes and has no trouble detecting all the drives. It's not until Unraid boots when the issues seem to arise.

I installed an LSI 9300-8i HBA as well as an Icy Dock 5.25 bay recently on my server and have had some issues with one of the four drives connected to the HBA on startup. I have three cache SSDs and one 2.5" HDD (array) installed in the dock which is connected to the HBA. For some reason, when I start up Unraid the one HDD is missing. All three cache SSDs are detected just fine. If I manually reseat the drive and refresh the GUI, the drive is then found. The drive is detected in the LSI BIOS. Also, it appears the card has been pre-flashed to IT mode. So, I don't think the issue is with the HBA. I have swapped bays in the dock and there is no change - the 2.5" HDD is still missing on startup and SDDs are detected - ruling out an issue with the SAS cable or the dock connections. Before I had the HBA installed, the HDD was connected to a SATA port directly on the motherboard. From a previous thread, I noticed someone (I think it was Squid, actually) mention that by moving a drive from a mobo SATA port to an HBA, Unraid may have issues locating it. I went ahead and rebuilt the array without the 2.5" HDD, then precleared and added the drive back in (connected to the HBA) and the issue still persists. If I swap the 2.5" HDD with one of the 3.5" HDDs connected to a mobo SATA port, all drives are detected on startup. This may have to be my fix but it's not ideal. I would like to be able to get another four bay Icy Dock to expand my array, utilizing the four unused SATA-to-SAS cables, and not have to worry about manually reseating the drives on startup and be able to auto start the array on startup. Alternatively, I could put all my array drives on the HBA (the ones that evidently don't have any issue being connected to the HBA, that is) and directly connect these future 2.5" drives to the mobo but my instinct is to prioritize array and parity drives on the mobo SATA ports, as possible, assuming that should be more stable (though, I may be overthinking that). The one thing I have not ruled out is issues with the specific 2.5" drive. I don't know for sure that others will have a similar issue. Any thoughts? Diagnostics are attached - the drive I'm having issues with is ST2000LX001-1RG174_WDZCD6W4 (sdd) Peeking at the diagnostics, I'm seeing "device /dev/sdd problem getting id". Not sure what is the issue here. After reseating, Unraid gets the ID just fine. Any help is appreciated. Icy Dock https://www.newegg.com/icy-dock-mb994sp-4sb-1/p/N82E16817994142?Item=N82E16817994142 LSI 9300-8i https://www.newegg.com/lsi-9300-8i-sata-sas/p/N82E16816118217?Item=9SIAKN7JK63639 homeone-diagnostics-20230522-1450.zip