10-18-2012 11:27 AM - edited 10-18-2012 12:05 PM
Download and ins tall the SanDisk SSD toolkit. Once installed you can use the update tab to update the firmware of your SSD. For instructions see the SSD toolkit help file.
New changes since version R211:
10-18-2012 03:32 PM
I've not followed the specifics of the problems w/ TRIM support. By installing R211, will any uncollected garbage and other errors from R201 be automatically resolved? Or do I need to do a secure erase and restore from a backup to realize all of the fixes in R211?
10-18-2012 04:15 PM
From what I understood, TRIM was still working, but the controller was just not as fast as before to clean the trimmed cells.
So it should be all right. Just upgrade as I did, no issue.
10-19-2012 04:28 AM
I was able to upgrade with no issues so far. I have 3 SSDs of different brands (SanDisk, Patriot, Corsair) and each is updated differently. SanDisk required a reboot into Linux while at least one of the others allowed the update directly from Win 7.
10-19-2012 06:16 AM
Updating in windows is not as reliable as with a bootable disc. Windows can have different drivers, and all version of windows, this can affect the success of the update.
10-19-2012 07:13 AM
Yet, They work fine from windows with very few reported issues.
Correct answer is... Making a linux boot disk is the least path of resistance when it comes to cost and time...
Those other brands like Intel and Samsung also have beautiful Windows based tools that do so much more than show smart info amd make a boot disk... that requires hiring windows programmers and expensive development...
10-19-2012 09:52 PM
Yet another great firmware update from SanDisk. That makes it sound like there are many, no, only two.
There is something that I must mention that I have never before seen work correctly in a FW update for a SSD. While I was preparing the update, I remembered that my SanDisk EX 120GB SSD was connected to the Marvell 9128 SATA III chipset, not my boards standard Intel SATA chipset. No other SSD FW update I have performed (I have done many) would work or even detect the target SSD when connected to a secondary SATA controller. I am also using the standard Marvell AHCI driver (latest version) on the Marvell chipset.
My first reaction was, "Oh great, I need to change the EX SSD to the Intel SATA ports". But then I thought I would see what happens with the SSD on the Marvell controller, so I booted into the update tool. Sure enough, the tool detected and chose the EX SSD. I proceeded with the FW update, and it seemed to finish fine. The PC shutdown when I exited the tool, and I booted into Windows. I checked the firmware on the EX SSD, R211 was installed. The FW update worked perfectly on the Marvell SATA controller and driver pair.
I'm impressed that SanDisk was able to have their FW update tool work on the secondary SATA controller. Any other FW update tool requires the SSD to be connected to the primary SATA controller. IMO, this indicates the high quality of SanDisk's work. Great job programmers, and everyone involved with this update!
10-19-2012 10:27 PM
Very difficult to know what affect the earlier (SandForce sourced) firmware TRIM problem had on the deleted files on your SSD.
Let's assume that some of them were not cleaned up. The new firmware will be unaware of the deleted files, and WIndows 7 only sends a TRIM command for a deleted file once. Those deleted files will eventually be cleaned up by garbage collection, and it is not a big disaster to have a few files in that state on a SSD.
Still, we don't know how bad this issue affected a normally used SSD. The "torture tests" used to detect the TRIM bug are nothing like the way a SSD is typically used. The tests would fill the SSD completely with data files, and then delete some of them, and write and delete them again over and over continually, keeping the SSD filled to capacity. Then the SSD would be formatted, deleting all the files, which will trigger TRIM commands to be sent to the SSD for all the files. Benchmark tests were compared before and after the torture tests, and showed that performance was not immediately restored.
If you want a clean start, a SE and restore from a backup would be the best way to go. But without doing that, you will have all the benefits the new FW has as soon as it is installed. TRIM simply works better now, but the firmware cannot make up for mistakes of the past.