Fusion-IO Firmware Update

Discussion in 'Hard Drives and Solid State Drives' started by abq, Oct 22, 2016.

  1. nerdalertdk

    nerdalertdk Fleet Admiral

    Joined:
    Mar 9, 2017
    Messages:
    134
    Likes Received:
    53
    I have tried that firmware, but i may need to add the cards name in the firmware INFO file.

    "The ioMemory is currently running in a minimal state" <-- is this minimal mode?
     
    #81
  2. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    464
    Likes Received:
    216
    That's the physical hardware running in minimal mode (no block access, only access to the control (fctX) devices for firmware updates/etc.

    There's a lower level that you can load the driver that won't even try to load support for the cards. This can be used for problematic firmware reflashes/etc.

    I've used it a few times in the past, but I'm not sure where it's documented.
     
    #82
  3. nerdalertdk

    nerdalertdk Fleet Admiral

    Joined:
    Mar 9, 2017
    Messages:
    134
    Likes Received:
    53
    Newst update,

    Code:
    root@debian:/home//4.3.5/Firmware# fio-firmware /dev/fct0
    PCI Address, FW Version, FW Revision
    fio-firmware: Failed to get device info for /dev/fct0!
    fio-firmware: Failed to find device /dev/fct0
    
    Code:
    root@debian:/home//4.3.5/Firmware# fio-status -a
    
    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: 50.20 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.
    
    Code:
    root@debian:/home//4.3.5/Firmware# fio-update-iodrive -f -d /dev/fct0 fusion_4.3.5-20190313.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: Invalid firmware file fusion_4.3.5-20190313.fff for '/dev/fct0'.
    
    Thinking i might have an bad device so trying to figure that out so I can get it exchanged
     
    #83
    Last edited: Apr 30, 2019
  4. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    464
    Likes Received:
    216
    The invalid firmware file is a different error... something is wrong with that .fff file and how it was zipped up, or the format of the INFO file inside is incorrect.
     
    #84
  5. nerdalertdk

    nerdalertdk Fleet Admiral

    Joined:
    Mar 9, 2017
    Messages:
    134
    Likes Received:
    53
    I'm so ready to sent this card back

    Code:
    root@debian:/usr/share/fio/firmware/FW# ls -l
    total 77804
    -rw-r--r-- 1 root root    71292 Mar 13 17:55 avogadro_0.0.15.pdi
    -rw-r--r-- 1 root root    79260 Mar 13 17:55 cantor_0.0.10.pdi
    -rw-r--r-- 1 root root    79188 Mar 13 17:55 descartes_0.0.30.pdi
    -rw-r--r-- 1 root root     1286 Mar 13 17:55 errfw_0.0.3.bin
    -rw-r--r-- 1 root root    77352 Mar 13 17:55 feshbach_0.0.6.pdi
    -rw-r--r-- 1 root root    70372 Mar 13 17:55 fontanaiii_0.0.12.pdi
    -rw-r--r-- 1 root root 24315858 May  1 13:50 fw.fff
    -rw-r--r-- 1 root root 17241820 Mar 13 17:55 gen3_orange_fusion_8.9.9.118194.bin
    -rw-r--r-- 1 root root 17241820 Mar 13 17:55 gen3_plum_fusion_8.9.9.118194.bin
    -rw-r--r-- 1 root root 17241820 Mar 13 17:55 gen3_tangerine_fusion_8.9.9.118194.bin
    -rw-r--r-- 1 root root    71424 Mar 13 17:55 glycerin_0.0.11.pdi
    -rw-r--r-- 1 root root    79996 Mar 13 17:55 halphen_0.0.14.pdi
    -rw-r--r-- 1 root root   209284 May  1 13:49 INFO
    -rw-r--r-- 1 root root   220308 Mar 13 17:55 nce_1.0.9.100764.bin
    -rw-r--r-- 1 root root    70436 Mar 13 17:55 planck_0.0.14.pdi
    -rw-r--r-- 1 root root   400384 Mar 13 17:55 uefi-3001_4.3.5.1121.rom
    -rw-r--r-- 1 root root   400384 Mar 13 17:55 uefi-3002_4.3.5.1121.rom
    -rw-r--r-- 1 root root   400384 Mar 13 17:55 uefi-3003_4.3.5.1121.rom
    -rw-r--r-- 1 root root   400384 Mar 13 17:55 uefi-noboot-3001_4.3.5.1121.rom
    -rw-r--r-- 1 root root   400384 Mar 13 17:55 uefi-noboot-3002_4.3.5.1121.rom
    -rw-r--r-- 1 root root   400384 Mar 13 17:55 uefi-noboot-3003_4.3.5.1121.rom
    -rw-r--r-- 1 root root    79504 Mar 13 17:55 venturi_0.0.44.pdi
    -rw-r--r-- 1 root root    70436 Mar 13 17:55 whiteboard_0.0.11.pdi
    root@debian:/usr/share/fio/firmware/FW# fio-status -F adapter.oem_part_number_replacement /dev/fct0
    PFIO1000MP
    root@debian:/usr/share/fio/firmware/FW# fio-status -F adapter.part_number_pa /dev/fct0
    PA006041-115_3
    root@debian:/usr/share/fio/firmware/FW# vim INFO
    
    Code:
    [PA006086115]
    version = 8.9.9.118194
    file = gen3_tangerine_fusion_8.9.9.118194.bin
    format = bin
    ecc = 11b
    cntrpdiversion = 0.0.44
    cntrpdifile = venturi_0.0.44.pdi
    cntrpdiformat = pdi
    nce = 1f80000
    nceversion = 1.0.9.100764
    ncefile = nce_1.0.9.100764.bin
    errfw = 1f80000
    errfwversion = 0.0.3
    errfwfile = errfw_0.0.3.bin
    optrom = 3c00000
    optromversion = 4.3.5.1121
    optromfile = uefi-noboot-3002_4.3.5.1121.rom
    
    Code:
    
    root@debian:/usr/share/fio/firmware/FW# zip -r fw.fff .
      adding: uefi-noboot-3003_4.3.5.1121.rom (deflated 0%)
      adding: errfw_0.0.3.bin (deflated 2%)
      adding: halphen_0.0.14.pdi (deflated 47%)
      adding: venturi_0.0.44.pdi (deflated 47%)
      adding: uefi-3002_4.3.5.1121.rom (deflated 0%)
      adding: descartes_0.0.30.pdi (deflated 47%)
      adding: planck_0.0.14.pdi (deflated 42%)
      adding: uefi-3003_4.3.5.1121.rom (deflated 0%)
      adding: INFO (deflated 98%)
      adding: nce_1.0.9.100764.bin (deflated 34%)
      adding: cantor_0.0.10.pdi (deflated 47%)
      adding: uefi-noboot-3002_4.3.5.1121.rom (deflated 0%)
      adding: gen3_orange_fusion_8.9.9.118194.bin (deflated 59%)
      adding: gen3_plum_fusion_8.9.9.118194.bin (deflated 59%)
      adding: gen3_tangerine_fusion_8.9.9.118194.bin (deflated 59%)
      adding: uefi-noboot-3001_4.3.5.1121.rom (deflated 0%)
      adding: uefi-3001_4.3.5.1121.rom (deflated 0%)
      adding: avogadro_0.0.15.pdi (deflated 42%)
      adding: feshbach_0.0.6.pdi (deflated 47%)
      adding: whiteboard_0.0.11.pdi (deflated 42%)
      adding: glycerin_0.0.11.pdi (deflated 46%)
      adding: fontanaiii_0.0.12.pdi (deflated 42%)
    root@debian:/usr/share/fio/firmware/FW# fio-update-iodrive -d /dev/fct0 fw.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 '/dev/fct0' had an error while updating. Internal failure.
    
     
    #85
  6. nerdalertdk

    nerdalertdk Fleet Admiral

    Joined:
    Mar 9, 2017
    Messages:
    134
    Likes Received:
    53
    Right now i'm stuck with 4.3.5 since older don't compile on newest debian 4.9.0-9-amd64
     
    #86
  7. tjk

    tjk Active Member

    Joined:
    Mar 3, 2013
    Messages:
    236
    Likes Received:
    32
    4.3.5 package is the latest firmware, which contains the following:

    Code:
    Found 1 VSL driver package:
       4.3.5 build 1121 Storport Driver: loaded
    
    Found 2 ioMemory devices in this system
    
    Adapter: ioMono  (driver 4.3.5)
            Cisco UCS 1000GB MLC Fusion ioMemory PX, Product Number:PFIO1000MP, SN:FIO2046901E
            PCIe Power limit threshold: 24.75W
            Connected ioMemory modules:
              fct0: 04:00.0,        Product Number:PFIO1000MP, SN:FIO2046901E
    
    fct0    Attached
            ioMemory Adapter Controller, Product Number:PFIO1000MP, SN:1611G0487
            PCI:04:00.0, Slot Number:5
            Firmware v8.9.9, rev 20190313 Public
            1000.00 GBytes device size
            Internal temperature: 43.80 degC, max 46.76 degC
            Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00%
            Contained Virtual Partitions:
              fct0: ID:0, UUID:a92de60b-ecf6-fe49-afcf-bea5d399d64c
     
    #87
  8. tjk

    tjk Active Member

    Joined:
    Mar 3, 2013
    Messages:
    236
    Likes Received:
    32
    Hey @acquacow QQ for you...if I don't install any of the FIO drivers, windows 2019 installs 4.3.3.957 and the OS can see the card, format it, etc, however there are no fio* tools installed obviously for fw updates and such.

    I assume this is fine, since the 4.3.3 driver is supplied by SanDisk, or will I see better memory management by install the entire VSL package, which is 4.3.5 but not for Windows 2019 (although it runs).

    Thanks!
     
    #88
  9. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    464
    Likes Received:
    216
    Memory consumption is 100% driven by the size of the writes you make to the card.

    I'd install all the fio-utils and probably update to the latest driver/firmware.
     
    #89
  10. nerdalertdk

    nerdalertdk Fleet Admiral

    Joined:
    Mar 9, 2017
    Messages:
    134
    Likes Received:
    53
  11. tx12

    tx12 New Member

    Joined:
    May 17, 2019
    Messages:
    9
    Likes Received:
    0
    BTW, every time you experience troubles with iodrive on Linux, and looking for help, please post result of
    dmesg | grep fio
    because all the real information is printed by iomemory-vsl driver to your syslog.
     
    #91
  12. gtech1

    gtech1 New Member

    Joined:
    May 27, 2019
    Messages:
    5
    Likes Received:
    0
    acquacow: could really use your help. I bought a Cisco UCS 2600GB MLC Fusion ioMemory PX off eBay and none of the info so far has helped.

    The PA is:

    fio-status -F adapter.part_number_pa /dev/fct0
    PA006187-107_5

    And I don't find anything like that in the firmware/INFO file.

    Here are the full details of the card as fio-status -a reports

    fio-status -a

    Found 1 VSL driver package:
    4.3.0 build 769 Driver: loaded

    Found 1 ioMemory device in this system

    Adapter: ioMono (driver 4.3.0)
    Cisco UCS 2600GB MLC Fusion ioMemory PX, Product Number:pFIO2600MPS, SN:FIO2046F01E
    ioMemory Adapter Controller, PN:pFIO2600MPS
    Product UUID:1dde1cc0-2ab4-565a-af7e-e63d007c2194
    PCIe Power limit threshold: 74.75W
    PCIe slot available power: unavailable
    Connected ioMemory modules:
    fct0: 04:00.0, Product Number:pFIO2600MPS, SN:FIO2046F01E

    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:pFIO2600MPS, SN:1624D0011
    !! ---> There are active errors or warnings on this device! Read below for details.
    ioMemory Adapter Controller, PN:pFIO2600MPS
    Microcode Versions: App:0.0.13.0
    Powerloss protection: not available
    PCI:04:00.0, Slot Number:4
    Vendor:1aed, Device:3002, Sub vendor:1137, Sub device:150
    Firmware v8.7.6, rev 20140819 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: 47.74 degC, max 49.71 degC
    Internal voltage: avg 1.01V, max 1.01V
    Aux voltage: avg 1.80V, max 1.81V
    Rated PBW: 32.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.
     
    #92
  13. Marsh

    Marsh Moderator

    Joined:
    May 12, 2013
    Messages:
    2,109
    Likes Received:
    960
    #93
  14. gtech1

    gtech1 New Member

    Joined:
    May 27, 2019
    Messages:
    5
    Likes Received:
    0
    The problem was figuring out which part number to replace... I figured it out by downloading the Cisco UCS bin file and browsing through it. I ended up adding this in INFO file


    [PA006187107]
    version = 8.9.9.118194
    file = gen3_tangerine_fusion_8.9.9.118194.bin
    format = bin
    ecc = 11b
    cntrpdiversion = 0.0.15
    cntrpdifile = avogadro_0.0.15.pdi
    cntrpdiformat = pdi
    nce = 1f80000
    nceversion = 1.0.9.100764
    ncefile = nce_1.0.9.100764.bin
    errfw = 1f80000
    errfwversion = 0.0.3
    errfwfile = errfw_0.0.3.bin
    optrom = 3c00000
    optromversion = 4.3.4.977
    optromfile = uefi-noboot-3002_4.3.4.977.rom

    I updated the firmware successfully and now it reads:


    ~ # fio-status -a

    Found 1 VSL driver package:
    4.3.4 build 977 Driver: loaded

    Found 1 ioMemory device in this system

    Adapter: ioMono (driver 4.3.4)
    Cisco UCS 2600GB MLC Fusion ioMemory PX, Product Number:pFIO2600MPS, SN:FIO2046F01E
    ioMemory Adapter Controller, PN:pFIO2600MPS
    Product UUID:1dde1cc0-2ab4-565a-af7e-e63d007c2194
    PCIe Bus voltage: avg 12.10V
    PCIe Bus current: avg 0.70A
    PCIe Bus power: avg 8.53W
    PCIe Power limit threshold: 74.75W
    PCIe slot available power: unavailable
    Connected ioMemory modules:
    fct0: 04:00.0, Product Number:pFIO2600MPS, SN:FIO2046F01E

    fct0 Detached
    ioMemory Adapter Controller, Product Number:pFIO2600MPS, SN:1624D0011
    ioMemory Adapter Controller, PN:pFIO2600MPS
    Microcode Versions: App:0.0.15.0
    Powerloss protection: protected
    PCI:04:00.0, Slot Number:4
    Vendor:1aed, Device:3002, Sub vendor:1137, Sub device:150
    Firmware v8.9.9, rev 20180621 Public
    2600.00 GBytes device size
    Format: v500, 634765625 sectors of 4096 bytes
    PCIe slot available power: 75.00W
    PCIe negotiated link: 8 lanes at 5.0 Gt/sec each, 4000.00 MBytes/sec total
    Internal temperature: 45.77 degC, max 50.20 degC
    Internal voltage: avg 1.01V, max 1.01V
    Aux voltage: avg 1.80V, max 1.81V
    Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00%
    Active media: 100.00%
    Rated PBW: 32.00 PB, 100.00% remaining
    Lifetime data volumes:
    Physical bytes written: 7,483,392
    Physical bytes read : 80,537,184
    RAM usage:
    Current: 85,640,000 bytes
    Peak : 85,640,000 bytes
     
    #94
  15. F1ydave

    F1ydave Member

    Joined:
    Mar 9, 2014
    Messages:
    118
    Likes Received:
    21
    Thanks for this guys, got my firmware updated, just started with HP's oldest packages and worked my way up till it was recognized (I think i installed 3 or 4 packages)....couldn't get exsi to do anything. Maybe the esxi6.x vib file will install now with the latest firmware matching.

    Fingers crossed


    Does anyone know what the tiny external power connector cable is called?
     
    #95
    Last edited: Jun 27, 2019
  16. nerdalertdk

    nerdalertdk Fleet Admiral

    Joined:
    Mar 9, 2017
    Messages:
    134
    Likes Received:
    53
    If you can provide 75w over pcie you don’t need it as far as I know of


    Btw. Did anyone manage to convert on to an HP/HPE branded one ?
     
    #96
  17. F1ydave

    F1ydave Member

    Joined:
    Mar 9, 2014
    Messages:
    118
    Likes Received:
    21
    I can't tell if that is happening since ESXi still wont let me see the device even though it has accepted the VIB's. Windows 7 matched drivers and firmware...esxi is not matching I guess...this is ridiculous.

    Not sure why it wont attach...
    Capture.PNG

    I am about to try to convert this HP branded...
     
    #97
    Last edited: Jun 27, 2019
  18. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    464
    Likes Received:
    216
    The connector is a hirose plug. I posted the pinouts/etc either in this thread or the other main Fusion-io thread.

    We used to have PC Connection make a lot of custom versions of them for us in the early days...
     
    #98
  19. F1ydave

    F1ydave Member

    Joined:
    Mar 9, 2014
    Messages:
    118
    Likes Received:
    21
    I found your previous post, thank you. Ill link it for anyone who stumbles upon this thread. HERE


    Now to try to get this HP IODRIVE 2, to work in ESXi 6.7... day 3...:(
     
    #99
  20. F1ydave

    F1ydave Member

    Joined:
    Mar 9, 2014
    Messages:
    118
    Likes Received:
    21
    I was able to update my ESXi 6.7u2 drivers for my HP IODRIVE2 1205GB MLC (for Proliant Servers) using the Sandisks drivers 3.2.16 without any problems. Firmware matches...but I had previously updated that to 7.1.17 in windows using driver 3.2.8 or 3.2.11 in windows 7. I don't recall which exactly.

    IOdrive now shows up in storage adapters list and the overprovisioned 900 GB partition @ 512 bytes!

    The trick was signing up on link.westerndigital.com to get the newest fusion drivers.


    Just for fun, I tried the PA004154011 and PA004154-011 edit in the INFO file, but it threw me a CSR unavailable and I didn't want to force the install.
     
    #100
    Last edited: Jun 28, 2019
Similar Threads: Fusion-IO Firmware
Forum Title Date
Hard Drives and Solid State Drives Fusion-io ioFX drivers and firmware issues Nov 2, 2019
Hard Drives and Solid State Drives Fusion-io / Sandisk SX300 1.6TB Firmware Update Sep 15, 2016
Hard Drives and Solid State Drives Fusion-IO HP IO Accelerator Firmware Question Jan 4, 2016
Hard Drives and Solid State Drives Fusion-IO firmware revisions Apr 28, 2015
Hard Drives and Solid State Drives fusion-io error(-22) Dec 12, 2018

Share This Page