6 more days until the PB! :cool:Quote:
Originally Posted by Anvil
Printable View
6 more days until the PB! :cool:Quote:
Originally Posted by Anvil
The 40GB drive has amazed me!
(got 3 more of them and I'll be keeping them, all of them are in use as boot drives with ~1TB of data written)
The 330 is rather nice as well, when prices settle it should be a great low cost alternative.
I need more time with the V4s, what I can say is that the 256GB drive does not behave like the 128GB.
One more reallocated sector on the X25-V, it is now 46.
MWI on the 330 changed to 99, should be able to find out exactly when using the log-file.
(current values are 21.81TB Host writes, NAND writes are at 15729GB)
Samsung 830 256GB Day 68
1,628,111.97GiB
1,589.95 TiB
279.63 MB/s Average
1615 Hours
7072 Wear Leveling Count
MWI 1
6/0 Erase/Program Fail
Used Reserved Block Count: 12/24572 sectors
It's getting... a little slow.
Just tried a secure erase on the vertex 4, but no dice ... the drive continues to die after a loop or two, disconnecting with the same error experienced before.
At least it seems that the drive lets you get your data off it though ... I guess it is a small blessing.
Vertex 4 being removed from testing with disgust! The end.
Gonna have to start thinking of a new drive to test.
This thread and Anvils app thread got "Sticky" designation. :clap:
About time. :up:
Woot and I see that Anvil even got the MOD tag ...gratz one of the few threads I make a point at looking at daily.
Congratz Anvil :)
My update comes later tonight. This nice weather must be enjoyed first. :cool:
Todays update:
m4
945.7750 TiB
3983 hours
Avg speed 74.36 MiB/s.
AD gone from 74 to 69.
P/E 16292.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=492104
Intel X25-M G1 80GB
652.10 TiB
23295hours
Reallocated sectors : 161 to 162
Available Reserved space: 90
MWI=124
MD5 =OK
42.77 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492108
Intel X25-E 64GB
123.52 TiB
382-30=352 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.08 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492106
Samsung 830 256GB Day 68
1,645,138.28GiB
1,606.58 TiB
284.20 MB/s Average
1632 Hours
7146 Wear Leveling Count
MWI 1
6/0 Erase/Program Fail
Used Reserved Block Count: 12/24572 sectors
Attachment 127120
@canthearu
391.26TiB is the latest recording I've got for the V4, how much did the last effort add to this?
A pity about the V4, much too early.
--
The 330s MWI changed to 98 this afternoon, looks like it'll take a few readings before it stabilizes.
MWI 99
Host Writes F1 (241) 691942*32=21263GiB = 21.11TiB
NAND Writes F9 (249) 15230GB = 14.87TiB
MWI 98
Host Writes F1 (241) 957613*32=30643616 = 29.22TiB
NAND Writes F9 (249) 21086GB = 20.59TiB
Intel 330 120GB
30.64TB Host writes
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 98
[F1] Total LBAs Written 1003997
[F2] Total LBAs Read 22623
[F9] Total NAND Writes 22110GB
POH 106
MD5 OK
122.55MiB/s on avg (~9 hours)
--
Kingston SSDNow 40GB (X25-V)
985.91TB Host writes
Reallocated sectors : 05 46 up 1
Available Reserved Space : E8 99
POH 8831
MD5 OK
36.92MiB/s on avg (~9 hours)
--
Both drives had a short break 9 hours ago, I had to check that MD5 testing was correctly configured for the 330. (Host reads were stuck, all was OK)
... and Thanks!
RIP V4.
I guess there is not much more to do with current SATA technology, the SSD market is going to stabilize until SATA 12 Gbps comes. The question is, which company selling SSD will survive until then? All of them?
@Anvil
The v4 did virtually nothing while in zombie mode, so I'm going to take it from the time of the first error - (maybe 100GB overall added after first error, which is virtually nothing)
Vertex 4 Death Certificate:
Date of Death: 25/5/2012 - 8:15am (UTC +8 Timezone)
Days of Operation: Approx day 39
Cause of Death: Excessive bad blocks cause drive to enter panic lock state during erase phase.
Total ASU Writes are 400,650.26 GiB (391.25 TiB)
Total Host writes as per SMART 403,316.99 GiB (393.86 TiB)
Remaining life: 31 (61 new - 30 used on old firmware)
Disappointing result for a 128gb drive!
Opps, the poor old Intel 520 got left behind in all this commotion:
Intel 520 60GB - Day 93.5
Drive hours: 2,188
ASU GiB written: 693,156.65 GiB (676.91 TiB)
Avg MB/s: 93.47 MB/s
MD5: OK
Host GB written (F1): 698,113.12 GiB (681.75 TiB, 22339620 raw)
NAND writes (F9): 494,215 GiB (482.63 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): 1
The V4 did slightly better than the Octane... Not that either one performed
any kind of acceptable.
Christopher ... I'm less inclined to now believe that you simply got a drive with dodgy NAND. Something else is killing the NAND prematurely.
What could kill just one part of one NAND device? Who knows?Quote:
Originally Posted by canthearu
I've prepped up a new drive, the M3P 128GB. I should start it up soon, but preliminary testing shows that it should be able to just about match the 830 256GB's speed at half the capacity, and that pleases me.
UPDATE
The M3P is baking in the oven now... it doesn't look like the MWI works (I'm terribly angered by this), unless MWI is based on >5KPE cycles or something. Either that, or it's based solely on reallocations (very possible). It's averaging around 270MB/s for the first couple of hours.
@Christopher/ canthearu
The V4 and Octane both used IMFT 25nm? The first post does not indicate the NAND part number. Do you know what it is?
Edit:
According to the info in the first page of the thread there is a consistent premature failure of all drives that have used Indilinx controllers, regardless of model or NAND type used. Only two of the Indilinx drives managed to get past the MWI, but considering the NAND that was used in those drives they should have lasted longer. The other three failed well before the MWI expired.
There is nothing wrong with the Marvell controller. It has been used problem free by Intel & Micron for years. I’d say that this is clear evidence that Indilinx firmware is the problem and not the NAND.
• Crucial M225 64 GB – Samsung 51nm (SLC?) = 880 TB (Exceeded)
• OCZ Vertex Turbo 64 GB – Samsung 51nm (SLC?) = 116 TB (MWI – 58)
• OCZ Vertex Turbo 64 GB – Samsung 51nm (SLC)? = 499 TB (Exceeded)
• Octane 128 GB – Intel 25nm = 303.82 TB (MWI – 85)
• Vertex 4 128GB – Intel 25nm = 393 TB (MWI – 31)
I split the failed drives chart so that the drives that did not meet it's MWI specification are separated in a new chart.
(the original was getting crowded)
Attachment 127128
Attachment 127129
@Christopher
My 330 does not update Host Reads (it needs assistance), not sure how to handle it but it appears to be stuck until it's given a small break. (weird)
Could be the same thing with the M3P, give it some time, it might start moving.
270 MB/s is awesome for a 128GB drive, what are your "settings"?
Anvil, if I’m reading the table in the first post correctly it looks like the Kingston V100+ reached MWI 0 @ 196 TB. It then notched up a total of 368 TB before it died. It used 32nm Toshiba NAND, so I guess the P/E spec was 5K (?). (Actual = 6K+)
I noticed and did find it a bit strange
Host Writes/Capacity is not the same as MWI though so it could be that MWI still had some left.
(will have to go back and find some screenshots or look at the SMART attributes and values)
I can’t remember if P/E specs are based on the minimum or average count. It’s in the thread somewhere and I believe Intel stated it was the minimum, but I can’t be 100% sure.
If it is the minimum then relocations should (in theory) not occur until after the MWI has expired. If it is average it would be reasonable for relocations to occur.
It would be interesting to do a chart to see when relocations first appeared for each drive tested and map them to the P/E cycle count. I started to do it, but its way too much work to go through all the posts to find out. (Not too bad to do if the log files are still available).
Anyway let’s assume that the P/E count is based on the minimum count. A relocation event before the P/E count has expired should not occur. If it does occur it should be a limited and isolated occurrence. Relocations past the MWI should be expected, but as the X25-V and other drives have shown writes can go significantly past the MWI without resulting in major relocations. Compare that to the Octane and V4, which both used IMFT NAND (AFAIK).
$OCZ Octane (Relocations started at MWI 97 and then rapidly accelerated to 226 before total failure of the drive)
$OCZ Vertex 4 128 GB (Relocations started at MWI 52 and then rapidly accelerated to 243 before total failure drive.)
Samsung 830 256 GB – First relocation occurred past the MWI (1,160.90 TB) and has slowly increased to 12 having written a further 446 TB of data.
Edit:
As the MWI is based on the theoretical P/E count it should be possible to determine the combined sum of WA & WL for each drive that has been tested at the point that the MWI expired (assuming the drive reported decent SMART info).
Capacity *P/E spec / ((WA) * (WL)) = Total theoretical write capability
Ao1,
V4 128GB Intel 29F64G08ACME3
Octane 128GB Intel 29F64G08ACME2
The 830 really has 6, and not 12, reallocation events. Somehow, the 830's used reserved block count attribute is double runtime bad block count. Reallocated sector count is 2048 x Used Reserve.
Not sure why this is, exactly as I don't think it's using 2MB blocks, but I don't think it's had 12 reallocations regardless.
Anvil,
I just think Plextor couldn't add a traditional MWI. Like the Octane, the M3P is just using reallocations to determine MWI (the pre 1.03FW already possessed a reallocated sector count). This would have been much easier to add then a "real" MWI counter. All in all, I was very excited to see all the new attributes in 1.03, but it looks as though they're mostly useless (aside from the write counter).
Plextor M3P 128GB Day 0
12,267.39 GiB
11.98 TiB
268.31 MB/s Average
10 Hours
Rellocated Event Count 0
Attachment 127138
Attachment 127139
Samsung 830 256GB Day 69
1,665,964.47 GiB
1,626.91 TiB
299.17 MB/s Average
1653 Hours
7260 Wear Leveling Count
MWI 1
6/0 Erase/Program Fail
Used Reserved Block Count: 12/24572 sectors
The M3P is using the 9174-BLD2, Toshiba TH58TEG702HBA4C 24nm Toggle in 8 packages x4 die x32gbit.
I'm using 39.5 GB (42,479,930,379 bytes) static data.
Test officially started 27-May-2012 02:22:32 hours.