SSD Write Endurance 25nm Vs 34nm

Intel 330 120GB

256.17TB Host writes
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 71
[F1] Total LBAs Written 8394035
[F2] Total LBAs Read 31991 // looks OK
[F9] Total NAND Writes 184903GB
POH 655
MD5 OK

123.44MiB/s on avg (~28 hours)

--

Kingston SSDNow 40GB (X25-V)

1049.03TB Host writes (34374762*32)
Reallocated sectors : 05 48
Available Reserved Space : E8 99
POH 9385
MD5 OK

33.21MiB/s on avg (~23 hours)

--

Some of the drives aren't up to date. (just a few days off)

Attachment 127749

Make sure to download the new build, it no longer allows the MD5 testfile to be cached.


Download link

Samsung 830 256GB Day 92

(GiB) 2,278,395.09
(TiB) 2 224.99

(Avg) 294,47MB/s

(B1) Wear Leveling Count: 9886

(B6) Erase Fail Count: 7
(05) Reallocated Sectors: 28672
(POH) 2248

Plextor M3P 128GB Day 22

(GiB) 582,785.07
(TiB) 568.12

(Avg) 276.03 MB/s
(POH) 599

-------------------------------------------------------

Intel 330 120GB

260.43TB Host writes
1010GiB Host reads
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 71
[F1] Total LBAs Written 8533905
[F2] Total LBAs Read 32332 // looks OK
[F9] Total NAND Writes 187990GB
POH 665
MD5 OK

123.59MiB/s on avg (~38 hours)

--

Kingston SSDNow 40GB (X25-V)

1050.18TB Host writes (34412198*32)
Reallocated sectors : 05 48
Available Reserved Space : E8 99
POH 9395
MD5 OK

33.19MiB/s on avg (~33 hours)

--

I've upgraded one of my instances of ASU .... the new version does not seem to be helping WRT actually reading the MD5 off disk

Quote:

---

Originally Posted by canthearu

We have another kingston here :P

But seriously, these Mtron drives are proving to be seriously unreliable/fragile. Just highlights the importance of firmware quality.

SLC + bad firmware = still a bad drive

---

It feels very much like the Kingston V+100. It's dropping out every 2-3 day but luckily for me the high WA burns through P/E.

Todays update:
I've been a little busy with visitors from my family the last couple of day. Here are fresh numbers :up:

m4
1075.7994 TiB
4514 hours
Avg speed 73.59 MiB/s.
AD gone from 6 to 255 to 251
P/E 18536.
CE 58
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=495207

Intel X25-M G1 80GB
724.83 TiB
23805 hours
Reallocated sectors : 172 to 200
Available Reserved space: 74 to 73
MWI= 42
MD5 =OK
39.97 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=495205

Intel X25-E 64GB
320.06 TiB
986-30=956 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI= 98 to 97
MD5 =OK
90.96 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=495211

Mtron Pro 7025 32GB
ASU write 56.1501 TiB
Host write 104,79630 TiB
Total host write 152,3318 TiB
Day 18
MWI= 96 to 95
MD5 =OK
47.79 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=495209

The Mtron has dropped out 1 time tha last 3 days. The rest is ok and running fine.

Quote:

---

Originally Posted by canthearu

I've upgraded one of my instances of ASU .... the new version does not seem to be helping WRT actually reading the MD5 off disk

---

Hmmm

You should update all instances of the app. (as the old app could leave a copy of the source-file in the buffer)
Is the source file located on the same drive as is being tested?
Is there some AV that could interfere? (by scanning the file and leaving it in the buffer, if so, disable scanning on MD5 extensions or the TEST folder)

I'll have another look but there should be no reason to the file being buffered.

There will be an update one of these days as generating the checksum has been optimized. (a bit faster)

Samsung 830 256GB Day 93

(GiB) 2,304,864.77
(TiB) 2,250.83

(Avg) 294.68MB/s

(B1) Wear Leveling Count: 10 000

(B6) Erase Fail Count: 7
(05) Reallocated Sectors: 28672
(POH) 2273

Plextor M3P 128GB Day 23

(GiB) 607,939.62
(TiB) 593.69

(Avg) 276.41 MB/s
(POH) 624

-------------------------------------------------------

Quote:

---

Originally Posted by Anvil

Hmmm

You should update all instances of the app. (as the old app could leave a copy of the source-file in the buffer)
Is the source file located on the same drive as is being tested?
Is there some AV that could interfere? (by scanning the file and leaving it in the buffer, if so, disable scanning on MD5 extensions or the TEST folder)

I'll have another look but there should be no reason to the file being buffered.

There will be an update one of these days as generating the checksum has been optimized. (a bit faster)

---

Ah, moving the source file to another drive has fixed the md5 testing :)

I will post an update in a few hours ... let speeds somewhat stabalize again.!

