Sandisk PX600 Cisco PCIE SSD

nerdalertdk

Fleet Admiral
Mar 9, 2017
151
63
28
::1
Just got mine, but It dont look good

Fusion-IO Firmware Update


[UPDATE 6/5/2019]

Got it working with newst firmwere.
To anyone trying to update it here is what i did

  1. Install Windows 2016 server
  2. Download newst drivers from SanDisk site and install them
  3. Install fio Util
  4. Run fio-status -a
  5. Install winzip (the real one)
  6. Open the firmware file with winzip (not unzip, but open)
  7. Install Notepad++
  8. Edit the INFO file inside the zip file (you can right click and select open) Fusion-io ioDrive 2 1.2TB Reference Page
    1. My PN was PA006041115
  9. Save it in Notepad++
  10. Say yes to update the firmware Zip file
  11. now you can update the firmware
  12. fio-update-iodrive.exe -f -d/dev/fct0 fusion_4.3.5-20190313.fff
  13. Uninstall Windows
  14. Install Debian :D
My patch firmware fil use it at own risk

fusion_4.3.5-20190313-unpack.zip

Code:
C:\Utilities>fio-status.exe -a

Found 1 VSL driver package:
   4.3.5 build 1121 Storport 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 Bus voltage: avg 12.04V
        PCIe Bus current: avg 0.72A
        PCIe Bus power: avg 8.64W
        PCIe Power limit threshold: 74.75W
        PCIe slot available power: unavailable
        Connected ioMemory modules:
          fct0: 06:00.0,        Product Number:PFIO1000MP, SN:FIO20469027

fct0    Attached
        ioMemory Adapter Controller, Product Number:PFIO1000MP, SN:1611G0488
        ioMemory Adapter Controller, PN:PFIO1000MP
        Microcode Versions: App:0.0.44.0
        Powerloss protection: protected
        PCI:06:00.0, Slot Number:2
        Vendor:1aed, Device:3002, Sub vendor:1137, Sub device:13d
        Firmware v8.9.9, rev 20190313 Public
        1000.00 GBytes device size
        Format: v501, 1953125000 sectors of 512 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: 43.80 degC, max 58.57 degC
        Internal voltage: avg 1.01V, max 1.01V
        Aux voltage: avg 1.79V, max 1.81V
        Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00%
        Active media: 100.00%
        Rated PBW: 12.00 PB, 100.00% remaining
        Lifetime data volumes:
           Physical bytes written: 136,549,954,784
           Physical bytes read   : 668,072,315,232
        RAM usage:
           Current: 442,533,184 bytes
           Peak   : 442,533,184 bytes
        Contained Virtual Partitions:
          fct0: ID:0, UUID:3d7f6348-4b45-426a-8d89-a09eda7ad302

fct0    State: Online, Type: block device, Device: \\?\PhysicalDrive2
        ID:0, UUID:3d7f6348-4b45-426a-8d89-a09eda7ad302
        1000.00 GBytes device size
        Format: 1953125000 sectors of 512 bytes
        Sectors In Use: 67
        Max Physical Sectors Allowed: 1953125000
        Min Physical Sectors Reserved: 1953125000
 
Last edited:

tomaash

Member
Oct 11, 2016
98
39
18
Europe, Slovakia
I just updated mine to 4.3.4 with firmware package downloaded from HPE - was hoping my old DL360p Gen8 would pick it up better, but I guess there's more that needs flashing.

Code:
D:\data>fio-update-iodrive.exe -f -d/dev/fct0 ioaccelerator_4.3.4-20180621.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: [====================] (100%) \
 /dev/fct0 - successfully updated the following:
 Updated the firmware from 8.5.28 rev 20140617 to 8.9.9 rev 20180621
  Updated CONTROLLER from 8.5.28.116474 to 8.9.9.118194
  Updated SMPCTRL from 0.0.36 to 0.0.44
  Updated NCE from 0.1.2.630 to 1.0.9.100764
  Updated ECC1 from 0.0.3 to 0.0.3

Reboot this machine to activate new firmware.
 

tomaash

Member
Oct 11, 2016
98
39
18
Europe, Slovakia
It's still Cisco branded. Also iLO is not picking up temp readings so fans go crazy.

Code:
D:\data>fio-status -a

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

Found 1 ioMemory device in this system

