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*
That presupposes I want that drive anywhere near me. And, if I'm honest, it's no bug. I think the issue here is that much of the flash being used is not that great. It only takes one not so good die to ruin the whole drive. 7 of 8 NAND devices may be straight golden, but that 8th one can just be terrible sometimes. The first turbo I did was like that. But my displeasure with the Octane really centers more on its Godawful SMART data and poor relative value. All drives will have some sort of redundancy in higher and mid range capacities soon, and for this very reason. A drive is only as good as the worst piece of flash on it. Make sure the worst flash on the drive is still pretty good, and you've got a deal IMHO.Quote:
Originally Posted by canthearu
Well, the vertex 4 has working smart information. Looks like my drive got a 600 GiB wear in test as well before being packaged (my drive was sealed and the sticker was intact for the anti-static back, so definitely new.Quote:
Originally Posted by Christopher
Patriot Torqx-2 64GB - Day 60
Drive hours: 1,462
ASU GiB written: 96,352.33 GiB (94.1 TiB)
Avg MB/s: 25.48 MB/s
MD5: OK
Bad blocks: 2 grown, 83 factory
Wear cycle counter: 6050 average erase cycles, 9283 maximum erase cycles.
Total ECC Error Count: 1
Intel 520 60GB - Day 52
Drive hours: 1,260
ASU GiB written: 392,671.79 GiB (383.47 TiB)
Avg MB/s: 93.91 MB/s
MD5: OK
Host GB written (F1): 395,413.34 GiB (386.15 TiB, 12653227 raw)
NAND writes (F9): 279,989 GiB (273.43 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 108 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 9
Notes:
Changed to Intel rapid storage drivers 10.8. Getting somewhat of an improvement with the torqx 2 drive, and a little improvement for the Intel 520 drive.
Updated windows. Rebooted and the Torqx 2 fixed it's power on hours counter ... weird.
Also worked out how to correct the ASU counter, so using that for the Torqx 2, and including it in the intel stats now.
Really? The Plextors supposedly go through "20 hours of burn in testing" which probably means they just write a couple hundred GiB. That's a good thing, but I wonder how they swing that at the factory. Adding 20 hours to the build process can't be cheap.Quote:
Originally Posted by canthearu
690,895 GiB
289.96MB/s
The 830 is now over 3000 PE cycles, but it's still at 17 MWI. I've been told it's "3000" PE cycle flash, so one of those numbers is wrong probably.
Attachment 125412
------------------------------------------
351,527GiB
84.53MB/s
Just... awesome.
Attachment 125411
I haven't decided yet, not sure that I've got one that really needs testing, some are already getting a bit old...Quote:
Originally Posted by Christopher
If I can't make up my mind in due time for the 1 year "anniversary" for the thread I'll find some way to randomly select one.
A good thing that one can spot when things really start to fail...Quote:
Originally Posted by Christopher
If this was a real drive with important data you'd have ample time for a "backup".
That's why I haven't considered using the Plextor, it's just not worth it.Quote:
Originally Posted by Christopher
Attachment 125413
I'll leave the Octane in the chart. (until it can be physically checked)
Kingston SSDNow 40GB (X25-V)
879.25TB Host writes
Reallocated sectors : 05 41
Available Reserved Space : E8 99
POH 7895
MD5 OK
33.37MiB/s on avg (~166 hours)
Todays update:
Intel X25-M G1 80GB
516.76 TiB
22387 hours
Reallocated sectors : 89 to 93
Available Reserved space: 94
MWI=216 to 205
MD5 =OK
42.18 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=486818
m4
712.7236 TiB
3053 hours
Avg speed 73.09 MiB/s.
AD gone from 206 to 201.
P/E 12346.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=486819
The vertex 4 had 4 hours on the clock when I first put it in. So at least in the case of the vertex 4, it isn't so bad.Quote:
Originally Posted by Christopher
I'm on the lookout for a new #3 drive. There just isn't anything screaming out "test me! test me!".Quote:
Originally Posted by Anvil
I'm considering an Intel 330, but I think I want something a little further off the beaten path. Something bizarre perhaps. Or I still have the Mushkin Chronos Deluxe 120GB, but if I run it, I may do so overprovisioned.
When I finally make it back to the homestead, I'll try and use the OCZ bootable .iso to destructive flash 1.13 again, but I do expect a steaming plate of failure. Until that time, I'm hoping it doesn't crash the endurance rig.Quote:
Originally Posted by Anvil
I've had to turn off my endurance rig for today as it was malfunctioning and I didn't have time to fix it. It will be a quick 10-11 hour retention test!
I think the Intel RST 10.8 drivers are causing a problem, as the Intel 520 has disconnected a couple of times since installing them a couple of days ago. Funny enough, I can still read the SMART from the Intel 520 so the drive certainly isn't dead. I'll try a newer version, but worst comes to worse, I'll revert back to MSAHCI. (but the torqx 2 is 25% faster writing with ioStor, so hopefully I can get it working)
Which RST OROM is your mobo running? I'm sticking with 10.6 for a while.Quote:
Originally Posted by canthearu
I have never checked ... old P35 board here, so probably running 7.5 or. I've kept an eye on the situation, but since I've never had a problem with my boards so I've never been particularly worried about it.Quote:
Originally Posted by Christopher
I can possibly build an updated rom and include a newer OROM (I've done an older nvidia ASUS board some time back)
Keep us in the loop. I wonder if perhaps the 520's SF heritage is rearing is questionable head. I don't think so, as you would have perhaps experienced the issue earlier.
It is likely just the intel drivers giving me grief. the msahci driver worked perfectly for 2 months before this problem started happening.
But will keep updated
I'm pretty sure I have been using 10.8 since it was released, that is on the Z68 used for Endurance testing.
I'll double check, anyways I've been using the Intel drivers all along as I always install in raid-mode.
edit:
It is 10.8.0.1003, RAID option ROM is 10.6.0.1091
The driver is dated mid November 2011.
Well, I've gone back to msahci drivers for now.
My endurance system motherboard is very old now, so throwing the latest drivers on it doesn't always work out.
Could be a bad combo of MB and driver although I'm pretty sure that the drivers should be backwards compatible.
Are the drives back up and running?
Yep, drives came through 10 hours (turned off) without a problem. Endurance testing restarted
I'll let them go for a week. If I have no more problems, I'll be happy that it isn't a drive problem and I'll try the older driver's of Asus website.
I know this is an Plextor but with that size it looks interesting :p:
Link
They already got it in stock at several Norwegian webshops.
The 64GB Plextor M3 has been available in the US (newegg) for a while (1-2 months?). I think I even posted about it on XS when it first showed up.
I've seem to have missed that one.
Todays update:
Intel X25-M G1 80GB
519.80 TiB
22409 hours
Reallocated sectors : 93 to 97
Available Reserved space: 94
MWI=205 to 199
MD5 =OK
42.05 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=486975
m4
718.0030 TiB
3074 hours
Avg speed 73.10 MiB/s.
AD gone from 201 to 198.
P/E 12434.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=486974
Only 50 TiB until the last m4 record is breaken :D
Samsung 830 256 Day 31
719,649.19GiB
702.78TiB
289.97 MB/s Average
3142 Wear Leveling Count
MWI 13
0/0 Erase/Program Fail
OCZ Vertex Turbo 64 Day 48
359,903.87GiB
351.46TiB
84.55 MB/s Avg
6432 Avg PE count
-100 MWI
0/0/0 Read/Program/Erase Fail
------------------------------------------------------
Attachment 125436Attachment 125437
Decided that I'm too lazy to reinstall windows on my desktop, it is working fine and touching it is bad ... so the vertex 4 goes into the endurance rig. Besides, the octane drive failing early doesn't give me the most confidence in this drive.
I've updated the OROM to 8.9 on my P5K-E/Wifi-AP motherboard, using the BIOS links provided by OCZ. Hopefully that will resolve the stability difficulties I have been having.
Just copying static data to drive now . . . . stupid wireless network.
Endurance system stats (this is for all drives)
Intel Pentium E5400 at 2.7ghz (stock)
Asus P5K-E/Wifi-AP motherboard (modified BIOS, 8.9 OROM)
4gig RAM
Windows 7 x64
Will post again with performance figures and drive settings once this copy is done.
Ok, drive information:
Compression: 46% (picture will show 0%, I changed it right after)
Static Data: 58.6 GiB
Some benchies:
Attachment 125445Attachment 125446
CrystaldiskInfo ... Smart is working:
Attachment 125447
Endurance (quick compared to my intel 520):
Attachment 125448
Patriot Torqx-2 64GB - Day 62
Drive hours: 1,501
ASU GiB written: 99,295.62 GiB (96.9685 TiB)
Avg MB/s: 25.82 MB/s
MD5: OK
Bad blocks: 2 grown, 83 factory
Wear cycle counter: 6232 average erase cycles, 9553 maximum erase cycles.
Total ECC Error Count: 1
Intel 520 60GB - Day 54
Drive hours: 1,299
ASU GiB written: 403,933.5 GiB (394.46 TiB)
Avg MB/s: 92.15 MB/s
MD5: OK
Host GB written (F1): 406,743.78 GiB (397.21 TiB, 13015801 raw)
NAND writes (F9): 288,013 GiB (281.26 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 120 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 7
Vertex 4 128GB - Day 1
Drive hours: 24
ASU GiB written: 1,033.52 GiB (1.01 TiB)
Avg MB/s: 160.12 MB/s
MD5: OK
Sector GB written (E8): 1,766.08 GiB (1.72 TiB, 3703733049 raw)
Reallocated sectors (05): 0
Raw Read Error Rate (01): 7
Remaining Life (E9): 100
Todays update:
Intel X25-M G1 80GB
523.16 TiB
22431 hours
Reallocated sectors : 97 to 101
Available Reserved space: 94 to 93
MWI=199 to 193
MD5 =OK
43.34 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=487144
m4
723.6908 TiB
3097 hours
Avg speed 73.08 MiB/s.
AD gone from 198 to 195.
P/E 12529.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=487145
Let's see how the Vertex4 does as a contrast to the Octane.
EDIT
It should [The Vertex4] should perform like the Octane but with better ECC. The Avg MB/s are very similar.
Attachment 125453
I'll update post 1 as well with the new drive.
@canthearu
I've put IMFT as NAND maker, did you check if it was Intel or Micron?
I've also put 512MB but I'm not sure if the 128GB drive used 256MB or 512MB?
--
Kingston SSDNow 40GB (X25-V)
885.02TB Host writes
Reallocated sectors : 05 41
Available Reserved Space : E8 99
POH 7946
MD5 OK
33.27MiB/s on avg (~217 hours)
@Anvil
I havn't cracked it open. I don't want to void the warrenty if I get a particularly early death. Should be IMFT.
Cache is 512meg (actually 1gig, but only 512meg active, as per anandtech review)
Controller is: Indilinx Everest 2 (yes, it is based on the new marvell controller, but given indilinx firmware is quite different, it shouldn't be lumped in with other marvell drives for now)
Patriot Torqx-2 64GB - Day 63
Drive hours: 1,524
ASU GiB written: 101,350.75 GiB (98.97 TiB)
Avg MB/s: 26.16 MB/s
MD5: OK
Bad blocks: 2 grown, 83 factory
Wear cycle counter: 6361 average erase cycles, 9749 maximum erase cycles.
Total ECC Error Count: 1
Intel 520 60GB - Day 55
Drive hours: 1,322
ASU GiB written: 411,510.79 GiB (401.87 TiB)
Avg MB/s: 90.57 MB/s
MD5: OK
Host GB written (F1): 414,391.28 GiB (404.68 TiB, 13260521 raw)
NAND writes (F9): 293,423 GiB (286.55 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 109 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 5
Vertex 4 128GB - Day 2
Drive hours: 53
ASU GiB written: 13,705.07 GiB (13.38 TiB)
Avg MB/s: 142.79 MB/s
MD5: OK
Sector GB written (E8): 14,505.28 GiB (14.17 TiB, 30419775523 raw)
Reallocated sectors (05): 0
Raw Read Error Rate (01): 6
Remaining Life (E9): 99
Notes:
* Still having problems with Intel rst driver 10.8. Trying 8.9 from asus's website now .... though it is somewhat slower.
* 2 days until the Intel 520 reaches MWI 1
* The MWI works on the Vertex 4
Looks like samsung is going to break 1PiB before anything else. 290MB/s avg write speed is 2-4 times faster than the next best things.
maybe, but its use of PE cycles is agonizingly slow. Even though it's 3K PE rated flash, 177 is still at 8/8/3342 -- so I don't get it. I think it [MWI] may be based on 4K PE cycles.Quote:
Originally Posted by devsk
Attachment 125464
Attachment 125466
Attachment 125465
Samsung 830 256 Day 33
766,392.54GiB
748.43TiB
291.00 MB/s Average
3342Wear Leveling Count
MWI 8
0/0 Erase/Program Fail
OCZ Vertex Turbo 64 Day 50
373,049.81GiB
364.29TiB
84.55 MB/s Avg
6666 Avg PE count
-100 MWI
0/0/0 Read/Program/Erase Fail
to
------------------------------------------------------
Both drives continue to get ever so slightly faster over time. The 830 was averaging in the low/mid 280s weeks ago and is now at 291MB/s. The VT continues to gain a 10th of a MB/s every so often.
Todays update:
Intel X25-M G1 80GB
526.97 TiB
22457 hours
Reallocated sectors : 101 to 105
Available Reserved space: 93
MWI=193 to 186
MD5 =OK
43.21 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=487414
m4
730.1086 TiB
3123 hours
Avg speed 73.07 MiB/s.
AD gone from 195 to 191.
P/E 12636.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=487415
So the search for a new drive continues:
Here is mystery candidate alpha:
Attachment 125476
Those are some sexy numbers, but there are so many to choose from. I'm praying for a firmware update for the m3p which will add more smart data because I really would like to run it.
dont waste that m3p, i will kill you.
Scary if proposition if you've ever met him in person.Quote:
Originally Posted by Computurd
Patriot Torqx-2 64GB - Day 64
Drive hours: 1,546
ASU GiB written: 103,257.71 GiB (100.83 TiB)
Avg MB/s: 25.03 MB/s
MD5: OK
Bad blocks: 2 grown, 83 factory
Wear cycle counter: 6475 average erase cycles, 9918 maximum erase cycles.
Total ECC Error Count: 1
Intel 520 60GB - Day 56
Drive hours: 1,344
ASU GiB written: 418,176.87 GiB (408.38 TiB)
Avg MB/s: 96.30 MB/s
MD5: OK
Host GB written (F1): 421,119.5 GiB (411.25 TiB, 13475824 raw)
NAND writes (F9): 298,163 GiB (291.17 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 114 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 3
Vertex 4 128GB - Day 3
Drive hours: 78
ASU GiB written: 23434.16 GiB (22.88 TiB)
Avg MB/s: 151.91 MB/s
MD5: OK
Sector GB written (E8): 24,300.17 GiB (23.73 TiB, 50961154621 raw)
Reallocated sectors (05): 0
Raw Read Error Rate (01): 6
Remaining Life (E9): 97
Notes:
a) New Endurance Testing system:
Intel i3-2120
Gigabyte Z77M-D3H motherboard.
8gig DDR3
using Intel RST driver 11.0
b) Vertex 4 has some problems with smart still:
* Seems to be counting hours fast.
* Sometimes doesn't respond with a correct remaining life value.
Maybe a later update will fix this buggyness ... but it shows the lack of polish on these controllers.
c) Intel's Matrix Raid 8.9 driver doesn't seem to support TRIM at all, and the vertex 4 was a LOT slower and buggier without TRIM. My advise would be to never use the vertex 4 on a system without trim.
Just a guess:Quote:
Originally Posted by canthearu
on Corsair Performance Pro 128GB same bug on Intel chipset (using Crystaldiskinfo 4.6.0. with Plextor PX-128M2P support): hours counting is faster (I remember something like 1 hour every 10 min)
On Amd chipset Power on count = Power on hours.
Firmware 1.08 changelog for Plextor PX-M2P:
http://www.plextor-digital.com/index...7/task,finish/
Date: 2011/11/17
Issue : SMART attribute (power on hours).
Cause : Due to EEPROM power_on_hours add one every 10 min, we should divide by six when response it.
Modify: [HostSata.c]
Todays update:
Intel X25-M G1 80GB
530.86 TiB
22483 hours
Reallocated sectors : 105 to 110
Available Reserved space: 93
MWI=186 to 182
MD5 =OK
43.17 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=487536
m4
736.6889 TiB
3149 hours
Avg speed 73.07 MiB/s.
AD gone from 191 to 188.
P/E 12746.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=487537
Not that severe ... seems to be counting a few extra hours a day.Quote:
Originally Posted by Gilgamesh
rofl :) i really try to be friendly! just imo the M3P right now is about the hottest thing on the market. just my opinion, but i would hate to see one murdered, even for science :)Quote:
Originally Posted by Kain665
(V4 might tickle my fancy though, once she matures a bit)
Kingston SSDNow 40GB (X25-V)
891.79TB Host writes
Reallocated sectors : 05 41
Available Reserved Space : E8 99
POH 8005
MD5 OK
33.22MiB/s on avg (~276 hours)
--
@canthearu
I believe the first RST supporting TRIM was 9.6. (will check)
Patriot Torqx-2 64GB - Day 65
Drive hours: 1,546
ASU GiB written: 105,346.75 GiB (102.88 TiB)
Avg MB/s: 25.10 MB/s
MD5: OK
Bad blocks: 2 grown, 83 factory
Wear cycle counter: 6604 average erase cycles, 10109 maximum erase cycles.
Total ECC Error Count: 1
Intel 520 60GB - Day 57
Drive hours: 1,368
ASU GiB written: 426,158.42 GiB (416.17 TiB)
Avg MB/s: 96.12 MB/s
MD5: OK
Host GB written (F1): 429145.44 GiB (419.09 TiB, 13732654 raw)
NAND writes (F9): 303,842 GiB (296.72 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 114 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 2
Vertex 4 128GB - Day 4
Drive hours: 105
ASU GiB written: 35,792.95 GiB (34.95 TiB)
Avg MB/s: 149.13 MB/s
MD5: OK
Sector GB written (E8): 36,720.81 GiB (35.86 TiB, 77009128623 raw)
Reallocated sectors (05): 0
Raw Read Error Rate (01): 6
Remaining Life (E9): 96
Notes: No longer monitoring OCZ-VERTEX4 with smartlog ... it may be causing my smart problems on the vertex4.
Intel just hit MWI = 1 at 419.12TiB (host writes on drive)
Life may start getting intereting from here on ... maybe
Todays update:
Intel X25-M G1 80GB
533.91 TiB
22504 hours
Reallocated sectors : 110 to 114
Available Reserved space: 93
MWI=182 to 176
MD5 =OK
43.17 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=487616
m4
741.8432 TiB
3170 hours
Avg speed 73.07 MiB/s.
AD gone from 188 to 185.
P/E 12832.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=487618
I'm not sure if I dare to do a retention test on the m4 when it passes 800 TiB based on the last time I was here. :confused:
There are two things you should know - one, its not an M3P. And two, I can totally take you in a fight.Quote:
Originally Posted by Computurd
Attachment 125564Attachment 125565
vt64
387,230 GiB
378.15 TiB
830 256GB
814,296 GiB
795.22 TiB
The 830 is at MWI 2 with 3550 wear leveling count.
The 830 had 75 hours and 215GB host writes on it at the start of testing. After 810 hours, its at 814GiB. 290.68MB/s over the last 400 hours or so. Not too shabby.
you know, my laptop has the ich8m southbridge, and it supports AHCI, but no Intel drivers past Matrix 8. And I'm pretty sure it supports TRIM.
21 April 2007 - T13e07154r6/ Data Set Management Proposal ATA8-ACS2/ Initial Draft
22 October 2009 – Windows 7 released
26 October 2009 - Intel release f/w update to enable TRIM on their X25M G2 drives
19 March 2010 – Intel’s first TRIM enabled driver - RST 9.6.0.1014
Seems like a life time ago, but its only couple of years.
So, from this data, what is the most enduring drive available in the 200-300 USD range?
oh lord :rolleyes: Your feisty, and I like that :) but then again, so was my last cellmate, and we all know how that ended...... :bananal:Quote:
There are two things you should know - one, its not an M3P. And two, I can totally take you in a fight.
Are you actually going to make use of that endurance? If not, then endurance shouldn't be your primary thought.Quote:
Originally Posted by thegoatman
I am about to make a new build within two months, which will likely be the last one I can afford for at least 4 years, probably more. So I may very well.
Other considerations are price, capacity and bugginess.
Typical yearly writes to an SSD for desktop loads are less then 10 TiB a year.Quote:
Originally Posted by thegoatman
Virtually any SSD can handle that for a few years .... even the old barefoot drives .... the real risk is with the controller or NAND outright failing, or a power surge, or some other kind of instadeath failure.
For $300, you are probably best off with a crucial M4 256gig. Not a particularly special drive by any means, but cheap, generally reliable and well polished. Won't have the highest endurance rating ever, but will still give you a good 600TiB of service before the Media is officially worn out ... and possibly another 1PiB or more afterwards. Not that you would ever reach that point.
right. What about the samsung one? $30 more and it looks to be 30% faster, if I understand the specs properly.
As far as my longevity concerns above go: The way everything I have read made it sound, I was thinking I might get, oh, MAYBE 6 years out of one. I guess that's incorreect.
If you budget stretches enough, the Samsung 830 is a great choice. Fast and reliable.Quote:
Originally Posted by thegoatman
No-one really knows how long you will get out of a drive, that is pretty random .... what I do know is that you are not going to wear it out doing any normal sort of things with your computer any time soon.
Attachment 126013
---
Kingston SSDNow 40GB (X25-V)
895.23TB Host writes
Reallocated sectors : 05 41
Available Reserved Space : E8 99
POH 8036
MD5 OK
33.20MiB/s on avg (~307 hours)
:shock2:Quote:
Originally Posted by Computurd
I can echo the -not going to wear it out doing any normal sort of things with your computer anytime soon.- bit. when I first got my SSDs, I too was under the impression of-extremely fragile/shortlived and followed every SSD tweak guide I could find, which wasn't really much of an issue with me because I have multiple drives to store data to, and got used to it very quickly. My 2 (seemingly unkillable from the testing happening here) X-25V drives stand right at this moment with:Quote:
Originally Posted by canthearu
Power on Hours: 14 929 and 14 978
MWI:99 and 99
Host Writes:1.56TB and 1.70TB
as reported by the intel SSD toolbox (in a RAID0 array- where they have spent ~95% of their life so far)
Todays update:
Intel X25-M G1 80GB
537.63 TiB
22529 hours
Reallocated sectors : 114 to 120
Available Reserved space: 93 to 92
MWI=176 to 169
MD5 =OK
43.06 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=487742
m4
748.1641 TiB
3195 hours
Avg speed 73.08 MiB/s.
AD gone from 185 to 181.
P/E 12938.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=487743
Samsung 830 256 Day 36
846,887.35 GiB
827.03 TiB
290.36 MB/s Average
842 Hours
3691 Wear Leveling Count
MWI 1
0/0 Erase/Program Fail
OCZ Vertex Turbo 64 Day 53
396,957.33 GiB
387.65 GiB
84.60 MB/s Avg
1340 hours
7096 Avg PE count
-100 MWI
0/0/0 Read/Program/Erase Fail
--------------------------------------------------\\
The Samsung 830 finally hit MWI 1 at 1/1/3600 WLC 177.
I'll look through the logs to try and estimate when it hit MWI 1 more precisely.
--------------------------------------------------\\
I'm about to perform some testing on the Octane to see if I can resurect it.
Wish me luck.
You have mixed up the TiB written for the Turbo and the 830
So I took some time to see if I could resurrect the Octane.
Turns out, it wasn't necessary.
THE OCTANE LIVES!!
I'd very much like to take credit for this, that through my vast powers I was able to bring the dead back to life... but it is not so. It just crapped out and needed a power cycle. That is not very desirable behavior from a modern drive, but it's not like it happened once every 30 hours.
Apparently, it just pulled a [insert your own reference here] on me. It just... dropped out. Since I wasn't there to physically confirm this until a short while ago, testing is back on.
Attachment 126061
Attachment 126062
Other business --
OCZ Octane 128GB--
On the power cycle, POH reset but 6 new blocks went bad (while it was sleeping presumably).
OCZ Vertex Turbo 64GB --
Oh, and 1 of the 3 "Indilinx-Specific" SMART attributes have increased from 0 to 13 (attribute D3). I have no idea what this means, but I'd very much like to know.
Samsung 830 256GB --
The 830s CRC Error Count has increased to 2 (attribute C7)
-----------------
Actually, it looks like the Indilinx D3 attribute is SATA Error Count CRC. If the 830 and the VT are having the same problem at the same time, then it could be a host issue (??).
You just experienced the same as I did with the Kingston V+100, and it sucks every time it happens. :down:
Is the Kingston V+ using a Samsung controller or a Toshiba controller?Quote:
Originally Posted by B.A.T
Product # SNV225 = Samsung
Product # SNVP325 = Toshiba
The Kingston V+100 uses an T6UG1XBG from Toshiba.
Patriot Torqx-2 64GB - Day 67
Drive hours: 1,618
ASU GiB written: 109,693.08 GiB (107.12 TiB)
Avg MB/s: 25.43 MB/s
MD5: OK
Bad blocks: 2 grown, 83 factory
Wear cycle counter: 6872 average erase cycles, 10502 maximum erase cycles.
Total ECC Error Count: 1
Intel 520 60GB - Day 59
Drive hours: 1,416
ASU GiB written: 442,356.84 GiB (431.99 TiB)
Avg MB/s: 95.60 MB/s
MD5: OK
Host GB written (F1): 445,423.94 GiB (434.98 TiB, 14253566 raw)
NAND writes (F9): 315,361 GiB (307.97 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 117 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 1
Vertex 4 128GB - Day 6
Drive hours: 160
ASU GiB written: 60,235.34 GiB (58.82 TiB)
Avg MB/s: 146.09 MB/s
MD5: OK
Sector GB written (E8): 61,285.02 GiB (59.85 TiB, 128523997843 raw)
Reallocated sectors (05): 0
Raw Read Error Rate (01): 6
Remaining Life (E9): 93
Note: New Endurance rig appears to be very stable. Not a single crash since starting endurance testing on this motherboard.
Todays update:
Intel X25-M G1 80GB
541.00 TiB
22552 hours
Reallocated sectors : 120 to 123
Available Reserved space: 92
MWI=169 to 163
MD5 =OK
43.02 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=487988
m4
753.8942 TiB
3218 hours
Avg speed 73.09 MiB/s.
AD gone from 181 to 178.
P/E 13033.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=487987
Only 3 days left :D
The Octane... (sigh.) I'm not sure that it dropped out. It seems to have crashed the three programs that make use of SMART info and it's instance of ASU. I had to shut down the rig after months and months of uptime. It's put like 1.5PiB though the controller since it's last reboot.
I have moved the Octane to another rig temporarily to see what the hell is going on.
That is very strange. It probably is not your rig but your are right about testing it in a nother rig to make sure.
Hmmm. I think the Octane is causing some BSoDs in my main system where it's now located. It's hard to be sure, but it seems like it's creating all sorts of random issues. I don't want to lay it all at the feet of the Octane, but it's looking like it.
Reallocations are up to 238 now, but MWI is still at 85.
-----------------------------------------------------
OCZ Octane 128GB Day ??
311,111.64 GiB
303.82 TiB
159.22 MB/s
Reallocations 238
-----------------------------------------------------
OCZ Vertex Turbo Day 55
402,345.40 GiB
392.91 TiB
84.24 MB/s
Avg Erase Count 7193
Program/Erase/Read Failures 0/0/0
1359 Hours
-----------------------------------------------------
Samsung 830 Day 37
866,754.41 GiB
846.45 TiB
288.07 MB/s
Wear Leveling Count: 1/1/3777
Program/Erase Failures 0/0
862 Hours
-----------------------------------------------------
The Endurance Rig was restarted about 2.5 hours ago.
very interesting, what are your thoughts on the octane, rapidly dying?