SSD Write Endurance 25nm Vs 34nm

[bluestang]

Bravo

Well, then here is another one for you...

I deleted the static data form the M225, copied the original back over again to it and...wait for it...performed MD5 test again and...wait for it...it passed!

[Christopher]

Now that's dying gracefully!

That's the feel-good story of the day. You could probably use the drive for another couple years as a system drive and not even notice the almost 1PB of writes on it. Nothing would surprise me when it comes to the M225 Turbo.

[bluestang]

Now that's dying gracefully!

That's the feel-good story of the day. You could probably use the drive for another couple years as a system drive and not even notice the almost 1PB of writes on it. Nothing would surprise me when it comes to the M225 Turbo.

What are you talking about...I think I'm going to continue with endurance testing.

FWIW, it looks like I "only" lost data for 3 files: 2 FLAC (95.4MB and 93.8MB) and 1 MP3 (6.42MB) files.

[Christopher]

Good to hear that the rumors of the M225's demise were greatly exaggerated.

[Hopalong X]

M-225 "The Rise of the Phoenix"

[Anvil]

Kingston SSDNow 40GB (X25-V)

494.56TB Host writes
Reallocated sectors : 05 12
Available Reserved Space : E8 99

MD5 OK

33.88MiB/s on avg (~59 hours)

--

Corsair Force 3 120GB

01 90/50 (Raw read error rate)
05 2 (Retired Block count)
B1 50 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 413423 (Raw writes) ->404TiB
F1 550276 (Host writes) ->537TiB

MD5 OK

106.33MiB/s on avg (~58 hours)

power on hours : 1590

B1 is down again from 51 to 50.

--

@bluestang

Great to see that it's working again, maybe you should increase the frequency of MD5 checks, I do mine every 20 loops.

[bluestang]

@bluestang

Great to see that it's working again, maybe you should increase the frequency of MD5 checks, I do mine every 20 loops.

Thanks, will do. I let it run 50 loops before I left work and the MD5 check and everything was good. Speed was up a couple MB/s. I also ran a MD5 check on the static data after that and all was good as well.

I'll let it run all day while I'm at work tomorrow. But will stop it before I leave for the Holiday until I get back on Monday. Don't want to take any chance while I'm not there!

[devsk]

Thanks, will do. I let it run 50 loops before I left work and the MD5 check and everything was good. Speed was up a couple MB/s. I also ran a MD5 check on the static data after that and all was good as well.

I'll let it run all day while I'm at work tomorrow. But will stop it before I leave for the Holiday until I get back on Monday. Don't want to take any chance while I'm not there!

This is after a D-flash Or you gave up on that? I think a D-flash will help this turbo past the 1PB mark. But definitely a feel good story of the day. M225 rises from the heap of bad clusters...

[bluestang]

M225->Vertex Turbo 64GB Update:

Ok, So I picked up on running the Endurance test again this morning. I changed ASU to run MD5 on my 1.59GB every 20 loops instead of 50 per Anvil's suggestion. I ran 101 loops and ASU MD5 checks were all good. I then ran a MD5 checksum on my 32.6GB static data after and that was good as well. Added C5-Read Failure Block Count (uncorrectable bit errors) to the mix as well.

825.41 TiB (907.55 TB) total
2123 hrs (Torture), 2970 hrs (Power-On)
16108 Raw Wear
118.94 MB/s avg for the last 3.36 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count (Realloc Sectors) at 17.
C5-Read Failure Block Count (uncorrectable bit errors) at 5.
1=Bnk 6/Blk 2406 - Erase Failure
2=Bnk 3/Blk 3925 - Erase Failure
3=Bnk 0/Blk 1766 - Erase Failure
4=Bnk 0/Blk 829 - Erase Failure
5=Bnk 4/Blk 3191 - Erase Failure
6=Bnk 7/Blk 937 - Erase Failure
7=Bnk 7/Blk 1980 - Erase Failure
8=Bnk 7/Blk 442 - Erase Failure
9=Bnk 7/Blk 700 - Erase Failure
10=Bnk 2/Blk 1066 - Erase Failure
11=Bnk 7/Blck 85 - Erase Failure
12=Bnk 4/Blk 3192 - Erase Failure
13=Bnk 7/Blk 280 - Erase Failure
14=Bnk 3/Blk 2375 - Erase Failure
15=Bnk 7/Blk 768 - Erase Failure
16=Bnk 7/Blk 765 - Erase Failure
17=Bnk 7/Blk 182 - Erase Failure
18=Bnk 5/Blk 939 - Read Failure
19=Bnk 5/Blk 1115 - Read Failure
20=Bnk 5/Blk 1011 - Read Failure
21=Bnk 7/Blk 3549 - Read Failure
22=Bnk 7/Blk 3556 - Read Failure



