Fusion-io ioDrive 2 1.2TB Reference Page

Indecided

Active Member
Sep 5, 2015
142
61
28
Thanks @acquacow for taking a look. Here's the fio-status -a output

Code:
Found 1 VSL driver package:
   4.3.7 build 1205 Storport Driver: loaded

Found 2 ioMemory devices in this system

Adapter: ioMono  (driver 4.3.7)
        Cisco UCS 1000GB MLC Fusion ioMemory PX, Product Number:PFIO1000MP, SN:aaabbbccc
        ioMemory Adapter Controller, PN:PFIO1000MP
        Product UUID:366c7cac-0c6a-5fc4-a688-65d66ccc683a
        PCIe Bus voltage: avg 11.98V
        PCIe Bus current: avg 0.71A
        PCIe Bus power: avg 8.48W
        PCIe Power limit threshold: 24.75W
        PCIe slot available power: unavailable
        Connected ioMemory modules:
          fct0: 05:00.0,        Product Number:PFIO1000MP, SN:aaabbbccc

fct0    Attached
        ioMemory Adapter Controller, Product Number:PFIO1000MP, SN:aaabbbccc
        ioMemory Adapter Controller, PN:PFIO1000MP
        Microcode Versions: App:0.0.44.0
        Powerloss protection: protected
        PCI:05:00.0
        Vendor:1aed, Device:3002, Sub vendor:1137, Sub device:13d
        Firmware v8.9.9, rev 20200113 Public
        1000.00 GBytes device size
        Format: v501, 1953125000 sectors of 512 bytes
        PCIe slot available power: 25.00W
        PCIe negotiated link: 8 lanes at 5.0 Gt/sec each, 4000.00 MBytes/sec total
        Internal temperature: 41.34 degC, max 53.15 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: 1,169,261,160,616
           Physical bytes read   : 974,149,019,424
        RAM usage:
           Current: 397,517,184 bytes
           Peak   : 444,698,944 bytes
        Contained Virtual Partitions:
          fct0: ID:0, UUID:629a7c7f-26e9-4fd1-af21-b8d69c4129a5

fct0    State: Online, Type: block device, Device: \\?\PhysicalDrive4
        ID:0, UUID:629a7c7f-26e9-4fd1-af21-b8d69c4129a5
        1000.00 GBytes device size
        Format: 1953125000 sectors of 512 bytes
        Sectors In Use: 234801
        Max Physical Sectors Allowed: 1953125000
        Min Physical Sectors Reserved: 1953125000

Adapter: ioMono  (driver 4.3.7)
        Cisco UCS 1000GB MLC Fusion ioMemory PX, Product Number:PFIO1000MP, SN:dddeeefff
        ioMemory Adapter Controller, PN:PFIO1000MP
        Product UUID:5e11d310-2e58-5671-891a-3a10d19a2c52
        PCIe Bus voltage: avg 11.94V
        PCIe Bus current: avg 0.68A
        PCIe Bus power: avg 8.16W
        PCIe Power limit threshold: 24.75W
        PCIe slot available power: unavailable
        Connected ioMemory modules:
          fct1: 04:00.0,        Product Number:PFIO1000MP, SN:dddeeefff

fct1    Attached
        ioMemory Adapter Controller, Product Number:PFIO1000MP, SN:dddeeefff
        ioMemory Adapter Controller, PN:PFIO1000MP
        Microcode Versions: App:0.0.44.0
        Powerloss protection: protected
        PCI:04:00.0
        Vendor:1aed, Device:3002, Sub vendor:1137, Sub device:13d
        Firmware v8.9.9, rev 20200113 Public
        1000.00 GBytes device size
        Format: v501, 1953125000 sectors of 512 bytes
        PCIe slot available power: 25.00W
        PCIe negotiated link: 8 lanes at 5.0 Gt/sec each, 4000.00 MBytes/sec total
        Internal temperature: 39.37 degC, max 49.71 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: 867,755,546,376
           Physical bytes read   : 767,244,060,576
        RAM usage:
           Current: 448,399,104 bytes
           Peak   : 449,288,704 bytes
        Contained Virtual Partitions:
          fct1: ID:0, UUID:e62248ab-d9e7-4fa2-a03f-b3f4d667b6bd

