SSD Write Endurance 25nm Vs 34nm

[canthearu]

On the other hand, if there is a chance that someone implemented a Read-Only state I'd say the odds are good on Intel and Micron.

If there were a true readonly mode ... the One_Hertz's Intel 320 drive probably should have triggered it ... It used all its spare space ... then some!

Maybe the Sandforce based drives (including intel 330/520) might go readonly when reserved space is exhausted ... but these drives don't seem to be able to properly identify blocks that are too worn and should be removed from service ... so important metadata ends up on them and the data disappears during downtime ... or the drive just up and panic locks! (The sandforce drives are quite well designed, but lack of proper testing tended to negate the design quality, maybe it has improved with LSI at the helm!)

More investigation needed *evil grin*

[Anvil]

One_Hertz drive was giving warnings (they all did in some way) so under normal circumstances one would simply replace the drive, it should have triggered read-only mode long before it finally died. (so, getting a drive into read-only mode looks to be impossible)

More investigation needed *evil grin*

I've got plenty of drives...

[canthearu]

Intel 520 60GB - Day 105

Drive hours: 2,466
ASU GiB written: 783,153.21 GiB (764.80 TiB)
Avg MB/s: 93.62 MB/s
MD5: OK

Host GB written (F1): 788,814.75 GiB (770.33 TiB, 25242072 raw)
NAND writes (F9): 558,420 GiB (545.33 TiB)

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

Sandisk Extreme G25 - 120gb - Day 5

Drive hours: 118
ASU GiB written: 49,603.28 GiB (48.44 TiB)
Avg MB/s: 120.47 MB/s
MD5: OK

Host GB written (F1): 50,075 GiB (48.90 TiB)
NAND writes (E9): 37,379 GiB (36.50 TiB)

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

No further re-allocations on the G25.

[Anvil]

I'll update the charts later tonight.

Interesting development on the SanDisk, re-allocations sort of resemble the X25-V. (early days though)

[Hopalong X]

Intel 320

Some of you may vaguely remember way back when (last summer??) I posted Intel pdf links for the Intel 320.

I had found in one of the Intel pdf's the Intel 320 had no read only point as some of the SSD's reportedly do.

It would write until it died...thus it did. Alas, poor Intel 320 we knew thee...

[Christopher]

Without the controller stepping in and declaring the drive read-only, you'd never see RO otherwise.... it just doesn't work like that. One manufacturer even measures life by % of the way to RO. But we'll never see it here, it could be more common if we were doing full-span random testing. Either way, for a drive to become RO it has to have no reserve space, and that's just not going to happen for us. Most will simply wake up dead one day with very few reallocations. Others, like the two Turbos, will have one die too damaged to continue (you could see it with the Turbos).

I only know two instances where drives had become RO, one was a defective drive on a manf. support forum which had 200 hours and no reserve space left, while another instance was a SF PCIe drive (it was detailed here in a thread IIRC). With millions of SSDs deployed, you'd think there would be more anecdotal evidence of drives hitting RO conditions.

[Christopher]

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

Plextor M3P 128GB Day 13
336,892.18 GiB
328.00 TiB

272.29 MB/s Average

348 Hours

Rellocated Event Count 0

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

Samsung 830 256GB Day 83

2,018,309.13 GiB
1,971.00 TiB

294.56 MB/s Average
1994 Hours

8763 Wear Leveling Count
MWI 1

7/0 Erase/Program Fail
Used Reserved Block Count: 14/28672 sectors
---------------------------------------

[B.A.T]

well done

the retention test is a good idea, don't forget to update to fw 0309 (or 000f)
to prevent the "5K hours bug"

bye
luke

Thank you
I'm going to wait it out until I'm closer to 5K hours. With so much P/E used I might not see 5K hours.

I'm planning on having a retention test next weekend (Friday-Sunday) on both drives, it will be the first for the 330, the V has had quite a few tests but it's been a while since last time. (probably at 800GiB)

An SSD getting into a true Read-Only state is what we have been "told" or told our-selves would happen, it does not look to happen in the real-world.
Even if it did, data-retention would make unplugging the drive a high risk sport.