Happy Turkey Day!!!

[Anvil]

Kingston SSDNow 40GB (X25-V)

497.04TB Host writes
Reallocated sectors : 05 12
Available Reserved Space : E8 99

MD5 OK

33.59MiB/s on avg (~80 hours)

--

Corsair Force 3 120GB

01 89/50 (Raw read error rate)
05 2 (Retired Block count)
B1 48 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 419604 (Raw writes) ->410TiB
F1 558504 (Host writes) ->545TiB

MD5 OK

106.34MiB/s on avg (~80 hours)

power on hours : 1612

B1 is down from 50 to 48.

[Anvil]

Kingston SSDNow 40GB (X25-V)

498.57TB Host writes
Reallocated sectors : 05 12
Available Reserved Space : E8 99

MD5 OK

33.47MiB/s on avg (~94 hours)

--

Corsair Force 3 120GB

01 90/50 (Raw read error rate)
05 2 (Retired Block count)
B1 47 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 423422 (Raw writes) ->413TiB
F1 563583 (Host writes) ->550TiB

MD5 OK

106.35MiB/s on avg (~94 hours)

power on hours : 1625

B1 is down from 48 to 47.

[Christopher]

Anvil,

I've been looking at the Force 3's 01 value, and while it jumps around quite a bit, overall it still seems pretty low. If the Micron AAA nand is actually better quality NAND than the Toshiba, maybe you'll get quite a bit more mileage out of the F3. The Toshiba toggle nand is faster, but perhaps not necessarily better.

Of course, writing slower than the Mushkin and having twice the flash helps too.

Doesn't the Intel 320s use async nand?

[bulanula]

More proof that the 50nm NAND in the Indilinx is ideal. The controller ain't that sucky in regards to WA either. Great job !

I am still skeptical of 25nm NAND and all the controller magic that is inside the new controllers. Anybody care to offer a C300 so I can see if I am right etc. ? Thanks !

[Anvil]

Kingston SSDNow 40GB (X25-V)

It just got past 500TB

500.20TB Host writes
Reallocated sectors : 05 12
Available Reserved Space : E8 99

MD5 OK

36.53MiB/s on avg (~13 hours)

--

Corsair Force 3 120GB

01 90/50 (Raw read error rate)
05 2 (Retired Block count)
B1 46 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 427093 (Raw writes) ->417TiB
F1 568470 (Host writes) ->555TiB

MD5 OK

106.35MiB/s on avg (~107 hours)

power on hours : 1638

B1 is down from 47 to 46.

--

@Christopher

01 looks to be uneventful so far on the F3, I'm not seeing anything useful so far.

I pretty sure the Intel 320 is using synch NAND, it was noted in one of the posts from either One_Hertz or Ao1.

[devsk]

More proof that the 50nm NAND in the Indilinx is ideal. The controller ain't that sucky in regards to WA either. Great job !

I am still skeptical of 25nm NAND and all the controller magic that is inside the new controllers. Anybody care to offer a C300 so I can see if I am right etc. ? Thanks !

Get one for yourself and figure it out! As easy as that! I think if you work nights at McDonalds, you will be good to report here in a couple of months....

[Anvil]

Kingston SSDNow 40GB (X25-V)

501.52TB Host writes
Reallocated sectors : 05 12
Available Reserved Space : E8 99

MD5 OK

34.79MiB/s on avg (~24 hours)

--

Corsair Force 3 120GB

01 86/50 (Raw read error rate)
05 2 (Retired Block count)
B1 47 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 430362 (Raw writes) ->420TiB
F1 572821 (Host writes) ->559TiB

MD5 OK

106.36MiB/s on avg (~118 hours)

power on hours : 1650

B1 has stopped decreasing and is up 1 from 46 to 47.

[Anvil]

Kingston SSDNow 40GB (X25-V)

510.19TB Host writes
Reallocated sectors : 05 12
Available Reserved Space : E8 99

MD5 OK

33.12MiB/s on avg (~101 hours)

--

Corsair Force 3 120GB

01 94/50 (Raw read error rate)
05 2 (Retired Block count)
B1 57 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 452101 (Raw writes) ->442TiB
F1 601748 (Host writes) ->588TiB

MD5 OK

106.37MiB/s on avg (~195 hours)

power on hours : 1727

B1 has jumped from 47 to 57 during the weekend.

[bluestang]

M225->Vertex Turbo 64GB Update:

Took the long weekend off and back to work now...

