54 reallcs now with the Octane. I've been checking it incessantly with my phone, and every time I look it's higher.
Printable View
54 reallcs now with the Octane. I've been checking it incessantly with my phone, and every time I look it's higher.
Graph shows a exponential relationship between time and bad sectors ... that is not good for the life of an ssd.Quote:
Originally Posted by Christopher
Todays update:
Intel X25-M G1 80GB
507.33 TiB
22325 hours
Reallocated sectors : 85 to 88
Available Reserved space: 94
MWI=224 to 220
MD5 =OK
46.47 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=486364
m4
697.0389 TiB
2991 hours
Avg speed 72.98 MiB/s.
AD gone from 213 to 210.
P/E 12084.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=486365
The Octane might still live long despite mwi going down towards 1. But it's exciting to follow the quick fall :DQuote:
Originally Posted by Christopher
Patriot Torqx-2 64GB - Day 58
Drive hours: 1,415 (903 Hours, 512 missing)
GiB written: 93,200 GiB (91.02 TiB)
Avg MB/s: 19.67 MB/s
MD5: OK
Bad blocks: 2 grown, 83 factory
Wear cycle counter: 5825 average erase cycles, 8934 maximum erase cycles.
Intel 520 60GB - Day 50
Drive hours: 1,213
Avg MB/s: 92.64 MB/s
MD5: OK
Host GB written (F1): 380,924.31 GiB (372 TiB, 12189578 raw)
NAND writes (F9): 269,724 GiB (263.40 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 118 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 13
I've added raw error rate and avaliable reserved space as these may come into play later in the Intel's drives life. The Intel is finally reaching the final stretch of its MWI and it is a complete mystery to me how far this drive will go or how it will die.
the Octane.... what can I say?
142 reallocations
MWI has gone to 0, back to 100, and is now sitting at 91.
The other drives are model citizens.
More chart pr0n:
Attachment 125351
830 256GB
641,506.63GiB
OCZ Vertex Turbo
336,754.80GiB
OCZ Octane
301,334.65GiB
Interesting that MWI is based on relocations. Have you rebooted at any stage? If so did the relocations reset? Have you tried an MD5 test?Quote:
Originally Posted by Christopher
The amount of relocations is obviously not normal behaviour for Intel or Hynix NAND. Either the controller is mistakenly calling out relocations or something is having a remarkable impact on the NAND to induce this type of behaviour. :confused:
More likely a firmware bug than the quasi-9174 controller being at fault. Although if OCZ is running the controller at a higher clock rate, I suppose there could be some strange interaction between the controller and the NAND flash.Quote:
Originally Posted by Ao1
I've been traveling lately, just got home and business is as usual for the little drive, tomorrow will be 11 months of testing.
(closing in on a year of testing)
Kingston SSDNow 40GB (X25-V)
873.60TB Host writes
Reallocated sectors : 05 41
Available Reserved Space : E8 99
POH 7846
MD5 OK
33.55MiB/s on avg (~117 hours)
^ Incredible. My 830 is coming up for the 3 month data retention test next week I believe.
The X25-V is a rockstar. 11 months and 1.1 million thread views.
Anvil, have you put any more thought into the next drive?
A01 -- I've not rebooted or cycled the system in weeks. I've been out of town for this week and won't be back for another week or so. I feared reallocations might reset with a power cycle, but the more I think about it, the less likely I think it is to happen.Quote:
Originally Posted by johnw
I believe one plane/die is sub par. If that one plane/die/etc goes, that's the end of the road. If these reallocations are occuring over the entirety of the flash, then the outlook is slightly more hopeful. I don't want this damn thing to die before I get home to yank it out of the rig.
But there have to be implications for substantially increasing clockspeed of the controller. It could bite them in the ass long term.
-------------------------------------------
170 reallocations and 89 MWI
Jesus, I just looked 5 seconds later and reallocations are now 172.
-------------------------------------------
The 830 is at 2810PE and the Vertex Turbo is 6032PE without reallocations. I estimate the Octane has used somewhere in the neighborhood of ~2600.
Todays update:
Intel X25-M G1 80GB
511.13 TiB
22349 hours
Reallocated sectors : 88 to 89
Available Reserved space: 94
MWI=220 to 216
MD5 =OK
46.46 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=486565
m4
702.9650 TiB
3015 hours
Avg speed 73.00 MiB/s.
AD gone from 210 to 206.
P/E 12183.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=486564
@Christopher: I guess the octane hit that brick wall of reallocated sectors it was creating for itself. Very unusual for a marvell controller to do that. I must get one of these drives one day and see if it is repeatable.
@BAT: Your new M4 is looking even better then the old M4, and is getting close to the same wear. It is showing less CRC corrections, and fewer read errors. Maybe 25nm fabrication quality has improved over the last 6 months.
226 reallocations at the last log. MWI decreased by 115 from the 226 popped blocks.
Maybe a secure erase would help .... but probably not.Quote:
Originally Posted by Christopher
Too bad for the octane. Let's hope the Vertex 4 doesn't suffer the same misbehavior.
True the x-25V is something else. Got 2 of them, very pleased to see it breaking records.
Patriot Torqx-2 64GB - Day 59
Drive hours: 1,438 (926 Hours, 512 missing)
GiB written: 94,736 GiB (92.52 TiB)
Avg MB/s: 20.80 MB/s
MD5: OK
Bad blocks: 2 grown, 83 factory
Wear cycle counter: 5921 average erase cycles, 9084 maximum erase cycles.
Intel 520 60GB - Day 51
Drive hours: 1,236
Avg MB/s: 93.22 MB/s
MD5: OK
Host GB written (F1): 388,069.63 GiB (378.97 TiB, 12418228 raw)
NAND writes (F9): 274,787 GiB (268.35 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 118 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 11
Notes:
I have a Vertex 4-120gig sitting here ... I'm having difficulty deciding whether to replace one of my older drives or just put the vertex 4 to the sword!
I can confirm that the vertex 4 has a working total write sector count and hour/poweroff counters! Don't know about lifetime counter.
Biggest difference betwheen them is firmware. The first had fw 0002 and this one uses fw 0009.Quote:
Originally Posted by canthearu
The first had higher writespeed (88 MiB/s) but I don't know if that count for anything.
This time I'm going to break 800 TiB and maybe it'll reach 1 PiB..... :woot:
I'm not there in person, but the octane is un detectable. I was thinking a reflash of 1.13fw might help.
But the OCZ toolbox can't detect it either.
canthearu:
Put th Vertex 4 to the sword! :D
I'm never testing a drive without decent smart data again. Not happening. Hell, OCZ should thank me for buying (it's not even a good value) and putting their -- (insert adjective here) -- drive in my precious endurance rig. I was thinking they were gonna bring the rain... And I was wrong.
Less then 300TiB written, probably can still get RMA replacement. *evil grin*