Fusion-io ioDrive 2 1.2TB Reference Page

DetroitJD

New Member
Jan 9, 2019
6
0
1
Detroit, Mi
Well, got it all done, installed, and firmware is incompatible. Tried to flash to 4.3.4 and it's unfortunately a Cisco card that can't be flashed with anything other than the Cisco firmware. Vendor-locked cards are a plague.

Going to edit the firmware mainfest, add this part number, and try to flash it with the stock SanDisk firmware.

...If he bricks it, he bricks it.
 

acquacow

Well-Known Member
Feb 15, 2017
680
362
63
40
Yeah. drop me the firmware files for each somewhere and I can probably merge them if you can't.

I haven't opened the VSL 4 firmware yet, but I didn't hear of them changing any of that format with the new version.
 

DetroitJD

New Member
Jan 9, 2019
6
0
1
Detroit, Mi
I threw 3.2.16 up on my google drive. Not sure how to get the proper version into the manifest on this firmware.

It's a Cisco ioDrive, so flashing it with a non-Cisco firmware may brick it, from what I understand. Any thoughts?

Latest:
[ 14.528204] fioerr ioDrive 0000:06:00.0: 12293 Minimum firmware version supported is 8.9.4. Current firmware version is 8.7.6.
[ 14.528241] fioerr ioDrive 0000:06:00.0: 12313 MINIMAL MODE DRIVER: Firmware is incompatible.
[ 14.699266] fioerr Cisco UCS 1300GB MLC Fusion ioMemory PX 0000:06:00.0: 18456 Unable to attach - explicitly disabled.
[ 14.699337] fioerr Cisco UCS 1300GB MLC Fusion ioMemory PX 0000:06:00.0: 18461 Auto attach failed with error EINVAL: Invalid argument


fusion_3.2.16-20180821.fff
 
Last edited:

acquacow

Well-Known Member
Feb 15, 2017
680
362
63
40
I threw 3.2.16 up on my google drive. Not sure how to get the proper version into the manifest on this firmware.

It's a Cisco ioDrive, so flashing it with a non-Cisco firmware may brick it, from what I understand. Any thoughts?

Latest:
[ 14.528204] fioerr ioDrive 0000:06:00.0: 12293 Minimum firmware version supported is 8.9.4. Current firmware version is 8.7.6.
[ 14.528241] fioerr ioDrive 0000:06:00.0: 12313 MINIMAL MODE DRIVER: Firmware is incompatible.
[ 14.699266] fioerr Cisco UCS 1300GB MLC Fusion ioMemory PX 0000:06:00.0: 18456 Unable to attach - explicitly disabled.
[ 14.699337] fioerr Cisco UCS 1300GB MLC Fusion ioMemory PX 0000:06:00.0: 18461 Auto attach failed with error EINVAL: Invalid argument


fusion_3.2.16-20180821.fff
It won't brick it, it just won't work.

The firmware file is a zipfile and inside it is a manifest that matches drive part #s to specific firmware files.
The trick is to match your part # with the fusion-io part# and see which firmware file it uses, then add that entry to the latest sandisk firmware.

You just need to lookup your part # in the cisco-branded firmware file.

-- Dave
 

acquacow

Well-Known Member
Feb 15, 2017
680
362
63
40
Alright, people keep asking me, so...example time.

I have two bundles and two cards, getting them to 3.2.11 was easy, as both Fusion-io and Dell supported up to that version.
- Fusion-io: fusion_3.2.11-20150618
- Dell: dell_iodrive_3.2.11-20150618

Now, Sandisk has a newer 3.2.16 with a 3.2.16 firmware I'd like to use. This is nice and easy for the Fusion-io-branded card, but won't go so well for Dell or IBM branded cards.

What you need to do is unzip the .fff firmware file included in your packages and look at the INFO file contained inside.

If you load up the drivers for your device, you have access to some extended information via specifying fields for the fio-status command.
From here we can extract the actual fusion-io part # for the cards.

Example from one of my Dell cards:
# fio-status -F adapter.oem_part_number_replacement /dev/fct0
1XF66
# fio-status -F adapter.part_number_pa /dev/fct0
PA004151-017_5


Now if I take that and search my dell firmware info file, I find:

[PA004151017]
version = 7.1.17.116786
file = gen2_49_salmon_dell_mono_3fp_7.1.17.116786.bin
format = bin
ecc = 49b
dpfile = gen2_49_salmon_dual_dell_mono_3fp_7.1.17.116786.bin
dpformat = bin
dpecc = 49b
cntrpdiversion = 1.0.35
cntrpdifile = carre_1.0.35.pdi
cntrpdiformat = pdi
optrom = 1e00000
optromversion = 3.2.11.1581
optromfile = uefi-3.2.11.1581.rom

[PA004151-017]
version = 7.1.17.116786
file = gen2_49_salmon_dell_mono_3fp_7.1.17.116786.bin
format = bin
ecc = 49b
dpfile = gen2_49_salmon_dual_dell_mono_3fp_7.1.17.116786.bin
dpformat = bin
dpecc = 49b
cntrpdiversion = 1.0.35
cntrpdifile = carre_1.0.35.pdi
cntrpdiformat = pdi
optrom = 1e00000
optromversion = 3.2.11.1581
optromfile = uefi-3.2.11.1581.rom


