I already have the M3P and Chronos Deluxe. I'm a fan of the Kingston though, and naturally, I also really dig the 830. I very much would like to test an 830 128GB, but I'm already doing the 256GB.
Printable View
I already have the M3P and Chronos Deluxe. I'm a fan of the Kingston though, and naturally, I also really dig the 830. I very much would like to test an 830 128GB, but I'm already doing the 256GB.
Todays update:
m4
860.8958 TiB
3650 hours
Avg speed 74.64 MiB/s.
AD gone from 119 to 117.
P/E 14853.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=490347
Intel X25-M G1 80GB
603.36 TiB
22962 hours
Reallocated sectors : 154
Available Reserved space: 90
MWI=124
MD5 =OK
41.94 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490345
Intel X25-E 64GB
7.23 TiB
(49-30)=19 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
106.09 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490348
http://www.diskusjon.no/index.php?ap...tach_id=490346
The retention test went fine and the G1 is running fine again. Due to bad weather the power was out a couple of hours during the night. Everything is ok now.
Wow, BAT I really thought the X25-E would do an average of around 160MB/s. I really thought it would be faster on average.
Samsung 830 256 Day 55
1,312,193.38 GiB
1,281.43 TiB
292.49 MB/s Average
1298 Hours
5700 Wear Leveling Count
MWI 1
4/0 Erase/Program Fail
Used Reserved Block Count: 8/16384 sectors
----------------------
The 830 is all alone now.
That's too bad about the VT. Only 7 Initial and 3 Erase Bad Blocks. That's not really alot. It gave up cause of all the Bad Read Blocks.
I guess if we want one that works like it's supposed to ...it has to actually be a Crucial :)
Christopher: "Killer of SSD" indeed!
I think you have killed more SSDs then I've owned!
Very sad about the VT though, I thought it would have lasted a fair bit longer to be honest.
I'm responsible for the deaths of 10 or 11 SSDs. Only a couple of those were drives I wasn't trying to kill. I'm up to three dead in the past three days!Quote:
Originally Posted by canthearu
Ha, I only own 10 SSDs :)
The loop start at around 130 MiB/s and climbs to around 160 MiB/s but the 9 sec waiting between each loop pulls the avg down. I can try to shorten that some more.Quote:
Originally Posted by Christopher
B.A.T., you are the Bravest Man on the Face of the Earth.... don't be afraid to experiment. Considering the fact that there is 80GB of SLC on the 64GB E, I wouldn't hesitate to drop the the wait between loops or reduce pause per 1K files deleted. You need all the help you can get.
Thanks for that :)
With 5 sec between each loop the avg increases to 112 MiB/s. I'll try a couple of loops with 2 GB freespace since it so much OP.
Considering how much like the Gen1 80GB it is, I'd say it's performance is pretty damn good.
It really is :)
Maybe I need to treat it like the G1 with regular maintenace. I'll know in a couple of days.
Hmm, the X25-E would probably exceed 10PiB before failing .... gonna be a long wait if it is.
Let it run for some time (until i settles), it is interesting seeing how that drive develops the next few days.
~100MB/s w/o TRIM is pretty good for this workload, as the Intel does no background GC it wont benefit from extra pausing though.
The only cleaning the X25-V gets is the occational cleaning using the Toolbox, usually a few weeks between those.
My drive is still bootable so on it's 1 year day of testing I might try booting it. (3 more days)
I'm curios about how the wmi will perform. Then it's easyer to predict how much time this will take :)
I'm expecting/hoping for more.Quote:
Originally Posted by canthearu
The 64GB is rated for 2 petabytes of random writes, it'll be a long wait.
With an estimated avg speed of 90 MiB/s (I know I'm conservative here) I'll write 2,6 PiB a year.
Anvil has been testing for a year in 3 days and I'm only 6 weeks away from my first year. I'll think I'm up for the challenge :)
I've left the Vertex Turbo in the chart this time, as it wasn't updated in the previous chart.
Attachment 126748
Attachment 126747
Now I'm paranoid about the erase failures on the 830, and I can't stop checking in on it. It made it a good deal beyond MWI before the first reallocation, but now I'm gun shy. I already had to bury the Vertex Turbo in an unmarked grave.
I try to check in on the V a few times per day, it's not much one can do.
I have tried using the default windows driver (still raid mode) and the V was undoubtedly slower, within ~35-40 hours it had dropped below 30MiB/s.
Using the Intel 10 series driver (currently using 10.8) is clearly a winner vs the default one, the V can go for weeks at ~33MiB/s
The Torqx 2 has popped 8 more blocks since yesterday ... I'm preparing the funeral now.
That is a bit early, less than 150 TiB.
The Intel 520 looks to be doing fine.
As long as those blocks aren't all on the same die or plane you should be golden. At least, that's what I keep telling myself.
Todays update:
m4
866.3879 TiB
3671 hours
Avg speed 74.63 MiB/s.
AD gone from 117 to 114.
P/E 14945.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=490490
Intel X25-M G1 80GB
606.44 TiB
22984 hours
Reallocated sectors : 154 to 155
Available Reserved space: 90
MWI=124
MD5 =OK
41.94 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490492
Intel X25-E 64GB
14,87 TiB
71-30=41 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
102.55 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490491
I haven't read all 173 pages but is there any drives in Raid0, Curious on the effects of no TRIM
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...
Congrats on the 1 year birthday
Absolutely amazing .... the X25-V continues to plough on.
Guys, you got more work coming :) We need someone to confirm that this new tech works:
http://www.techpowerup.com/166123/ST...Endurance.html
Samsung 830 256GB Day 59
1,406,466.30 GiB
1,373.50 TiB
294.37 MB/s Average
1393 Hours
6135 Wear Leveling Count
MWI 1
4/0 Erase/Program Fail
Used Reserved Block Count: 8/16384 sectors
Kingston SSDNow 40GB (X25-V)
958.61TB Host writes
Reallocated sectors : 05 43
Available Reserved Space : E8 99
POH 8594
MD5 OK
33.23MiB/s on avg (~82 hours)
Since I power cycled the 830 today, I did the update. 4 hours later, the PE cycle count is still the same. I can't tell you how irritating this is... I bet it takes 72 hours to start incrementing again.
WOW! congrats! I believe that was the impetus for this very thread :)
great to see it go the full year, has anyone ever went back and checked that Japanese website where they were testing their drive? i wonder if it is still going?
btw you guys are awesome, all that have offered up drives are real contributors, and that is reflected in the milliion+ views of this thread.
Truly one of the most epic threads ever :)
Perhaps in commemoration of a truly epic human endeavor Samsung will meet me halfway and fix 177 WEAR LEVELING COUNT!Quote:
Originally Posted by Computurd
I forget to check for firmware updates on the Samsung.
I'm sure we'll get noticed when there is a new one.
Correcting 177 should be an easy fix, at least that's what one would think.
It's actually started increasing again, so it shouldn't be too far off from where it should be. 03 is still the latest FW, but I'm surprised there haven't been any since. It took only 9 or so hours to start increasing again, not 72.Quote:
Originally Posted by Anvil
Todays update:
m4
888.4214 TiB
3758 hours
Avg speed 74.48 MiB/s.
AD gone from 107 to 102.
P/E 15319.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=490861
Intel X25-M G1 80GB
618.88 TiB
23070 hours
Reallocated sectors : 156
Available Reserved space: 90
MWI=124
MD5 =OK
42.06 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490863
Intel X25-E 64GB
45.09 TiB
157-30=127 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.49 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490862
Patriot Torqx-2 64GB - Day 92 - Not running
Drive hours: 2,036
ASU GiB written (previous run): 144,175.53 GiB (140.8 TiB)
ASU GiB written (current run): 0.00 GiB (0 TiB)
ASU GiB written (Total): 144,175.53 GiB (140.8 TiB)
Avg MB/s: 0 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 84
Drive hours: 1,964
ASU GiB written: 625,572.45 GiB (610.91 TiB)
Avg MB/s: 95.40 MB/s
MD5: OK
Host GB written (F1): 630,028.75 GiB (615.26 TiB, 20160920 raw)
NAND writes (F9): 446,021 GiB (435.57 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 31
Drive hours: 759 (556 + 203)
ASU GiB written: 329,433.46 GiB (321.71 TiB)
Avg MB/s: 125.83 MB/s
MD5: OK
Sector GB written (E8): 332,337.96 GiB (324.55 TiB, 486156078177 + 210807149746 raw)
Reallocated sectors (05): 1
Raw Read Error Rate (01): 6
Remaining Life (E9): 48 (78 current - 30)
Time to attempt to resurrect the Torqx 2 drive --- again!
Kingston SSDNow 40GB (X25-V)
960.52TB Host writes
Reallocated sectors : 05 43
Available Reserved Space : E8 99
POH 8611
MD5 OK
33.22MiB/s on avg (~98 hours)
Attachment 126848
Attachment 126847
The Vertex 4 is getting close to 3K which is spec for the NAND. (according to some review sites)
A few weeks back, I tried to calculate how many PE cycles the V4's firmware associated with MWI. It looked as though the MWI was based on 7K PE cycles. Canthearu's V4 only had 100TB back then, so maybe I did something wrong. But the flash is only 3K rated.
Based on MWI it looks to aim for ~5K.
(~2700 cycles and 48% remaining)
Samsung 830 256GB Day 60
1,427,874.66GiB
1,394.41 TiB
282.48 MB/s Average
1415 Hours
6204 Wear Leveling Count
MWI 1
5/0 Erase/Program Fail
Used Reserved Block Count: 10/20480 sectors
Well, MWI is going down a lot quicker for the V4 on 1.4RC.
Typical OCZ to cheap out on the NAND and not tell anyone.
It does seem to be decreasing faster on 1.4RC6. In the calculations I performed, the MWi was at 88 and I assumed 115GB per PE cycle. At the time, it worked out to around 7K PE cycles that MWI was based on. They may have tweaked it for RC6.Quote:
Originally Posted by canthearu
So, if I'm reading the charts correctly, currently the highest endurance drives are Intel & Samsung?
Also, just to clarify, Anvil, does your utility do any crc checks of the data in the read cycle (i.e. will it catch any errors if the drive mis-writes or mis-reads them back to your application?) Basically seeing if we have the data here that would also help bound bit error expectations on the drives that are being tested.
The second chart shows estimated current PE cycle count for presently running drives (not the past drives). So far Intel, Crucial, and Samsung are doing the best, but then, 6 of the 8 are made by those three companies. And they each own fabs, so it shouldn't be that surprising.Quote:
Originally Posted by stevecs
There is a MD5 test which is being performed every n loops, default is every 5 loops.Quote:
Originally Posted by stevecs
I perform the test on a ISO image, about 2GB in size.
(the file doesn't sit on the drive, it's copied to the drive when testing is due, in case there is an error it is reported)
Nope, the Torqx 2 is finished. While it did secure erase and I was able to push slightly more data to it ... windows event viewer is continually reporting write errors and ASU is unresponsive. I think it also crashed my endurance rig/HTPC last night.
My last status update is probably accurate enough for this drive. Add on 5TiB if you care.
Torqx 2 = dead and unloved :)
Like my MTRONS and Turbos and Octane, it too is an also-ran. The Phison needs some work.
The departure of the Torqx 2 was expected, not overly impressive.
I'm debating what to use as the next drive, the SF drives have been done almost to death and so I'm looking at something else.
There are some great offers on 128GB Petrol, Octane and m4, some of them have been done (Octane) and the m4 is currently being tested in 64GB capacity.
Late last night I started thinking about testing 3K drives, i.e. Intel 330 or the Kingston HyperX 3K, they are both interesting drives but then we are back on the SF controller...
(still got the Force 3 though, could do some other compression ratio testing...)
3K units are very interesting and the plextor m3/m3p would have been a good contestant. :)
Im looking forward to that to see what toshibas 24nm nands doing :)Quote:
Originally Posted by B.A.T
Todays update:
m4
895.2967 TiB
3785 hours
Avg speed 74.44 MiB/s.
AD gone from 102 to 98.
P/E 15435.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=490951
Intel X25-M G1 80GB
622.76 TiB
23097 hours
Reallocated sectors : 156 to 157
Available Reserved space: 90
MWI=124
MD5 =OK
42.03 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490955
Intel X25-E 64GB
54.54 TiB
184-30=154 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.46 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490953
Still deciding if I should throw a sandisk extreme 120gig into the mix .... they are quite inexpensive, and would be interesting to test the 24nm NAND.
That is an interesting drive!
I was considering that one but the shop that sells them extremely cheap doesn't sell to businesses. (I won't get a tax refund)
Looks like the Intel 330 could be it!
Plextors are still too expensive here, the M3P (~$260) is more or less 2x the price of a SanDisk Extreme and about $50 more than most other drives like the Intel 520 (~$210), almost $100 more than an m4 ($165).
I happen to not be using my 128GB M3P at the moment... It has host writes and MWI now...
Actually, I'm not using most of my drives. But I really want to test the M3P!
They're $210 here at the moment, but the 128GB 830 is only $109 this weekend, so if I were making a buying decision, I'd take the 830. Since I already own the M3P, the choice is clear.
Can anyone think of a good reason not to test it?
I won't be entering a M3P so feel free :)
Agility 4s are starting to surface, wonder whats up with that vs Vertex 4?
Not much info on the Agility 4, this is all I have found on the 128GB (Agility 4 Max R/W 400 MB/ 300 MB sec)
Samsung 830 256GB Day 61
1,452,304.28GiB
1,418.26 TiB
297.51 MB/s Average
1438 Hours
6311 Wear Leveling Count
MWI 1
5/0 Erase/Program Fail
Used Reserved Block Count: 10/20480 sectors
Intel 520 60GB - Day 86
Drive hours: 2,011
ASU GiB written: 637,689.27 GiB (622.74 TiB)
Avg MB/s: 95.42 MB/s
MD5: OK
Host GB written (F1): 642,255.88 GiB (627.20 TiB, 20552188 raw)
NAND writes (F9): 454,676 GiB (444.02 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 108 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 1
Vertex 4 128GB - Day 33
Drive hours: 801 (556 + 245)
ASU GiB written: 345,315.27 GiB (337.22 TiB)
Avg MB/s: 123.96 MB/s
MD5: OK
Sector GB written (E8): 348,370.44 GiB (340.21 TiB, 486156078177 + 244429690650 raw)
Reallocated sectors (05): 4
Raw Read Error Rate (01): 6
Remaining Life (E9): 44 (74 current - 30)
Hmm, 3 more bad blocks in the last 48h. Hopefully this vertex 4 isn't following the same path as the octane before it.
Might not be a good idea to flash to 1.4 as SMART values are reset.
The next 48hours should tell if there is something going on, there shouldn't be that much in common with the Octane except for the casing.
Except for the same people writing the firmware!Quote:
Originally Posted by Anvil
Todays update:
m4
901.3566 TiB
3809 hours
Avg speed 74.39 MiB/s.
AD gone from 98 to 95.
P/E 15538.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=491341
Intel X25-M G1 80GB
626.27 TiB
23121hours
Reallocated sectors : 157 to 158
Available Reserved space: 90
MWI=124
MD5 =OK
42.19 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491343
Intel X25-E 64GB
62.85 TiB
208-30=178 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.36 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491345
It's like looking at grass grow but now it's only 2 weeks left before 1 PiB is broken :)
I'm also considering to throw in a C300 128GB since Vapor never returned here. Got a couple of them laying around and it could be interesting to compare with the m4.
@canthearu
I forgot about that one :)
@B.A.T
Looking good, not much variation in speed on the E.
A C300 would be great!
Can you manage all the drives on one rig :)
I'll order something by Monday!
I got 8 SATA ports on that motherboard so no problem. Just need to manage some power and sata cables behind the hdd cage.
Next time I'll remove the Torqx 2 from the chart.
Attachment 126897
--
Kingston SSDNow 40GB (X25-V)
966.06TB Host writes
Reallocated sectors : 05 43
Available Reserved Space : E8 99
POH 8659
MD5 OK
37.93MiB/s on avg (~6 hours)
@canthearu
Is there anything you'd like to add or adjust on the Torqx 2 summary?
(the list is updated in post #1)
@Anvil
You need to change model name to Torqx 2.
Also, the Torqx 2 was showing a lot of write failures in the windows log and extremely unresponsive at the end.
I'm running now 1155 Z77 board now if that makes a difference if you want to put it in.
I'll fix it.
When did you make the change to Z77?
I think I'm going to skip IB, a bit surprised that it's hotter than SB, maybe they can get it fixed in some revision.
About when I got the vertex 4 (probably 1 week after) I got the Z77 board along with an i3-2120
IB Board: Maybe
IB CPU: Probably Not
That is a good point, chipset USB3 and probably Thunderbolt on some boards.
(must check)
A bit random, but somehow I think this thread will be running for a very long time.
The vast bulk of the NAND market is for mobile devices. Performance for mobile devices is more dependent on larger block performance, hence continuing increases in page sizes as NAND geometry shrinks. This of course is not helpful for SSD’s, so as page sizes increase and NAND geometry shrinks SSD controllers become more complex. Geometry shrinks get progressively harder, but the limit is still not known. The pace of geometry shrinks (and the resulting changes in NAND composition) is really the technology driver for SSD’s. The controllers have to keep up. In this context it’s easy to see that controllers have a very limited life span and consequently I think this is why the controller market has consolidated.
The very structure of NAND may change altogether.
Attachment 126930
NAND die shrinks
Attachment 126932
Attachment 126933
Bring on the 3D ReRAM :)
Attachment 126934
Samsung 830 256GB Day 63
1,495,909.52GiB
1,640.85 TiB
292.17 MB/s Average
1415 Hours
6500 Wear Leveling Count
MWI 1
5/0 Erase/Program Fail
Used Reserved Block Count: 10/20480 sectors
Todays update:
m4
907.8599 TiB
3834 hours
Avg speed 74.36 MiB/s.
AD gone from 95 to 91.
P/E 15648.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=491478
Intel X25-M G1 80GB
630.06 TiB
23146 hours
Reallocated sectors : 158
Available Reserved space: 90
MWI=124
MD5 =OK
42.33 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491482
Intel X25-E 64GB
71.77 TiB
233-30=203 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.31 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491480
With this speed on the E it'll write 3.6 PiB the next year :shocked:
Quote:
Originally Posted by B.A.T
I'm not 100% convinced that you can actually wear out the E's 50nm SLC unless you're doing full span high QD random writes... who knows?:shrug:
First I need to find out how long it takes to mwi=1%. Then it's possible to do some predictions.
You could reset the timed workload media workload and it would be possible to tell quite quickly how long it will take for the MWI to expire.
What I found with the 830 is that 4k RW did not wear out the drive any quicker because the write speeds were so slow in comparison to the normal ASU workload. I would suspect that 4K RW at QD 34 would help reduce wear whilst maintaining a higher write speed, but it would be interesting to experiment and monitor using the workload timer. Lol, I paid £600 each for 2 of the X25-E’s when they very first came out and now I see Christopher picks one up for peanuts. I’ll keep my eye out for one.