Fusion-IO Firmware Update

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,625
2,043
113
Thanks @i386 i recall that thread/post too I just wasn't sure if we needed the file system to match the low level format and/or how they affect each other when they're different and the same. I'd be interested in learning more about the differences and affects of these too if anyone has a resource to share.
 

acquacow

Well-Known Member
Feb 15, 2017
784
439
63
42
Fio-format can format the drive 512, 1024, 2048 and 4096 byte block sizes.
I think @acquacow said in another thread that with smaller block sizes the drive performs better but can use more ram.
Smaller low level formatting will deliver more IOPS at smaller bock sizes, but overall performance won't really change no matter what you format it to.

If you format it to 4K and are writing blocks smaller than 4k, then performance will suffer.
 

Rocxxr

New Member
Mar 31, 2018
10
0
1
34
I have IBM IoDrive2 drives but are the below type of files from sandisk interchangeable with the different branded IoDrive2 for a esxi deployment?
libvsl-600-1.0.0-3.2.15.1699.zip
scsi-iomemory-vsl-60L-3.2.15.1699-offline_bundle-5351806.zip


Or are the dell/ibm/hp files required as is the case when upgrading firmware.
 
Last edited:

acquacow

Well-Known Member
Feb 15, 2017
784
439
63
42
You need the IBM firmware file for the IBM drives, else you have to unzip the sandisk firmware file and add in the IBM cards info (correctly).

I have all the IBM firmware files if you can't find them online...
 

Rocxxr

New Member
Mar 31, 2018
10
0
1
34
You need the IBM firmware file for the IBM drives, else you have to unzip the sandisk firmware file and add in the IBM cards info (correctly).

I have all the IBM firmware files if you can't find them online...
I thought the files I listed are not firmware files though, I thought those were drivers required for esxi?
All of the drivers are compatible, it's the OEM-specific firmware you have to use, unless you unzip the firmware and put your card into the manifest, but that is a pita...

ESX 5.5 ships with fusion-io drivers already installed, though I forget which version. You'll want to do an esx software vib list, find it, then remove the built-in driver.

I'd get the latest drivers from sandisk's site that match the latest firmware you can get from IBM.

If you want to put a current firmware on, I can work on setting that up for you mid next week when I'm back home.
 
Last edited:

acquacow

Well-Known Member
Feb 15, 2017
784
439
63
42
You listed the 3.2.15 driver, so you'll need a 3.2.15 firmware on the card from the OEM vendor. I don't know at which version IBM stopped at, but the last version I have from them is 3.2.8

Your best bet is to use the ESX driver for 3.2.8, or unzip the latest firmware file from sandisk and add your cards info to the manifest and re-zip it up.

Then you can use 3.2.15.
 

Morteza Soltani

New Member
Feb 9, 2019
3
0
1
Hello,

I bought 2*640GB MLC ioDrive (AP1-004-640-CS-0001) and I want to setup them into DL360P G8 server. I download a firmware from HP website (below URL) but I received the following error:

Error: Firmware file does not contain firmware for device 'fct0', part '00377700201'

command : fio-status -a

result:

Adapter: Single Adapter

APPLE-MOBILEME IODRIVE 640GB MLC, Product Number:AP1-004-640-CS, SN:482109

Pseudo Low-Profile ioDIMM Adapter, PN:00119200000

External Power: NOT connected

PCIe Bus voltage: min 11.96V max 12.17V

PCIe Bus current: max 0.46A

PCIe Bus power: max 5.59W

PCIe Power limit threshold: 24.75W

PCIe slot available power: unavailable

Connected ioMemory modules:

fct0: Product Number:AP1-004-640-CS, SN:482109


fct0 Status unknown: Driver is in MINIMAL MODE:

The firmware on this device is not compatible with the currently installed version of the driver

ioDrive 640GB, Product Number:AP1-004-640-CS, SN:482109

!! ---> There are active errors or warnings on this device! Read below for details.

ioDrive 640GB, PN:00377700201

Powerloss protection: not available

PCI:04:00.0

Vendor:1aed, Device:1005, Sub vendor:1aed, Sub device:1010

Firmware v5.0.6, rev 101583 Public

Geometry and capacity information not available.

Format: not low-level formatted

PCIe slot available power: unavailable

PCIe negotiated link: 4 lanes at 2.5 Gt/sec each, 1000.00 MBytes/sec total

Internal temperature: 45.77 degC, max 46.26 degC

Internal voltage: avg 1.01V, max 2.38V

Aux voltage: avg 2.47V, max 2.38V

Rated PBW: 10.00 PB

Lifetime data volumes:

Physical bytes written: 0

Physical bytes read : 0

RAM usage:

Current: 0 bytes

Peak : 0 bytes


ACTIVE WARNINGS:

The ioMemory is currently running in a minimal state.


Thanks
 

acquacow

Well-Known Member
Feb 15, 2017
784
439
63
42
Neat, you got one of the elusive Apple ioDrive that we made.

That's not going to work with HP firmware.

You're going to need to use the latest firmware from sandisk/wd and first attempt that.

If that doesn't work, you need to unzip the firmware file and make an entry for your device, but that'll take some work and you'll have to come back to me and the other ioDrive thread for assistance with that.

Based on the part-number, you're going to want to copy/paste this entry:
[003777002]
version = 7.1.17.116786
file = gen1_39_green_mono_fusion_7.1.17.116786.bin
format = bin
ecc = 39b
avrversion = 65793
avrfile = iomono_avr_65793.bin
avrformat = bin

