Samsung 830 256GB Day 144
(GiB) 3,609,534
(TiB) 3,524
(PiB) 3.46
(Avg) 296.75 MB/s
(B1) Wear Leveling Count: 15,629
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
(POH) 3558
-------------------
Printable View
Samsung 830 256GB Day 144
(GiB) 3,609,534
(TiB) 3,524
(PiB) 3.46
(Avg) 296.75 MB/s
(B1) Wear Leveling Count: 15,629
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
(POH) 3558
-------------------
Here are todays update:
m4
1399.5832 TiB
5801 hours
Avg speed 74.54 MiB/s.
AD 77 to 67
P/E 24041.
C3 4647
CE 58
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=500286
Intel X25-M G1 80GB
861.79 TiB
25087 hours
Reallocated sectors : 188 to 255 to 20
Available Reserved space: 11 to 6
MWI= 68 to 44
MD5 =OK
25.61 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=500284
Intel X25-E 64GB
723.57 TiB
2268-30=2238 hours
Reallocated sectors : 27 to 37
Available Reserved space: 99 to 98
MWI= 95
MD5 =OK
91.53 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=500285
Mtron Pro 7025 32GB
Paused until new firmware is updated.
The G1 is now very close to 1% spare area. Just hope I get home in time....:)
So, the samsung 830 seems to go on and on, it just won't give up! I am considering upgrading to a SSD and seeing the 830 withstand the torture like that... I think I know what I'll buy.
Great thread!
Samsung 830 256GB Day 146
(GiB) 3,643,414
(TiB) 3,558
(PiB) 3.50
(Avg) 296.16 MB/s
(B1) Wear Leveling Count: 15,776
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
(POH) 3603
-------------------
We're 7/8ths of the way to 4PiB
Here are todays update:
m4
1408.0741 TiB
5834 hours
Avg speed 74.53 MiB/s.
AD 67 to 62
P/E 24186.
C3 4647
CE 58
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=500404
Intel X25-M G1 80GB
864.35 TiB
25120 hours
Reallocated sectors : 20 to 74
Available Reserved space: 6 to 2
MWI= 44 to 38
MD5 =OK
25.34 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=500406
Intel X25-E 64GB
734.02 TiB
2301-30=2271 hours
Reallocated sectors : 37 to 42
Available Reserved space: 98
MWI= 95
MD5 =OK
91.49 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=500405
Mtron Pro 7025 32GB
Paused until new firmware is updated.
Getting closer.....
Don't worry bat, the Intel drive will probably chug on for a while longer ... because running out of avaliable reserved space never stopped the old 40gig Intel 320.
Sandisk Extreme G25 - 120gb - Day 72
Drive hours: 1662
ASU GiB written: 719,753.27 GiB (702.88 TiB)
Avg MB/s: 125.12 MB/s
MD5: OK
Host GB written (F1): 724,730 GiB (707.74 TiB)
NAND writes (E9): 541,054 GiB (528.37 TiB)
Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 118 normalized
Media Wearout Indicator (E7): 10 normalized
Wear Range Delta (B1): 4 raw
Reported Uncorrectable Errors (BB): 0 raw
Hey, I need an SSD for the server/WS that I am building. I only need 60GB at most, I do intend to manually over provision between 20-30%, perhaps 50% for the heck of it if the drive is 200GB+
My budget is 300$, I want this SSD to last as long as possible. If it doesn't last 10 years It's garbage for me. At the same time, I don't want to be spending useless $$. If a simple intel 520 120GB SSD will do, that's nice. but if a 256GB 520 or samsung 830 or Crucial M4 would be significantly better, why not. What would you recommend?
I did see that, it looks awesome :) In Canada this SSD is rare, I did find it at 200$ + S/H and tax so 240$. So this is the best bang/$ for extreme longevity? I know M4s are dirt cheap I see the 64GB one doing well, I've seen the 512GB around 350$ etc. Out of curiosity how do the 128/256/512 M4s do?
Here are todays update:
m4
1413.8236 TiB
5857 hours
Avg speed 74.53 MiB/s.
AD 62 to 59
P/E 24284.
C3 4647
CE 58
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=500538
Intel X25-M G1 80GB
866.00 TiB
25143 hours
Reallocated sectors : 74 to 107
Available Reserved space: 2 to 0
MWI= 38
MD5 =OK
25.14 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=500537
Intel X25-E 64GB
741.04 TiB
2324-30=2294 hours
Reallocated sectors : 42 to 48
Available Reserved space: 98
MWI= 95
MD5 =OK
91.46 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=500536
Mtron Pro 7025 32GB
Paused until new firmware is updated.
0% spare area.... What is next? I'll be traveling the next 48h so I'll try to keep an eye out for the G1 but I can't make any promises.
Samsung 830 256GB Day 149
(GiB) 3,718,760
(TiB) 3,631
(PiB) 3.57
(Avg) 296.38 MB/s
(B1) Wear Leveling Count: 16,101
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
(POH) 3675
-------------------
Sandisk Extreme G25 - 120gb - Day 76
Drive hours: 1758
ASU GiB written: 759,116.77 GiB (741.33 TiB)
Avg MB/s: 121.47 MB/s (66.37 hours)
MD5: OK
Host GB written (F1): 764,290 GiB (746.38 TiB)
NAND writes (E9): 570,624 GiB (557.25 TiB)
Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 112 normalized
Media Wearout Indicator (E7): 10 normalized
Wear Range Delta (B1): 4 raw
Reported Uncorrectable Errors (BB): 0 raw
Speed a bit low because I was gaming on the HTPC yesterday. It has slowly been recovering.
ok I am not doing the endurance test but thought I would post 2 things here that stand out on my 830.
it has crc errors, I noticed christopher's has 0 even after all his endurance testing. mine has a raw value of 82.
also I have a non 0 value for POR recovery count which is D.
Seems ssd life pro cant predict life left due to missing values.
My 830's CRC Error count is actually 2. It's actually a SATA error count. Mine increased when another drive I was testing died.
I've caused my Vertex 4 to completely lockup (but not kill it, secure erase saves it) via using ASU over a couple of days:
http://www.ocztechnologyforum.com/fo...l=1#post750877
The drive not only slowed down while performing a full surface wipe, but it also locked the drive up, indicating some kind of resource leak in the OCZ firmware that isn't cleaned up during heavy writes. If OCZ fix this, I will continue endurance testing, but until then, the V4 is suspended.
So because your drive showed this behaviour we have a FW issue?
1 drive with this behaviour means 1million are bad? No one else has complained about this...just you
if you used the drive normally as an end user does did it show an issue?
If the drive needed a secure erase, I guess all the data was lost. And when data is lost, the drive is called unreliable. If indeed it is a firmware bug, then yes, 1 million SSDs are bad until the bug is fixed.
Unless my drive is faulty, you do have a firmware issue, whether you want to believe it or not, and whether you fix it or not. I should not be able to be able to induce a complete lockup in an SSD no matter what sequence and timing of LBA writes I perform. I gave the drive ample time to recover before I ran the final write pass that locked up, so this issue is accumulative and not self correcting. Since you haven't said that you cannot reproduce my results I'll assume it is not just my drive.
And, I did not say the drives were bad, I said the drive had a issue and I was hitting it and hence I was suspending my endurance test on it. Do not put words in my mouth.
As for low write load desktop end users, sure, of course they won't notice this issue any time soon. Firmware 1.5 has only been out a couple of months. However, this kind of accelerated stress testing can show what a user will see in months/years of use.
Stress testing like what I did should really be part of your standard firmware testing. Don't peddle crap about usage models to cover for not running the hard yards in validation.
request an RMA...
I have run a 256GiB Vtx4 on 1.5 continually for days/weeks stress testing 100% of the drive, it got HOT, it kept going and its now sat in my macbook pro.
Vtx4's can run warm, you may have just heated that drive up and it took a dump...
Seriously though, 1 guy with an issue making it sound like the whole FW is broken...you really do need to see the big picture, I ONLY act and report issues when I see there is an issue...if we all jumped when 1 guy reports his drive took a dump you would never get beta FW never mind final
I will say this 1 last time...the VTX4 is designed to deliver fast writes BUT you have to let the drive FW work as intended, this means there is a possibility to push the drive outside of how it was designed to work....BUT end users who just use the drives never do this. In most cases the drive will just crawl...in your case something else happened but its never happened to me or any of the beta testers and not at HQ where we have been testing Vtx4 continually for months now continually.
We do NOT have a FW issue...you just think we do, if we did I would have a forum full of people with the same exact issue...and I don't, and neither does inhouse support...please see there is a massive machine watching and they jump ONLY when there is something to jump for.
If you want an RMA please PM Ryder on the ocz forum....and please stop wearing out your drive needlessly, we do not warrant nand burn remember, no one does
Some off topic: I am working as a software developer and I believe I have heard the "it's client fault" story tens, maybe hundreds of times and mostly from my boss, even when the problems were real.
Now Tony, you said something about "heat" and "dump". Are there any heat related issues with Vertex 4 series that we should know? Is it less tolerant to heat compared to Vertex 2 & 3? If yes, then does it have any heat protection (speed throttle, etc) ? Or any particular scenarios when it takes a dump?
I am watching with high interest the Vertex 4 endurance, however now it seems totally disappointing compared to Samsung 830.
Fair enough, if you think it is an individual drive issue, I'll request an RMA (or buy a new drive, I'm impatient and the V4 keeps dropping in price)
I doubt it, winter here and ambient temps don't get beyond 20C. There would be reports all over the place if the vertex 4 was overheating. Also don't forget that i'm testing a 128gig drive, vs the 256gig drive in your system which behaved differently.
Never said the entire firmware was broken, but I do question how strenuous your firmware testing has been if this been missed. And I will freely take it all back if it does indeed prove to be an individual drive problem. I do feel that it is a firmware problem, but the world is not perfect and these things happen, and I have been wrong in the past :)
Besides, don't take my critisims too harshly ... I do like the vertex 4 and it is an interesting drive. If I had really hated it, I would never have bought a second drive after killing the first :)
But that is the whole point of this exercise :)Quote:
If you want an RMA please PM Ryder on the ocz forum....and please stop wearing out your drive needlessly, we do not warrant nand burn remember, no one does
Besides, I have never asked for a RMA on a drive with worn out NAND. However I did appreciate being offered a possible RMA on the previous drive I tested and do feel that the RMA processes of OCZ are among the smoothest.
Sandisk Extreme G25 - 120gb - Day 79
Drive hours: 1833
ASU GiB written: 790,032.42 GiB (771.52 TiB)
Avg MB/s: 127.10 MB/s (68.36 hours)
MD5: OK
Host GB written (F1): 795,359 GiB (776.72 TiB)
NAND writes (E9): 593,839 GiB (579.92 TiB)
Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 112 normalized
Media Wearout Indicator (E7): 10 normalized
Wear Range Delta (B1): 3 raw
Reported Uncorrectable Errors (BB): 0 raw
Hmmm.
Sandisk Extreme G25 - 120gb - Day 83
Drive hours: 1925
ASU GiB written: 821,335.01 GiB (802.09 TiB)
Avg MB/s: 124.95 MB/s (23.31 hours)
MD5: OK
Host GB written (F1): 826,816 GiB (807.44 TiB)
NAND writes (E9): 617,345 GiB (602.88 TiB)
Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 110 normalized
Media Wearout Indicator (E7): 10 normalized
Wear Range Delta (B1): 4 raw
Reported Uncorrectable Errors (BB): 0 raw
Steady as it goes for the sandisk extreme.
Attachment 129685
I wonder if the Kingston E100 is as reliable as they claim: http://www.techpowerup.com/171171/Ki...prise-SSD.html .
Weird that they would only give it a 3 year warranty with these claims...
Samsung 830 256GB Day 157
(GiB) 3,942,364
(TiB) 3,849
(PiB) 3.78
(Avg) 297.58 MB/s over the past 1200 hours
(B1) Wear Leveling Count: 17,063
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
(POH) 3887
-------------------
I've been out of town, so I've haven't had the chance to post any updates lately, but TBH not much has happened... just a lot more writes. We're getting close to the 4 million GiB mark though.
'Twill be a momentous occasion. But then again, the M4 is at almost 1.5 PiB.
You didn't know but this Samsung is in fact a demigod, it can throw the data you send to him to the heavens so he's not hurt :P
Haven't checked on this thread in a long while. That M4 is just insane, 1.5BB on a 64GB drive is just ridiculous. http://smiliesftw.com/x/eek5boink.gif
Almost 4PB....that's damn impressive. Would love to see more 256GB drives get put to the test. It'd also be interesting to see how the 128GB 830 fairs to see just how much of an advantage the increased nand amount actually yields...or close to it maybe.
The M4 and the 830 are the 6gbps drives you want if you like writing a lot of data. Interestingly, the 64GB M4 and the 256GB 830 are about identical in terms of avg speed/capacity. Coincidence? Perhaps, but I don't think you'd have an issue getting 1.5PB on a 64GB 830 either.
Yes, Coincidence. They're just well built drives, I doubt Samsung and Micron would be sharing anything with each other.
No, I mean, if the 830 is 4x larger and 4x faster than the m4, perhaps they have equal amounts of recovery time and this is a large part of their success. It could just be their proprietary nand management techniques. It could be lots of things, but if you own a fab and have a proprietary controller (the M4's Marvell is pretty much their own controller in the end), you should be able to make a drive that lasts a long, long time.
Been a while since my last update. My holyday is over and I get more time to have fun here :)
Here are todays update:
m4
1487.5670 TiB
6148 hours
Avg speed 74.24 MiB/s.
AD 59 to 17
P/E 25552.
C3 4647 to 5683
CE 58
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=501574
Intel X25-M G1 80GB .
882.42 TiB
25434 hours
Reallocated sectors : 107 to 255 to 74
Available Reserved space: 0 to 59 to 31
MWI= 38 to 255 to 233
MD5 =OK
21.65 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=501575
Intel X25-E 64GB
830.36 TiB
2615-30=2585 hours
Reallocated sectors : 48 to 148
Available Reserved space: 98 to 95
MWI= 95 to 94
MD5 =OK
90.48 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=501573
Mtron Pro 7025 32GB
Paused until new firmware is updated.
The G1 decided that it had some more spare area hidden so the counter went from 0 to 59 and started to count down again. Very strange behaviour.
The m4 just keeps going and going and going.... Not much change just a little more cumulative corrected ecc.
What does concern me is the number of bad sectors on that SLC drive ....
That suprised me too. It burns through sectors at the same rate the G1 did in the begining.
Samsung 830 256GB Day 159
(GiB) 3,989,792
(TiB) 3,896
(PiB) 3.83
(Avg) 297.73 MB/s over the past 1200+ hours
(B1) Wear Leveling Count: 17,267
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
Attachment 129744
(POH) 3932
-------------------
I'm starting to get the feeling that this 830 might not ever die. Perhaps there is a critical point of wear beyond which the drive starts degrading rapidly? I can only hope.
Maybe it is the error correction that makes the difference. Drives with weak error correction implementation will show a gradual increase of bad sectors, just like Intel G1 while those with a strong one will have a fast degradation at the end. Probably the lack of a complex ECC in X25-E 64GB (at least not as complex as in the MLC drives) is forcing it to mark bad blocks faster.
Sandisk Extreme G25 - 120gb - Day 86
Drive hours: 2002
ASU GiB written: 855,241.02 GiB (835.20 TiB)
Avg MB/s: 125.53 MB/s (100.03 hours)
MD5: OK
Host GB written (F1): 860,890 GiB (840.71 TiB)
NAND writes (E9): 642,808 GiB (627.74 TiB)
Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 115 normalized
Media Wearout Indicator (E7): 10 normalized
Wear Range Delta (B1): 4 raw
Reported Uncorrectable Errors (BB): 0 raw
Samsung 830 256GB Day 160
(GiB) 4,012,542
(TiB) 3,918
(PiB) 3.85
(Avg) 297.75 MB/s over the past 1200+ hours
(B1) Wear Leveling Count: 17,365
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
(POH) 3953
-------------------
Hey guys,
Think we can get a graph done with all drives that have been tested and at what point they died? and the fact I want to see the Samsung 830 at 4PB :)
The first page of the thread has most of what you're looking for. Anvil will occasionally post a current report for drives currently being run thru the ringer.
Here are todays update:
m4
1502.8526 TiB
6209 hours
Avg speed 74.13 MiB/s.
AD 17 to 8
P/E 25818.
C3 5683 to 6349
CE 58
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=501794
Intel X25-M G1 80GB
883.15 TiB
25495 hours
Reallocated sectors : 74 to 202
Available Reserved space: 31 to 24
MWI= 233 to 1
MD5 =OK
20.25 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=501795
Intel X25-E 64GB
848.63 TiB
2676-30=2646 hours
Reallocated sectors : 148 to 172
Available Reserved space: 95 to 94
MWI= 94
MD5 =OK
90.18 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=501793
Mtron Pro 7025 32GB
Paused until new firmware is updated.
When I took the screendump of the ASU G1 the program was slow and felt non-responsive. I had to wait 4-5 sec before I could save the screendump. I think something might happen this weekend so I'll check up on it more often then normal.... Exciting :D
Sandisk Extreme G25 - 120gb - Day 88
Drive hours: 2049
ASU GiB written: 876,012.60 GiB (855.48 TiB)
Avg MB/s: 125.50 MB/s (147.13 hours)
MD5: OK
Host GB written (F1): 881,765 GiB (861.10 TiB)
NAND writes (E9): 658,408 GiB (642.98 TiB)
Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 117 normalized
Media Wearout Indicator (E7): 10 normalized
Wear Range Delta (B1): 4 raw
Reported Uncorrectable Errors (BB): 0 raw
Just a quick chart (because we all love charts)
Attachment 129792
Edit: Changed Title of Graph to TiB and updated Christopher's drive
Samsung 830 256GB Day 162
(GiB) 4,074,346
(TiB) 3,978
(PiB) 3.91
(Avg) 298.08 MB/s over the past 1200+ hours
(B1) Wear Leveling Count: 17,631
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
(POH) 4012
-------------------
Another Graph .. this time Available Space Write Cycles
Attachment 129793
Here are todays update:
m4
1514.4436 TiB
6256 hours
Avg speed 74.08 MiB/s.
AD 8 to 1
P/E 26020
C3 6349 to 7200
CE 58
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=502057
Intel X25-M G1 80GB
883.32 TiB
25542 hours
Reallocated sectors : 202 to 241
Available Reserved space: 24 to 21
MWI= 1 to 255 to 21
MD5 =OK
1.73 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=502054
Intel X25-E 64GB
862.56 TiB
2722-30=2692 hours
Reallocated sectors : 172 to 193
Available Reserved space: 94
MWI= 94
MD5 =OK
90.03MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=502056
Mtron Pro 7025 32GB
Paused until new firmware is updated.
The write speed has dropped to around 1 MiB/s on the G1. I think it's not long until it is finished. ASU is still slow and unresponsive but the drive still works and read speed is good.
Here are todays update:
m4
1520.7107 TiB
6281 hours
Avg speed 74.04 MiB/s.
AD 1 to 0 to 255 to 254
P/E 26129
C3 7200 to 7561
01 (Raw read error rate) 0 to 2
CE 58
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=502162
Intel X25-M G1 80GB
883.41 TiB
25566 hours
Reallocated sectors : 241 to 255 to 56
Available Reserved space: 21 to 17
MWI= 21 to 0 to 255 to 237
MD5 =OK
1.15 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=502163
Intel X25-E 64GB
870.04 TiB
2747-30=2717 hours
Reallocated sectors : 193 to 200
Available Reserved space: 94 to 93
MWI= 94
MD5 =OK
89.93 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=502161
Mtron Pro 7025 32GB
Paused until new firmware is updated.
The G1 has stabilized at 1 MiB/s but still hangs in there. Just have to wait and see what happens this week. Another development. The m4 has reportet its first raw read error rate. The last time it got these at 600TiB but still no reallocated sectors. :D
Hi guys :)
I've been out of town for a few weeks, my drives are OK but have been idle for some time, I'll get them restarted tomorrow.
I'll catch up the next few days.
(hopefully most drives are still running)
Sandisk Extreme G25 - 120gb - Day 91
Drive hours: 2119
ASU GiB written: 906,771.14 GiB (885.52 TiB)
Avg MB/s: 125.47 MB/s (216.82 hours)
MD5: OK
Host GB written (F1): 912,676 GiB (891.29 TiB)
NAND writes (E9): 681,522 GiB (665.55 TiB)
Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 119 normalized
Media Wearout Indicator (E7): 10 normalized
Wear Range Delta (B1): 4 raw
Reported Uncorrectable Errors (BB): 0 raw
Here are todays update with a little sad news:
m4
1523.2666 TiB
6306 hours
Avg speed 75.29 MiB/s.
AD 254 to 250
P/E 26237
C3 7561 to 7907
01 (Raw read error rate) 2 to 3
CE 58 to 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=502246
Intel X25-M G1 80GB
883.46 TiB
25576-18632=6944 hours
Reallocated sectors : 56 to 72
Available Reserved space: 17 to 16
MWI= 237 to 235
MD5 =OK
1.17 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=502251
http://www.diskusjon.no/index.php?ap...tach_id=502250
Intel X25-E 64GB
877.62 TiB
2772-30=2742 hours
Reallocated sectors : 200 to 205
Available Reserved space: 93
MWI= 94
MD5 =OK
89.39 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=502247
Mtron Pro 7025 32GB
Paused until new firmware is updated.
At 08:42 this morning the G1 pulled his last breath and went away silently. It just couldn't take any more after 10.5 months of torture. I tried every trick in the book but I can't get it to connect again.
R.I.P Intel X25-M G1 80GB :(
My plans now is to update the firmware of my Mtron and Vertex 1 and throw them back in the blender :D
That G1 went out like a boss. 10.5 months of no TRIM is hardly a small victory. In reality, it must have written 5x that much internally. If it had TRIM.......
Samsung 830 256GB Day 164
(GiB) 4,150,202
(TiB) 4,052
(PiB) 3.98
(Avg) 297.41 MB/s over the past 1300+ hours
(B1) Wear Leveling Count: 17,958
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
(POH) 4098
-------------------
Yeah, the G1 went pretty well :)
I just did 24h retention test on sandisk ... didn't worry it at all.
I'm sure the Sammy 830 has passed the 4PB mark by now...hats off to Samsung for one solid and steady controller and to Chris for puttin' the screws to it in the quest(s) to see which drives go above and (waaay) beyond expectations. Altho the controller does have a lot of nand to work with vs other drives tested...I'm betting the 128GB and 64GB do just as well with respect to those drive sizes. Getting 2PB out of a 64GB Sammy wouldn't be a huge shocker, tho it'd be damn impressive.
Here are todays update:
m4
1531.6987 TiB
6338 hours
Avg speed 74,97 MiB/s.
AD 250 to 245
P/E 26380
C3 7907 to 9220
01 3
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=502375
Intel X25-E 64GB
887.50 TiB
2805-30=2775 hours
Reallocated sectors : 205 to 219
Available Reserved space: 93
MWI= 94
MD5 =OK
87.64 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=502376
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 165
(GiB) 4,184,385
(TiB) 4,086
(PiB) 4.01
(Avg) 297.20 MB/s over the past 1300+ hours
(B1) Wear Leveling Count: 18,106
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
(POH) 4114
-------------------
And that is 4PiB! Haven't had an erase failure in over 2 PiB.
:up:
Congrats to Sam(sung) and Chris.
Congratz Chris :clap:
Next stop 6 PiB.
Next stop could be never. At this rate, I'll be posing updates for the next 73 years.
Attachment 129879
I am surprised that such a drive can cost so competitively, could it even match SLC ?
what the ... ultra durable toughness drive like X25-V!
830's NAND is truly Toggle MLC.
Grateful to Christopher :clap:
Sandisk Extreme G25 - 120gb - Day 93
Drive hours: 2171
ASU GiB written: 929,637.00 GiB (907.85 TiB)
Avg MB/s: 125.54 MB/s (50.60 hours)
MD5: OK
Host GB written (F1): 935,659 GiB (913.73 TiB)
NAND writes (E9): 698,702 GiB (682.33 TiB)
Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 109 normalized
Media Wearout Indicator (E7): 10 normalized
Wear Range Delta (B1): 3 raw
Reported Uncorrectable Errors (BB): 0 raw
May I dare dream of having a drive reach 1 PiB (well, without having to do something dumb like breaking out an Intel 510 or something!)
Since it came up, the 830 is using 27nm Samsung 1.0 Toggle. But IMHO the M4 getting 1.5PiB at 64GB is far more impressive... But it's only a matter of time before the 830 gets there.
IMO the Samsung 830 is far more impressive, as it has a lot more flash chips inside! The failure of each flash chip is statistically independent, which means it's more difficult to get a large drive with good quality flash chips together, than to get a small drive. Think of the cost of display/monitor - the price does not grow linearly with respect to area, but grows exponentially!
I don't think you can typically expect the drive endurance to increase linearly with capacity in real world testing, but I'm no expert. If you ask me the 830 is the most impressive drive to date. 4PiB is no joke.
Just wanted to comment that this thread made me go run out and grab an 830 for my notebook. It's performing well, even on my ancient 2011 SATA II hardware. My only complaint is that it gets the palm area where the drive resides considerably warmer than before. I was writing 150GB or so to the drive at 200+MB/s, but I never noticed that area get that warm before.
Here are todays update:
m4
1541.8668 TiB
6378 hours
Avg speed 74,88 MiB/s.
AD 245 to 239
P/E 26553
C3 9220 to 11450
01 3 to 5
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=502545
Intel X25-E 64GB
899.39 TiB
2844-30=2814 hours
Reallocated sectors : 219 to 237
Available Reserved space: 93 to 92
MWI= 94
MD5 =OK
87.36 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=502546
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
The 830 gets warm; under prolonged writing mine stays around 52c, and it's in open air. The 830 is great for laptops since it only draws .38w at idle -- though load consumption is as much a
6w for the larger capacities.
Here are todays update:
m4
1547.8740 TiB
6401 hours
Avg speed 74,90 MiB/s.
AD 239 to 236
P/E 26656
C3 11450 to 11796
01 5
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=502613
Intel X25-E 64GB
906.38 TiB
2868-30=2838 hours
Reallocated sectors : 237 to 248
Available Reserved space: 92
MWI= 94
MD5 =OK
87.19 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=502614
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
The drive is undetected in bios. Tried it from 3 different machines. The G1 is truly dead.
Samsung 830 256GB Day 168
(GiB) 4,265,360
(TiB) 4,165
(PiB) 4.09
(Avg) 297.53 MB/s over the past 1400+ hours
(B1) Wear Leveling Count: 18,454
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
(POH) 4198
-------------------
The 830's instantaneous estimated speed is 350MB/s for most of the loop! If it weren't for the average being almost 1500 hours, avg/MBs would most likely be quite high.
350 MiB/s write speed after 4 PiB is ridiculous fast and impressive. :)
Here are todays update:
m4
1554.0292 TiB
6425 hours
Avg speed 74,93 MiB/s.
AD 236 to 232
P/E 26760
C3 11796 to 15808
01 5 to 6
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=502746
Intel X25-E 64GB
913.48 TiB
2892-30=2862 hours
Reallocated sectors : 248 to 255 to 7
Available Reserved space: 92
MWI= 94
MD5 =OK
87.01 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=502747
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
My 256GB under test runs between 50c and 54c. The 512GB is slightly slower in some places, slightly faster In others compared to the 256GB. They share the same number of dice, but the 512GB uses 64Gbit dice while the rest use 32gbit dies. I haven't run the 512GB for any length of time under endurance testing though.
Sandisk Extreme G25 - 120gb - Day 96
Drive hours: 2239
ASU GiB written: 959,599.64 GiB (937.11 TiB)
Avg MB/s: 125.13 MB/s (39.87 hours)
MD5: OK
Host GB written (F1): 965,764 GiB (943.13 TiB)
NAND writes (E9): 721,201 GiB (704.30 TiB)
Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 110 normalized
Media Wearout Indicator (E7): 10 normalized
Wear Range Delta (B1): 4 raw
Reported Uncorrectable Errors (BB): 0 raw
The 330 has been acting up and so the X25-V is running solo. (the 330 is idle)
I'l get back to tonight with a proper report. (been travelling a lot lately)
Sandisk Extreme G25 - 120gb - Day 98
Drive hours: 2288
ASU GiB written: 981,462.60 GiB (958.46 TiB)
Avg MB/s: 125.41MB/s (81.37 hours)
MD5: OK
Host GB written (F1): 987,735 GiB (964.58 TiB)
NAND writes (E9): 737,627 GiB (720.34 TiB)
Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 112 normalized
Media Wearout Indicator (E7): 10 normalized
Wear Range Delta (B1): 4 raw
Reported Uncorrectable Errors (BB): 0 raw
Will post new graphs in a few minutes :)
Attachment 129969
Attachment 129970
Bat's poor X25-M 80GB has the final stats on death. I'll update other drives if people post their updates!
Edit 1: Updated BAT's Drives
Here are todays update:
m4
1570.9176 TiB
6491 hours
Avg speed 75.06 MiB/s.
AD 232 to 223
P/E 27047
C3 15808 to 26044
01 6 to 10
CE 90
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=502984
Intel X25-E 64GB
932.79 TiB
2957-30=2927 hours
Reallocated sectors : 7 to 32
Available Reserved space: 92 to 91
MWI= 94 to 93
MD5 =OK
86.57 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=502985
Mtron Pro 7025 32GB
Paused until new firmware is updated.
OCZ Vertex 1 120GB
Will start after an update to the latest firmware.
Status of the Intel 330 120GB
831.75TB Host writes
2.81TiB Host reads
Reallocated sectors : 05 1184 +797 (387)
Available Reserved Space : E8 100 ""
MWI 1 (9)
[B5] Program fail count 563 (186)
[B6] Erase fail count 621 (201)
[F1] Total LBAs Written 27254740
[F2] Total LBAs Read 86201
[F9] Total NAND Writes 600556GB // ~586TiB
POH 2605 (1824)
MD5 --
---.--MiB/s on avg (hours)
It's not running any tests (just idling), will have a closer look at it this weekend, most likely on a different computer.
--
Kingston SSDNow 40GB (X25-V)
1210.15TB Host writes (39654321*32)
Reallocated sectors : 05 78 +5
Available Reserved Space : E8 98
POH 10856
MD5 OK
33.15MiB/s on avg (~60 hours)
--
I'll have a look at the events logged by SMARTLog, they should be telling some of the story.
Samsung 830 256GB Day 172
(GiB) 4,349,371
(TiB) 4,247
(PiB) 4.17
(Avg) 297.64 MB/s over the past 1400+ hours
(B1) Wear Leveling Count: 18,816
(B6) Erase Fail Count: 9
(05) Reallocated Sectors: 36864
(POH) 4269
-------------------
The 830 is boring me.
So I think I'm going to try another drive -- but this time, I'm goinng to do full span random testing with either 4K or 8K. And it will probably be a drive already tested by me or someone else.
Attachment 129990
Attachment 129991
Just a graph update since Anvil and Christopher did updates.
Attachment 129993
Woohoo, 1 million GB written!