Seems like common sense but after hours of frustration with a 9361-8i card (legitimate card, I got it from eBay but it came with a proper retail box), I got it to work with two of my SAS SSDs for Cache Cade.
The card has a 8GB CV module, and Cache Cade key. Following Murphy's Law, I decided to check for updates to the firmware and installed storlci and co. After that, I grabbed the latest ZIP archive and began flashing. I came across a file "70-26832-00_Ptolemy4GB_GG_VPD.rom". I decided to go ahead and flash it after checking the CV module had a less recent number, and per the title, a nasty mess ensued. The two SAS SSDs that were working before, now exhibit this behavior:
---------------------------------------------------------------------------------
EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp Type
---------------------------------------------------------------------------------
252:0 9 UGood - 5.457 TB SATA HDD N N 512B HGST HDN726060ALE614 U -
252:1 10 UGood - 5.457 TB SATA HDD N N 512B HGST HDN726060ALE614 D -
252:2 11 UGood - 5.457 TB SATA HDD N N 512B HGST HDN726060ALE614 D -
252:3 8 UGood - 5.457 TB SATA HDD N N 512B HGST HDN726060ALE614 D -
252:4 12 UBad - 0 KB SAS HDD Y N 512B HUSMR1625ASS201 U -
252:5 16 UBad - 0 KB SAS HDD Y N 512B HUSMR1625ASS201 U -
252:6 14 UGUnsp - 0 KB SAS HDD N N 0 KB HSSC0480S5xnNMRI U -
252:7 15 UGUnsp - 0 KB SAS HDD N N 0 KB HUSMR1640ASS204 U -
I have tried everything from cold starts, to clearing all configuration settings, to switching to JBOD mode and back, and nothing brings back the 1625 HGST SAS SSDs. They remain UBad, and whenever I try anything they just forbid any chances to the state of the drives.
The worst thing is that they are reported as 0 size, but their sector information reports that properly (512, 520 for the 1640 and 0480S drives, they need reformatting).
I'm at a loss here, so I would appreciate any help. I already filed a ticket with LSI too.
For now the take away lesson is "don't mess with firmware while sleep deprived". But every now and then we screw up with things we usually never bother ourselves with.
The card has a 8GB CV module, and Cache Cade key. Following Murphy's Law, I decided to check for updates to the firmware and installed storlci and co. After that, I grabbed the latest ZIP archive and began flashing. I came across a file "70-26832-00_Ptolemy4GB_GG_VPD.rom". I decided to go ahead and flash it after checking the CV module had a less recent number, and per the title, a nasty mess ensued. The two SAS SSDs that were working before, now exhibit this behavior:
---------------------------------------------------------------------------------
EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp Type
---------------------------------------------------------------------------------
252:0 9 UGood - 5.457 TB SATA HDD N N 512B HGST HDN726060ALE614 U -
252:1 10 UGood - 5.457 TB SATA HDD N N 512B HGST HDN726060ALE614 D -
252:2 11 UGood - 5.457 TB SATA HDD N N 512B HGST HDN726060ALE614 D -
252:3 8 UGood - 5.457 TB SATA HDD N N 512B HGST HDN726060ALE614 D -
252:4 12 UBad - 0 KB SAS HDD Y N 512B HUSMR1625ASS201 U -
252:5 16 UBad - 0 KB SAS HDD Y N 512B HUSMR1625ASS201 U -
252:6 14 UGUnsp - 0 KB SAS HDD N N 0 KB HSSC0480S5xnNMRI U -
252:7 15 UGUnsp - 0 KB SAS HDD N N 0 KB HUSMR1640ASS204 U -
I have tried everything from cold starts, to clearing all configuration settings, to switching to JBOD mode and back, and nothing brings back the 1625 HGST SAS SSDs. They remain UBad, and whenever I try anything they just forbid any chances to the state of the drives.
The worst thing is that they are reported as 0 size, but their sector information reports that properly (512, 520 for the 1640 and 0480S drives, they need reformatting).
I'm at a loss here, so I would appreciate any help. I already filed a ticket with LSI too.
For now the take away lesson is "don't mess with firmware while sleep deprived". But every now and then we screw up with things we usually never bother ourselves with.