Fusion-io ioDrive 2 1.2TB Reference Page

Discussion in 'Hard Drives and Solid State Drives' started by Patrick, Sep 14, 2016.

  1. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    476
    Likes Received:
    234
    If you don't need the data, you can just format it and drop a blank lebmap on, then overwrite the card a few times and it'll build a new map of any bad cells (you'll see it in the syslog prefixed with fioinf and fioerr).

    You have to find a version of the driver that has fio-read-lebmap and fio-write-lebmap in them. I think they took them out at some point.
     
    #221
  2. tx12

    tx12 New Member

    Joined:
    May 17, 2019
    Messages:
    9
    Likes Received:
    0
    I've already tried that and (unlike on gen2), that doesn't work on gen3 for me. I'm getting format errors:

    After driver load with lebmap present, but empty:
    Code:
    Unable to recover management NV data (-2)
    Init NV data
    After format started:
    Code:
    ***************************************************
    ***            No media format found!           ***
    ***      Please contact Customer Support.       ***
    ***************************************************
    And either format or sure-erase fails to continue. Looks like something changed on gen3...
     
    #222
  3. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    476
    Likes Received:
    234
    Well, if you can't get sure-erase to complete, (it wipes the leb-map) there might be something else wrong.

    There might be some more hidden flags for sure-erase that might get it to complete. It doesn't sound like anyone used --purge, which would also wipe the FPGA and brick the card...

    In the past, I have had to load the drivers into minimal mode and alternate sure-erase and format until one eventually completed. I probably went back and forth ~50 times before I had success.
     
    #223
  4. cw823

    cw823 Active Member

    Joined:
    Jan 14, 2014
    Messages:
    220
    Likes Received:
    41
    Googlefu isn't working for me. Have an X9SRL with 5x of the 1.2TB drives in it, ESX 6.7. Latest driver for ESX and firmware for cards is installed. Says PCI slots are locked at 25W, would like to increase but cannot find instructions for doing so ON ESX. I have registered and have access to downloads, but I'm not sure what else I need to install; fio-config does not work.
     
    #224
  5. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    476
    Likes Received:
    234
    fio-config is for windows.

    You need to use esxcfg to set module parameters and this page from the Fusion-io ESXi user guide on SanDisk's website:

    upload_2019-5-27_20-7-6.png
     
    #225
  6. gtech1

    gtech1 New Member

    Joined:
    May 27, 2019
    Messages:
    5
    Likes Received:
    0
    Did anyone get the iomemory driver from Sandisk working properly with CentOS 7.6 ? It installs fine for me but fails to load.

    fio-status -a shows:

    Found 1 ioMemory device in this system
    Driver version: Driver not loaded

    This is what I installed:
    iomemory-vsl-3.10.0-862.el7.x86_64-3.2.16.1731-1.0.el7.centos.x86_64
     
    #226
  7. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    476
    Likes Received:
    234
    Yeah, I'm running it on 7.6 on a few machines.

    My guess is that you updated to the 3.10.0-957 kernel w/o rebuilding the VSL source against it.

    Go get the iomemory-vsl-3.2.16.1731-1.0.src.rpm from sandisk's site, then install gcc, make, rpm-build, kernel-headers, kernel-devel, and rsync

    Then rpmbuild --rebuild on the src rpm and it'll output a kernel module that works with your newer kernel.


    From my system:

    rpmbuild --rebuild iomemory-vsl-3.2.16.1731-1.0.src.rpm
    rpm -ivh /root/rpmbuild/RPMS/x86_64/iomemory-vsl-3.10.0-957.1.3.el7.x86_64-3.2.16.1731-1.0.el7.x86_64.rpm

    Uninstall the old version first, and once the new version is installed, run dracut -f to rebuild your init files so that the old version isn't in your boot image.

    Then go into your /etc/dracut.conf and add the following line to prevent the vsl from ending up in your boot image:
    omit_drivers+="iomemory-vsl"


    -- Dave
     
    #227
    Last edited: May 31, 2019
  8. naimc

    naimc New Member

    Joined:
    Jun 13, 2016
    Messages:
    4
    Likes Received:
    4
    Question for acquacow. We purchased a few SX350-6400 Cisco branded cards. 54-91-72338-6400G. This will be used on Windows servers.

    They are currently at firmware 8.9.1. to update them, based on your Post I have to find the Product ID , 54-91-72338-6400G in an original Cisco firmware file in .fff format. Based on my research the original file would be ucs-c-fusion-io-pfios64002.8.9.9.118194.bin reference here Release Bundle Contents for Cisco UCS Manager, Release 3.1

    In the Bin file I would find the section that defines [54-91-72338-6400G] which I could then past in a new generic sandisk update. still have not figured what latest version I would upgrade too.

    It seems impossible to get ucs-c-fusion-io-pfios64002.8.9.9.118194.bin, is there any other way to extrapolate that data that would be present in the firmware fill ?


    C:\Program Files\Common Files\VSL Utils>fio-status -a

    Found 1 VSL driver package:
    4.2.1 build 1138 Driver: loaded

    Found 1 ioMemory device in this system

    Adapter: ioMono (driver 4.2.1)
    Cisco UCS 6400GB SanDisk ioMemory SX350, Product Number:pFIOS64002, SN:
    ioMemory Adapter Controller, PN:5491-72338-6400G
    Product UUID:df1ca345-bed1-5c0f-b89f-e0a32a16d7ea
    PCIe Bus voltage: avg 12.25V
    PCIe Bus current: avg 0.66A
    PCIe Bus power: avg 8.03W
    PCIe Power limit threshold: 24.75W
    PCIe slot available power: unavailable
    Connected ioMemory modules:
    fct0: 07:00.0, Product Number:pFIOS64002, SN:

    fct0 Detached
    ioMemory Adapter Controller, Product Number:pFIOS64002, SN:
    ioMemory Adapter Controller, PN:5491-72338-6400G
    Microcode Versions: App:0.0.13.0
    Powerloss protection: protected
    PCI:07:00.0, Slot Number:2
    Vendor:1aed, Device:3001, Sub vendor:1137, Sub device:19d
    Firmware v8.9.1, rev 20150611 Public
    6400.00 GBytes device size
    Format: v501, 1562500000 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: 59.55 degC, max 70.87 degC
    Internal voltage: avg 1.02V, max 1.03V
    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: 22.00 PB, 100.00% remaining
    Lifetime data volumes:
    Physical bytes written: 4,879,602,384
    Physical bytes read : 5,848,772,608
    RAM usage:
    Current: 34,080,000 bytes
    Peak : 325,950,784 bytes

    fio-status -F adapter.part_number_pa /dev/fct0
    54-91-72338-6400G
     
    #228
  9. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    476
    Likes Received:
    234
    Check the output of
    fio-status /dev/fct0 -F adapter.part_number_legacy

    See if you can dig up the actual PA# for the card vs the adapter_part_number, which I think is a cisco ID.

    See if part_number_legacy and adapter_part_number are different.

    If so, look for the legacy # in the official sandisk firmware file that is closest to yours and add your cisco part number in a new section next to it with the same entries.

    -- Dave
     
    #229
  10. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    476
    Likes Received:
    234
    #230
    zxv likes this.
  11. naimc

    naimc New Member

    Joined:
    Jun 13, 2016
    Messages:
    4
    Likes Received:
    4
    thanks for the tips.

    C:\Windows\system32>fio-status /dev/fct0 -F adapter.part_number_legacy
    5491-72338-6400G

    Still was wondering about the what the original Cisco firmware would like so I found it !

    I downloaded ucs-k9-bundle-c-series.4.0.4b.C.bin from https://software.cisco.com/download/home/283612660/type/283655658/release/4.0(4b)

    Extracted .\ucs-k9-bundle-c-series.4.0.4b.C.bin\ucs-k9-bundle-c-series.4.0.4b.C\.\isan\plugin_img\ucs-c-fusion-io-pfios64002.8.9.9.118194.bin

    Extracted .\ucs-c-fusion-io-pfios64002.8.9.9.118194\.\blob\INFO

    [​IMG]
    found the two entried for my card:
    [5491-72338]
    version = 8.9.9.118194
    file = gen3_orange_fusion_8.9.9.118194.bin
    format = bin
    ecc = 11b
    cntrpdiversion = 0.0.14
    cntrpdifile = planck_0.0.14.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.0.769
    optromfile = uefi-3001_4.3.0.769.rom

    [549172338]
    version = 8.9.9.118194
    file = gen3_orange_fusion_8.9.9.118194.bin
    format = bin
    ecc = 11b
    cntrpdiversion = 0.0.14
    cntrpdifile = planck_0.0.14.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.0.769
    optromfile = uefi-3001_4.3.0.769.rom

    then noticed that the firmware version in blob where very recent. so I renamed blob to UCS_fusion_8.9.9.118194.fff.

    And with nothing to loose I flashed it !

    and it worked. after a reboot I was able to install the latest verison 4.3.5 Sandisk generic drivers

    [​IMG]

    C:\Windows\system32>fio-status

    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 6400GB SanDisk ioMemory SX350, Product Number:pFIOS64002, SN:FIO2112K020
    PCIe Power limit threshold: 24.75W
    Connected ioMemory modules:
    fct0: 07:00.0, Product Number:pFIOS64002, SN:FIO2112K020

    fct0 Attached
    ioMemory Adapter Controller, Product Number:pFIOS64002, SN:1710D0106
    PCI:07:00.0, Slot Number:2
    Firmware v8.9.9, rev 20170222 Public
    6400.00 GBytes device size
    Internal temperature: 58.57 degC, max 66.93 degC
    Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00%
    Contained Virtual Partitions:
    fct0: ID:0, UUID:8f56d942-5b22-414e-93b6-2d282f60aa2a

    fct0 State: Online, Type: block device, Device: \\?\PhysicalDrive1
    ID:0, UUID:8f56d942-5b22-414e-93b6-2d282f60aa2a
    6400.00 GBytes device size
     
    #231
    NobleX13 likes this.
  12. zxv

    zxv The more I C, the less I see.

    Joined:
    Sep 10, 2017
    Messages:
    152
    Likes Received:
    46
    #232
  13. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    476
    Likes Received:
    234
    Thanks!
     
    #233
    kalim116 likes this.
  14. kalim116

    kalim116 New Member

    Joined:
    Jun 20, 2019
    Messages:
    2
    Likes Received:
    0
    @acquacow can i use my Dell Fusion ioDrive2 3TB in my PC? I got it running as a Storage Device in my PC. My windows 7 was running on my 128GB SATA SSD. But it died today i dont know why. Now i wanted to ask you if i can install Windows 10 on the Dell Fusion ioDrive 2 and Boot my Windows from it? I got the Fusion drive hooked into my AS Rock 970M Pro3 PCIeX16 slot next to my Graphic card. The Fusion Drive has a PCIeX8 attachment.
    I would be very thankful if you could help me.
     
    #234
  15. acquacow

    acquacow Active Member

    Joined:
    Feb 15, 2017
    Messages:
    476
    Likes Received:
    234
    No, you can't boot from it w/o a TON of UEFI hackery that I haven't had time to look into.
     
    #235
    kalim116 likes this.
  16. kalim116

    kalim116 New Member

    Joined:
    Jun 20, 2019
    Messages:
    2
    Likes Received:
    0
    Okay thanks a lot. Me as an amateur have no Chance to get this running. I will have to buy a new SATA or M2 SSD
     
    #236
  17. NobleX13

    NobleX13 Member

    Joined:
    Oct 2, 2014
    Messages:
    46
    Likes Received:
    11
    Great work! I am going down this same road for the 1.3TB SX350 I just got from eBay. You are a lifesaver for posting this.
     
    #237
  18. lnxpro

    lnxpro New Member

    Joined:
    Mar 1, 2016
    Messages:
    4
    Likes Received:
    0
    #238
  19. nerdalertdk

    nerdalertdk Fleet Admiral

    Joined:
    Mar 9, 2017
    Messages:
    135
    Likes Received:
    53
  20. Louis

    Louis New Member

    Joined:
    Jul 7, 2019
    Messages:
    2
    Likes Received:
    0
    I would say hold on for a while, i got myself 2x iodrive2 1.3tb for 100$ Canadian each+ shipping on ebay. Both have more than 90% life remaining
     
    #240
Similar Threads: Fusion-io ioDrive
Forum Title Date
Hard Drives and Solid State Drives Fusion-IO ioDrive - General Channel Initiliaze Failure Apr 19, 2018
Hard Drives and Solid State Drives Fusion-io ioDrive Linux Drivers (HP branded / non-branded) discovery May 17, 2015
Hard Drives and Solid State Drives Fusion-io iodrive - This device cannot start. (Code 10) Apr 20, 2015
Hard Drives and Solid State Drives Fusion-io ioFX drivers and firmware issues Nov 2, 2019
Hard Drives and Solid State Drives fusion-io error(-22) Dec 12, 2018

Share This Page