Did a little more reading and found that fio-sure-erase is not working anymore on newer linux kernels. The relevant issue on the RemixVSL github: [BUG] Kernel memory overwrite attempt detected to SLUB object 'fusion_user_ll_request' · Issue #115 · RemixVSL/iomemory-vsl
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
It appears the current workaround is to install on an OS with an older kernel or to use the “slub” branch that bypasses this issue somehow. I was able to install and build the driver from the slub branch on Ubuntu 24.04.3 and could use fio-sure-erase to rescue the drive.
Paging @acquacow ... Do you happen to have the pinout for the auxiliary power connector on the SX350 6.4TB? The 4 pin connector looks like this:
But, I cannot see any markings on the PCB to tell me which two pins are +12v and which ones are GND. I'm putting a few of these n my SAN nodes and am gonna create a harness to power them from the 12v rail directly.
Help?
But, I cannot see any markings on the PCB to tell me which two pins are +12v and which ones are GND. I'm putting a few of these n my SAN nodes and am gonna create a harness to power them from the 12v rail directly.
Help?
Answering my own question... (I'm fairly sure of this).
That connector is NOT for external power. Sandisk did away with external 12v connectivity starting with SX300 series, because their stated reason is that "modern" motherboards can supply enough power to the slots themselves.
This begs the question...Does Supermicro adhere "strictly" to the 25w limit on x8 slots or can it supply more than that? I'm not sure. I'll turn on the power override at the driver level and run some tests to see if the performance is different.
Hi!
I have an sx350 6400 card. I cannot for the life of me get a block device to appear on Debian. I've tried editing the config file for the firmware, but nothing is working out. Any ideas?
And this is how I'm trying to edit the INFO file.
I have an sx350 6400 card. I cannot for the life of me get a block device to appear on Debian. I've tried editing the config file for the firmware, but nothing is working out. Any ideas?
Code:
root@iscsi:~# uname -a
Linux iscsi 6.1.0-31-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07) x86_64 GNU/Linux
root@iscsi:~# fio-update-iodrive /root/vsl_downloads/fusion_4.3.7-20200113.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: This kernel prevents userspace access to device memory while the iomemory driver is loaded.
Retry after completing one of the following:
a) Unload the iomemory_vsl4 driver
b) OR Set the kernel parameter 'iomem=relaxed' and reboot the kernel
c) OR disable the restriction using sysctl and the dev.mem.restricted parameter.
See ioMemory documentation.
root@iscsi:~# fio-status -a
Found 1 VSL driver package:
4.3.7 build 1205 Driver: loaded
Found 1 ioMemory device in this system
Adapter: ioMono (driver 4.3.7)
ioMemory SX350-6400, Product Number:Y12DP, SN:US0Y12DP7605464D0004A00
ioMemory Adapter Controller, PN:J5F1V
Product UUID:abc2e003-a8ce-5e66-b2f9-2e64ba27d2df
External Power Threshold Override: 74.75W
PCIe Power limit threshold: 74.75W
PCIe slot available power: unavailable
PCIe negotiated link: 8 lanes at 5.0 Gt/sec each, 4000.00 MBytes/sec total
Connected ioMemory modules:
fct0: 01:00.0, Product Number:Y12DP, SN:US0Y12DP7605464D0004A00
fct0 Status unknown: Driver is in MINIMAL MODE:
The firmware on this device is not compatible with the currently installed version of the driver
ioMemory Adapter Controller, Product Number:Y12DP, SN:1605D011D
!! ---> There are active errors or warnings on this device! Read below for details.
ioMemory Adapter Controller, PN:J5F1V
Microcode Versions: App:0.0.13.0
Powerloss protection: not available
PCI:01:00.0
Vendor:1aed, Device:3001, Sub vendor:1028, Sub device:1fc0
Firmware v8.9.1, rev 20150408 Public
Geometry and capacity information not available.
Format: not low-level formatted
PCIe slot available power: 26.00W
PCIe negotiated link: 8 lanes at 5.0 Gt/sec each, 4000.00 MBytes/sec total
Internal temperature: 28.05 degC, max 30.02 degC
Internal voltage: avg 1.01V, max 1.02V
Aux voltage: avg 1.80V, max 1.81V
Rated PBW: 22.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.
root@iscsi:~# fio-status -F adapter.part_number_pa /dev/fct0
54-91-71514-6400G
root@iscsi:~# fio-status -F adapter.oem_part_number_replacement /dev/fct0
J5F1V
Code:
[54-91-71514]
version = 8.9.9.118194
file = gen3_tangerine_fusion_8.9.9.118194.bin
format = bin
ecc = 11b
cntrpdiversion = 0.0.15
cntrpdifile = avogadro_0.0.15.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.7.1205
optromfile = uefi-noboot-3002_4.3.7.1205.rom
[549171514]
version = 8.9.9.118194
file = gen3_tangerine_fusion_8.9.9.118194.bin
format = bin
ecc = 11b
cntrpdiversion = 0.0.15
cntrpdifile = avogadro_0.0.15.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.7.1205
optromfile = uefi-noboot-3002_4.3.7.1205.romPlease point me in the right direction, because I'm starting to see double from all the endless guides and stuff
The build was like this: Then a similar installation of fio-utils:
Code:
git clone https://github.com/snuf/iomemory-vsl4
cd iomemory-vsl4
make dpkg
dpkg -i iomemory-vsl4-6.1.0-31-amd64_4.3.7.1205-1.0_amd64.deb
Last edited: