I'm trying to get one of both 840s. I have big plans for them.
Printable View
I'm trying to get one of both 840s. I have big plans for them.
Kingston SSDNow 40GB (X25-V)
1313.71TB Host writes 43047921*32)
Reallocated sectors : 05 768 -
Available Reserved Space : E8 86 (86)
POH 11798
MD5 OK
31.69MiB/s on avg (~210 hours)
--
Here are todays update:
m4
1826.5500 TiB
7500 hours
Avg speed 74.20 MiB/s.
AD 84 to 77
P/E 31434
C3 18643515 to 25789687
01 4903 to 6832 (1)
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=506909
Intel X25-E 64GB
1.19 PiB
3965-30=3935 hours
Reallocated sectors : 38 to 76
Available Reserved space: 75 to 74
MWI= 92
MD5 =OK
79.98 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=506910
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
Samsung 830 256GB Day 219
(GiB) 5,413,221
(TiB) 5,286
(PiB) 5.19
(Avg) 298.51 MB/s over the past 2500+ hours
(B1) Wear Leveling Count: 23,144
(B6) Erase Fail Count: 13
(B6) Runtime Bad Block Count: 21
(05) Reallocated Sectors: 86016
(POH) 5296
-------------------
Two more reallocations, one read failure and one more erase failure.
Another read failure.
840 TLC in stock.
Who's first?
The 830 dropped 2 more read failures over the past ten hours, making 23 total (13 erase, 10 read).
Samsung 830 256GB Day 221
(GiB) 5,480,044
(TiB) 5,351
(PiB) 5.26
(Avg) 298.66 MB/s over the past 2500+ hours
(B1) Wear Leveling Count: 23,693
(B6) Erase Fail Count: 13
(B6) Runtime Bad Block Count: 26
(05) Reallocated Sectors: 106496
(POH) 5369
-------------------
Even more read failures.... this number of read failures was the end of the Plextor, 3 OCZs, and probably a few others. The 830 seems perfectly fine though.
The 830 is also twice the size of the Plextor :)
And the OCZ drives tended to start dieing after a couple of hundred erase block failures, the samsung is only on 40.
Edit: The plextor reached almost 6 million reallocated sectors before failing outright.
http://www.xtremesystems.org/forums/...=1#post5117724
Here are todays update:
m4
1850.0077 TiB
7595 hours
Avg speed 74.08 MiB/s.
AD 77 to 63
P/E 31842
C3 25789687 to 48482335
01 6832 to 13329 (1)
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=507228
Intel X25-E 64GB
1.19 PiB
3965-30=3935 hours
Reallocated sectors : 76 to 173
Available Reserved space: 74 to 71
MWI= 92
MD5 =OK
79.98 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=507227
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
Sorry for OT, but Anandtech tested Intel 335 240GB (IMFT 20nm sync):
http://www.anandtech.com/show/6388/i...240gb-review/2
"In a few days, I managed to write a total of 37.8TB to the NAND and during that time, the MWI had dropped from 92 to 79. In other words, I used up 13% of the drive's available P/E cycles. This is far from being good news. Based on the data I gathered, the MWI would hit 0 after around 250TB of NAND writes, which translates to less than 1,000 P/E cycles."
http://images.anandtech.com/doci/6388/MWI%20graph.png
preliminary endurance test is "shocking" :confused:
I hope that is just only a bugged firmware.
Kingston SSDNow 40GB (X25-V)
1327.31TB Host writes 43493397*32)
Reallocated sectors : 05 768 -
Available Reserved Space : E8 86 (86)
POH 11971
MD5 OK
31.76MiB/s on avg (~333 hours)
--
As for the 335, even if the figures are correct it'll still do ~200++TiB. ("normal" users will have updated their drives long before one hits 50TiB)
I expect there'll be a few ~20nm drives thrown into the test shortly, a 335 might be one of them.
Intel's not having an easy time with their 20NM parts. I wouldn't be surprised if <1000 P/E cycles was the case, maybe 1500.
I dunno, so far as I can tell, manufacturers set MWI completely arbitrarily. You'll notice the drive used up exactly no reserved space in that time. It could still easily hit 3k P/E cycles, but Intel certianly seems to have set MWI very conservatively on those drives.
Perhaps it's a warranty consideration? I mean, the 830 exhausted its MWI 180 days ago. It's written 4.5 more petabytes since then, so while Anand's statement doesnt fill me with confidence, it wont keep me up at night. But if they set the warranty length by MWI... It makes more sense. You also have to think that keeping 20nm flash within error specs is hard after a little bit of wear, so the reduction in MWI could be to keep uBER in check. The enterprise spec from JEDEC is 10^16, I don't know what the consumer spec is, but maybe it goes out of spec after a few thousand PE cycles (and isn't so much an endurance issue).
---------
I actually read the review, and I think there is merely something wrong with the FW. I've had two drives both ship with MWI less than 100. In one case it was FW, and in another it was just caused by reallocations out of the box.
Intel ssd warranty don't cover MWI to 1 on OEM version.
"Any Product the usage of which has reached its write endurance limit, as measured by the SMART attribute (E9) “Media
Wear-out Indicator” value of “1”, as set forth above."
On Boxed there isn't warranty limitation.
Perhaps Intel want preserve 335 "cheap" series, but I think on bugged firmware.
OT closed: :)
Samsung 830 256GB Day 223
(GiB) 5,559,835
(TiB) 5,429
(PiB) 5.33
(Avg) 298.76 MB/s over the past 2500+ hours
(B1) Wear Leveling Count: 24,037
(B6) Erase Fail Count: 14
(B6) Runtime Bad Block Count: 37
(05) Reallocated Sectors: 151552
(POH) 5435
-------------------
Reallocations have been growing steadily over the past week, one every few hours.
Samsung 830 256GB Day 225
(GiB) 5,601,463
(TiB) 5,155
(PiB) 5.37
(Avg) 298.77 MB/s over the past 2000+ hours
(B1) Wear Leveling Count: 24,216
(B5) Program Fail Count: 0
(B6) Erase Fail Count: 14
(B7) Runtime Bad Block Count: 41
(05) Reallocated Sectors: 167936
Read Failures: 27
(POH) 5475
-------------------
Here are todays update:
m4
1882.8672 TiB
7727 hours
Avg speed 73.79 MiB/s.
AD 63 to 44
P/E 32412
C3 48482335 to 104131897
01 13329 to 30726 (1)
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=507731
Intel X25-E 64GB
1.25 PiB
4192-30=4162 hours
Reallocated sectors : 173 to 255 to 43
Available Reserved space: 71 to 67
MWI= 92 to 91
MD5 =OK
79.21 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=507732
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
Samsung 830 256GB Day 228
(GiB) 5,687,048
(TiB) 5,553
(PiB) 5.45
(Avg) 298.86 MB/s over the past 2000+ hours
(B1) Wear Leveling Count: 25,586
(B5) Program Fail Count: 0
(B6) Erase Fail Count: 14
(B7) Runtime Bad Block Count: 59
(05) Reallocated Sectors: 167936
Read Failures: 45
(POH) 5557
-------------------
Here are todays update:
m4
1897.9654 TiB
7789 hours
Avg speed 73.67 MiB/s.
AD 44 TO 35
P/E 32674
C3 104131897 to 136440144
01 30726 to 41196 (1)
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=507936
Intel X25-E 64GB
1.26 PiB
4253-30=4223 hours
Reallocated sectors : 43 to 85
Available Reserved space: 67 to 66
MWI= 91
MD5 =OK
79.03 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=507937
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
Samsung 830 256GB Day 230
(GiB) 5,732,148
(TiB) 5,597
(PiB) 5.50
(Avg) 298.86 MB/s over the past 2000+ hours
(B1) Wear Leveling Count: 24,781
(B5) Program Fail Count: 0
(B6) Erase Fail Count: 15
(B7) Runtime Bad Block Count: 68
(05) Reallocated Sectors: 278528
Read Failures: 53
(POH) 5600
-------------------
The 830 is continuing to fail blocks predictably and steadily, which is reassuring to see.