3.2TB SSD for $240

I have my SX 350 3.2TB working just fine in proxmox. Putting your storage volume of choice on top of it is manual though since the GUI doesn't enumerate /dev/fioX devices.
 
Should work on 2022 (worked on server 2019 at least). Proxmox you can do, but you’ll have to compile drivers yourself (https://forum.proxmox.com/threads/c...oscale-and-ioscale2-cards-with-proxmox.54832/). Supposedly works on TrueNAS as well (haven’t tried that personally though) via compiling your own driver. ESXi support ended after 6.7u3 when VMware killed off compatibility for all the older drivers.
I run 2x 6.4tb on truenas scale. It works but is a huge pita to setup
 
There's 4 (well 3 now) sx350 6.4TB going for 400 USD. He says not used much, and open to offers.

https://www.ebay.ca/itm/186398376241
I’d take the low usage with a grain of salt in the absence of screenshots with “fio-status” output. I’ve had the misfortune of buying dead ones that ebay sellers had not even tested.

That said, the sx350 6.4tb was one of the last/best FusionIO drives, something like 20+ PBW endurance. They’re a bit faster than the older drives too.
 
He's got good feedback for other enterprisy related equipment. 'sides ebay is always a gamble :)


$300/ea in USD. He sounds like a company too as he states he has the 3.2TB version as well.
Err yeah 300, I meant 400 CAD. Don't ask.
 
I’d take the low usage with a grain of salt in the absence of screenshots with “fio-status” output. I’ve had the misfortune of buying dead ones that ebay sellers had not even tested.

That said, the sx350 6.4tb was one of the last/best FusionIO drives, something like 20+ PBW endurance. They’re a bit faster than the older drives too.
Good point about the fio-status info!

I asked the seller for a screenshot with fio-status output and was told the drives were already packaged for shipping and he wouldn't be able to test them in a system. He said to make an offer, so I threw in $225 (USD) last night to see what would happen.
The offer was accepted this morning, I'll report back fio-status when I get the drive.

He's got good feedback for other enterprisy related equipment. 'sides ebay is always a gamble :)



Err yeah 300, I meant 400 CAD. Don't ask.
Yeah, his feedback convinced me to try an offer and see what happens. If the drive isn't dead or near end of life with PBs written, this will be a steal for less than the price of the 3.2TB one I picked up when this thread started! :cool:
 
Good point about the fio-status info!

I asked the seller for a screenshot with fio-status output and was told the drives were already packaged for shipping and he wouldn't be able to test them in a system. He said to make an offer, so I threw in $225 (USD) last night to see what would happen.
The offer was accepted this morning, I'll report back fio-status when I get the drive.


Yeah, his feedback convinced me to try an offer and see what happens. If the drive isn't dead or near end of life with PBs written, this will be a steal for less than the price of the 3.2TB one I picked up when this thread started! :cool:
So it appears that the drive is not DOA, I just haven't been able to get the driver loaded properly.

Super long story short, I assumed it would be plug-n-play on my Win7 machine that has a similar Fusion 3.2Tb drive. However, that 3.2Tb drive is from the ioScale line, which uses VSL3 as the driver software. The 6.4Tb Fusion drive is part of the ioMemory line, which uses VSL4. According to the manual, VSL3 and VSL4 can't be run concurrently.

With that in mind, I spent a week trying to get an open-source driver to work on my Linux machine, but I keep getting a debug error during boot-up about the motherboard providing 0mW (yes, zero) of power to the PCIe slot this drive is plugged into. That was two weeks ago and now it looks like I'll be moving several states away, so I won't have time to devote to further troubleshooting this drive on my Linux machine.

It's likely a compatibility issue with either my motherboard (AX370 1st gen Ryzen board, BIOS has probably never been updated) or the Linux distro I'm running (which may not properly process/support iommu for VSL4 to function properly). Like I said, I really don't have time to figure out which part of my system is the culprit, but I am confident that the drive is not the issue since the fio-status command works (and states at the top of the command output "Driver not loaded") and prints out PN, SN, capacity, etc. Fio-attach won't work without the driver being loaded, which is the part I'm stuck at. With moving expenses coming up, the money would be more helpful than the drive.

If anyone is interested in this drive, I'll sell it for what I paid+shipping. I'm more than happy to provide the fio-status screenshot as well and will refund the purchase of the drive if it ends up being DOA or nonfunctional. I'd rather have someone on this thread who missed this sale use the drive rather than it sit dormant in my computer as it moves between storage boxes and states over the next year.

Feel free to DM me with interest or questions!
 
So it appears that the drive is not DOA, I just haven't been able to get the driver loaded properly.

Super long story short, I assumed it would be plug-n-play on my Win7 machine that has a similar Fusion 3.2Tb drive. However, that 3.2Tb drive is from the ioScale line, which uses VSL3 as the driver software. The 6.4Tb Fusion drive is part of the ioMemory line, which uses VSL4. According to the manual, VSL3 and VSL4 can't be run concurrently.

With that in mind, I spent a week trying to get an open-source driver to work on my Linux machine, but I keep getting a debug error during boot-up about the motherboard providing 0mW (yes, zero) of power to the PCIe slot this drive is plugged into. That was two weeks ago and now it looks like I'll be moving several states away, so I won't have time to devote to further troubleshooting this drive on my Linux machine.

It's likely a compatibility issue with either my motherboard (AX370 1st gen Ryzen board, BIOS has probably never been updated) or the Linux distro I'm running (which may not properly process/support iommu for VSL4 to function properly). Like I said, I really don't have time to figure out which part of my system is the culprit, but I am confident that the drive is not the issue since the fio-status command works (and states at the top of the command output "Driver not loaded") and prints out PN, SN, capacity, etc. Fio-attach won't work without the driver being loaded, which is the part I'm stuck at. With moving expenses coming up, the money would be more helpful than the drive.

If anyone is interested in this drive, I'll sell it for what I paid+shipping. I'm more than happy to provide the fio-status screenshot as well and will refund the purchase of the drive if it ends up being DOA or nonfunctional. I'd rather have someone on this thread who missed this sale use the drive rather than it sit dormant in my computer as it moves between storage boxes and states over the next year.

Feel free to DM me with interest or questions!
I found out more than I wanted to about these drives this last week. I had a fun time getting mine working as well.

If you check the firmware version it (should) say v8.9.1, which is the v4.2.1 drivers. You need to match up drivers to firmware version or update firmware. Being that they are Cisco drives you need one of their corp accounts to login and download the updated firmware. Or fiddle with the lenovo firmware/drivers that can be downloaded until you get something that works.
I got mine to work, but boot and shutdown take like two minutes, not sure if that's normal for them or it's just my "custom" firmware. Either way I don't reboot much so. Though if someone does have a Cisco account... Mind downloading an iso for me?

I did find out some other stuff about fio-config while dicking around:

use to speed up attach scanning (default 3100)
fio-config /dev/fct0 -p RMAP_MEMORY_LIMIT_MiB 16100
If true, use 1024 byte PCIe rx buffer. This improves performance but causes NMIs on some specific hardware.
fio-config /dev/fct0 -p USE_LARGE_PCIE_RX_BUFFER 1
Not sure if it'll make any difference, but
fio-config /dev/fct0 -p WIN_LOG_VERBOSE 0

Edit: Rated PBW: 22.00 PB, 97.67% remaining
 
Back
Top