And then change the header to be:
[00377700201]

The previously existing [003777002] should work for you though, so just try the sandisk firmware first.

-- Dave
 

acquacow

Well-Known Member
Feb 15, 2017
784
439
63
42
Oh, and thing to note about the apple drives, I don't think they default to 640GB formatting by default. I think they are ~720GB with no overprovisioning, so you'll want to use fio-format and manually set them to 640GB once operational.
 
  • Like
Reactions: Morteza Soltani

acquacow

Well-Known Member
Feb 15, 2017
784
439
63
42
Sorry. I am newbie in this.
How can I copy and paste entry? Where should I do?
I don't think you'll have to, but if you do, refer to the other thread I linked you.

Honestly, if you just purchased that drive, I'd return it and get one of the 1.2TB ioDrive IIs that are selling for $145ea right now.
 
  • Like
Reactions: Morteza Soltani

Emil Vals

New Member
Dec 26, 2017
3
0
1
48
I just bought onr of those 1.2TB drive on Ebay. I have it installed in Windows 10 without issues but what tool can I use to see stats about the drive (fw version, usage etc...)?
 

jfeldt

Member
Jul 19, 2015
48
9
8
54
I just bought onr of those 1.2TB drive on Ebay. I have it installed in Windows 10 without issues but what tool can I use to see stats about the drive (fw version, usage etc...)?
If you have it installed without issues, then "fio-status -a" from a command prompt.
 
  • Like
Reactions: Emil Vals

Emil Vals

New Member
Dec 26, 2017
3
0
1
48
If you have it installed without issues, then "fio-status -a" from a command prompt.
Thank you. :)

Rated PBW: 17.00 PB, 100.00% remaining
Lifetime data volumes:
Physical bytes written: 519,793,616,528
Physical bytes read : 332,472,535,856
 

nerdalertdk

Fleet Admiral
Mar 9, 2017
228
118
43
::1
Hi @acquacow

could you may be help me, just got an Cisco version

Code:
Found 1 VSL driver package:
   4.3.5 build 1121 Driver: loaded

Found 1 ioMemory device in this system

Adapter: ioMono  (driver 4.3.5)
        Cisco UCS 1000GB MLC Fusion ioMemory PX, Product Number:pFIO1000MP, SN:FIO20469027
        ioMemory Adapter Controller, PN:pFIO1000MP
        Product UUID:eee62379-1c6e-573f-ba81-031687f927f2
        PCIe Power limit threshold: 74.75W
        PCIe slot available power: 75.00W
        PCIe negotiated link: 8 lanes at 5.0 Gt/sec each, 4000.00 MBytes/sec total
        Connected ioMemory modules:
          fct0: 06:00.0,        Product Number:pFIO1000MP, SN:FIO20469027

fct0    Status unknown: Driver is in MINIMAL MODE:
                The firmware on this device is not compatible with the currently installed version of the driver
        ioMemory Adapter Controller, Product Number:pFIO1000MP, SN:1611G0488
!! ---> There are active errors or warnings on this device!  Read below for details.
        ioMemory Adapter Controller, PN:pFIO1000MP
        Microcode Versions: App:0.0.36.0
        Powerloss protection: not available
        PCI:06:00.0
        Vendor:1aed, Device:3002, Sub vendor:1137, Sub device:13d
        Firmware v8.5.28, rev 20140617 Public
        Geometry and capacity information not available.
        Format: not low-level formatted
        PCIe slot available power: 75.00W
        PCIe negotiated link: 8 lanes at 5.0 Gt/sec each, 4000.00 MBytes/sec total
        Internal temperature: 49.71 degC, max 51.19 degC
        Internal voltage: avg 1.00V, max 1.01V
        Aux voltage: avg 1.79V, max 1.79V
        Rated PBW: 12.00 PB
        Lifetime data volumes:
           Physical bytes written: 0
           Physical bytes read   : 0
        RAM usage:
           Current: 0 bytes
           Peak   : 0 bytes

        ACTIVE WARNINGS:
            The ioMemory is currently running in a minimal state.
But i just get an internal error on all commands

Code:
 fio-update-iodrive cisco_iodrive_4.2.5-20160412.fff
WARNING: DO NOT TURN OFF POWER OR RUN ANY IODRIVE UTILITIES WHILE THE FIRMWARE UPDATE IS IN PROGRESS
  Please wait...this could take a while

Updating: [                    ] (  0%) /
Error: Device 'fct0' had an error while updating. Internal failure.
Code:
fio-attach /dev/fct0
Attaching: [====================] (100%)
Error: Device '/dev/fct0' had an error while attaching. Device is not in a valid state to handle request.
Additional details about the error may be found in system logs.
Code:
Apr 27 23:29:20 debian kernel: [ 1301.531925] fioinf Cisco UCS 1000GB MLC Fusion ioMemory PX 0000:06:00.0: IOCTL 0xc0196834 unsupported in minimal mode
 

acquacow

Well-Known Member
Feb 15, 2017
784
439
63
42
Adapter: ioMono (driver 4.3.5)
...
fio-update-iodrive cisco_iodrive_4.2.5-20160412.fff
Looks like you're trying to flash a 4.2 firmware with a 4.3 driver.

Driver and firmware versions must be matched with the VSL.

You need to flash with fusion_4.3.5-20190313.fff

Worst case, you may need to boot with the driver in minimal mode, and then try to reflash and fio-sure-erase it.