@barrybgb wrote:
I am certainly glad this came out. Better late than never.
Pretty sad that Sandisk had no comment while we all were ranting about any information.
I just downloaded the firmware but will wait until I get home so i can do a full backup on my work Leveno T410 laptop. I have a 480G in this one.
I also have 2x 240G at home sitting on the shelf. I wanted to make a Raid 0 with them until I found about the Trim issue.
All three of the drives came with R201 and I thought at the time I was good to go.
What a huge dissapointment.
I wanted to replace my 2x Vertex4 in Raid 0 at home with the Extreme 240G’s but have been waiting patiently for the update.
When I get home, I will image the drive, secure erase, do the update, then re-image and retest.
Here are the scores for the 480G now. I did one for each partition.
480G Partition C
Pretty sad 4K results indeed.
480G Partition D
AS SSD Partition C
Pretty sad benchmarks here, don’t you agree? I don’t have the original benchmark I did when I first got this drive but I know it was much better than this.
It took awhile to figure out how to upload images here.
As soon as I update the drive, I will post new benchmarks.
(BTW, I don’t think I will be buying Sandisk anytime soon after this fiasco on their part.)
Is there a reason all my images disappeared? Is there a size limit and what is the limit?
Wierd? One minute they are gone and the next they return. Gremlins.
Clearly a SATA II laptop, and add the fact that it is a laptop, with all its power saving options enabled, and you certainly do not have a benchmarking power house.Quite normal results for those circumstances. You’re also using msahci, not a high performance driver.
You did not use your other SanDisk EX SSDs in RAID 0 because of the TRIM bug? TRIM in RAID 0 is ONLY supported on Intel 7 series chipsets (except X79), with an IRST Option ROM of 11.0 or above (depends on your mother board’s UEFI/BIOS installing it) and an IRST driver of 11.0 or above. I’ve used SSDs in RAID 0 on systems with no TRIM for years, they work just fine, no performance loss at all. Of course, I use them normally, not the torture tests needed to show TRIM is not working.
Sigh, fiasco on SanDisk’s part? ALL SSD manufactures that used the 5.0 SandForce firmware had the partially working TRIM. FW 5.0 was a new/rewrite of the 3.x firmware, with improved performance, but alas, the TRIM bug. Now while we don’t know if SanDisk used SandForce 5.03, or 5.04, the 5.03 firmware was a step backwards in some respects, since it is a mix of 5.0 and 3.x FW, for a quick fix of the TRIM bug using 3.x code. FW 5.04 is the true, full 5.0 FW, with a true TRIM fix. That took longer to produce, and is likely why SanDisk’s “delay” in providing an update occurred, they are probably using 5.04.
No SSD manufacture sets release dates on FW, they release it when it’s ready. If they do set a date, that’s because it is done and they decide to say it’s ready next week, for example.