So this card gets the gen2_49_salmon firmware images.

Now, if you search your latest SanDisk firmware, it won't have any PA004151 entries in it, but will have plenty of gen2_49_salmon entries in it.

Here's an example from the SanDisk firmware file that has all the same line options as our Dell card in the Dell firmware:
[PA005067002]
version = 7.1.17.116786
file = gen2_49_salmon_fusion_7.1.17.116786.bin
format = bin
ecc = 49b
dpfile = gen2_49_salmon_dual_fusion_7.1.17.116786.bin
dpformat = bin
dpecc = 49b
cntrpdiversion = 1.0.35
cntrpdifile = carre_1.0.35.pdi
cntrpdiformat = pdi
optrom = 1e00000
optromversion = 3.2.16.1731
optromfile = uefi-3.2.16.1731.rom


You can see that the bin file versions haven't changed, but the optrom has.

Double check that the entry you are using matches yours line-for-line and simply copy and paste one of those updated SanDisk entries twice, creating two new entries, and put your Dell PA#s at the top. Make sure you are creating one for the non-hyphenated and the hyphenated version (you may not need both, but I haven't tested what happens if you don't have both).

eg:
[PA004151017]
version = 7.1.17.116786
file = gen2_49_salmon_fusion_7.1.17.116786.bin
format = bin
ecc = 49b
dpfile = gen2_49_salmon_dual_fusion_7.1.17.116786.bin
dpformat = bin
dpecc = 49b
cntrpdiversion = 1.0.35
cntrpdifile = carre_1.0.35.pdi
cntrpdiformat = pdi
optrom = 1e00000
optromversion = 3.2.16.1731
optromfile = uefi-3.2.16.1731.rom

[PA004151-017]
version = 7.1.17.116786
file = gen2_49_salmon_fusion_7.1.17.116786.bin
format = bin
ecc = 49b
dpfile = gen2_49_salmon_dual_fusion_7.1.17.116786.bin
dpformat = bin
dpecc = 49b
cntrpdiversion = 1.0.35
cntrpdifile = carre_1.0.35.pdi
cntrpdiformat = pdi
optrom = 1e00000
optromversion = 3.2.16.1731
optromfile = uefi-3.2.16.1731.rom


Then just save that INFO text file, re-zip the firmware folder, rename it back to .fff and update your ioDrive normally.

Hopefully this helps,

-- Dave
 

miniserver32

New Member
Jan 21, 2019
2
0
1
Hello, i need your help :)
I bought "Fusion iODrive II MLC PCIe IBM 1.2TB High IOPS MLC SSD IBM 90Y4378", but need using with HP Proliant DL360p Gen8 server.
What i need to do for it ?
As far as I know this iODrive working only with IBM servers?
 

acquacow

Well-Known Member
Feb 15, 2017
680
362
63
40
That ioDrive will work in any server/desktop, but as stated in my prior post, you are locked to the IBM firmware file.

Follow my above post and add your card's definitions to the latest WD/sandisk firmware (and all future firmwares you download) and you'll be fine.

The PA# may even be physically printed somewhere on the PCB of the card, so you might not even need to load the IBM driver to find it.

-- Dave
 
  • Like
Reactions: miniserver32

thalooka

New Member
Oct 20, 2018
10
0
1
@acquacow you know how to fix

Error: Unable to read midprom from device '/dev/fct0'.
Error: Unable to read midprom from device '/dev/fct1'.

i already trie'd format or sure erase but both say "Error: Device '/dev/fct1' had an error while formatting: Device is not in a valid state to handle request."

would be glad about your helping flashpro hand^^
 

acquacow

Well-Known Member
Feb 15, 2017
680
362
63
40
There's an --update-mid flag for fio-update-iodrive somewhere. That may fix it.

Did you follow the recommended update path in the docs? What was your firmware at before the flash, and what are you trying to flash to?

Also, when all else fails, fio-sure-erase will re-low-level the card and clean most things up.
 

thalooka

New Member
Oct 20, 2018
10
0
1
@acquacow was on 3.2.15 n gone to 3.2.16 its an duo and all went fine until the reboot to activate new firmware.
Fio sure erase fails aswell I hope to be able to rescue it with the mid update u mentioned since force didn't have a effect aswell
 

thalooka

New Member
Oct 20, 2018
10
0
1
@acquacow so just arrived home, the fio sure erase fails with "Device is not in an valid state"
the --update-mid isnt recognized from fio-update-iodrive, maybe its another flag?
 

acquacow

Well-Known Member
Feb 15, 2017
680
362
63
40
I forget the exact syntax for updating the midprom, I usually have to run strings against the command and pull the flags out. The one I gave you is probably incorrect.
 

acquacow

Well-Known Member
Feb 15, 2017
680
362
63
40
Try and reflash the old firmware to it with the OEM drivers.

You may need a -f to force the downgrade.

Follow that with a fio-sure-erase on the drive to re-low-level format it.