Adapter: ioMono  (driver 4.3.4)
        Cisco UCS 1000GB MLC Fusion ioMemory PX, Product Number:PFIO1000MP, SN:FIO20469021
        ioMemory Adapter Controller, PN:PFIO1000MP
        Product UUID:aca49bd5-25e0-54a6-8527-85ae741dd832
        PCIe Bus voltage: avg 12.24V
        PCIe Bus current: avg 0.71A
        PCIe Bus power: avg 8.75W
        PCIe Power limit threshold: 24.75W
        PCIe slot available power: unavailable
        Connected ioMemory modules:
          fct0: 07:00.0,        Product Number:PFIO1000MP, SN:FIO20469021

fct0    Attached
        ioMemory Adapter Controller, Product Number:PFIO1000MP, SN:1611G0495
        ioMemory Adapter Controller, PN:PFIO1000MP
        Microcode Versions: App:0.0.44.0
        Powerloss protection: protected
        PCI:07:00.0, Slot Number:2
        Vendor:1aed, Device:3002, Sub vendor:1137, Sub device:13d
        Firmware v8.9.9, rev 20180621 Public
        1000.00 GBytes device size
        Format: v500, 244140625 sectors of 4096 bytes
        PCIe slot available power: unavailable
        PCIe negotiated link: 8 lanes at 5.0 Gt/sec each, 4000.00 MBytes/sec total
        Internal temperature: 45.77 degC, max 61.03 degC
        Internal voltage: avg 1.01V, max 1.02V
        Aux voltage: avg 1.79V, max 1.81V
        Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00%
        Active media: 100.00%
        Rated PBW: 12.00 PB, 99.99% remaining
        Lifetime data volumes:
           Physical bytes written: 655,829,165,944
           Physical bytes read   : 129,237,468,192
        RAM usage:
           Current: 109,730,688 bytes
           Peak   : 112,293,248 bytes
        Contained Virtual Partitions:
          fct0: ID:0, UUID:3d44914d-b2af-b443-bef5-6643c6fb831d

fct0    State: Online, Type: block device, Device: \\?\PhysicalDrive1
        ID:0, UUID:3d44914d-b2af-b443-bef5-6643c6fb831d
        1000.00 GBytes device size
        Format: 244140625 sectors of 4096 bytes
        Sectors In Use: 32377
        Max Physical Sectors Allowed: 244140625
        Min Physical Sectors Reserved: 244140625
I used your approach, except I used 7zip and standard Notepad.
 
  • Like
Reactions: T_Minus

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,009
1,569
113
CA
Mine was detected in Windows 7 but couldn't use it, haven't had time to try anything else, was hoping I could boot to linux and update firmware and use it that way, are you guys saying you can ONLY get it updated via Windows or why are you using windows instead of Linux ?
 

tomaash

Member
Oct 11, 2016
98
39
18
Europe, Slovakia
Driver & firmware versions must match in order to use it. You can update firmware with newer driver version loaded though.
I don't see why update wouldn't work in Linux, for me Windows is just easier clicky clack :)
 

nerdalertdk

Fleet Admiral
Mar 9, 2017
151
63
28
::1
My problem on Linux was the zip format I think, could only get it working by open the zip and update the file and not unzip and zip it
 

nerdalertdk

Fleet Admiral
Mar 9, 2017
151
63
28
::1
Hi all

So they just released a new driver 4.3.6 and i'm trying to upgrade to it, sadly i will not upgrade the firmware :(

I can upgrade the driver to 4.3.6 but that will not see the card

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 Bus voltage: avg 12.03V
    PCIe Bus current: avg 0.72A
    PCIe Bus power: avg 8.68W
    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    Detached
    ioMemory Adapter Controller, Product Number:PFIO1000MP, SN:1611G0488
    ioMemory Adapter Controller, PN:PFIO1000MP
    Microcode Versions: App:0.0.44.0
    Powerloss protection: protected
    PCI:06:00.0
    Vendor:1aed, Device:3002, Sub vendor:1137, Sub device:13d
    Firmware v8.9.9, rev 20190313 Public
    900.00 GBytes device size
    Format: v501, 219726562 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.28 degC, max 50.69 degC
    Internal voltage: avg 1.01V, max 1.01V
    Aux voltage: avg 1.79V, max 1.81V
    Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00%
    Active media: 100.00%
    Rated PBW: 12.00 PB, 100.00% remaining
    Lifetime data volumes:
       Physical bytes written: 217,746,137,784
       Physical bytes read   : 785,688,982,848
    RAM usage:
       Current: 75,440,000 bytes
       Peak   : 197,675,968 bytes
Code:
root@san1:/tmp/Drivers# fio-update-iodrive Firmware/fusion_4.3.6-20191010.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.
Even update with the PCI address fails

