Direction is in post #21 of this link
https://forums.servethehome.com/index.php?threads/sandisk-px600-cisco-pcie-ssd.24167/page-2
https://forums.servethehome.com/index.php?threads/sandisk-px600-cisco-pcie-ssd.24167/page-2
Direction is in post #21 of this link
https://forums.servethehome.com/index.php?threads/sandisk-px600-cisco-pcie-ssd.24167/page-2
[549172336]
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.6.1173
optromfile = uefi-3002_4.3.6.1173.rom
[5491-72336]
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.6.1173
optromfile = uefi-3002_4.3.6.1173.rom
Can you run fio-status -a? Does the card format? You can try to flash the official WD firmware if you haven't already, since the two are usually loosely tied to each other.I am not sure if I totally hosed the card I recently got or not. It is a PFIO1300MPS MLC Fusion io Memory PX (It looks like a px-600.) I updated the firmware and drivers and it resulted in the following for the fio-status:
Adapter: ioMono (driver 4.3.7)
Cisco UCS 1300GB MLC Fusion ioMemory PX, Product NumberFIO1300MPS, SN:1439G0105
ioMemory Adapter Controller, PNFIO1300MPS
Product UUID:61424ac0-43f2-5af7-9e33-0cab90ce207f
PCIe Power limit threshold: 74.75W
PCIe slot available power: unavailable
Connected ioMemory modules:
fct0: 83:00.0, Product NumberFIO1300MPS, SN:1439G0105
fct0 Status unknown: Driver is in MINIMAL MODE:
Device has a hardware failure
ioMemory Adapter Controller, Product NumberFIO1300MPS, SN:1439G0105
!! ---> There are active errors or warnings on this device! Read below for details.
ioMemory Adapter Controller, PNFIO1300MPS
Microcode Versions: App:0.0.30.0
Powerloss protection: not available
PCI:83:00.0
Vendor:1aed, Device:3002, Sub vendor:1137, Sub device:14f
Firmware v8.9.9, rev 20200113 Public
Geometry and capacity information not available.
Format: not low-level formatted
PCIe slot available power: 75.00W
PCIe negotiated link: 8 lanes at 5.0 Gt/sec each, 4000.00 MBytes/sec total
Internal temperature: 44.79 degC, max 45.77 degC
Internal voltage: avg 1.01V, max 1.01V
Aux voltage: avg 1.78V, max 1.79V
Rated PBW: 16.00 PB, 100.00% remaining
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.
Any suggestions would be appreciated, otherwise it looks like I have a new paperweight and conversation piece. lol.
The current code doesn't let you run both together due to a conflict in card enumeration in the corresponding drivers. We hope to fix it at some point, but PRs always welcome.I bought one of these for $77, which for 1.2 TB storage, is one hell of a deal. However, i also managed to score an SX 350 3.2 TB card.
I've been reading kinda contradictory info, reading that you cannot use an ioDrive with an ioMemory card at the same time, but the manual has vague references to a Unified driver.
Is it really true, than old gen 2 cards cannot work with the newer ones?
The problem is not the codebase at this point. We've cleaned it up pretty well so that merging them wouldn't be overly difficult. The problem lies that we don't have the source code for the hw driver, so we can't fix simple issues like naming conflicts, or missing symbols that were in the original vsl driver, but not in vsl4. If someone can get us that source code, we'd be a lot better off.The original plan was to be able to mix and match VSL 3.x and 4.x devices, but it never happened... too much code change.
You can pass one through to a VM and have both in the same host if you want though.
Yeah, that's where all the intellectual property lies... that isn't going to be opened up.The problem is not the codebase at this point. We've cleaned it up pretty well so that merging them wouldn't be overly difficult. The problem lies that we don't have the source code for the hw driver, so we can't fix simple issues like naming conflicts, or missing symbols that were in the original vsl driver, but not in vsl4. If someone can get us that source code, we'd be a lot better off.
VSL VERSION
FIRMWARE VERSION
FIRMWARE BUILD NUMBER
FIRMWARE FILENAME
1.2.6 3.0.0 36867 highiops_36867_1.fff
1.2.7 Â Â 3.0.0 36867 highiops_36867_1.fff
2.2.3 Â Â 5.0.6 101583 highiops_101583_6.fff
2.3.1 Â 5.0.7 101971 highiops_101971_4.fff
2.3.10 Â Â 5.0.7 107053 highiops_107053.fff
3.1.1 Â Â 6.0.2 108609 highiops_108609.fff
3.2.3 Â 7.1.13 109322 highiops_3.2.3-20130221.fff
3.2.6 Â Â 7.1.15 110356 highiops_3.2.6-20131003.fff
I wrote up a basic wiki for flashing cards, but for vsl4. snuf/iomemory-vsl4. Steps are mostly going to be same, but for the older cards you want to match all of the file versions in the original driver.Hi,
I'm trying to update an IBM branded Fusion io drive card, but can't find the proper ibm firwmare file to flash in, based on this matrix,
So far I am able to get the card working using a very old version; and was able to determine it is running firmware version 101583, which from my understanding I need to update to 101971, then 107053 and so on.Code:VSL VERSION FIRMWARE VERSION FIRMWARE BUILD NUMBER FIRMWARE FILENAME 1.2.6 3.0.0 36867 highiops_36867_1.fff 1.2.7 Â Â 3.0.0 36867 highiops_36867_1.fff 2.2.3 Â Â 5.0.6 101583 highiops_101583_6.fff 2.3.1 Â 5.0.7 101971 highiops_101971_4.fff 2.3.10 Â Â 5.0.7 107053 highiops_107053.fff 3.1.1 Â Â 6.0.2 108609 highiops_108609.fff 3.2.3 Â 7.1.13 109322 highiops_3.2.3-20130221.fff 3.2.6 Â Â 7.1.15 110356 highiops_3.2.6-20131003.fff
I was only able to find IBM firmware 2.3.1.0 [highiops_107053.fff] and 3.2.8-2 [highiops_3.2.8-20140508.fff]
IBM doesn't seem to have a 2.3.1, just a 2.3.1.0 which reports "Couldn't find the firmware in the FFF file for the device's part number" when I do fio-update-iodrive.
View attachment 14185
Using the wealth of information here, I was able to run fio-status -a reports two part numbers, neither I can find in the INFO file inside of fff (renamed to .zip)
PN: 00119200000 or PN:00214102104 (the 2nd number for the block device comes close to many matches, but none are exact, and it seems to be too many digits).
eg:
[002143004]
version = 5.0.7
file = mono39_ibm_107053.bin
format = bin
ecc = 39b
avrversion = 65793
avrfile = iomono_avr_65793.bin
View attachment 14186
I'm sort of stuck how to proceed further, as I don't want to guess, and brick the thing.
Here is the info extracted from the running UI:
View attachment 14187
Would anyone have the firmware files, so I can upgrade this sucker to the latest?
thanks for any advice.
Jonathan
He can't use VSL4 with a gen1 card though.I wrote up a basic wiki for flashing cards, but for vsl4. snuf/iomemory-vsl4. Steps are mostly going to be same, but for the older cards you want to match all of the file versions in the original driver.
Edit: make sure to grab the latest driver from github:
for 5.x linux kernels: snuf/iomemory-vsl
If you don't care about the data on the card, you can just jump to the latest driver/firmware combo (for vsl3) and do a fio-format on the card.Thanks so much everyone!
With the older card, can I flash directly to 3.2.16 firmware, using the firmware from Sandisks site? (Newest I see is 3.2.15 listed here SanDisk Dell Support | Store under ioDrive, Windows and 3.2.15-Dell ? Or I need to upgrade it in steps ?
Thanks for the link on the vsl4 flashing guide - I did find a link there for vsl3 will study the procedure a bit more!
Thanks again!
Jonathan
I realized he had a gen1 after I wrote up the wiki. The steps are pretty much the same though - the filenames are different, but same concept.He can't use VSL4 with a gen1 card though.
You may want to link the steps I put up, plus the driver/firmware compatibility table:I realized he had a gen1 after I wrote up the wiki. The steps are pretty much the same though - the filenames are different, but same concept.