You can get the same Kingston as I have for £199 each at amazon Run for it!!
Printable View
You can get the same Kingston as I have for £199 each at amazon Run for it!!
Vertex 4 reallocated sectors at 15.
I'm seriously doubting this drive is going to last more then another 100-200TiB.
Intel 520 60GB - Day 88
Drive hours: 2,058
ASU GiB written: 653,647.21 GiB (638.33 TiB)
Avg MB/s: 95.42 MB/s
MD5: OK
Host GB written (F1): 658,293.19 GiB (642.86 TiB, 21065382 raw)
NAND writes (F9): 466,026 GiB (455.10 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 112 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 1
Vertex 4 128GB - Day 35
Drive hours: 844 (556 + 288)
ASU GiB written: 366,203.35 GiB (357.62 TiB)
Avg MB/s: 124.59 MB/s
MD5: OK
Sector GB written (E8): 369,363.89 GiB (360.71 TiB, 486156078177 + 288456133860 raw)
Reallocated sectors (05): 16
Raw Read Error Rate (01): 6
Remaining Life (E9): 39 (69 current - 30)
12 new bad blocks for the vertex 4. Upgrading ASU and restarting testing.
What sort of over-provisioning is there by default on the Vertex 4?
@Anvil
The normal 7% from the conversion of binary gigabytes (GiB) into decimal gigabytes. (GB)
OK, so the norm then.
I normally over-provision ~10% on most drives, especially if they are in a raid.
(during my V4 128GB testing it has been set to 100GB, 19.5GB over-provisioning)
Todays update:
m4
913.7974 TiB
3857 hours
Avg speed 74.35 MiB/s.
AD gone from 91 to 88.
P/E 15749.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=491588
Intel X25-M G1 80GB
633.51 TiB
23169hours
Reallocated sectors : 158 to 159
Available Reserved space: 90
MWI=124
MD5 =OK
42.44 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491592
Intel X25-E 64GB
79.86 TiB
257-30=227 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.23 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491590
Just out of curiosity are you guys doing this with MHDD or similar (cutting the drive/changing the MaxLBA) or is this something else with a custom firmware? The handful of SSD's here I've just cut the drives but haven't really done a lot of stress testing to see the efficacy of that.
None of the drives in the endurance test have been given additional overprovisioning.
Vertex 4 at 21 reallocations now (359.91 TiB in ASU)
Kingston SSDNow 40GB (X25-V)
971.74TB Host writes
Reallocated sectors : 05 43
Available Reserved Space : E8 99
POH 8708
MD5 OK
33.90MiB/s on avg (~55 hours)
Yep, all but 2 or 3 in the last 48h.
The Kingston can go for months and then pop a few sectors.
Re-allocations have been showing movements for a long time though, they just don't accelerate like some other drives tend to do.
On the positive side, it does inform about whats to happen, much too early though.
Lets see how much it can take...
Todays update:
m4
919.4075 TiB
3879 hours
Avg speed 74.34MiB/s.
AD gone from 88 to 84.
P/E 15844.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=491695
Intel X25-M G1 80GB
636.77 TiB
23191 hours
Reallocated sectors : 159
Available Reserved space: 90
MWI=124
MD5 =OK
42.52 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491699
Intel X25-E 64GB
87.55 TiB
279-30=249 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.21 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491697
Samsung 830 256GB Day 63
1,549,609.88GiB
1,513.29 TiB
290.85 MB/s Average
1535 Hours
6732 Wear Leveling Count
MWI 1
6/0 Erase/Program Fail
Used Reserved Block Count: 12/24576 sectors
------------
Another realloc happened last night.
Attachment 127006
I'll update if canthearu posts on the 520.
The plan is to start testing a new drive tomorrow, that is if it gets here.
--
Kingston SSDNow 40GB (X25-V)
974.80TB Host writes
Reallocated sectors : 05 43
Available Reserved Space : E8 99
POH 8735
MD5 OK
33.66MiB/s on avg (~82 hours)
Looks like we are hitting 1 PiB with just a couple of days between us :)
I'm waiting a little with the C300. GullLars might sell me one of his C300 64GB when he updates his raid0 setup.
It could be a close race to 1PB, 1 PiB you should win :)
I noticed the post about the C300, would be great!
I hoped the Samsung 830 64GB could join me all the way but sadly no.....
I wonder how far they can go?!? Looks like only the sky is the limit :)
I really think that 830 64GB could have made it to the moon by now, it's too bad it went through weeks of super high WA. Had it not, it would have had 900TB when I stopped testing.