On the other hand, if there is a chance that someone implemented a Read-Only state I'd say the odds are good on Intel and Micron.

So, it's a tough one, I'm set on performing a test next weekend, it may end in "tears" though
(if it makes it through the test there will be no more retention testing on the V)

Ok. I'll do something similar. I'll start the retention test today with both the G1 and m4. It'll be 12, 24 and 48h and it'll be the last for the m4 while the G1 will get more with 200 TiB intervals for now.

[B.A.T]

Todays update:

m4
1037.9935 TiB
4355 hours
Avg speed 74.55 MiB/s.
AD gone from 21 to 16
P/E 17882.
CE 26
MD5 OK.
Reallocated sectors : 00


Intel X25-M G1 80GB
705.33 TiB
23665 hours
Reallocated sectors : 152 to 158
Available Reserved space: 75
MWI= 44
MD5 =OK
38.90 MiB/s on avg


Intel X25-E 64GB
246.80 TiB
753-30=723 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI= 98
MD5 =OK
92.13 MiB/s on avg


Mtron Pro 7025 32GB
ASU write 27.0836 TiB
Host write 49,5474 TiB
Total host write 97,0830 TiB
Day 8
MWI= 98 to 97
MD5 =OK
47.08 MiB/s on avg


The Mtron dropped another point of MWI. I looked in the log and it's 30 TiB of host write for 1% drop. That means MWI=1% will take 3 PiB of host write and 1,5 TPiB of ASU write. The WA is almost 2:1 at the moment.

[Anvil]

Intel 330 120GB

182.58TB Host writes
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 80
[F1] Total LBAs Written 5982882
[F2] Total LBAs Read 30852 // not much use in this one
[F9] Total NAND Writes 131796GB
POH 475
MD5 OK

122.28MiB/s on avg (~34 hours)

--

Kingston SSDNow 40GB (X25-V)

1028.83TB Host writes (33712720*32)
Reallocated sectors : 05 46
Available Reserved Space : E8 99
POH 9203
MD5 OK

34.32MiB/s on avg (~34 hours)

--

Endurance_cr_20120610-11.png

[Christopher]

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

Plextor M3P 128GB Day 14
357,158.80 GiB
348.78 TiB

271.63 MB/s Average

369 Hours

Rellocated Event Count 0

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

Samsung 830 256GB Day 84

2,039,545.02 GiB
1,991.74 TiB

291.56 MB/s Average
2016 Hours

8855 Wear Leveling Count
MWI 1

7/0 Erase/Program Fail
Used Reserved Block Count: 14/28672 sectors
---------------------------------------

1.96PiB LBA writes on the 830.

[Kain665]

Maybe the 830 will make it to 3TB...

[Christopher]

I'm losing 850GiB a day, or 5.9TiB a week, with the 830 in the endurance rig. It's just 10MB/s avg less a second (vs. my main system). Not a huge loss, but an irritating one. I've tried everything I could think of to get the H67's speed up, but to no avail. The 830 is just being held back by the platform. The M3P is only a couple MB/s less on average though, so it's not a big concern.

[Kain665]

You're using the Intel controller on the H67, correct? What is your main system?

[Christopher]

You're using the Intel controller on the H67, correct? What is your main system?

It's a Z68. Both are on the same RST drivers. The Z68 I'm using just has better storage performance, period. I can't necessarily explain it all, but it's just faster than the H67 and P67s I've been using.

[Zaxx]

It's a Z68. Both are on the same RST drivers. The Z68 I'm using just has better storage performance, period. I can't necessarily explain it all, but it's just faster than the H67 and P67s I've been using.

I've heard more than a couple of folks say that the Z68 is edging out the new Z77s as well...strange...not that I'm complaining lol

[Christopher]

I've heard more than a couple of folks say that the Z68 is edging out the new Z77s as well...strange...not that I'm complaining lol

