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)
Printable View
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)
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.
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.?
thank you
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.
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.
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:
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:
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.
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.