I'm glad you tested the power-off data retention on the Intel. Do you remember how many days it was powered off?
Printable View
I'm planning on doing the data retention test on both of my drives at ~500TiB, I was thinking of 4-5 days completely disconnected.
Just for the record, the Toshiba toggle mode NAND used on the SF2 drives are 32nm, not 34nm.
I rebooted the pc last night so the drives have been up for 24 and a few minutes.
(the pc was online for 17 days)
Kingston SSDNow 40GB (X25-V)
453.22TB Host writes
Reallocated sectors : 12
MD5 OK
35.28MiB/s on avg (~25 hours)
--
Corsair Force 3 120GB
01 94/50 (Raw read error rate)
05 2 (Retired Block count)
B1 66 (Wear range delta)
E6 100 (Life curve status)
E7 17 (SSD Life left)
E9 311167 (Raw writes)
F1 414179 (Host writes)
MD5 OK
106.73MiB/s on avg
power on hours : 1218
B1 is down from 69 to 66 this time, same reduction as E7 (MWI).
I got a Windows detected a hard disk problem pop up message, but everything appears to be fine. It triggered for the Mushkin, but for no apparent reason. All SMART stuff seems to be unchanged from last night, still 5 retirements.
Mushkin Chronos Deluxe 60 Update, Day 45
3.3.2FW
05 5
Retired Block Count
B1 11
Wear Range Delta
F1 442911
Host Writes
E9 341716
NAND Writes
E6 100
Life Curve
E7 10
Life Left
Average 128.95MB/s Avg
Intel RST drivers, Celeron G530 Biostar TH67+
1043 Hours Work
Time 1 month 13 days 11 hours
12 GiB Minimum Free Space
I got an email from CDI with the same Health Bad warning, not sure why either.
Why would Windows and CDi just now decide the drive was about to die? Its been at MWI 10 for weeks.
And I'm back. First something completely off topic :)
http://www.diskusjon.no/index.php?ap...tach_id=466662
On topic
Second: The M4 is dead. Just like the Samsung 470 it couldn't last without power for some time, in this case 9 days. I've tried to power on and off, and i several pc but no luck. Do you have any ideas I should try?
Third: The MTRON is something wrong with. I've tried it in my foldingrig but without any luck. I get the same problems as before and the system feels sluggish and sometime hangs. I'm going to send it back to GullLars and he can rma it. They come with 5 years warranty som he might get something new and shiny :)
The Intel X25-M G1 and the Kingston V+100 is back in the test again and all looks normal at this moment.
Great picture of the new Tech support crew. :up::welcome:
The M4 was giving problems before this? If so, I guess I missed the posting.:(
awww! So cute! Congrats again man!
Wow! That's out of the blue! I was hoping it would make it to 1PB. Looks like Vertex Turbo is the one which has the 1PB torch in hand now.
May be we should take a break on Vertex Turbo and have it sit idle, powered off for few days to see if it still keeps going! I have a vague memory that bluestang has been powering it off during the day on working days.
It seems that the MWI might not be so overly conservative after all. 1 year to hold data without a charge after the MWI has expired seems excessive. I wonder how much the MWI would change if the requirement to hold data changed to 3 months as it is with enterprise.
Zads :stick: :D
It is rated at 1 year after hitting MWI-1.
How far was the M4 past the MWI-1?
It hit MWI-1 at 178TiB. It was up to around 600TiB of writes if memory serves.
Way past MWI 1. If it had been stopped at that point it should have held its data as speced.
After that holding data is questionable to length of time.
Same as asking how long it will continue to write data.
You are all making the new specs with the testing. :up:
This was my last result update.
m4
768.5687 TiB
2749 hours
Avg speed 88.43 MiB/s.
AD gone from 171 to 169.
P/E 13330.
Value 01 (raw read error rate) has changed from 43 to 46.
MD5 OK.
Reallocated sectors : 00
The M4 passed MWI-1 at 170.8 TiB.
There were no problems before I turned my rig off the 28th oct. It just didn't like 9 days without power.
Sad... I was really hoping to see M4 past 1TB. Maybe P/E rating is not conservative at all considering the requirements. I believe it would be better to add a 7-14 days of rest between each 100TB milestone, to check data retention.
It's not like it was expected to fail but we are way beyond the specs :)
The spec is 72TB for the Crucial iirc.
I don't think it matters if the pause was 7 or 9 days, it might fail withing hours of disconnecting but we will never know what really happened to B.A.T's drive. It would have been interesting to know if it was a NAND failure or some other part that caused the failure.
As a result of this failure I'll be playing it a bit safe on my drives, I'll start off with 12 hours and then increase in 12hour steps up to 4-5 days.
My drives are turning 500TiB within a few weeks, the Force 3 is not down to MWI 0 yet though, it will be before it hits 500TiB.
Too bad to see the M4 die like that. BUT where is the C300. That should be able to do 1 PB I think quite easily. Vapor, where are you LOL ???
So it looks as though even though the M4 had no bad blocks, the NAND just couldn't hold a charge in each cell without power. If that is the case, you'd expect the Vertex Turbo to go much longer while retaining data. I guess at some point these drives just become volatile storage, but I'm more than a little surprised that the M4 never flagged any of these blocks as anything but good.
I still don't know why Crystal Disk Info keeps emailing me with [601] and [701] BAD messages, nor why Windows thinks the Mushkin is dying too. Perhaps they know something I don't?
You should be able to disable the emails, the CDI messages are most likely based on SMART, there is no other source of info for the drives.
(unless there are issues related to the drive that are found in the Event log, as in e.g. timeouts, which is not very likely as it should show in other ways)
Of course I can disable the emails, but nothing has changed with the Mushkin in weeks, really. Looking at the SMART data, I can't determine why it is that Windows and CDI seem to think there is something wrong.
The Event Viewer does show a couple of generic SMART based "your drive is going to die" errors. I was just wondering why - if it's based on MWI, then why didn't Windows protest much earlier? It's been at MWI 10 for almost 200TB, and that's the only questionable SMART attribute. I had set up the CDI emails to alert me if anything interesting had happened while I was away, and I'm more curious as to why Windows has a problem now, and not earlier if it's just based on MWI depletion.
Kingston SSDNow 40GB (X25-V)
455.80TB Host writes
Reallocated sectors : 12
MD5 OK
34.10MiB/s on avg (~47 hours)
--
Corsair Force 3 120GB
01 90/50 (Raw read error rate)
05 2 (Retired Block count)
B1 64 (Wear range delta)
E6 100 (Life curve status)
E7 16 (SSD Life left)
E9 317600 (Raw writes)
F1 422741 (Host writes)
MD5 OK
106.85MiB/s on avg (~47 hours)
power on hours : 1240
B1 is down from 66 to 64.
@Christopher
It would have helped if you posted some screenshots (I know they don't work)
CDI is not some magical tool, it reports when values are below thresholds, some SMART values are said to predict failures and some are not. If the SMART value is said to be predicting failure it's likely that CDI will generate an event/warning.
The SMART attributes that predict failure are the following (for a typical SF2xxx series drive)
1, 5, C4, E6 and E7
Mushkin Chronos Deluxe 60 Update, Day 46
3.3.2FW
05 5
Retired Block Count
B1 10
Wear Range Delta
F1 453641
Host Writes
E9 350000
NAND Writes
E6 100
Life Curve
E7 10
Life Left
Average 132.11MB/s Avg
Intel RST drivers, Celeron G530 Biostar TH67+
1066 Hours Work
Time 1 month 14 days 10 hours
12 GiB Minimum Free Space
-----------------------------------------------------------
I feel like I'm really making some progress now. Host writes just hit 350TB, and speed seems to be marginally higher.
I traded out another drive for my FW0001 M4 64GB drive last weekend, and I've been playing with it. The lack of SMART attribs to capture host writes is irritating though.
Kingston SSDNow 40GB (X25-V)
457.38TB Host writes
Reallocated sectors : 12
MD5 OK
33.79MiB/s on avg (~61 hours)
--
Corsair Force 3 120GB
01 94/50 (Raw read error rate)
05 2 (Retired Block count)
B1 63 (Wear range delta)
E6 100 (Life curve status)
E7 14 (SSD Life left)
E9 321580 (Raw writes)
F1 428041 (Host writes)
MD5 OK
106.87MiB/s on avg (~47 hours)
power on hours : 1255
B1 is down from 64 to 63.
M225->Vertex Turbo 64GB Update:
693.57 TiB (762.58 TB) total
1816.79 hrs (Torture), 2615 hrs (Power-On)
13716 Raw Wear
122.49 MB/s avg for the last 69.19 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count (Realloc Sectors) from 11 to 12.
(1=Bnk 6/Blk 2406; 2=Bnk 3/Blk 3925; 3=Bnk 0/Blk 1766; 4=Bnk 0/Blk 829; 5=Bnk 4/Blk 3191; 6=Bnk 7/Blk 937; 7=Bnk 7/Blk 1980; 8=Bnk 7/Blk 442; 9=Bnk 7/Blk 700; 10=Bnk 2/Blk 1066; 11=Bnk 7/Blck 85; 12=Bnk 4/Blk 3192)
I have no plans on doing a power-off state on the M225 until I reach 1 PB :)
P.S. -- Any mods reading this thread want to get the darn attachments fixed already!
You guys all missed a key milestone. :p: This thread has passed ˝ million views :up: