SSD Write Endurance 25nm Vs 34nm

Kingston SSDNow 40GB (X25-V)

583.01TB Host writes
Reallocated sectors : 05 15 Increased by 1
Available Reserved Space : E8 99
POH 5277
MD5 OK

34.18MiB/s on avg (~20 hours)

--

Corsair Force 3 120GB

01 95/50 (Raw read error rate)
05 2 (Retired Block count)
B1 49 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 585940 (Raw writes) ->572TiB
F1 779900 (Host writes) ->762TiB

MD5 OK

106.87MiB/s on avg (~20 hours)

power on hours : 2258

--

I had to update a utility and so the testing on both drives were re-started about 20 hours ago.

An update on WRD and then a new one that includes Raw Error Read Rate for the Force 3

http://www.ssdaddict.com/ss/Force3/F...2011_12_24.png


http://www.ssdaddict.com/ss/Force3/F...2011_12_25.png

A brief summary so far.

http://www.ssdaddict.com/ss/Endurance_failed_drives.png

http://www.ssdaddict.com/ss/Enduranc...ly_running.png

...

Christmas will be over here in seven minutes, but I thought I would wish you all a merry Christmas before it is over.

Well then, let me be the first to wish you a happy new year. Hopefully the Samsung will die soon as the testing rig is going to start getting crowded in 2012.

Due to a poweroutage I have no update today. It's been out since 23.00 yesterday and we still have no power. Because of the bad weather I hope the rig is ok and I can continue tomorrow.

The weather's been pretty bad the past few days, pretty OK today though. (and no power outage in my area)

@B.A.T and Anvil...stay safe and good luck.

Thank you Bluestang :) The worst part is over (the wind) but still no power. 20 hours and counting.....

And we're back again. Everything is OK and the test is running again. All ssd got an unexpected retention test for 24h and they all passed :)

I have a question here: it looks like ASU's Endurance testing would drastically increase the MFT size of NTFS, which is probably responsible for WinHex being extremely slow to traverse a partition for a snapshot. How do I shrink the size of MFT if I no longer plan to run Endurance testing?

Paragon looks to do the trick. (the free version should work)

If you ran the test without static files on a large capacity drive then one can expect MFT to grow beyond normal size, for normal usage/size it should not be an issue.

Link

Kingston SSDNow 40GB (X25-V)

588.58TB Host writes
Reallocated sectors : 05 16 Increased by 1
Available Reserved Space : E8 99
POH 5326
MD5 OK

33.14MiB/s on avg (~69 hours)

--

Corsair Force 3 120GB

01 92/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 599788 (Raw writes) ->586TiB
F1 798326 (Host writes) ->780TiB

MD5 OK

106.05MiB/s on avg (~69 hours)

power on hours : 2308

I’ve just been trying to figure out the Samsung 830 data.

I’ve assumed:

• 5K P/E cycles.
• Host writes = F1*512/1,073,741,824 = GiB
• B1 RAW = P/E cycles count

It seems strange that the Host Writes per P/E cycles ratio remained consistently wrong until the theoretical P/E cycle count had expired. Once the theoretical P/E cycle count had expired the WA came out at; Avg 3.93.

It would be interesting to see how these results compared to another 64GB 830, however it seems it is possible to calculate host writes and approximate the MWI/ NAND Writes & WA using the basic SMART data that is provided. W/A is quite savage, but then again so are the sustained write speeds (at least until you get to MWI = 0).

Did anything come of the 470 autopsy? Is the 320 still going?

http://img543.imageshack.us/img543/8...mycompared.png

The 830 has a serious defect in the sense that PE cycle counts do not increase until a reboot (essentially, though they do increase slightly). To get the 'true' PE count I'd have to reboot, which I will do now. I'm not there physically, so if anything was to go wrong, it would be several days before I could be there to fix it.

6672 is what its at now, but a reboot did not do anything. It needs a power cycle which I cannot perform until I get back.

Christmas update:
Kingston V+100
315.6061 TiB
1638 hours
Avg speed 25.38 MiB/s
AD still 1.
168= 1 (SATA PHY Error Count)
P/E?
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=473330http://www.diskusjon.no/index.php?ap...tach_id=473327

Intel X25-M G1 80GB
178,5906 TiB
19877 hours
Reallocated sectors : 00
MWI=152 to 151
MD5 =OK
46.71 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=473329http://www.diskusjon.no/index.php?ap...tach_id=473326

m4
135.3233 TiB
494 hours
Avg speed 78.39 MiB/s.
AD gone from 24 to 21.
P/E 2380.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=473331http://www.diskusjon.no/index.php?ap...tach_id=473328

The power cut of again from 03 to 14 today but everything is back up now. Only strange thing is that the X25-M and the m4 has dropped their write speed with a couple of MiB/s.

320 is still going...

7425 reallocated sectors (up by 1), 684.5tb.

Quote:

---

Originally Posted by Christopher

