Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Would have expected the card to go into read-only mode considering the error message of a pad being write-protected.
Perhaps it's still worth it to experiment a little with with different driver/os-version combos. Not exactly very optimistic at this point though. Kinda making me lose faith in using these
This was my 'spare card' that was covering for my 3.2T model until I got a new server to run that in.
Perhaps it's still worth it to experiment a little with with different driver/os-version combos. Not exactly very optimistic at this point though. Kinda making me lose faith in using these
This was my 'spare card' that was covering for my 3.2T model until I got a new server to run that in.Hello, I have ended up with an OLD iodrive2 that I am trying to get working in my win10 desktop for no other reason than I want it. in trying to get it going I have tried a few driver version off of the san disk site. I went through this in trying to identify which firmware to put on it but the PA number (PA003717-027_5) doesn't exist in the info files.
C:\WINDOWS\system32>fio-status -a
Found 1 ioMemory device in this system
Driver version: 3.2.15 build 1699
Adapter: Single Adapter
Fusion-io ioDrive2 Mono 1.300TB, Product Number:F00-001-1T30-CS-0001, SN:1152D1006, FIO SN:1205A05CD
ioDrive2 Mono Adapter, PNA003717027
SMP(AVR) Versions: App Version: 1.0.10.0, Boot Version: 1.0.3.1
External Power: NOT connected
PCIe Power limit threshold: Disabled
PCIe slot available power: unavailable
Connected ioMemory modules:
fct0: SN:1152D0315
fct0 Status unknown: Driver is in MINIMAL MODE:
The firmware on this device is not compatible with the currently installed version of the driver
ioDrive2 Controller, SN:1152D0315
!! ---> There are active errors or warnings on this device! Read below for details.
ioDrive2 Controller
SMP(AVR) Versions: App Version: 1.0.21.0, Boot Version: 1.0.2.1
Located in slot 0 Center of ioDrive2 Mono Adapter SN:1205A05CD
Powerloss protection: not available
PCI:05:00.0
Vendor:1aed, Device:2001, Sub vendor:1aed, Sub device:2001
Firmware v6.0.0, rev 105900 Public
Geometry and capacity information not available.
Format: not low-level formatted
PCIe slot available power: 25.00W
PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total
Internal temperature: 71.86 degC, max 71.86 degC
Internal voltage: avg 1.02V, max 1.02V
Aux voltage: avg 2.49V, max 2.49V
Rated PBW: 17.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.
C:\WINDOWS\system32>fio-status -a
Found 1 ioMemory device in this system
Driver version: 3.2.15 build 1699
Adapter: Single Adapter
Fusion-io ioDrive2 Mono 1.300TB, Product Number:F00-001-1T30-CS-0001, SN:1152D1006, FIO SN:1205A05CD
ioDrive2 Mono Adapter, PN
A003717027SMP(AVR) Versions: App Version: 1.0.10.0, Boot Version: 1.0.3.1
External Power: NOT connected
PCIe Power limit threshold: Disabled
PCIe slot available power: unavailable
Connected ioMemory modules:
fct0: SN:1152D0315
fct0 Status unknown: Driver is in MINIMAL MODE:
The firmware on this device is not compatible with the currently installed version of the driver
ioDrive2 Controller, SN:1152D0315
!! ---> There are active errors or warnings on this device! Read below for details.
ioDrive2 Controller
SMP(AVR) Versions: App Version: 1.0.21.0, Boot Version: 1.0.2.1
Located in slot 0 Center of ioDrive2 Mono Adapter SN:1205A05CD
Powerloss protection: not available
PCI:05:00.0
Vendor:1aed, Device:2001, Sub vendor:1aed, Sub device:2001
Firmware v6.0.0, rev 105900 Public
Geometry and capacity information not available.
Format: not low-level formatted
PCIe slot available power: 25.00W
PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total
Internal temperature: 71.86 degC, max 71.86 degC
Internal voltage: avg 1.02V, max 1.02V
Aux voltage: avg 2.49V, max 2.49V
Rated PBW: 17.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.
Add this to your INFO file in the firmware.fff and zip it back up.Hello, I have ended up with an OLD iodrive2 that I am trying to get working in my win10 desktop for no other reason than I want it. in trying to get it going I have tried a few driver version off of the san disk site. I went through this in trying to identify which firmware to put on it but the PA number (PA003717-027_5) doesn't exist in the info files.
C:\WINDOWS\system32>fio-status -a
Found 1 ioMemory device in this system
Driver version: 3.2.15 build 1699
Adapter: Single Adapter
Fusion-io ioDrive2 Mono 1.300TB, Product Number:F00-001-1T30-CS-0001, SN:1152D1006, FIO SN:1205A05CD
ioDrive2 Mono Adapter, PN
SMP(AVR) Versions: App Version: 1.0.10.0, Boot Version: 1.0.3.1
External Power: NOT connected
PCIe Power limit threshold: Disabled
PCIe slot available power: unavailable
Connected ioMemory modules:
fct0: SN:1152D0315
fct0 Status unknown: Driver is in MINIMAL MODE:
The firmware on this device is not compatible with the currently installed version of the driver
ioDrive2 Controller, SN:1152D0315
!! ---> There are active errors or warnings on this device! Read below for details.
ioDrive2 Controller
SMP(AVR) Versions: App Version: 1.0.21.0, Boot Version: 1.0.2.1
Located in slot 0 Center of ioDrive2 Mono Adapter SN:1205A05CD
Powerloss protection: not available
PCI:05:00.0
Vendor:1aed, Device:2001, Sub vendor:1aed, Sub device:2001
Firmware v6.0.0, rev 105900 Public
Geometry and capacity information not available.
Format: not low-level formatted
PCIe slot available power: 25.00W
PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total
Internal temperature: 71.86 degC, max 71.86 degC
Internal voltage: avg 1.02V, max 1.02V
Aux voltage: avg 2.49V, max 2.49V
Rated PBW: 17.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.
Use the 3.2.15 windows installer Fusion_ioMemory_VSL_3.2.15.1699_x64.exe
Code:
[PA003717-027]
version = 7.1.17.116786
file = gen2_49_crimson_fusion_7.1.17.116786.bin
format = bin
ecc = 49b
cntrpdiversion = 1.0.34
cntrpdifile = leibniz_1.0.34.pdi
cntrpdiformat = pdi
adaptpdiversion = 1.0.22
adaptpdifile = brahe_1.0.22.pdi
adaptpdiformat = pdiOf course, make sure that gen2_49_crimson_fusion_7.1.17.116786.bin and the other file names are actually present and the correct version in your firmware file. I only have 3.2.16 extracted here, but I think it's identical to 3.2.15....
-- Dave
Guess I am a little different I know mine is a 3tb HP version and i would like to use the 3.2.16 firmware but i get
Error: Firmware file does not contain firmware for device 'fct0', part 'PA005091001'.
I assume that the method would be similar for the 1.2tb versions if you guys could help that would be awesome
and output of
fio-status -a
Error: Firmware file does not contain firmware for device 'fct0', part 'PA005091001'.
I assume that the method would be similar for the 1.2tb versions if you guys could help that would be awesome
and output of
fio-status -a
Code:
Found 1 ioMemory device in this system
Driver version: 3.2.14 build 1675
Adapter: Single Controller Adapter
HP 3000GB MLC PCIe ioDrive2 for ProLiant Servers, Product Number:721458-B21, SN:3UN807G001
ioDrive2 Adapter Controller, PN:721551-001
External Power: NOT connected
PCIe Bus voltage: avg 12.12V
PCIe Bus current: avg 0.92A
PCIe Bus power: avg 11.20W
PCIe Power limit threshold: 24.75W
PCIe slot available power: unavailable
Connected ioMemory modules:
fct0: Product Number:721458-B21, SN:1419D05FE
fct0 Attached
ioDrive2 Adapter Controller, Product Number:721458-B21, SN:1419D05FE
ioDrive2 Adapter Controller, PN:721551-001
SMP(AVR) Versions: App Version: 1.0.21.0, Boot Version: 1.0.6.1
Located in slot 0 Center of ioDrive2 Adapter Controller SN:1419D05FE
Powerloss protection: protected
PCI:06:00.0
Vendor:1aed, Device:2001, Sub vendor:1590, Sub device:85
Firmware v7.1.17, rev 116786 Public
3000.00 GBytes device size
Format: v500, 5859375000 sectors of 512 bytes
PCIe slot available power: unavailable
PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total
Internal temperature: 45.28 degC, max 46.76 degC
Internal voltage: avg 1.02V, max 1.02V
Aux voltage: avg 2.49V, max 2.49V
Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00%
Active media: 100.00%
Rated PBW: 37.00 PB, 99.90% remaining
Lifetime data volumes:
Physical bytes written: 37,760,995,902,072
Physical bytes read : 66,640,310,265,672
RAM usage:
Current: 970,466,112 bytes
Peak : 970,466,112 bytes
Contained VSUs:
fioiom0: ID:0, UUID:7c552119-2855-496a-9bd4-28fbf807a370
fioiom0 State: Online, Type: block device
ID:0, UUID:7c552119-2855-496a-9bd4-28fbf807a370
3000.00 GBytes device size
Format: 5859375000 sectors of 512 bytesHI everybody,
I have been reading this topic for a few days but no luck on solutions.
I hope someone can point me in the right direction.
I have 2 Sandisk ioDrive II 785GB (rev 4) drives installed in an old Dell T410 server. (dual Xeon 5 series, 128GB mem)
I am using Proxmox on Ubuntu 7.3 and i can not get them to work.
They are stuck in minimal state, i can not attach, detach, or even sure-erase them.
What i have done so far:
Fio status
PCI check
Anyone have an idea what is going on here?
EDIT: typo's
I have been reading this topic for a few days but no luck on solutions.
I hope someone can point me in the right direction.
I have 2 Sandisk ioDrive II 785GB (rev 4) drives installed in an old Dell T410 server. (dual Xeon 5 series, 128GB mem)
I am using Proxmox on Ubuntu 7.3 and i can not get them to work.
They are stuck in minimal state, i can not attach, detach, or even sure-erase them.
What i have done so far:
- I installed the legacy drivers
- I installed the drivers from the GitHub - RemixVSL/iomemory-vsl: Updated Fusion-io iomemory VSL Linux (version 3.2.16) driver for recent kernels.
- I updated the firmware (succesfully, no errors)
- Updates proxmox to the newest kernel and installed the drivers again from Github.
Code:
root@pxmx:~# demsg -T | grep fio
-bash: demsg: command not found
root@pxmx:~# dmesg -T | grep fio
[Sat Mar 4 18:13:30 2023] <6>fioinf VSL configuration hash: 8f82ea05bdf1195cb400fb48e4ef09fc49b3c1aa
[Sat Mar 4 18:13:30 2023] <6>fioinf
[Sat Mar 4 18:13:30 2023] <6>fioinf Copyright (c) 2006-2014 Fusion-io, Inc. (acquired by SanDisk Corp. 2014)
[Sat Mar 4 18:13:30 2023] <6>fioinf Copyright (c) 2014-2016 SanDisk Corp. and/or all its affiliates. (acquired by Western Digital Corp. 2016)
[Sat Mar 4 18:13:30 2023] <6>fioinf Copyright (c) 2016-2018 Western Digital Technologies, Inc. All rights reserved.
[Sat Mar 4 18:13:30 2023] <6>fioinf For Terms and Conditions see the License file included
[Sat Mar 4 18:13:30 2023] <6>fioinf with this driver package.
[Sat Mar 4 18:13:30 2023] <6>fioinf
[Sat Mar 4 18:13:30 2023] <6>fioinf ioDrive driver 6.1.10-1-f3a056d-3.2.16.1731 loading...
[Sat Mar 4 18:13:30 2023] <6>fioinf ioDrive 0000:06:00.0: mapping controller on BAR 5
[Sat Mar 4 18:13:30 2023] <6>fioinf ioDrive 0000:06:00.0: MSI enabled
[Sat Mar 4 18:13:30 2023] <6>fioinf ioDrive 0000:06:00.0: using MSI interrupts
[Sat Mar 4 18:13:30 2023] <6>fioinf ioDrive 0000:06:00.0.0: Starting master controller
[Sat Mar 4 18:13:30 2023] <6>fioinf ioDrive 0000:06:00.0.0: PMP Address: 1 1 1
[Sat Mar 4 18:13:30 2023] <6>fioinf ioDrive 0000:06:00.0.0: SMP Controller Firmware APP version 1.0.35 0
[Sat Mar 4 18:13:30 2023] <6>fioinf ioDrive 0000:06:00.0.0: SMP Controller Firmware BOOT version 0.0.9 1
[Sat Mar 4 18:13:33 2023] <6>fioinf ioDrive 0000:06:00.0.0: Required PCIE bandwidth 2.000 GBytes per sec
[Sat Mar 4 18:13:33 2023] <6>fioinf ioDrive 0000:06:00.0.0: Board serial number is 1221D2168
[Sat Mar 4 18:13:33 2023] <6>fioinf ioDrive 0000:06:00.0.0: Adapter serial number is 1221D2168
[Sat Mar 4 18:13:33 2023] <6>fioinf ioDrive 0000:06:00.0.0: Default capacity 785.000 GBytes
[Sat Mar 4 18:13:33 2023] <6>fioinf ioDrive 0000:06:00.0.0: Default sector size 512 bytes
[Sat Mar 4 18:13:33 2023] <6>fioinf ioDrive 0000:06:00.0.0: Rated endurance 11.00 PBytes
[Sat Mar 4 18:13:33 2023] <6>fioinf ioDrive 0000:06:00.0.0: 100C temp range hardware found
[Sat Mar 4 18:13:33 2023] <6>fioinf ioDrive 0000:06:00.0.0: Maximum capacity 845.000 GBytes
[Sat Mar 4 18:13:35 2023] <6>fioinf ioDrive 0000:06:00.0.0: Firmware version 7.1.17 116786 (0x700411 0x1c832)
[Sat Mar 4 18:13:35 2023] <6>fioinf ioDrive 0000:06:00.0.0: Platform version 16
[Sat Mar 4 18:13:35 2023] <6>fioinf ioDrive 0000:06:00.0.0: Firmware VCS version 116786 [0x1c832]
[Sat Mar 4 18:13:35 2023] <6>fioinf ioDrive 0000:06:00.0.0: Firmware VCS uid 0xaeb15671994a45642f91efbb214fa428e4245f8a
[Sat Mar 4 18:13:35 2023] <6>fioinf ioDrive 0000:06:00.0.0: Powercut flush: Enabled
[Sat Mar 4 18:13:35 2023] <6>fioinf ioDrive 0000:06:00.0.0: PCIe power monitor enabled (master). Limit set to 35.0 watts.
[Sat Mar 4 18:13:35 2023] <6>fioinf ioDrive 0000:06:00.0.0: Thermal monitoring: Enabled
[Sat Mar 4 18:13:35 2023] <6>fioinf ioDrive 0000:06:00.0.0: Hardware temperature alarm set for 100C.
[Sat Mar 4 18:13:35 2023] <6>fioinf ioDrive 0000:06:00.0: Found device fct0 (Fusion-io ioDrive2 785GB 0000:06:00.0) on pipeline 0
[Sat Mar 4 18:13:35 2023] <3>fioerr Fusion-io ioDrive2 785GB 0000:06:00.0: failed to map append request
[Sat Mar 4 18:13:35 2023] <3>fioerr Fusion-io ioDrive2 785GB 0000:06:00.0: request page program 00000000e6ed7e3d failed -22
[Sat Mar 4 18:13:36 2023] <6>fioinf ioDrive 0000:06:00.0.0: stuck flush request on startup detected, retry iteration 1 of 3...
[Sat Mar 4 18:13:36 2023] <6>fioinf ioDrive 0000:06:00.0.0: Starting master controller
[Sat Mar 4 18:13:36 2023] <6>fioinf ioDrive 0000:06:00.0.0: PMP Address: 1 1 1
[Sat Mar 4 18:13:36 2023] <6>fioinf ioDrive 0000:06:00.0.0: SMP Controller Firmware APP version 1.0.35 0
[Sat Mar 4 18:13:36 2023] <6>fioinf ioDrive 0000:06:00.0.0: SMP Controller Firmware BOOT version 0.0.9 1
[Sat Mar 4 18:13:39 2023] <6>fioinf ioDrive 0000:06:00.0.0: Required PCIE bandwidth 2.000 GBytes per sec
[Sat Mar 4 18:13:39 2023] <6>fioinf ioDrive 0000:06:00.0.0: Board serial number is 1221D2168
[Sat Mar 4 18:13:39 2023] <6>fioinf ioDrive 0000:06:00.0.0: Adapter serial number is 1221D2168
[Sat Mar 4 18:13:39 2023] <6>fioinf ioDrive 0000:06:00.0.0: Default capacity 785.000 GBytes
[Sat Mar 4 18:13:39 2023] <6>fioinf ioDrive 0000:06:00.0.0: Default sector size 512 bytes
[Sat Mar 4 18:13:39 2023] <6>fioinf ioDrive 0000:06:00.0.0: Rated endurance 11.00 PBytes
[Sat Mar 4 18:13:39 2023] <6>fioinf ioDrive 0000:06:00.0.0: 100C temp range hardware found
[Sat Mar 4 18:13:39 2023] <6>fioinf ioDrive 0000:06:00.0.0: Maximum capacity 845.000 GBytes
[Sat Mar 4 18:13:40 2023] <6>fioinf ioDrive 0000:06:00.0.0: Firmware version 7.1.17 116786 (0x700411 0x1c832)
[Sat Mar 4 18:13:40 2023] <6>fioinf ioDrive 0000:06:00.0.0: Platform version 16
[Sat Mar 4 18:13:40 2023] <6>fioinf ioDrive 0000:06:00.0.0: Firmware VCS version 116786 [0x1c832]
[Sat Mar 4 18:13:40 2023] <6>fioinf ioDrive 0000:06:00.0.0: Firmware VCS uid 0xaeb15671994a45642f91efbb214fa428e4245f8a
[Sat Mar 4 18:13:40 2023] <6>fioinf ioDrive 0000:06:00.0.0: Powercut flush: Enabled
[Sat Mar 4 18:13:41 2023] <3>fioerr ioDrive 0000:06:00.0.0: could not find canonical value across 16 pads
[Sat Mar 4 18:13:41 2023] <3>fioerr ioDrive 0000:06:00.0.0: MINIMAL MODE DRIVER: hardware failure.
[Sat Mar 4 18:13:41 2023] <6>fioinf ioDrive 0000:06:00.0: Found device fct0 (Fusion-io ioDrive2 785GB 0000:06:00.0) on pipeline 0
[Sat Mar 4 18:13:41 2023] <6>fioinf fct0: stuck flush request got better on retry.
[Sat Mar 4 18:13:41 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: probed fct0
[Sat Mar 4 18:13:41 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: Attaching explicitly disabled
[Sat Mar 4 18:13:41 2023] <3>fioerr Fusion-io ioDrive2 785GB 0000:06:00.0: auto attach failed with error EINVAL: Invalid argument
[Sat Mar 4 18:13:41 2023] <6>fioinf ioDrive 0000:02:00.0: mapping controller on BAR 5
[Sat Mar 4 18:13:41 2023] <6>fioinf ioDrive 0000:02:00.0: MSI enabled
[Sat Mar 4 18:13:41 2023] <6>fioinf ioDrive 0000:02:00.0: using MSI interrupts
[Sat Mar 4 18:13:41 2023] <6>fioinf ioDrive 0000:02:00.0.0: Starting master controller
[Sat Mar 4 18:13:41 2023] <6>fioinf ioDrive 0000:02:00.0.0: PMP Address: 1 1 1
[Sat Mar 4 18:13:41 2023] <6>fioinf ioDrive 0000:02:00.0.0: SMP Controller Firmware APP version 1.0.35 0
[Sat Mar 4 18:13:41 2023] <6>fioinf ioDrive 0000:02:00.0.0: SMP Controller Firmware BOOT version 0.0.9 1
[Sat Mar 4 18:13:43 2023] <6>fioinf ioDrive 0000:02:00.0.0: Required PCIE bandwidth 2.000 GBytes per sec
[Sat Mar 4 18:13:43 2023] <6>fioinf ioDrive 0000:02:00.0.0: Board serial number is 1239D2015
[Sat Mar 4 18:13:43 2023] <6>fioinf ioDrive 0000:02:00.0.0: Adapter serial number is 1239D2015
[Sat Mar 4 18:13:43 2023] <6>fioinf ioDrive 0000:02:00.0.0: Default capacity 785.000 GBytes
[Sat Mar 4 18:13:43 2023] <6>fioinf ioDrive 0000:02:00.0.0: Default sector size 512 bytes
[Sat Mar 4 18:13:43 2023] <6>fioinf ioDrive 0000:02:00.0.0: Rated endurance 11.00 PBytes
[Sat Mar 4 18:13:43 2023] <6>fioinf ioDrive 0000:02:00.0.0: 100C temp range hardware found
[Sat Mar 4 18:13:43 2023] <6>fioinf ioDrive 0000:02:00.0.0: Maximum capacity 845.000 GBytes
[Sat Mar 4 18:13:44 2023] <6>fioinf ioDrive 0000:02:00.0.0: Firmware version 7.1.17 116786 (0x700411 0x1c832)
[Sat Mar 4 18:13:44 2023] <6>fioinf ioDrive 0000:02:00.0.0: Platform version 16
[Sat Mar 4 18:13:44 2023] <6>fioinf ioDrive 0000:02:00.0.0: Firmware VCS version 116786 [0x1c832]
[Sat Mar 4 18:13:44 2023] <6>fioinf ioDrive 0000:02:00.0.0: Firmware VCS uid 0xaeb15671994a45642f91efbb214fa428e4245f8a
[Sat Mar 4 18:13:44 2023] <6>fioinf ioDrive 0000:02:00.0.0: Powercut flush: Enabled
[Sat Mar 4 18:13:44 2023] <6>fioinf ioDrive 0000:02:00.0.0: PCIe power monitor enabled (master). Limit set to 35.0 watts.
[Sat Mar 4 18:13:44 2023] <6>fioinf ioDrive 0000:02:00.0.0: Thermal monitoring: Enabled
[Sat Mar 4 18:13:44 2023] <6>fioinf ioDrive 0000:02:00.0.0: Hardware temperature alarm set for 100C.
[Sat Mar 4 18:13:45 2023] <6>fioinf ioDrive 0000:02:00.0: Found device fct1 (Fusion-io ioDrive2 785GB 0000:02:00.0) on pipeline 0
[Sat Mar 4 18:13:45 2023] <3>fioerr Fusion-io ioDrive2 785GB 0000:02:00.0: failed to map append request
[Sat Mar 4 18:13:45 2023] <3>fioerr Fusion-io ioDrive2 785GB 0000:02:00.0: request page program 00000000bd3628aa failed -22
[Sat Mar 4 18:13:46 2023] <6>fioinf ioDrive 0000:02:00.0.0: stuck flush request on startup detected, retry iteration 1 of 3...
[Sat Mar 4 18:13:46 2023] <6>fioinf ioDrive 0000:02:00.0.0: Starting master controller
[Sat Mar 4 18:13:46 2023] <6>fioinf ioDrive 0000:02:00.0.0: PMP Address: 1 1 1
[Sat Mar 4 18:13:46 2023] <6>fioinf ioDrive 0000:02:00.0.0: SMP Controller Firmware APP version 1.0.35 0
[Sat Mar 4 18:13:46 2023] <6>fioinf ioDrive 0000:02:00.0.0: SMP Controller Firmware BOOT version 0.0.9 1
[Sat Mar 4 18:13:47 2023] <6>fioinf ioDrive 0000:02:00.0.0: Required PCIE bandwidth 2.000 GBytes per sec
[Sat Mar 4 18:13:47 2023] <6>fioinf ioDrive 0000:02:00.0.0: Board serial number is 1239D2015
[Sat Mar 4 18:13:47 2023] <6>fioinf ioDrive 0000:02:00.0.0: Adapter serial number is 1239D2015
[Sat Mar 4 18:13:47 2023] <6>fioinf ioDrive 0000:02:00.0.0: Default capacity 785.000 GBytes
[Sat Mar 4 18:13:47 2023] <6>fioinf ioDrive 0000:02:00.0.0: Default sector size 512 bytes
[Sat Mar 4 18:13:47 2023] <6>fioinf ioDrive 0000:02:00.0.0: Rated endurance 11.00 PBytes
[Sat Mar 4 18:13:47 2023] <6>fioinf ioDrive 0000:02:00.0.0: 100C temp range hardware found
[Sat Mar 4 18:13:47 2023] <6>fioinf ioDrive 0000:02:00.0.0: Maximum capacity 845.000 GBytes
[Sat Mar 4 18:13:49 2023] <6>fioinf ioDrive 0000:02:00.0.0: Firmware version 7.1.17 116786 (0x700411 0x1c832)
[Sat Mar 4 18:13:49 2023] <6>fioinf ioDrive 0000:02:00.0.0: Platform version 16
[Sat Mar 4 18:13:49 2023] <6>fioinf ioDrive 0000:02:00.0.0: Firmware VCS version 116786 [0x1c832]
[Sat Mar 4 18:13:49 2023] <6>fioinf ioDrive 0000:02:00.0.0: Firmware VCS uid 0xaeb15671994a45642f91efbb214fa428e4245f8a
[Sat Mar 4 18:13:49 2023] <6>fioinf ioDrive 0000:02:00.0.0: Powercut flush: Enabled
[Sat Mar 4 18:13:49 2023] <3>fioerr ioDrive 0000:02:00.0.0: could not find canonical value across 16 pads
[Sat Mar 4 18:13:49 2023] <3>fioerr ioDrive 0000:02:00.0.0: MINIMAL MODE DRIVER: hardware failure.
[Sat Mar 4 18:13:50 2023] <6>fioinf ioDrive 0000:02:00.0: Found device fct1 (Fusion-io ioDrive2 785GB 0000:02:00.0) on pipeline 0
[Sat Mar 4 18:13:50 2023] <6>fioinf fct1: stuck flush request got better on retry.
[Sat Mar 4 18:13:50 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:02:00.0: probed fct1
[Sat Mar 4 18:13:50 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:02:00.0: Attaching explicitly disabled
[Sat Mar 4 18:13:50 2023] <3>fioerr Fusion-io ioDrive2 785GB 0000:02:00.0: auto attach failed with error EINVAL: Invalid argument
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0xc030684d unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0x80286828 unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0xc0196834 unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0x80606886 unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0xc0196834 unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0xc0196834 unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0xc038684a unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0x80106874 unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0xc0196834 unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0xc0196834 unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0xc058682b unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0xc0196834 unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:06:00.0: IOCTL 0xc0196834 unsupported in minimal mode
[Sat Mar 4 18:16:00 2023] <6>fioinf Fusion-io ioDrive2 785GB 0000:02:00.0: IOCTL 0xc030684d unsupported in minimal mode
Code:
~# fio-status -a
Found 2 ioMemory devices in this system
Driver version: 3.2.16 build 1731
Adapter: Single Controller Adapter
Fusion-io ioDrive2 785GB, Product Number:F00-001-785G-CS-0001, SN:1221D2168, FIO SN:1221D2168
ioDrive2 Adapter Controller, PN:PA004137008
External Power: NOT connected
PCIe Power limit threshold: 35.00W
PCIe slot available power: 25.00W
PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total
Connected ioMemory modules:
fct0: Product Number:F00-001-785G-CS-0001, SN:1221D2168
fct0 Status unknown: Driver is in MINIMAL MODE:
Device has a hardware failure
ioDrive2 Adapter Controller, Product Number:F00-001-785G-CS-0001, SN:1221D2168
!! ---> There are active errors or warnings on this device! Read below for details.
ioDrive2 Adapter Controller, PN:PA004137008
SMP(AVR) Versions: App Version: 1.0.35.0, Boot Version: 0.0.9.1
Located in slot 0 Center of ioDrive2 Adapter Controller SN:1221D2168
Powerloss protection: not available
PCI:06:00.0, Slot Number:5
Vendor:1aed, Device:2001, Sub vendor:1aed, Sub device:2001
Firmware v7.1.17, rev 116786 Public
Geometry and capacity information not available.
Format: not low-level formatted
PCIe slot available power: 25.00W
PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total
Internal temperature: 56.60 degC, max 57.09 degC
Internal voltage: avg 1.02V, max 1.02V
Aux voltage: avg 2.49V, max 2.49V
Rated PBW: 11.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.
Adapter: Single Controller Adapter
Fusion-io ioDrive2 785GB, Product Number:F00-001-785G-CS-0001, SN:1239D2015, FIO SN:1239D2015
ioDrive2 Adapter Controller, PN:PA004137008
External Power: NOT connected
PCIe Power limit threshold: 35.00W
PCIe slot available power: 25.00W
PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total
Connected ioMemory modules:
fct1: Product Number:F00-001-785G-CS-0001, SN:1239D2015
fct1 Status unknown: Driver is in MINIMAL MODE:
Device has a hardware failure
ioDrive2 Adapter Controller, Product Number:F00-001-785G-CS-0001, SN:1239D2015
!! ---> There are active errors or warnings on this device! Read below for details.
ioDrive2 Adapter Controller, PN:PA004137008
SMP(AVR) Versions: App Version: 1.0.35.0, Boot Version: 0.0.9.1
Located in slot 0 Center of ioDrive2 Adapter Controller SN:1239D2015
Powerloss protection: not available
PCI:02:00.0, Slot Number:1
Vendor:1aed, Device:2001, Sub vendor:1aed, Sub device:2001
Firmware v7.1.17, rev 116786 Public
Geometry and capacity information not available.
Format: not low-level formatted
PCIe slot available power: 25.00W
PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total
Internal temperature: 56.11 degC, max 56.60 degC
Internal voltage: avg 1.02V, max 1.02V
Aux voltage: avg 2.50V, max 2.50V
Rated PBW: 11.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:
~# fio-pci-check -v
Root Bridge PCIe 8000 MB/sec needed max
Current control settings: 0x010f
Correctable Error Reporting: enabled
Non-Fatal Error Reporting: enabled
Fatal Error Reporting: enabled
Unsupported Request Reporting: enabled
Payload size: 128
Max read size: 128
Current status: 0x0000
Correctable Error(s): None
Non-Fatal Error(s): None
Fatal Error(s): None
Unsupported Request(s): None
link_capabilities: 0x00003c41
Maximum link speed: 2.5 Gb/s per lane
Maximum link width: 4 lanes
Current link_status: 0x00003041
Link speed: 2.5 Gb/s per lane
Link width is 4 lanes
Bridge 0000:00:07.00 (06-06) (8086:340e)
Needed 2000 MB/sec Avail 2000 MB/sec
Current control settings: 0x012f
Correctable Error Reporting: enabled
Non-Fatal Error Reporting: enabled
Fatal Error Reporting: enabled
Unsupported Request Reporting: enabled
Payload size: 256
Max read size: 128
Current status: 0x0000
Correctable Error(s): None
Non-Fatal Error(s): None
Fatal Error(s): None
Unsupported Request(s): None
link_capabilities: 0x00003c82
Maximum link speed: 5.0 Gb/s per lane
Maximum link width: 8 lanes
Current link_status: 0x00007042
Link speed: 5.0 Gb/s per lane
Link width is 4 lanes
ioDrive 0000:06:00.0 (2001) Firmware 116786
Current control settings: 0x283e
Correctable Error Reporting: disabled
Non-Fatal Error Reporting: enabled
Fatal Error Reporting: enabled
Unsupported Request Reporting: enabled
Payload size: 256
Max read size: 512
Current status: 0x0000
Correctable Error(s): None
Non-Fatal Error(s): None
Fatal Error(s): None
Unsupported Request(s): None
link_capabilities: 0x0000f442
Maximum link speed: 5.0 Gb/s per lane
Maximum link width: 4 lanes
Slot Power limit: 25.0W (25000mw)
Current link_status: 0x00000042
Link speed: 5.0 Gb/s per lane
Link width is 4 lanes
Current link_control: 0x00000000
Not modifying link enabled state
Not forcing retrain of link
Bridge 0000:00:0a.00 (02-02) (8086:3411)
Needed 2000 MB/sec Avail 2000 MB/sec
Current control settings: 0x012f
Correctable Error Reporting: enabled
Non-Fatal Error Reporting: enabled
Fatal Error Reporting: enabled
Unsupported Request Reporting: enabled
Payload size: 256
Max read size: 128
Current status: 0x0000
Correctable Error(s): None
Non-Fatal Error(s): None
Fatal Error(s): None
Unsupported Request(s): None
link_capabilities: 0x00003c42
Maximum link speed: 5.0 Gb/s per lane
Maximum link width: 4 lanes
Current link_status: 0x00007042
Link speed: 5.0 Gb/s per lane
Link width is 4 lanes
ioDrive 0000:02:00.0 (2001) Firmware 116786
Current control settings: 0x283e
Correctable Error Reporting: disabled
Non-Fatal Error Reporting: enabled
Fatal Error Reporting: enabled
Unsupported Request Reporting: enabled
Payload size: 256
Max read size: 512
Current status: 0x0000
Correctable Error(s): None
Non-Fatal Error(s): None
Fatal Error(s): None
Unsupported Request(s): None
link_capabilities: 0x0000f442
Maximum link speed: 5.0 Gb/s per lane
Maximum link width: 4 lanes
Slot Power limit: 25.0W (25000mw)
Current link_status: 0x00000042
Link speed: 5.0 Gb/s per lane
Link width is 4 lanes
Current link_control: 0x00000000
Not modifying link enabled state
Not forcing retrain of linkAnyone have an idea what is going on here?
EDIT: typo's
Last edited:
Nope, i have no windows machine available...
I guess i will have to install one..
I will try that next week.
Until then i am open to other suggestions.
I guess i will have to install one..
I will try that next week.
Until then i am open to other suggestions.
I am running intel xeons, isn't that the code for AMD processors?
I already put " iommu=pt " as an addition in /etc/default/grub, is that not enough?
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet iommu=pt"I am trying to compile the vsl3.2.16 for my ubuntu (I need to switch to ubuntu from debian due to some other incompatibility with debian). I am getting a compiliation error:
/git/iomemory-vsl/root/usr/src/iomemory-vsl-3.2.16/include/fio/port/common-linux/commontypes.h:37:10: fatal error: stddef.h: No such file or directory
37 | #include <stddef.h>
| ^~~~~~~~~~
compilation terminated.
Full output is here:
I followed the instructions provided by @goob for debian:
1. git checkout v4.20.1
2. cd root/usr/src/iomemory-vsl-3.2.16
3. make
4. insmod iomemory-vsl.ko
I am able to build main branch but cannot make it work for the old branch.
/git/iomemory-vsl/root/usr/src/iomemory-vsl-3.2.16/include/fio/port/common-linux/commontypes.h:37:10: fatal error: stddef.h: No such file or directory
37 | #include <stddef.h>
| ^~~~~~~~~~
compilation terminated.
Full output is here:
I followed the instructions provided by @goob for debian:
1. git checkout v4.20.1
2. cd root/usr/src/iomemory-vsl-3.2.16
3. make
4. insmod iomemory-vsl.ko
I am able to build main branch but cannot make it work for the old branch.
Last edited:
Just found out that I need to stay on main branch for ubuntu 22.04; switching branch is for old kernels/distros. I should have stayed on mainI am trying to compile the vsl3.2.16 for my ubuntu (I need to switch to ubuntu from debian due to some other incompatibility with debian). I am getting a compiliation error:
/git/iomemory-vsl/root/usr/src/iomemory-vsl-3.2.16/include/fio/port/common-linux/commontypes.h:37:10: fatal error: stddef.h: No such file or directory
37 | #include <stddef.h>
| ^~~~~~~~~~
compilation terminated.
Full output is here:
I followed the instructions provided by @goob for debian:
1. git checkout v4.20.1
2. cd root/usr/src/iomemory-vsl-3.2.16
3. make
I am able to build main branch but cannot make it work for the old branch.
Does anyone know why make dkms didn't work and had to do insmod?
intel_iommu=on then.
The options need to actually make it into your bootloader config, so once added, be sure to run a "dracut -f" to rebuild your boot images/etc.
dracut -f results in "command not found".
Is that a Ubuntu command?
I used 'update-grub' for a grub based system or 'proxmox-boot-tool refresh' for systemd based proxmox environments.
But you might have set me on the right path, i was using the wrong one
Thanks for your help!
Is that a Ubuntu command?
I used 'update-grub' for a grub based system or 'proxmox-boot-tool refresh' for systemd based proxmox environments.
But you might have set me on the right path, i was using the wrong one
Thanks for your help!
Last edited:
Can anyone confirm the sustained write speeds on the 825Gb version of this card? I used to get 800MB/sec at least but for some reason performance of the card went down on the new system and I cannot figure out why. Now I am getting 400MB/sec and I am not sure if this is the expected speed for this card.
Should be 1.5Gb/sec read, 1.1GB/sec write for any ioDrive II over 785GB. This will be slightly slower with a filesystem on it.
Your drive is the same as the 785, but with less over-provisioning, so you have a tad less write "buffer" for sustained write before you start putting pressure on the groomer.
You can adjust this over-provisioning yourself with fio-format to reduce formatted size and increase free NAND for sustained writes.