Intel 520 60GB - Day 117

Drive hours: 2,753
ASU GiB written: 878,292.56 GiB (857.70 TiB)
Avg MB/s: 93.37 MB/s (3 hours)
MD5: OK (verified off disk now)

Host GB written (F1): 884,428.22 GiB (863.70 TiB, 28301703 raw)
NAND writes (F9): 626,106 GiB (611.43 TiB)

Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 116 normalized
Available Reserved Space (AA): 100 normalized
Media Wearout Indicator (E9): 1

Sandisk Extreme G25 - 120gb - Day 17

Drive hours: 408
ASU GiB written: 173,413.05 GiB (169.35 TiB)
Avg MB/s: 123.36 MB/s (3 hours)
MD5: OK (verified off disk now)

Host GB written (F1): 174,517 GiB (170.43 TiB)
NAND writes (E9): 130,157 GiB (127.11 TiB)

Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 116 normalized
Media Wearout Indicator (E7): 67 normalized
Wear Range Delta (B1): 4 raw
Reported Uncorrectable Errors (BB): 0 raw

Edit: The Sandisk extreme MWI value seems to be tracking very close to the MWI on the Corsair Force 3. The sandisk seems to be controlling wear range delta much better though ... which could be an advantage at endgame!

http://www.xtremesystems.org/forums/...=1#post4967340

Quote:

---

Originally Posted by canthearu

Ah, moving the source file to another drive has fixed the md5 testing :)

I will post an update in a few hours ... let speeds somewhat stabalize again.!

---

Thanks for letting me know!

It should work even if the file is on the same drive, it will just not copy the file.
Give it another shot with the new build. (should be available this weekend, most likely Sunday)

--

Intel 330 120GB

274.10TB Host writes
1.02TiB Host reads
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 69
[F1] Total LBAs Written 8981645
[F2] Total LBAs Read 32467
[F9] Total NAND Writes 197849GB
POH 697
MD5 OK

123.55MiB/s on avg (~70 hours)

--

Kingston SSDNow 40GB (X25-V)

1053.85TB Host writes (34532729*32)
Reallocated sectors : 05 48
Available Reserved Space : E8 99
POH 9427
MD5 OK

33.18MiB/s on avg (~65 hours)

--

Attachment 127784

And again, the Samsung goes through the roof.

Both the 830 and M3P are, inexplicably, slightly faster. Not on average (those are higher too) but instantaneous speeds are faster. Crazy.

The Intel 520 is dead at day 118

Drive just panic locked without warning at 9:43am on the 23/6/2012. Attempts to resurrect it by plugging it into other computers have failed.

Final Stats:

Drive hours: 2,765
Host GB written (F1): 888,488.78 GiB (867.66 TiB, 28431641 raw)
NAND writes (F9): 628,987 GiB (614.25 TiB)

Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 116 normalized
Available Reserved Space (AA): 100 normalized
Media Wearout Indicator (E9): 1

While I did expect a bit more from the Intel 520, I guess this isn't a terrible result.

Damn...I had hoped it'd join the 1PB club. :rolleyes:

I'd be nice if Intel could analyze the corpse and see why the controller choked. It sure wasn't the nand...lol

Damn, canthearu, that's unfortuanate. And disappointing. You'd think this being the number one cause of death, more manufacturer resources would be devoted to making sure it doesn't happen.

----------------------------------------------------
Samsung 830 256GB Day 96

(GiB) 2,349,189.01
(TiB) 2 294.13

(Avg) 295.06 MB/s

(B1) Wear Leveling Count: 10,192

(B6) Erase Fail Count: 7
(05) Reallocated Sectors: 28672
(POH) 2316

Plextor M3P 128GB Day 25

(GiB) 649,620.10
(TiB) 634.39

(Avg) 276.74 MB/s
(POH) 666

-------------------------------------------------------
Averages are still gradually creeping higher.

Quote:

---

Originally Posted by Christopher

Both the 830 and M3P are, inexplicably, slightly faster. Not on average (those are higher too) but instantaneous speeds are faster. Crazy.

---

I have seen other M3P get faster as they get some wear on them, might be just now getting broke in

The speed increase from "break in" isn't probably what you're seeing with the M3P. You have to put a lot of wear on a drive before it's NAND's characteristics start to change, several thousand PE cycles. However, some drives also tune for workload. While it's uncommon with consumer drives, enterprise drives do this frequently.

Intel 330 120GB

292.06TB Host writes
1.07TiB Host reads
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 67
[F1] Total LBAs Written 9570306
[F2] Total LBAs Read 34942
[F9] Total NAND Writes 210815GB
POH 739
MD5 OK

123.57MiB/s on avg (~112 hours)

--

Kingston SSDNow 40GB (X25-V)

1058.69TB Host writes (34691177*32)
Reallocated sectors : 05 48
Available Reserved Space : E8 99
POH 9469
MD5 OK