Random performance is noticeably faster than the other 1155 boards I have, and sequential performance is a little better too. I'm in no hurry to upgrade to IB boards or anything. AFAIK, the H67 and Z68 are using the same OROMs too. I have a P67 on 11.xx oroms and drivers, and it has substantially worse storage performance, but that's because it's super aggressive on power savings.

I'm on a quest to squeeze the last bit of speed out of the M3P and 830, and dammit I want those 10MB/s back.

[B.A.T]

Todays update:

m4
12h retention test complete.
MD5 OK
No change in smart values.
24h starts now


Intel X25-M G1 80GB
12h retention test complete.
MD5 OK
No change in smart values.
24h starts now

Intel X25-E 64GB
254.68 TiB
777-30=747 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI= 98
MD5 =OK
92.35 MiB/s on avg


Mtron Pro 7025 32GB
ASU write 29.3400 TiB
Host write 53,7101 TiB
Total host write 101,2456 TiB
Day 9
MWI= 98 to 97
MD5 =OK
47.18 MiB/s on avg

[Anvil]

Todays update:

m4
12h retention test complete.
MD5 OK
No change in smart values.
24h starts now


Intel X25-M G1 80GB
12h retention test complete.
MD5 OK
No change in smart values.
24h starts now

Was it just a quick check or did you leave them connected for more than just minutes?
(doesn't really matter, just curious)


@christopher
the slower it runs the longer it lasts

[B.A.T]

I ran 5 loops with ASU just to be sure they worked OK and a MD5 check. A total of 2 h connected while I played with my kid.

[canthearu]

Intel 520 60GB - Day 107

Drive hours: 2,515
ASU GiB written: 799,299.51 GiB (780.57 TiB)
Avg MB/s: 93.41 MB/s
MD5: OK

Host GB written (F1): 805,041.25 GiB (786.17 TiB, 25761320 raw)
NAND writes (F9): 569,908 GiB (556.55 TiB)

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

Sandisk Extreme G25 - 120gb - Day 7

Drive hours: 168
ASU GiB written: 70,672.64 GiB (69.02 TiB)
Avg MB/s: 120.94 MB/s
MD5: OK

Host GB written (F1): 71,252 GiB (69.58 TiB)
NAND writes (E9): 53,162 GiB (51.92 TiB)

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

[ZOMGVTEK]

Who wants to buy the 'MacBook Pro with Retina Display' and write to the SSD until it fails?

It might be interesting...

[Christopher]

Arent the new MBPs just using the 830 now?

I just looked at Anand's WWDC coverage, and the Apple SSD he's benching looks a hell of a lot like a 512GB 830.

[Anvil]

Intel 330 120GB

196.47TB Host writes
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 78
[F1] Total LBAs Written 6437854
[F2] Total LBAs Read 30852 // not much use in this one
[F9] Total NAND Writes 141814GB
POH 508
MD5 OK

122.75MiB/s on avg (~67 hours)

--

Kingston SSDNow 40GB (X25-V)

1032.57TB Host writes (33835416*32)
Reallocated sectors : 05 46
Available Reserved Space : E8 99
POH 9236
MD5 OK

33.80MiB/s on avg (~67 hours)

[Kain665]

It's a Z68. Both are on the same RST drivers. The Z68 I'm using just has better storage performance, period. I can't necessarily explain it all, but it's just faster than the H67 and P67s I've been using.

Wierd.

Intel 520 60GB - Day 107

Drive hours: 2,515
ASU GiB written: 799,299.51 GiB (780.57 TiB)
Avg MB/s: 93.41 MB/s
MD5: OK

Host GB written (F1): 805,041.25 GiB (786.17 TiB, 25761320 raw)
NAND writes (F9): 569,908 GiB (556.55 TiB)

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

Sandisk Extreme G25 - 120gb - Day 7

Drive hours: 168
ASU GiB written: 70,672.64 GiB (69.02 TiB)
Avg MB/s: 120.94 MB/s
MD5: OK

Host GB written (F1): 71,252 GiB (69.58 TiB)
NAND writes (E9): 53,162 GiB (51.92 TiB)

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

The 520's raw error rate counter is fluctuating. I wonder what that speaks for the drive's health.