OCZ Sandforce Firmware update 1.23 (Vertex2, Agility2, Vertex-LE, Vertex2 Pro, Vertex2-EX, Vertex2-E

Vimes

Vimes

Vimes

Soldato
Joined
15 Oct 2005
Posts
6,868
Location
Earth, for now
Hello

I have just updated my 1.11 firmware to the 1.23 from the link below for my Vertex 2 60GB drive and all went well...

http://www.ocztechnologyforum.com/f...-Vertex2-Pro-Vertex2-EX-Vertex2-E-Agility2-E)

I did ensure that I had a backup of the drive first, just in case, and I did it with the SSD as a slave from my previous build of Windows 7 by booting from my old drive.

There is a version of their OCZ toolbox to download...

http://www.ocztechnologyforum.com/f...ves.-(Agility2-Vertex2-Vertex2-Pro-Vertex-LE)
 
lol, 98MB firmware image. What the eck does it contain, the kitchen sink libraries :p

/edit - added the corrected changelog OCZ has now posted

Changelog

Changes/additions since version 1.11

• Added support for a new capacity point: usable size (raw capacity) 360GB (392GB)

Issues resolved since version 1.11

• Improved latency behavior. This change does not impact average latency but rather reduces worst case latency
• Modified IDENTIFY data to indicate that the SANITIZE feature set is supported.
• Modified temperature read data functionality.
• Added extra handling of parity errors for improved Soft Error handling
• Added threshold value for SMART attribute 177 (B1h)
• Fixed the output of the IDENTIFY DEVICE request to properly indicate if the SMART Feature Set is enabled or disabled.
• Enabled flash write protection whenever core voltage is turned off.
• Corrected rare case where SATA link could be dropped during a write operation
• Improved handling of aborted NCQ commands
• Fixed corner case hang condition by properly handling a host issued COMRESET during the last DWORD of an NCQ data commend.
• Modified command handling to give precedence to COMRESET in the case of COMRESET during another SATA error
• Fixed a panic condition by correctly cleaning up after an internal DMA transfer.
• Modified SSD Life Left calculations that were sometimes reading low on new drives
• Fixed an issue that occurred when two commands are waiting for each other to complete.
• Fixed FW to handle a RAISE RAM parity error without panic

Changes/additions since version 1.21

• None.

Issues resolved since version 1.21

• Mitigated the possibility of data loss to last 10 minutes of real time maximum when drive is used with Windows 7 OS, drive indexing, and very slow rate of writing and drive experiences an unsafe shutdown.
• Fixed a rare condition in which a drive could hang on a SLEEP command.

Known open issues:

• SMART command B0 occasionally returns incorrect status.
• Trim command response times are longer than desired.
• Can't write-same the whole drive.
• Resetting SMART PHY event counters has no effect.
• Whitmore Lake (Intel 3100) Chipset Compatibility.
• Drive may fail during power cycling test with rapid and short cycles.
• Compatibility issue during Red Hat 5.4 Linux boot on nVidia MCP55 chipset
• Sleep followed by non-data commands can sometimes cause the drive to fail to respond to the nondata command.

http://www.ocztechnologyforum.com/f...-E-Agility2-E)&p=566525&viewfull=1#post566525
Click to expand...
 
Last edited:
Fourstar said:
lol, 98MB firmware image. What the eck does it contain, the kitchen sink libraries :p

I wasn't aware there was v1.21. Maybe they meant v1.11?
Click to expand...

From what I have read in other posts on the forum some users bought their drive with a 1.22 firmware. Others asked when that would be released and it was suggested that the 1.22 version would not be made as a flash upgrade but a 1.23 one would. Hence, I assume, the posting of the 1.23 firmware.
 
Vimes said:
From what I have read in other posts on the forum some users bought their drive with a 1.22 firmware.
Click to expand...

Ah, I see.

Also, remember new nand support is added to old FW code, this is what has happened with 1.22....its basically the same file as 1.11.

http://www.ocztechnologyforum.com/f...-firmware-1.22&p=564102&viewfull=1#post564102
Click to expand...


As there are no references to 1.21 anywhere I'm going to assume OCZ made a typo in their changelog and it is actually for 1.11->1.23
 
Im running two ocz vertex 2's in raid 0, would i have to split up the raid to update or can i do them together.

oh and nice to see that the long awaited toolbox doesn't work with intel rst 10 drivers
 
Last edited:
Just updated mine successfully. This is on an i5 laptop with Intel RST version 9 drivers. Didn't follow the recommended slave method, but did it directly in Win7 x64. Was careful to take a backup though.
 
OCZ has posted an updated changelog with the changes from FW 1.11 -> 1.21.
Have updated my post above.

Looks like a worthwhile update for those of us on 1.11
 
Think I'll wait until it works with v10 of Intel's RST driver. (I'm guessing I would have to downgrade to v9 again to perform the Firmware update?).
 
For anyone thats interested, I updated the firmware with the OS running on it and can advise that you should do it with the drive installed a secondary drive, as recommended.

Got bluescreen after firmware was downloaded to drive, then after reset drive was not seen. Powered machine off, then on again and it came back up :O

They say the lazy man takes the most pain, I guess this confirms it haha
 
BlueScreen etc.

EXACT the same happened to me.. applied Firmware...

"Download Completed.... --> Bluescreen --> reboot.. no device found.....

I nearly died.. xD I thought there was a problem during the flashing process xD

then I powered off, took a big breath, powered my mashine on and there it was :-D

so.. don't be scared ;-)
 
The same thing just happened to me. I restarted and the SSD was back.

Does this mean that the firmware was not applied correctly ? Do I require to re-flash as a secondary drive?

SSDUpdate is showing that it is infact new firmware 1.23 ... does this men it installed ok?
 
Well, not wanting to temp fate, but just updated mine to 1.23, restarted and booted back up fine. No BSOD, no need to power down :S

Flashed the drive in Windows 7 on without using it as a secondary drive. Only thing however is that the drive shows as the 3rd device in the BIOS.
 
mod1fied said:
Well, not wanting to temp fate, but just updated mine to 1.23, restarted and booted back up fine. No BSOD, no need to power down :S

Flashed the drive in Windows 7 on without using it as a secondary drive. Only thing however is that the drive shows as the 3rd device in the BIOS.
Click to expand...


Lucky :)

I had the BSOD and had to flash it by booting with the Win7 32bit DVD and the flash utility on a USB drive. BIOS order shouldn't matter just depends which port you have it plugged into.
 
My 120GB Vertex shipped with 1.23 (bought from OCUK last week).

I still see the issue with Gigabyte boards where on boot it throws up a message about SMART failure. But I see no issues and it works flawlessly and I didn't do a full rebuild).
 
My Gigabyte board (P35c DS3R rev 2.0) produced a SMART error during boot which was resolved by a BIOS update.
 
You must log in or register to reply here.
Back
Top Bottom