What we really need is a C300 drive here.
Will probably own the M4.
The main things that affect endurance right now :
-capacity of drive
-SLC or MLC based
-lithographic process of NAND
-WA of the controller
Printable View
What we really need is a C300 drive here.
Will probably own the M4.
The main things that affect endurance right now :
-capacity of drive
-SLC or MLC based
-lithographic process of NAND
-WA of the controller
WTF..Would you give the C300 requests a rest already!
If you want to see another one tested...then go buy one and test it yourself.
Bluestang,
When did the M225 get it's first reallocations? It was pretty far along if I recall. I could go back and look, but it's been so long that it's probably archived on papyrus.
@Christopher,
I threw my 1st Program Fail @ MWI 92 and another @ MWI 89. It stayed at 2 until it died.
Didn't throw an Erase Fail until MWI 49, then another @ MWI 35. No more until after MWI 0. Died with 25.
No Read Fails until 908TB. Died with 43.
I was on XP to around MWI 59, then I switched to Win 7.
I believe you are ahead of the game since running on Win 7 from the start and on FW 1.7...looking good!
Thanks, Bluestang. This drive looks pretty good so far. This VT64 version 2 is really more for vanity -- I want to get some crazy high numbers out of it.
Anyone to test Everest ?
By the way, there have been benches on the OCZ forum for Everest 2, pretty good performance.
You are welcome to become the first. An OCZ Petrol 64gig isn't terribly expensive.Quote:
Originally Posted by kensiko
I thought about the petrol... But then I got another Turbo. Besides, Everest was probably just a bridge product to get to Everest 2. I am holding back some drives to test if the Arrowana FW ever gets released for the original Indilinx................
Vertex Turbo 64 Day 9
63094.42
83.00MB/s
1130 Average Erase Count
78 MWI
216 hours
0/0/0 Program/Erase/Read Failures
Kingston SSDNow 40GB (X25-V)
773.36TB Host writes
Reallocated sectors : 05 28 1 up
Available Reserved Space : E8 99
POH 6898
MD5 OK
33.51MiB/s on avg (~47 hours)
Attachment 124459
Vertex Turbo 64 Day 10
70661.90GiB
83.11MB/s
1258 Average Erase Count
75 MWI
240 hours
0/0/0 Program/Erase/Read Failures
Patriot Torqx-2 64GB - Day 22
Drive hours: 528
GiB written: 31,032.76 GiB (30.3055 TiB)
Avg MB/s: 19.43 MB/s
Bad blocks: 2/0/83
Wear cycle counter: 0/1993/3035
Intel 520 60GB - Day 13
Drive hours: 335
Avg MB/s: 92.82 MB/s
Host GB written (F1): 94,975.19 GiB (92.75 TiB, 3039206 raw)
NAND writes (F9): 67,243 GiB (65.67 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Media Wearout Indicator (E9): 81
Impressive that the X25-V still keeps working.
Have you tried to take it offline for a couple of days and see how that works out :rolleyes:
I bet it will not wake up from that "sleep".
Vertex Turbo 64 Day 11
76972.06GiB
83.20MB/s
1379 Average Erase Count
73 MWI
263 hours
0/0/0 Program/Erase/Read Failures
Kingston SSDNow 40GB (X25-V)
778.92TB Host writes
Reallocated sectors : 05 30 2 up
Available Reserved Space : E8 99
POH 6998
MD5 OK
33.29MiB/s on avg (~96 hours)
So, does anyone here have an Plextor M3/M3P? Neither one has many SMART attributes, and I can't be sure what the attributes even are. If someone knows for a fact that they have a PE/wear leveling count attribute, I'd consider that good enough for testing purposes.
Rumors suggest that the upcoming firmware update (scheduled for April 2012) would enable endurance (MWI) in the SMART for the M3P.Quote:
Originally Posted by Christopher
Vertex Turbo 64 Day 12
84971.76GiB
83.00MB/s
1522 Average Erase Count
70 MWI
290 hours
0/0/0 Program/Erase/Read Failures
Patriot Torqx-2 64GB - Day 24
Drive hours: 575
GiB written: 34,271.21 GiB (33.4682 TiB)
Avg MB/s: 20.24 MB/s
Bad blocks: 2/0/83
Wear cycle counter: 0/2197/3338
Intel 520 60GB - Day 15
Drive hours: 381
Avg MB/s: 93.17 MB/s
Host GB written (F1): 109,998.81 GiB (107.42 TiB, 3519962 raw)
NAND writes (F9): 77,889 GiB (76.06 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Media Wearout Indicator (E9): 77
Vertex Turbo 64 Day 13
90714.05GiB
83.06MB/s
1625 Average Erase Count
68 MWI
309 hours
0/0/0 Program/Erase/Read Failures
Patriot Torqx-2 64GB - Day 25
Drive hours: 598
GiB written: 35,896.30 GiB (35.0550 TiB)
Avg MB/s: 19.92 MB/s
Bad blocks: 2/0/83
Wear cycle counter: 0/2299/3480
Intel 520 60GB - Day 16
Drive hours: 404
Avg MB/s: 93.20 MB/s
Host GB written (F1): 117,808.18 GiB (115.05 TiB, 3769862 raw)
NAND writes (F9): 83,421 GiB (81.47 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Media Wearout Indicator (E9): 75
Vertex Turbo 64 Day 14
97596.50GiB
83.13MB/s
1748 Average Erase Count
66 MWI
333 hours
0/0/0 Program/Erase/Read Failures
Vertex Turbo 64 Day 15
105410.50GiB
83.20MB/s
1893 Average Erase Count
63 MWI
359 hours
0/0/0 Program/Erase/Read Failures
The NAND on your vertex turbo is looking quite excellent (no failures at all so far)
Could be a record setter if this keeps up.
God, I sure hope so. The last one was infuriating, and this one is about to where the last one was when it died.Quote:
Originally Posted by canthearu