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.
The Plextor had 15 read failures, the 830 now has 16.Quote:
Originally Posted by canthearu
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.Quote:
Originally Posted by Gilgamesh
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.
So that's the difference between boxed and oem...had I known, I'd have paid the extra few bucks for that little extra piece of mind.Quote:
Originally Posted by Gilgamesh
So that's the difference between boxed and oem...had I known, I'd have paid the extra few bucks for that little extra piece of mind.Quote:
Originally Posted by Gilgamesh
I ended up buying a 120GB Intel 320 OEM, and the warranty on that was 1 year and not five. Totally busted if you ask me, but I suppose I bear most of the blame.Quote:
Originally Posted by Zaxx
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.
Is the 830 going to hit 6PB at this block failure rate?
Incidentally, looks like a typo on the WLC number...
When write amplification is taken into account, 24K Write Cycles sounds right. At 5.5PiB write, that is 22528 WLC. But that assumes a perfect 1.0 write amp. rate, which only a few SSDs can accomplish using compression (SandForce chips, I think). If we assume that 24781 WLC is the entire drive, then the drive has has 6.05 PiB written. 6.05 / 5.5 is a write amplification rate of ~ 1.1 Not too bad!
I believe so, but maybe not by much. There was a typo in the last update's WLC, this one is right. Incidentally, because the read and write failures are so steady and predictable, I think it bodes well for 6PB.Quote:
Originally Posted by gordo
The WLC is probably accurate for the whole drive, but most WLCs are usually for just a single device/channel/etc. I figured WA at 1.1 -- if you take the LBA written and divide it by WLC you get about 231GB written per PE cycle. lBA writes are ahead of ASU by about 15GB (I "lost" some writes for about 14 hours one day).Quote:
Originally Posted by vpr5703
And Since it came up, it looks like SF drives using non-2281 controllers (ones with better SMART data) have another attribute that shows GB erased in addition to host and raw writes. I'll have to perform some more in depth analysis, but it looks like the actual WA for a mostly incompressible workload is significantly higher than the host/raw number would indicate.
Here are todays update:
m4
1909.4236 TiB
7789 hours
Avg speed 73.58 MiB/s.
AD 35 to 29
P/E 32873
C3 136440144 to 172698757
01 41196 to 54019 (1)
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=508041
Intel X25-E 64GB
1.27 PiB
4299-30=4269 hours
Reallocated sectors : 85 to 130
Available Reserved space: 66 to 65
MWI= 91
MD5 =OK
78.89 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=508042
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
Here are todays update:
m4
1921.2473 TiB
7884 hours
Avg speed 73.46 MiB/s.
AD 29 to 23
P/E 33079
C3 172698757 to 221068763
01 54019 72375 (1)
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=508144
Intel X25-E 64GB
1.29 PiB
4348-30=4318 hours
Reallocated sectors : 130 to 183
Available Reserved space: 65 to 63
MWI= 91
MD5 =OK
78.72 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=508145
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
That is still pretty good, considering. I like where this drive is going. Gives me lots of hope (providing that my device doesn't bite the dust due to flash failure) that my drive will outlast my laptop.Quote:
Originally Posted by Christopher
Kingston SSDNow 40GB (X25-V)
1348.84TB Host writes 44198881*32)
Reallocated sectors : 05 768 -
Available Reserved Space : E8 86 (86)
POH 12257
MD5 OK
32.02MiB/s on avg (~194 hours)
--
Here are todays update:
m4
1927.2346 TiB
7908 hours
Avg speed 73.42 MiB/s.
AD 23 to 18.
P/E 33183
C3 221068763 to 247252828
01 72375 to 82343 (1)
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=508217
Intel X25-E 64GB
1.29 PiB
4372-30=4342 hours
Reallocated sectors : 183 to 205
Available Reserved space: 63 to 62
MWI= 91
MD5 =OK
78.72 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=508218
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 237
(GiB) 5,887,996
(TiB) 5,749
(PiB) 5.65
(Avg) 298.72 MB/s over the past 2000+ hours
(B1) Wear Leveling Count: 25,454
(B5) Program Fail Count: 0
(B6) Erase Fail Count: 17
(B7) Runtime Bad Block Count: 134
(05) Reallocated Sectors: 548864
Read Failures: 117
(POH) 5752
-------------------
It's chugging along still.
Shipment confirmed on a few 840 Pro's. (not meant for endurance testing though)
I'll be ordering a few non Pro's for testing, that is, if no one else had planned on testing the TLC's?
(anyways, testing more than one of these drives wouldn't hurt)
So, they are rapidly getting available in these parts of the world.
@Anvil
The TLC 840 sounds exciting :) There'll be no more drives for me before I get enough sparetime to fix the two that's been waiting the last couple of months. Looks like that won't happen before december.
Here are todays update:
m4
1945.4780 TiB
7983 hours
Avg speed 73.28 MiB/s.
AD 18 to 8.
P/E 33500
C3 247252828 to 337721144
01 82343 to 118725 (1)
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=508476
Intel X25-E 64GB
1.31 PiB
4447-30=4417 hours
Reallocated sectors : 205 to 255 to 5
Available Reserved space: 62 to 61
MWI= 91
MD5 =OK
78.41 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=508477
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
Anvil, waiting for the 120gig 840's to become avaliable. Other options include the intel 335, corsair neutron and plextor m5 pro.
I've ordered a samsung 840 TLC 120gig and a Plextor M5 pro 120gig
Will decide on the Plextor's fate after I play with it a bit .... but the 840 will burn :)
OK ;)
I might join in on testing the 840 at some later point, depending on your results.
The Pro's should be here by tomorrow, I'll play some on a PCIE 3.0 controller (9207) thats been sitting in it's box for a few months.
(A real shame that there has been no time to play)
that softens it up a bit, as mine is now on 130 now. Although I got no idea why its going up. 641 gig written to drive. 15 /p/e cycles done.Quote:
Originally Posted by Christopher
I've got a few of the new Sammies in 120s, but not sure what I'm going to do with them yet.
Christopher: Someone has to help me work out if these samsung 840's are any good! :)
I'm impressed with the read speed. To be certain, the write speed is not in the 830 's class, but considering TLC has seven guard bands and 8 voltage levels, I think it's a miracle it works at all! It's still supposed to be 3K PE cycles (I think) but the MWI is based on 1K PEs.Quote:
Originally Posted by canthearu
Sequential and random reads are significanty better than the 256GB 830, while write speed is worse than the 64GB 830. All writes are limited to about 130MB/s. All in all, I'm incredibly impressed -- it's faster than many of the SLC drives I have, and I don't just mean the MTRONS.
------
THe 830 is up to 12.5 trillion LBAs written. It's not significant in any way, except it sounds like a whole lot.
I've just received my samsung 840 120gig .... Will have a play with it later.
I don't think i'll be able to part with the M5 Pro yet ....
Christopher ... I'm impressed with the read performance of the samsung 840 as well. It is certainly the match of any normal MLC drive.
Anyway, time to get down to business ... to start off with, some benchmarks for the samsung 840:
http://www.canthearu.com/samsung840/asssd.png http://www.canthearu.com/samsung840/crystaldiskmark.png
http://www.canthearu.com/samsung840/ASU-performance.png
Read performance is fantastic .... easily as good as any SATA 6 drive I've seen.
Write performance, while not as good, is still as good as your average 120gig sandforce drive .... which really is plenty for the tasks it needs to do.
Initial smart values
http://www.canthearu.com/samsung840/initalsmart.png
Still plenty of juicy data there!
I benched the Pro's last night (128GB and 256GB), will be posting tonight in the Storage forum.
The Pro's are rather nice :)
Drive Details:
Make: Samsung
Model: 840
Capacity GB: 128 GB
Interface: SATA 6Gb/s
Controller: Samsung MDX
NAND maker: Samsung
NAND process: 21nm TLC
NAND part#: unknown
NAND P/E spec: 1000 cycles
NAND type: Toggle Mode
Testing Environment:
OS: Windows 7 x64
Hardware Platform: Intel 1155 Z77
Test Details:
Static Data: 39.2 GB
Over-Provisioning: 0 GB
% Compression: 46%
ASU Endurance test Started:
http://www.canthearu.com/samsung840/ASUStarted.png
There is a problem with some 840s and LBA writes ; right now, F1 won't increment past 2.04TB and may reset with power cycles. It's hardly a big deal, so if you see it, don't think you're going crazy.
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.Quote:
Originally Posted by Christopher
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
epic!Quote:
Originally Posted by christopher
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 ?
Read failures can cause data corruption, leading to hosed partitions. It's happened a few times to me.Quote:
Originally Posted by Demo
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.
Probably firmware fault.Quote:
Originally Posted by Demo
Since you can still see the drive in the BIOS, try booting parted magic and secure erasing the drive. That might reset it and get it going again.
Nothing short of legendary! :eek: :D Kudos to you for running this test for so long and cheers to Samsung for this determined brute of a drive, this thread was a huge factor for me in buying several Samsung 830s :up:Quote:
Originally Posted by Christopher
Already did, it would give out an I/O error and would not perform the secure erase.Quote:
Originally Posted by canthearu
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.
Kingston SSDNow 40GB (X25-V)
1388.55TB Host writes 45500018*32)
Reallocated sectors : 05 768 -
Available Reserved Space : E8 86 (86)
POH 12688
MD5 OK
31.92MiB/s on avg (~210 hours)
--
I'll have a look at the charts asap. (tonight or tomorrow)
Thanks for testing this one. Eagerly awaiting further progress. Ordered one yesterday and wonder if it will be good enough. I doubt I will be writing 10Gb a day on it, so I hope it will last fine as a main OS drive.Quote:
Originally Posted by canthearu
Now that you mention it, it is moderately epic.Quote:
Originally Posted by DeadlyFire
Far to modest my man...I guess it'll take 10 PiB to earn the title of truly epic. lol
Too lazy to search the thread....did you buy this drive 'off the shelf' so to speak or did samsung give it to ya?
It's just a retail box 830... Came with a copy of Arkham City, too. I don't game all that much, but I just recently got around to playing it -- it was moderately enjoyable. To put things in perspective though, BATs 64GB M4 is further along when you take capacity and speed into account... The 830 is four times as fast, but four times as big, too.Quote:
Originally Posted by Zaxx
Samsung 840 Day 14.5ish
Drive Hours: 344
ASU GiB Written: 123,784.38
Avg MB/s: 105.20 (37.63 hours)
MD5: OK
Wear Leveling Count (B1): 990 raw (1 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
http://www.canthearu.com/samsung840/...ance%20EOL.png
http://www.canthearu.com/samsung840/...t%20values.PNG
Why crystaldiskinfo only shows 2tb being written? Is it because the drive is tlc and unsupported or does it count it differently than A.S.U.?
Counter is broken. It counts up fine to 2TiB, then stops counting. Firmware bug.Quote:
Originally Posted by eddieobscurant
thank youQuote:
Originally Posted by canthearu
and thank you all for testing these drives for us. I'm planning to get a 500gb ssd for my laptop, now that the prices are "normal" and i was between the 830(proven stability/endurance) and the 840(faster random reads, minimal slower writes than the 830, for the 500gb version) since the 840 pro is too expensive for me, but i was worried about the endurance of the tlc nand since my laptop will also have some torrents with average 20gb/day , 24/7. But since the 120gb manages more than 120tb, i don't think i'll have a problem with the 500gb for 3-5 years.
For now, I'd still get the 830 ... it is cheaper and has beetter NAND. It is also well proven in the field.Quote:
Originally Posted by eddieobscurant
I won't argue with that!Quote:
Originally Posted by canthearu
But here in the states, the 830 is getting harder to find at such economical prices. I think the 830, while slower, isn't noticably outclassed by the 840 Pro.
Wow! 6PB!! I wonder if the forceGT can even come half as close to that!
I know canthearu is testing the Samsung 840, but is anyone on here testing an 840 Pro by any chance??
Here are todays update:
m4
2053.8234 TiB (2 PiB)
8440 hours
Avg speed 72.11 MiB/s.
AD 241 to 202.
P/E 35367
C3 614011911 to 1786518967
01 239518 to 957059(1)
05 0 to 2048 (Reallocated sectors count)
AA 0 to 1 (Grown failing block count)
C4 o to 1 (Reallocation event count)
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=510069
Intel X25-E 64GB
1.42 PiB
4903-30=4873 hours
Reallocated sectors : 157 to 255 to 72
Available Reserved space: 56 to 43
MWI= 91
MD5 =OK
76.03 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=510071
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
And that was that. 2PiB done and the first reallocated sector done. Wonder how much further it can hold out.
That's the equivalent of 8PiB on the 830! Excellent.Quote:
Originally Posted by B.A.T
Cheers for good work!
There is also quite intense durability IMFT(Micron)?s NAND and of course SAMSUNG.
The durability of the NAND itself is a problem that becomes overspec :clap:
Your drive might still make 8PiB yet!Quote:
Originally Posted by Christopher
Hi,
This sounds interesting - http://www.bbc.co.uk/news/technology-20579077
Regds, JR
Here are todays update:
m4
2063.1434 TiB
8487 hours
Avg speed 71.71 MiB/s.
AD 202 to 196.
P/E 35534
C3 1786518967 to 2266091151
01 957059 to 1402073(1)
05 2048
AA 1
C4 1
CE 90
MD5 OK.
http://www.diskusjon.no/index.php?ap...tach_id=510232
Intel X25-E 64GB
1.43 PiB
4950-30=4920 hours
Reallocated sectors : 72 to 226
Available Reserved space: 43 to 39
MWI= 91
MD5 =OK
75.79 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=510234
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
And today the m4 has endured a year of torture :bows: :worship:
I hope they'll provide the oven and crucible to handle hours of baking at 800C/1,472F...:eek:Quote:
Originally Posted by JR.
J/K...lol
Does make ya wonder if a 2.5in. enclosure could handle that kinda heat even if only applied to a few cells at a time. ATM it's looking like nand rebust-ness isn't too much in question a la the 6PB 830. I'm beginning to suspect it's the controllers that can't handle the milage. hmmm...
Nah, the controllers themselves are pretty rugged. They have higher Tmax ratings that the flash itself, but the firmware is a different story. Obviously, higher temps skew Vth, but a super short burst of high heat might be the ticket to making that stuff last longer.Quote:
Originally Posted by Zaxx
I do sometimes wonder about the drives using overclocked ARM silicon... that could be an issue long term.
Samsung 830 256GB Day 259
(GiB) 6,445,077
(TiB) 6,294
(PiB) 6.18
(Avg) 298.63 MB/s over the past 3400+ hours
(B1) Wear Leveling Count: 27,858
(B5) Program Fail Count: 0
(B6) Erase Fail Count: 40
(B7) Runtime Bad Block Count: 831
(05) Reallocated Sectors: 3,403,776
Read Failures: 791
Samsung 840 Day 19
Drive Hours: 454
ASU GiB Written: 164,332.41
Avg MB/s: 104.97 (147.59 hours)
MD5: OK
Wear Leveling Count (B1): 1315 raw (1 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 may be here for a while with this drive .... damn samsung and their conservative engineering :)
At least the drive wasn't rated on the ragged edge of its true endurance.
If Samsung 840 survives past 5000 cycles, then it will be a true wonder.
I don't know if you guys remember, but several months back one of my X25-Es died after a FW update (I think we were talking about X25-E FW and I found out the first FW revisions were bugged). After the lock up, just having the drive connected was enough to lock a system up, and after contacting Intel support, I couldn't get my hands on newer OEM-only FW.
The good news is, I took it out of the gear closet yesterday, and I was able to SE it with RHEL. It works fine now. I'd tried this a couple times over the past few months, but for some reason it worked this time. If only I could do that to one of the dead MTRONS.