The 830 has a serious defect in the sense that PE cycle counts do not increase until a reboot (essentially, though they do increase slightly). To get the 'true' PE count I'd have to reboot, which I will do now. I'm not there physically, so if anything was to go wrong, it would be several days before I could be there to fix it.

6672 is what its at now, but a reboot did not do anything. It needs a power cycle which I cannot perform until I get back.

---

Did you have to power cycle every day to get the revised B1 values that you have reported? What I was trying to point out is that the host writes per P/E count came out consistently at ~630GiB at every reading, until the P/E count hit 5,000. From that point onwards it came out consistently at ~16GiB.
The approx. theoretical writes capacity = 64 x 5,000 = 320,000 GiB, which was exceeded by the time host writes had reached 87,476GiB, giving a WA factor of 3.98 (Avg WA after 5,000 PE = 3.93).

Kingston SSDNow 40GB (X25-V)

590.94TB Host writes
Reallocated sectors : 05 17 Increased by 1 again, up 3 during the last week.
Available Reserved Space : E8 99
POH 5347
MD5 OK

33.03MiB/s on avg (~90 hours)

--

Corsair Force 3 120GB

01 94/50 (Raw read error rate)
05 2 (Retired Block count)
B1 44 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 605659 (Raw writes) ->591TiB
F1 806136 (Host writes) ->787TiB

MD5 OK

105.98MiB/s on avg (~90 hours)

power on hours : 2329

--

@Ao1

Any particular reason to why you are using 5K P/E on the Samsung 830, the 470 series points to 1K or 3K, hard to tell though.
It's an interesting drive, the 830's I've got are all for OS X so I won't be doing any testing on the drives I've currently got. (I think :))

http://www.ssdaddict.com/ss/Endurance_cr_20111228.png

Chart(s) are updated/placed in post#1
I'm looking into making some of the other charts that Vapor made.

Quote:

---

Originally Posted by Anvil

@Ao1

Any particular reason to why you are using 5K P/E on the Samsung 830, the 470 series points to 1K or 3K, hard to tell though.
It's an interesting drive, the 830's I've got are all for OS X so I won't be doing any testing on the drives I've currently got. (I think :))

---

Hmm… seems it uses 32nm with 3K P/E cycles.

“The 470 Series uses Samsung K8HDGD8U5M flash chips manufactured by Samsung on a 32-nano fabrication process. Moving to finer process technologies allows chip makers to squeeze more NAND dies out of a single wafer, but it also reduces the lifespan of those chips. Flash fabbed on a 50-nano process typically carries a write-erase endurance of 10,000 cycles, while 34-nano parts are generally rated for 5,000 cycles. According to Samsung, the 470 Series' flash chips have a write-erase endurance of only 3,000 cycles, which is on par with the longevity of 25-nano flash chips currently rolling off the line at Micron”.

http://techreport.com/articles.x/20087

If the WA for the endurance app workload is 3.93 the drive could “only” write ~50,000GIB of host writes before the MWI expired. If the B1 value only changes after a power cycle it would be worth re testing with frequent power cycles to more closely monitor changes to B1.

Quote:

---

Originally Posted by Anvil

Chart(s) are updated/placed in post#1
I'm looking into making some of the other charts that Vapor made.

---

Nice work on the first post summary. :up: If anyone has been logging attributes using SMARTLOG I would be happy to make a graph that plots out all of the SMART attributes on one graph, which might reveal some interesting correlations.

Ao1
I'll consider running the Endurance test on the 128GB Samsung 830 for a few hours if that could help shed some light on the Samsung 830 series.
It should be the same NAND process but there might be unknown differences to e.g page size.

I'll send you a copy of the logged attributes on my drives.
I have considered enabling SMART logging in ASU as well but it won't work on system drives. (for some strange reason)
The work is done it just needs to be stored somewhere, it could be a supplement to the logging done by SMARTLOG.

Here is a graph using SMARTLOG data collected by Anvil. It’s not showing anything of interest as it is only collecting data collected over a couple of days, however over time it would hopefully be possible to see correlating events, such as relocation events and error counts.

(BTW, I shifted the decimal place by 6 for On-the-fly ECC & Soft ECC values to keep a reasonable scale. Writes are on the second axis for the same reason).

http://img7.imageshack.us/img7/3498/smartlog.png

Todays update:
Kingston V+100
317.5828 TiB
1682 hours
Avg speed 25.37 MiB/s
AD still 1.
168= 1 (SATA PHY Error Count)
P/E?
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=473438http://www.diskusjon.no/index.php?ap...tach_id=473436

Intel X25-M G1 80GB
182,2931 TiB
19900 hours
Reallocated sectors : 00
MWI=151 to 150
MD5 =OK
49.70 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=473437http://www.diskusjon.no/index.php?ap...tach_id=473435

m4
141.6388 TiB
517 hours
Avg speed 80.42 MiB/s.
AD gone from 21 to 18.
P/E 2489.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=473439http://www.diskusjon.no/index.php?ap...tach_id=473434

This one is still in the works as I need to check the accurate GiB values for some of the drives.

http://www.ssdaddict.com/ss/Endurance_PEsummary.png