33.16MiB/s on avg (~107 hours)

--

B.A.T updated on the Norwegian site so the figures are more or less up to date.

Attachment 127820

Attachment 127821


The 520 did fine, I did expect some kind of warning though, a few disconnects or some other sign.
Well, it sets the bar for my 330, 2x of the 520 is acceptable.
The Force 3 had async NAND and a poor firmware, I believe the Force 3 would have done better if there was a solid fw from the start.

Samsung 830 256GB Day 97

(GiB) 2,366,892.23
(TiB) 2 311.42

(Avg) 294.86 MB/s

(B1) Wear Leveling Count: 10,269

(B6) Erase Fail Count: 7
(05) Reallocated Sectors: 28672
(POH) 2334

Plextor M3P 128GB Day 26

(GiB) 666,775.26
(TiB) 651.15

(Avg) 276.90MB/s
(POH) 684

-------------------------------------------------------

R.I.P Intel 520. A little early to die at only 600TiB of nand write.

Since XS was down last time I updated I'll just skip to the latest numbers.

Todays update:
m4
1095.5206 TiB
4592 hours
Avg speed 73.65 MiB/s.
AD 251 to 239
P/E 18871.
C3 3323
CE 58
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=495483

Intel X25-M G1 80GB
735.32 TiB
23883 hours
Reallocated sectors : 200 to 231
Available Reserved space: 73 to 70
MWI= 42 to 20
MD5 =OK
39.62 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=495482

Intel X25-E 64GB
344.34 TiB
1064-30=1034 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI= 97
MD5 =OK
90.98 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=495484

ASU write 64.6592 TiB
Host write 121,0753 TiB
Total host write 168,6109 TiB
Day 21
MWI= 95
MD5 =OK
46.63 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=495485

The Mtron has dropped out one time this morning but is OK now. The G1 is still losing reserve space but still looks strong. I also noted that CDI latest ver has added some information on the m4.
C3 has gone from unknown to Cumulative Corrected ECC and will help us to know the status of the nand. Looking back this value started increasing at 500 TiB but had the largest increase after the last retention test.

Both drives are just a little faster
Attachment 127845

Attachment 127846

Intel 330 120GB

301.50TB Host writes
1.28TiB Host reads
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 66
[F1] Total LBAs Written 9879456
[F2] Total LBAs Read 41807
[F9] Total NAND Writes 217629GB
POH 761
MD5 OK

123.75MiB/s on avg (~12 hours)

--

Kingston SSDNow 40GB (X25-V)

1061.34TB Host writes (34778194*32)
Reallocated sectors : 05 48
Available Reserved Space : E8 99
POH 9492
MD5 OK

36.49MiB/s on avg (~12 hours)

Sandisk Extreme G25 - 120gb - Day 20

Drive hours: 478
ASU GiB written: 203,794.93 GiB (199.02 TiB)
Avg MB/s: 122.44 MB/s (56.11 hours)
MD5: OK (verified off disk now)

Host GB written (F1): 205,050 GiB (200.24 TiB)
NAND writes (E9): 152,940 GiB (149.36 TiB)

Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 112 normalized
Media Wearout Indicator (E7): 61 normalized
Wear Range Delta (B1): 4 raw
Reported Uncorrectable Errors (BB): 0 raw

Todays update:

m4
1101.3860 TiB
4615 hours
Avg speed 74.21 MiB/s.
AD 239 to 236
P/E 18970.
C3 3323
CE 58
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=495584

Intel X25-M G1 80GB
738.09 TiB
23906hours
Reallocated sectors : 231 to 255 to 86
Available Reserved space: 70 to 63
MWI= 20
MD5 =OK
34.81 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=495583

Intel X25-E 64GB
351.83TiB
1087-30=1057 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI= 97
MD5 =OK
91.80 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=495585

Mtron Pro 7025 32GB
ASU write 67.3465 TiB
Host write 126,2116 TiB
Total host write 173,7471 TiB
Day 22
MWI= 95
MD5 =OK
48.03 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=495586

The Mtron dropped out this afternoon but after a restart is OK again. What's more interesting is the X25-M G1. A huge round of reallocated sectors and a 7% drop decrease in spare area makes me believe that it'll not reach 1 PiB at this rate.

Samsung 830 256GB Day 98

(GiB) 2,401,525.13
(TiB) 2 345.24

(Avg) 295.01 MB/s

(B1) Wear Leveling Count: 10,418

(B6) Erase Fail Count: 8
(05) Reallocated Sectors: 32768
(POH) 2367

Plextor M3P 128GB Day 27

(GiB) 699,695.62
(TiB) 683.30

(Avg) 277.22MB/s
(POH) 715

------------------------------------------------------
Finally, the 830 loses another block. New count is 8, up from 7.-