Code:
root@san1:~# fio-firmware
PCI Address, FW Version, FW Revision
06:00.0, 8.9.9, 20190313
root@san1:~# cd /tmp/Drivers/Firmware/
root@san1:/tmp/Drivers/Firmware# fio-update-iodrive -s 06:00.0 fusion_4.3.6-20191010.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 PCI address '06:00.0'.
 
Last edited:

nerdalertdk

Fleet Admiral
Mar 9, 2017
151
63
28
::1
Well got it working :S

had to unload the kernel module modprobe -r iomemory-vsl4

then i could upgrade with pci slot


Code:
root@san1:/tmp/Drivers/Firmware# fio-update-iodrive -f -s 06:00.0 fusion_4.3.6-20191010.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

WARNING: '06:00.0': YOU ARE ATTEMPTING TO FORCE A FIRMWARE VERSION DOWNGRADE - THIS MAY RESULT IN DATA LOSS
Do you wish to continue updating '06:00.0' [y/n]? y
Updating: [====================] (100%) |
 06:00.0 - successfully updated the following:
 Updated the firmware from 8.9.9 rev 20190313 to 8.9.9 rev 20191010
  Updated CONTROLLER from 8.9.9.118194 to 8.9.9.118194
  Updated SMPCTRL from 0.0.44 to 0.0.44
  Updated NCE from 1.0.9.100764 to 1.0.9.100764
  Updated ECC1 from 0.0.3 to 0.0.3

Reboot this machine to activate new firmware.
root@san1:/tmp/Drivers/Firmware#
 

acquacow

Well-Known Member
Feb 15, 2017
567
294
63
38
For all of you dealing with reflashing these, we have a Fusion-io master thread on this board that I've put reflash instructions into a year or so back.

No need to change vendor IDs/etc. just need to unzip the firmware.fff file, edit the info file and swap your board ID into the standard downloaded firmware from sandisk/WD.

https://forums.servethehome.com/index.php?threads/fusion-io-iodrive-2-1-2tb-reference-page.11287/

As for the HP fan speed issues, there was an updated HP bios that took care of that, the card won't ever talk to iLO, so don't worry about that.

-- Dave
 

nerdalertdk

Fleet Admiral
Mar 9, 2017
151
63
28
::1
Hi

My problem was not the firmware INFO trick. Its was more it would not load the 4.3.6 vsl driver and its said the firmware was older then the 4.3.5, also found out you need to hard reboot the system when you change firmware, reboot in the terminal was not enough

Also ILO do talk to the card
upload_2019-10-30_13-54-43.png
But have since found out, HPE did not use the Gen3 cards (ioMemory HHHL)

They only have the Gen2 (Vendor & Device ID 1AED:2001) the Cisco I have is "gen3" 1aed:3002.
Or at least I could not find a HPE card with the pci vender tag 1aed:300X

My "PCI fan" is only at 40% so I'm not complaining
 

acquacow

Well-Known Member
Feb 15, 2017
567
294
63
38
Yeah, you need to hard cycle the card to get the FPGA to load the new firmware, it doesn't do it live, it needs a power cycle.

If you have a gen3 card, just get the latest gen3 drivers from sandisk/wd and edit the INFO file to add the definition from the cisco card to it. You'll probably want to download and open a cisco firmware file to extract all the info for your card vs guessing at which entry to copy/paste and put your card ID on.
 

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,009
1,569
113
CA
@acquacow to rescue :D
I still have one of these 1TB cards sitting here I need to get playing around with :D

Anyone end up with a handful of the Px600? How are you using them?
 

nerdalertdk

Fleet Admiral
Mar 9, 2017
151
63
28
::1
The px600 is easy enough when you figure them out and discover dkms compiling

I can share my steps, figure out how to easy edit the info fil and not corrupt the zip file

again it’s not the firmware identifying that’s the problems it’s was the idea to “rebrand” it HPE so hp would love it move
 

acquacow

Well-Known Member
Feb 15, 2017
567
294
63
38
The firmware was setup this way to keep HP customers on HP tested/supported firmware so that they wouldn't just jump to something newer that HP didn't "support"

Same thing goes for Dell/IBM/Cisco...
 
  • Like
Reactions: nerdalertdk

nerdalertdk

Fleet Admiral
Mar 9, 2017
151
63
28
::1
You can find the driver for Debian 10, Kernel 4.19 here


Debian 10 change to GCC 8 which made the official one unable to compile
 
  • Like
Reactions: lowfat