2 years is a long time to test :shocked:
I need to develop some routine for SE. To bad intel closed off the toolbox for G1, because then it would have been real easy.
Printable View
2 years is a long time to test :shocked:
I need to develop some routine for SE. To bad intel closed off the toolbox for G1, because then it would have been real easy.
That's kind of a tough problem to solve. If you assume that the flash in the G1s lasts twice as long as the 34nm flavor, and you have twice as much of it as a X25-V, then factor in the sustained write speed (very similar to the X25-V)...
And you have a problem.
One thing you (potentially) could do to keep speed higher for longer is over provision the drive, but that's just going to make the drive last even longer...
Stopping to secure erase the drive ever few days: takes a lot more time, and more direct supervision.
B.A.T., you have your work cut out for you...
Of course, the M4 might last for another couple years too. Who knows? I would hate to bet against it at this point. And so far every drive has been a little surprising, but none more so than the M4. It's too bad the drives don't explode when they're done. That would be way more exciting.
I'll just have to find a way. SE every 2 day takes 5 min so it might be possible. It will be less work when the m4 is finished, but that might take weeks. It still very impressive even if the ecc has started to work.
All of the drives have been impressive. Maybe not the F40-A. But the M4 and both Intels are certainly impressive. The M4 is just getting "broken in".
Kingston SSDNow 40GB (X25-V)
427.32GB Host writes
Reallocated sectors : 12
MD5 OK
33.39MiB/s on avg (~84 hours)
--
Corsair Force 3 120GB
01 92/50 (Raw read error rate)
05 2 (Retired Block count)
B1 83 (Wear range delta)
E6 100 (Life curve status)
E7 35 (SSD Life left)
E9 248616 (Raw writes)
F1 331003 (Host writes)
MD5 OK
102.55MiB/s on avg (~84 hours)
power on hours : 990
B1 (WRD) is down again, from 84 to 83.
There is something you could try and that is simply filling the drive with large block sequential writes and then delete the file.Quote:
Originally Posted by B.A.T
It won't be the same as TRIM of course but that was the "old" way of doing it, it can be done from ASU but the options is not available in the "open" beta.
Okay, my first ssd was the G2 so I've never tried those things before. What is the most easiest approach?
I've copied acronis true image backup files to a striped raid array before, as its just one huge file (like 20 GB). Then you just delete it. I'm not sure how well it worked as I was trying to prevent performance degradation, so it wasn't terribly slow yet. Plus, that was with OPed G2 X25-Vs. The G2s were more resilient to begin with, so you may want to experiment with something like HD tach to take a performance baseline, then copy some huge .ISO/.tib/.whatever files and determine efficacy.
I can try something like that, it can actually just be a large zip file too. I'll test this tonight.
How long before the 320 is really dead with the slowing writes and all that ?
Todays update without screenshots. The forum just won't cooperate tonight. I'll put them in later in an edit.
m4
764.2669 TiB
2735 hours
Avg speed 88.25 MiB/s.
AD gone from 174 to 171.
P/E 13257.
Value 01 (raw read error rate) has changed from 30 to 43.
MD5 OK.
Reallocated sectors : 00
Kingston V+100:
185.1462 TiB
732 hours
Avg speed 75.81 MiB/s
AD gone from 17 to 8.
P/E?
MD5 OK.
Reallocated sectors : 00
Intel X25-M G1 80GB
13,7370 TiB Host writes
18696 hours
Reallocated sectors : 00
MWI=86 to 79
MD5 OK
52.08 MiB/s on avg
Filling the remaining space with a large file and deleting it worked like a charm. I'll just do that at the same time I update the screenshot
MTRON
Today I tried it on my work laptop without any luck. I get the same problems I had yesterday.
Kingston SSDNow 40GB (X25-V)
428.58GB Host writes
Reallocated sectors : 12
MD5 OK
33.31MiB/s on avg (~95 hours)
--
Corsair Force 3 120GB
01 85/50 (Raw read error rate)
05 2 (Retired Block count)
B1 82 (Wear range delta)
E6 100 (Life curve status)
E7 34 (SSD Life left)
E9 251665 (Raw writes)
F1 335055 (Host writes)
MD5 OK
102.54MiB/s on avg (~95 hours)
power on hours : 1001
B1 (WRD) is down again, it's now at 82.
I cant seem to upload any files either, so I'm going to post them when I can. I'm 450 miles away at the moment, but I've got screen captures so I'll handle that tomorrow... if XS cooperates.
Any more news about the Samsung and the 320 drives ? Vapor ?
Kingston SSDNow 40GB (X25-V)
430.00GB Host writes
Reallocated sectors : 12
MD5 OK
33.24MiB/s on avg (~108 hours)
--
Corsair Force 3 120GB
01 92/50 (Raw read error rate)
05 2 (Retired Block count)
B1 81 (Wear range delta)
E6 100 (Life curve status)
E7 33 (SSD Life left)
E9 255090 (Raw writes)
F1 339608 (Host writes)
MD5 OK
102.56MiB/s on avg (~108 hours)
power on hours : 1013
B1 (WRD) is down again, it's now at 81.
Any chance of some insights into why the B1 values are so different between the three SF drives currently being tested? SF drives are supposed to limit the delta between most and least worn blocks, yet even Christopher’s drive seems to be above the parameters that SF specify. :shrug:Quote:
Originally Posted by zads
Ao1, mine is at 9 now.
M225->Vertex Turbo 64GB Update:
601.75 TiB (661.63 TB) total
1610.39 hours
12071 Raw Wear
117.32 MB/s avg for the last 17.49 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count (Realloc Sectors) at 10.
(1=Bank 6/Block 2406; 2=Bank 3/Block 3925; 3=Bank 0/Block 1766; 4=Bank 0/Block 829; 5=Bank 4/Block 3191; 6=Bank 7/Block 937; 7=Bank 7/Block 1980; 8=Bank 7/Block 442; 9=Bank 7/Block 700; 10=Bank 2/Block 1066)
Kingston SSDNow 40GB (X25-V)
431.31GB Host writes
Reallocated sectors : 12
MD5 OK
33.19MiB/s on avg (~120 hours)
--
Corsair Force 3 120GB
01 92/50 (Raw read error rate)
05 2 (Retired Block count)
B1 80 (Wear range delta)
E6 100 (Life curve status)
E7 32 (SSD Life left)
E9 258282 (Raw writes)
F1 343849 (Host writes)
MD5 OK
102.58MiB/s on avg (~120 hours)
power on hours : 1025
B1 (WRD) is down again, from 81 to 80.
Looks like Vertex Turbo is going to overtake M4....:D This is a good race! An old timer and the new kid on the block.
Kingston SSDNow 40GB (X25-V)
432.82GB Host writes
Reallocated sectors : 12
MD5 OK
33.15MiB/s on avg (~133 hours)
--
Corsair Force 3 120GB
01 92/50 (Raw read error rate)
05 2 (Retired Block count)
B1 79 (Wear range delta)
E6 100 (Life curve status)
E7 31 (SSD Life left)
E9 261885 (Raw writes)
F1 348640 (Host writes)
MD5 OK
102.58MiB/s on avg (~133 hours)
power on hours : 1038
B1 (WRD) is down again, from 80 to 79.
Updated MWI/B1 graph with a trend line added. Wear levelling between least and most worn blocks is so different its looks like three completely different drives.
@One_Hertz. Anything interesting from the post mortem?
http://imageshack.us/photo/my-images/546/unledaoa.png/
That one drive has 25nm Micron and the other has 51nm Samsung is a little surprising. If they end up pulling close to each other at the end, I think some of the rules might not apply.Quote:
Originally Posted by devsk
Ao1,
I could try to add more static data to the Mushkin. Isn't the force 3 using 45GB of static data?
no, I meant vertex writes faster (by about >20%) than M4 and still going. So, it has the chance to overtake M4. But realistically, I have a feeling that its gonna get tired and die before it overtakes M4. But we will see. That's the reason why this race is exciting...:)Quote:
Originally Posted by Christopher