829.55 TiB (912.09 TB) total
2133 hrs (Torture), 3093 hrs (Power-On)
16183 Raw Wear
117.69 MB/s avg for the last 6.70 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count (Realloc Sectors) at 17.
C5-Read Failure Block Count (uncorrectable bit errors) at 5.
1=Bnk 6/Blk 2406 - Erase Failure
2=Bnk 3/Blk 3925 - Erase Failure
3=Bnk 0/Blk 1766 - Erase Failure
4=Bnk 0/Blk 829 - Erase Failure
5=Bnk 4/Blk 3191 - Erase Failure
6=Bnk 7/Blk 937 - Erase Failure
7=Bnk 7/Blk 1980 - Erase Failure
8=Bnk 7/Blk 442 - Erase Failure
9=Bnk 7/Blk 700 - Erase Failure
10=Bnk 2/Blk 1066 - Erase Failure
11=Bnk 7/Blck 85 - Erase Failure
12=Bnk 4/Blk 3192 - Erase Failure
13=Bnk 7/Blk 280 - Erase Failure
14=Bnk 3/Blk 2375 - Erase Failure
15=Bnk 7/Blk 768 - Erase Failure
16=Bnk 7/Blk 765 - Erase Failure
17=Bnk 7/Blk 182 - Erase Failure
18=Bnk 5/Blk 939 - Read Failure
19=Bnk 5/Blk 1115 - Read Failure
20=Bnk 5/Blk 1011 - Read Failure
21=Bnk 7/Blk 3549 - Read Failure
22=Bnk 7/Blk 3556 - Read Failure

[devsk]

M225->Vertex Turbo 64GB Update:

829.55 TiB (912.09 TB) total

We are getting close.... Just hang in there!

[Anvil]

Kingston SSDNow 40GB (X25-V)

512.29TB Host writes
Reallocated sectors : 05 12
Available Reserved Space : E8 99

MD5 OK

33.03MiB/s on avg (~120 hours)

--

Corsair Force 3 120GB

01 85/50 (Raw read error rate)
05 2 (Retired Block count)
B1 56 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 457389 (Raw writes) ->447TiB
F1 608784 (Host writes) ->595TiB

MD5 OK

106.37MiB/s on avg (~214 hours)

power on hours : 1746

B1 is down from last reading, from 57 to 56.

As the F3 is about to turn 600TiB I'll do another data retention test tonight, most likely on both drives.

[Computurd]

holy crap, cant believe that ol turbo is still turboing great to see things moving forward, man that intel is just durable as heck for the price as well

[bluestang]

M225->Vertex Turbo 64GB Update:

I thought I'd be brave and let it run overnight for the first time since "The Incident".

836.63 TiB (919.89 TB) total
~2149 hrs (Torture), 3112 hrs (Power-On)
16312 Raw Wear
116.79 MB/s avg for the last 17.57 hours (on W7 x64)
MD5 every 20 loops on 1.59GB file = OK
C4-Erase Failure Block Count (Realloc Sectors) from 17 to 18.
C5-Read Failure Block Count (uncorrectable bit errors) at 5.
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

[Christopher]

The M225 needs to go directly to the SSD hall of fame when it's work is done.

I broke out my Turbo 128GB in celebration of the M225 Turbo's resurrection, and kinda wish I had bought a second one instead of the Vertex LE100 (which, despite being pretty good, is no Turbo).

M225 "Turbo" =

[B.A.T]

Finally an update
I'm an a work trip but with only edge coverage on my cellphone I had trouble using teamviewer and surfing all to gether.
My Kingston has dropped out again. I tried a reboot but it still didn't come back. I'm home on friday and I'll try some more. And probably my rig had an reboot or something because ASU had stopped. It's up running again but there have been very little writing the last week.
Here are the current numbers from my Intel G1

Intel X25-M G1 80GB
76,0071 TiB
19251 hours
Reallocated sectors : 00
MWI=92 to 92
MD5 =OK
50.57 MiB/s on avg

[minpayne]

Can you guys continue the tests on the "dead" M4? Is it possible to use the official firmware update iso image burnt to disc to boot the computer and recognise the disk at all? When I accidentally deleted the firmware on my M4, I was able to force a re-write of the firmware to my M4 after a power cycling fix. I remember the parameter was -a to delete the firmware, then I power cycled it, and used parameter -u to force re-writing the firmware.

However I'd like to see another type of test, i.e. does the nand flash show significant volatility, once the MWI is exhausted? I'd like to have several SSDs of different brands/models to reach the MWI threshold then left powered off for a week or so and see if the contents are lost. By this we can know whether the "MWI Lasted" is indeed the best value to calculate the endurance.