fct1    State: Online, Type: block device, Device: \\?\PhysicalDrive3
        ID:0, UUID:e62248ab-d9e7-4fa2-a03f-b3f4d667b6bd
        1000.00 GBytes device size
        Format: 1953125000 sectors of 512 bytes
        Sectors In Use: 234801
        Max Physical Sectors Allowed: 1953125000
        Min Physical Sectors Reserved: 1953125000
Here's the output of fio-pci-check, it looks like it's a direct root port connection, no switching/bifurcation.

Code:
Root Bridge PCIe 26250 MB/sec needed max
DMI Device

      Bridge 0000:00:02.00 (04-04) (8086:3c04)
      PCI Express Root Port
          Needed 4000 MB/sec Avail 4000 MB/sec

            ioDrive3 0000:04:00.0 (3002) Firmware 20200113
            Fusion ioMemory VSL4 Device
                Slot Power limit: 25.0W (25000mw)

      Bridge 0000:00:02.02 (05-05) (8086:3c06)
      PCI Express Root Port
          Needed 4000 MB/sec Avail 4000 MB/sec

            ioDrive3 0000:05:00.0 (3002) Firmware 20200113
            Fusion ioMemory VSL4 Device
                Slot Power limit: 25.0W (25000mw)
 

acquacow

Well-Known Member
Feb 15, 2017
616
326
63
39
Hmm, all of that looks fine...

How are you testing read speeds? Do you have any output from a fio benchmark on each device you can share?

Thanks,

-- Dave
 

drizzler

New Member
Aug 20, 2021
1
0
1
Hello, is there any chance to rescue a duo drive section after a crashing flash process? the flashing process crashed at 15 % (computer freeze) and now 1 of 2 the two controlles/drivers is not recognized anymore.

I have a CH31 programmer to work with.

Any advices?

Thank you very much
 

acquacow

Well-Known Member
Feb 15, 2017
616
326
63
39
I don't have time to pull all the docs, but you might be able to load the VSL driver in minimal mode and re-flash it that way.
 

tx12

Member
May 17, 2019
27
29
13
Hello, is there any chance to rescue a duo drive section after a crashing flash process? the flashing process crashed at 15 % (computer freeze) and now 1 of 2 the two controlles/drivers is not recognized anymore.
Gen2 FIO cards feature a fallback firmware - in case of programming failure, default firmware with a very early revision date must be loaded enabling you to re-start the flash process. It's possible to disrupt a programming process in a way what would hang chip on a faulty firmware, but it's not too easy to achieve.

If one chip (or both) is not present on PCIe bus anymore (eg, not listed in lspci on Linux), your only option is to reflash it via Xilinx JTAG using programming tool called iMPACT and a compatible USB-JTAG adapter (like DLC9G or DLC10, or Digilent).
 

tx12

Member
May 17, 2019
27
29
13
BTW, are schematics and/or board files available for Gen2 / Gen3 cards? Would be so nice to have ;)
 

tx12

Member
May 17, 2019
27
29
13
You'd have to do some digging, but we open sourced the design of one of our cards as part of the opencompute project... so something is out there... I think it was for a gen2 ioscale card.
Yep, indeed, it can be spotted in some news from 2013 what ioscale card was "open sourced" to OCP. All I was able to find so far is that hardware description pdf and a STEP-file with 3D model for mechanics. All that is very far from being really open source.
I think Fusion-IO was trying hard to get into Facebook so they claimed that ioscale would be open sourced to OCP. But fact, nothing but a hardware description and a step-file were contributed. That's not anywhere close to real open source hardware, to say the least.

Anyway, this hardware description is much more detailed than any usual user manual.
 

acquacow

Well-Known Member
Feb 15, 2017
616
326
63
39
Well, they were open-sourcing the hardware, there was never any plan to open source the driver/firmware.
 

tx12

Member
May 17, 2019
27
29
13
Well, they were open-sourcing the hardware, there was never any plan to open source the driver/firmware.
Yes, but just a hardware description pdf is nowhere close to real hardware open sourcing. Open source materials for hardware are expected to include (at least) CAD source files for schematics and PCB layouts. Real OCP submissions usually include all of these.

Pretending to go open source without really open sourcing something is well expected from a company with closed source and obfuscated driver, anyway :)