Wondering if my 1.2TB IODrive2 is salvageable. It recently stopped working and running an fio-check gave me:
fio-pci-check didn't show any problems with the PCIE bus and I've been running 2 of these cards for several years without issue. Digging into the syslog I found these with relation to the problem:
The system runs the consistency check on the still working drive without issue, but doesn't see this drive at all. Is it fubar or is there a way to remap those bad pads or force it online? Attach and detach don't work.
Thanks,
Jason
Code:
Adapter: Single Controller Adapter
Fusion-io ioDrive2 1.205TB, Product Number:F00-001-1T20-CS-0001, SN:1208D5248, FIO SN:1208D5248
ioDrive2 Adapter Controller, PN:PA004137009
External Power Override: ON
External Power: NOT connected
PCIe Power limit threshold: Disabled
PCIe slot available power: unavailable
Connected ioMemory modules:
fct3: Product Number:F00-001-1T20-CS-0001, SN:1208D5248
fct3 Status unknown: Driver is in MINIMAL MODE:
General channel initialization failure
ioDrive2 Adapter Controller, Product Number:F00-001-1T20-CS-0001, SN:1208D5248
!! ---> There are active errors or warnings on this device! Read below for details.
ioDrive2 Adapter Controller, PN:PA004137009
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:1208D5248
Powerloss protection: not available
PCI:08: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: 26.00W
PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total
Internal temperature: 63.49 degC, max 74.81 degC
Internal voltage: avg 1.02V, max 1.02V
Aux voltage: avg 2.48V, 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.
Code:
2022-10-03T02:15:49.9641956Z - ERROR - FusionEventDriver - fct3: MINIMAL MODE DRIVER: General channel initialization failure. error code:-1
2022-10-03T02:15:49.4956171Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 0 byte 1 exp: 0xa8 act: 0x01
2022-10-03T02:15:49.4956231Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 0 byte 2 exp: 0x25 act: 0x02
2022-10-03T02:15:49.4956272Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 0 byte 3 exp: 0xcb act: 0x03
2022-10-03T02:15:49.4956314Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 1 byte 1 exp: 0xa8 act: 0x01
2022-10-03T02:15:49.4956353Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 1 byte 2 exp: 0x25 act: 0x02
2022-10-03T02:15:49.4956392Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 1 byte 3 exp: 0xcb act: 0x03
2022-10-03T02:15:49.4956432Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 2 byte 1 exp: 0xa8 act: 0x01
2022-10-03T02:15:49.4956471Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 2 byte 2 exp: 0x25 act: 0x02
2022-10-03T02:15:49.4956509Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 2 byte 3 exp: 0xcb act: 0x03
2022-10-03T02:15:49.4956550Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 3 byte 1 exp: 0xa8 act: 0x01
2022-10-03T02:15:49.4956588Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 3 byte 2 exp: 0x25 act: 0x02
2022-10-03T02:15:49.4956627Z - ERROR - FusionEventDriver - fct3: bad pad found: pad 7 bank 3 byte 3 exp: 0xcb act: 0x03
Code:
C:\WINDOWS\system32>fio-read-lebmap /dev/fct3
unexpected FUSION_IOCTL_QUERY_MEL result -22 (22).
Error: Failed to read MEL: Invalid input.
Thanks,
Jason