Anand just did a write up re: 840 endurance and noticed this too...decent little read. This thread is linked as well.
http://www.anandtech.com/show/6459/s...ce-of-tlc-nand
Printable View
Anand just did a write up re: 840 endurance and noticed this too...decent little read. This thread is linked as well.
http://www.anandtech.com/show/6459/s...ce-of-tlc-nand
Yeah, I'm seeing this bug.
The Anandtech Samsung 840 TLC died as well, right after the article was written. Not something I really expected from samsung. I'll probably retention test my 840 every couple of weeks.
The 840 pro seems to be seeing a number of failures under high load as well.
Time to start hammering out fw updates...I'm sure they've already begun.
It's cool that Mr. Vatto gave the 830 a shout out, but it actually has 5,850TiB on it at the moment, not the almost 5,000TiB he mentions.
Based on my calculations, a 120GB 840 should hit MWI 1 around 126TiB (under the endurance test). It's definitely spec'd for 1K PE cycles.
Here are todays update:
m4
1965.0628 TiB
8062 hours
Avg speed 73.19 MiB/s.
AD 8 to 1 to 255 to 253.
P/E 33836
C3 337721144 to 456606202
01 118725 to 167920 (1)
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=508633
Intel X25-E 64GB
1.33 PiB
4526-30=4496 hours
Reallocated sectors : 5 to 79
Available Reserved space: 61 to 59
MWI= 91
MD5 =OK
78.04 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=508634
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
Samsung 840 Day 1
Drive Hours: 26
ASU GiB Written: 7,458.54
Avg MB/s: 111.06 (15.52 hours)
MD5: OK
Wear Leveling Count (B1): 59 raw (94 normalized)
Reallocated blocks (B3,05): 0 (0 sectors)
Failure count (B5, B6): 0 program, 0 erase
Uncorrectable Error Count: 0
ECC Error Rate (C3): 0
Drive is chugging along fine .... One thing I've noticed is that TRIM occurs quite quickly and it always gets in it's 100meg of writes after each cycle (other drives often stalled right after all that TRIM and didn't recover quick enough to handle all 100meg of random writes before it timed out)
Samsung Magician Lifetime Indicator:
http://www.canthearu.com/samsung840/...gIndicator.png
Samsung 840 Day 3
Drive Hours: 75
ASU GiB Written: 23,882.93
Avg MB/s: 108.04 (11.4 hours)
MD5: OK
Wear Leveling Count (B1): 191 raw (81 normalized)
Reallocated blocks (B3,05): 0 (0 sectors)
Failure count (B5, B6): 0 program, 0 erase
Uncorrectable Error Count: 0
ECC Error Rate (C3): 0
I've been waiting for the 830 to hit 6PIB before posting another update. Shouldn't take too much longer.
Kingston SSDNow 40GB (X25-V)
1365.35TB Host writes 44739793*32)
Reallocated sectors : 05 768 -
Available Reserved Space : E8 86 (86)
POH 12475
MD5 OK
31.53MiB/s on avg (~92 hours)
--
Here are todays update:
m4
1984.9957 TiB
8143 hours
Avg speed 73.10 MiB/s.
AD 253 to 241.
P/E 34177
C3 456606202 to 614011911
01 167920 to 239518 (1)
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=508949
Intel X25-E 64GB
1.35 PiB
4607-30=4577 hours
Reallocated sectors : 79 to 157
Available Reserved space: 59 to 56
MWI= 91
MD5 =OK
77.59 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=508950
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
Samsung 840 Day 5
Drive Hours: 124
ASU GiB Written: 43,190.93
Avg MB/s: 110.47 (60.86 hours)
MD5: OK
Wear Leveling Count (B1): 345 raw (65 normalized)
Reallocated blocks (B3,05): 0 (0 sectors)
Failure count (B5, B6): 0 program, 0 erase
Uncorrectable Error Count: 0
ECC Error Rate (C3): 0
Samsung 840 Day 8
Drive Hours: 193
ASU GiB Written: 68,231.36
Avg MB/s: 112.75 (3.52 hours)
MD5: OK
Wear Leveling Count (B1): 545 raw (46 normalized)
Reallocated blocks (B3,05): 0 (0 sectors)
Failure count (B5, B6): 0 program, 0 erase
Uncorrectable Error Count: 0
ECC Error Rate (C3): 0
Amazing work gentlemen. Saw this article referenced on AnandTech.
Funny too, as my Intel 320 120GB is only 2.03 TiB in total writes. Guess at this useage, it should last well into the 2030's... ;)
Samsung 830 256GB Day 250
(GiB) 6,223,052
(TiB) 6,077
(PiB) 5.97
(Avg) 298.38 MB/s over the past 2000+ hours
(B1) Wear Leveling Count: 26,901
(B5) Program Fail Count: 0
(B6) Erase Fail Count: 25
(B7) Runtime Bad Block Count: 461
(05) Reallocated Sectors: 1,888,256
Read Failures: 436
(POH) 6177
-------------------
I couldn't wait until exactly 6PiB for the next update, so here it is: 5.97PiB
Guys, 175k IOPS from a SATA drive.
Christopher, how many sectors are there on the 830 to re-allocate to? Can we extrapolate out the (fairly steady?) reallocation rate and predict when it should run out of space and finally keel over?
For the record, 6PiB is insane. My 830 is averaging 8.5 GB writes/day. At that rate, the NAND would last until the year 4016 -- assuming it didn't get fried by a lightning surge, hurricane, earthquake, flood, nuclear bomb or meteor strike first. ;)
My 240Gb ForceGT suddenly failed after 5 months of use, it only had about 3Tb of host write on it.. It was working fine until a reboot and it became unpartitioned, it can be detected by the bios/os/parted magic but cannot be accessed.. I/O error of some sorts. What could have possibly caused this ?
Samsung 830 256GB Day 252
(GiB) 6,282,908
(TiB) 6,135
(PiB) 6.03
(Avg) 298.49 MB/s over the past 3400+ hours
(B1) Wear Leveling Count: 27,159
(B5) Program Fail Count: 0
(B6) Erase Fail Count: 27
(B7) Runtime Bad Block Count: 542
(05) Reallocated Sectors: 2,220,032
Read Failures: 515
(POH) 6133
-------------------
https://www.box.com/shared/static/3y...h6zx0mk0ym.png
And that's what 6PiB looks like.
Samsung 840 Day 13
Drive Hours: 321
ASU GiB Written: 111,733.01
Avg MB/s: 105.73 (5.02 hours)
MD5: OK
Wear Leveling Count (B1): 894 raw (11 normalized)
Reallocated blocks (B3,05): 0 (0 sectors)
Failure count (B5, B6): 0 program, 0 erase
Uncorrectable Error Count: 0
ECC Error Rate (C3): 0
Drive has nearly reached it's specified lifetime writes.