SSD Write Endurance 25nm Vs 34nm

[bluestang]

M225->Vertex Turbo 64GB Update:

Soooo, I started the test back up this morning after letting it sit idle over the weekend...It ran for 104 loops/3.63 hrs at 117.61 MB/s and C5 jumped from 7 to 15 in that time. MD5 in ASU still showed OK. Stopped test as I needed to reboot after an update and afterwards drive was unresponsive, but still showed up in BIOS and OS. Mulitiple attempts of unplugging/powering off did not help this time. So, I was forced to do a full format and lost ~2 TiB of logging from ASU (I have ASU data from Friday though). I now have to re-copy static data over and start test back up, but here is a minor update...

868.82 TiB (955.28 TB) total.
~2224 hrs (Torture), 3257 hrs (Power-On).
16896 Raw Wear.
117.61 MB/s avg for the last 3.63 hours (on W7 x64).
MD5 every 20 loops on 1.59GB file = OK.
C4-Erase Failure Block Count (Realloc Sectors) at 24.
C5-Read Failure Block Count (uncorrectable bit errors) from 7 to 15.
1=Bnk 6/Blk 2406 - Erase Failure C4
2=Bnk 3/Blk 3925 - Erase Failure C4
3=Bnk 0/Blk 1766 - Erase Failure C4
4=Bnk 0/Blk 829 - Erase Failure C4
5=Bnk 4/Blk 3191 - Erase Failure C4
6=Bnk 7/Blk 937 - Erase Failure C4
7=Bnk 7/Blk 1980 - Erase Failure C4
8=Bnk 7/Blk 442 - Erase Failure C4
9=Bnk 7/Blk 700 - Erase Failure C4
10=Bnk 2/Blk 1066 - Erase Failure C4
11=Bnk 7/Blck 85 - Erase Failure C4
12=Bnk 4/Blk 3192 - Erase Failure C4
13=Bnk 7/Blk 280 - Erase Failure C4
14=Bnk 3/Blk 2375 - Erase Failure C4
15=Bnk 7/Blk 768 - Erase Failure C4
16=Bnk 7/Blk 765 - Erase Failure C4
17=Bnk 7/Blk 182 - Erase Failure C4
18=Bnk 5/Blk 939 - Read Failure C5
19=Bnk 5/Blk 1115 - Read Failure C5
20=Bnk 5/Blk 1011 - Read Failure C5
21=Bnk 7/Blk 3549 - Read Failure C5
22=Bnk 7/Blk 3556 - Read Failure C5
23=Bnk 4/Blk 1961 - Erase Failure C4
24=Bnk 7/Blk 1862 - Erase Failure C4
25=Bnk 7/Blk 111 - Erase Failure C4
26=Bnk 5/Blk 902 - Read Failure C5
27=Bnk 7/Blk 560 - Erase Failure C4
28=Bnk 7/Blk 827 - Erase Failure C4
29=Bnk 6/Blk 482 - Erase Failure C4
30=Bnk 5/Blk 167 - Read Failure C5
31=Bnk 7/Blk 1771 - Erase Failure C4
32=Bnk 5/Blk 956 - Read Failure C5
33=Bnk 5/Blk 1242 - Read Failure C5
34=Bnk 5/Blk 1461 - Read Failure C5
35=Bnk 5/Blk 1800 - Read Failure C5
36=Bnk 5/Blk 1030 - Read Failure C5
37=Bnk 5/Blk 1074 - Read Failure C5
38=Bnk 5/Blk 1128 - Read Failure C5
39=Bnk 5/Blk 1427 - Read Failure C5

So a total (B8+C3+C4+C5) of 49 Bad Blocks out of 32768.

[Anvil]

M225->Vertex Turbo 64GB Update:

Soooo, I started the test back up this morning after letting it sit idle over the weekend...It ran for 104 loops/3.63 hrs at 117.61 MB/s and C5 jumped from 7 to 15 in that time. MD5 in ASU still showed OK. Stopped test as I needed to reboot after an update and afterwards drive was unresponsive, but still showed up in BIOS and OS. Mulitiple attempts of unplugging/powering off did not help this time. So, I was forced to do a full format and lost ~2 TiB of logging from ASU (I have ASU data from Friday though).
...
868.82 TiB (955.28 TB) total.
~2224 hrs (Torture), 3257 hrs (Power-On).
...

As long as SMART is working and you've got the total there really is no problem, let's hope that it doesn't happen again

[bluestang]

As long as SMART is working and you've got the total there really is no problem, let's hope that it doesn't happen again

Just logged in to my work PC and checked on it... 958 TB and going!
Bad block counts haven't moved since last update...Let's hope I didn't just jinx it!!