Printable View
No, but the two G1 Intel drives aren't using TRIM. Generally speaking, without TRIM W.A. is higher, average speed is lower. If you look in the charts, the drives without TRIM are noted (see Anvil's update a few posts back).Quote:
Originally Posted by AMD_Freak
Samsung 830 256GB Day 56
1,338,797.80 GiB
1,307.41 TiB
293.95 MB/s Average
1325 Hours
5815 Wear Leveling Count
MWI 1
4/0 Erase/Program Fail
Used Reserved Block Count: 8/16384 sectors
Kingston SSDNow 40GB (X25-V)
951.52TB Host writes
Reallocated sectors : 05 42 (up 1)
Available Reserved Space : E8 99
POH 8532
MD5 OK
33.33MiB/s on avg (~20 hours)
Todays update:
m4
873.0461 TiB
3697 hours
Avg speed 74.57 MiB/s.
AD gone from 114 to 111.
P/E 15058.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=490677
Intel X25-M G1 80GB
610.23 TiB
23010 hours
Reallocated sectors : 155 to 156
Available Reserved space: 90
MWI=124
MD5 =OK
42.20 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490676
Intel X25-E 64GB
23,96 TiB
97-30=67 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.42 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490675
Kingston SSDNow 40GB (X25-V)
953.08TB Host writes
Reallocated sectors : 05 42
Available Reserved Space : E8 99
POH 8546
MD5 OK
33.28MiB/s on avg (~33 hours)
Just 1 day to go!
Samsung 830 256GB Day 57
1,362,943.72 GiB
1,331.00 TiB
290.72 MB/s Average
1349 Hours
5919 Wear Leveling Count
MWI 1
4/0 Erase/Program Fail
Used Reserved Block Count: 8/16384 sectors
Kingston SSDNow 40GB (X25-V)
954.25TB Host writes
Reallocated sectors : 05 43 (1 up)
Available Reserved Space : E8 99
POH 8556
MD5 OK
33.26MiB/s on avg (~43 hours)
Tonight, it will be 1 year since the test started. (in about 15 hours)
(it started the 16th of May 2011 at 02:20 AM)
Probably the toughest trial an ssd has endured :shocked:
And quite a testimony of perseverance :up:
Patriot Torqx-2 64GB - Day 90
Drive hours: 2,036
ASU GiB written (first run): 137,907.07 GiB (134.68 TiB)
ASU GiB written (current run): 6,268.46 GiB (6.12 TiB)
ASU GiB written (Total): 144,175.53 GiB (140.8 TiB)
Avg MB/s: 20.57 MB/s
MD5: OK
Bad blocks: 20 grown, 83 factory
Wear cycle counter: 9067 average erase cycles, 13875 maximum erase cycles.
Total ECC Error Count: 1
SATA PHY error count: 250
Intel 520 60GB - Day 82
Drive hours: 1,919
ASU GiB written: 611,308.40 GiB (596.98 TiB)
Avg MB/s: 94.92 MB/s
MD5: OK
Host GB written (F1): 615,608.66 GiB (601.18 TiB, 19699477 raw)
NAND writes (F9): 435,813 GiB (425.60 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 115 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 1
Vertex 4 128GB - Day 29
Drive hours: 718 (556 + 162)
ASU GiB written: 310,567.51 GiB (303.29 TiB)
Avg MB/s: 125.40 MB/s
MD5: OK
Sector GB written (E8): 313,245.90 GiB (305.90 TiB, 486156078177 + 170768184054) raw)
Reallocated sectors (05): 1
Raw Read Error Rate (01): 6
Remaining Life (E9): 52 (82 current - 30)
Lots more bad blocks on the Torqx 2, and the vertex 4 popped it's first bad block!
The write speed on the Torqx shows that it's not really comfortable with the workload, is there some cleaning you could perform.
If you run a typical benchmark, how does it perform?
I wonder if there are factory marked bad blocks on the other drives, the m4 carries that attribute as well as a few others.
What I'm saying is that a few bad blocks is not the end of the world. :)
Some of my C300s, m4s got a lot of bad blocks and they were already there when I got them.
Speaking of the Torqx 2, I shut down the computer after doing some windows updates just after posting the status up.
I wanted to make sure TRIM was active, however the drive decided it was not going to be readable again. I am going to have to secure erase it, then put it back in and not reboot the endurance computer again until it is really dead.
There isn't anything I can do for the Torqx 2 performance wise, it is just a terrible chipset that doesnt handle writes well. it scores pretty poorly for it in benchmarks after all the NAND is initally used.
The V4 is only 10TB ahead of the Octane when it started in with reallocations. Of course, it made it to 300TB in 18 days.Quote:
Originally Posted by canthearu
If you post an update tomorrow and there are more reallocations, I'd start to worry (ala the Octane and both VTs).
Since we were discussing it the other day --
after talking with Intel support, it turns out that 8860 is different from 8850 only because the drives are made in different locations. For some reason, Intel FW gets a new designation when the drive is made at a different factory, so 8860 and 8850 are the same thing.
That's probably not the most elegant way to put it. Oh, and my dead E is out of warranty by a month.
That is just tought luck.... :shakes:
That's just terrible, it doesn't respond to diagnostics or anything at all?Quote:
Originally Posted by Christopher
(your talk to Intel resulted in nothing?)
I emailed them last week, the email told me to call. I called, sat on hold for 40 minutes, then was told I had contacted the wrong department (their phone system doesn't have an SSD department yet), so they transferred me to the right people. I discussed the issues and asked if there was some way to get ahold of the newer firmware (8860) because I could reflash it if I had newer FW (you can't downflash or reflash to the same version). That's when I was told that there was no newer FW than 8850 -- 8860 just means it was made in a different factory.
I can see the SMART data for the drive with Linux, I tried SEing it with PartedMagic, I tried other things as well, but any access of the drive causes the system to hang.
You live, you learn I guess. The lady I spoke with was quite nice, but there's nothing for it...
I was also able to run some diagnostics with linux, so I did quick and extended self tests, but they post passed.
Todays update:
m4
879.2797 TiB
3722 hours
Avg speed 74.55MiB/s.
AD gone from 111 to 107.
P/E 15163.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=490785
Intel X25-M G1 80GB
613.73 TiB
23034 hours
Reallocated sectors : 156
Available Reserved space: 90
MWI=124
MD5 =OK
42.13 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490788
Intel X25-E 64GB
32,52 TiB
121-30=91 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.48 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490789
Will the Intel Tool Box work on the E or is it one of the early uncompatible versions?Quote:
Originally Posted by Christopher
If Intel TB will work with it you can run a full diagnostic scan from the TB.
I'm not sure it would help but I thought it worth mentioning.
Toolbox hangs on drive detection.Quote:
Originally Posted by Hopalong X
Kingston SSDNow 40GB (X25-V)
955.98TB Host writes
Reallocated sectors : 05 43
Available Reserved Space : E8 99
POH 8571
MD5 OK
33.25MiB/s on avg (~59 hours)
:bday:
It survived 1 Year
:bday:
AWESOME! Let me be the first to say congratulations!Quote:
Originally Posted by Anvil
Samsung 830 256GB Day 58
1,387,397.65 GiB
1,354.88 TiB
291.73 MB/s Average
1373 Hours
6024 Wear Leveling Count
MWI 1
4/0 Erase/Program Fail
Used Reserved Block Count: 8/16384 sectors
Thanks!
Lets hope it lasts past 1PiB.
Hard to tell how long it will last, one can only be surprised by what this little drive has done so far.
Attachment 126797
Congratulations!! :clap:Quote:
Originally Posted by Anvil
1 year and the drive refuses to die...