SSD Write Endurance 25nm Vs 34nm

[Anvil]

Kingston SSDNow 40GB (X25-V)

461.49TB Host writes
Reallocated sectors : 12

MD5 OK

33.39MiB/s on avg (~98 hours)

--

Corsair Force 3 120GB

01 92/50 (Raw read error rate)
05 2 (Retired Block count)
B1 66 (Wear range delta)
E6 100 (Life curve status)
E7 12 (SSD Life left)
E9 331905 (Raw writes)
F1 441785 (Host writes)

MD5 OK

106.93MiB/s on avg (~98 hours)

power on hours : 1291

B1 is 2 up from last reading : from 64 to 66.

[bulanula]

I think this just goes to show that 50nm > 34nm > 25nm. It is just physics. No amount of controller mambo-jumbo black magic voodoo will stop the NAND from losing charge and other such stuff at those small sizes etc. Electron loss is more pronounced the smaller the cells get I think etc.

I think the old Vertex drive still has some way to go before it dies. If you turn it off it would be quite nice to know what happens etc.

Where is Vapor / C300 ?

[Christopher]

Mushkin Chronos Deluxe 60 Update, Day 49
3.3.2FW

05 7
Retired Block Count

B1 11
Wear Range Delta

F1 476018
Host Writes

E9 367276
NAND Writes

E6 100
Life Curve

E7 10
Life Left

Average 130.52MB/s Avg
Intel RST drivers, Celeron G530 Biostar TH67+

1115 Hours Work
Time 1 month 16 days 11 hours

11 GiB Minimum Free Space

-------------------------------------------------------------

I figured out what the cause for CDI and Windows error messages was -- it turns out that the Raw Read Error rate is dipping below threshold periodically. It's currently at 42, but it goes up and down constantly. When RRER goes below threshold CDI and Win7 figure the drive is bad. I don't know what the hell RRER actually is, but it seems more like some kind of timer than anything else.

UPDATE
Within the last few minutes I got another realloc. Thats 8 now, and they're gettin more frequent. That's 3 prog fails, 2 erase fails, and 3 that didn't count towards those two catagories.

[Anvil]

Kingston SSDNow 40GB (X25-V)

462.52TB Host writes
Reallocated sectors : 12

MD5 OK

32.70MiB/s on avg (~109 hours)

--

Corsair Force 3 120GB

01 94/50 (Raw read error rate)
05 2 (Retired Block count)
B1 67 (Wear range delta)
E6 100 (Life curve status)
E7 11 (SSD Life left)
E9 334511 (Raw writes)
F1 445253 (Host writes)

MD5 OK

104.89MiB/s on avg (~109 hours)

power on hours : 1302

B1 is 1 up from last reading : from 66 to 67.

Not sure what is going on, it has dropped 2MiB/s in speed just overnight, maybe it's fighting the Wear Range Delta.

Also, E7 is now almost at the end of the line. (it stops reporting at 10)

[bluestang]

M225->Vertex Turbo 64GB Update:

712.20 TiB (783.07 TB) total
1859.80 hrs (Torture), 2664 hrs (Power-On)
14051 Raw Wear
118.79 MB/s avg for the last 22.33 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count (Realloc Sectors) from 12 to 13.
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
13=Bnk 7/Blk 280

[devsk]

Without updates on M4, this thread feels so empty...

[bluestang]

Looks like I'll need to hit around 17800-17900 P/E cycles to hit 1 PB.

[Christopher]

Looks like I'll need to hit around 17800-17900 P/E cycles to hit 1 PB.

You can do it. I have faith.

That's not even twice the rated PE cycles. The M4 made it 4.44x rated PE cycles, but in fairness, the Micron sync 25nm NAND should probably be rated at 5KPE instead of 3KPEs.

I'd guess that the Vertex Turbo should make it to 20000 to 25000PE cycles.

[B.A.T]

Without updates on M4, this thread feels so empty...

I'm really missing it. It would probably have made 1PiB, but now we never know.

Looks like I'll need to hit around 17800-17900 P/E cycles to hit 1 PB.

It would have been fun to have at least one ssd passing 1 PiB. With your current speed it won't take to long
o
Todays update:
Kingston V+100
208.1311 TiB
821 hours
Avg speed 75.34 MiB/s
AD still 1.
P/E?
MD5 OK.
Reallocated sectors : 00


Intel X25-M G1 80GB
28,6346 TiB Host writes
18784 hours
Reallocated sectors : 00
MWI=57 to 50
MD5 OK
52.56 MiB/s on avg

[Anvil]

Status has changed to Caution for the Force 3. (as expected)

[bluestang]

FYI in case anyone hasn't looked lately (I know I haven't till today)...

SSDLife latest version is 2.1.38
CrystalDiskInfo latest version is 4.1.3

[Christopher]

I got two more reallocations overnight. So it looks like they're accelerating -- The first two happened two weeks in to the test, the second two happened two weeks later, and the other six have happened this week. It looks like I'm getting to the point where it should start getting interesting.

[One_Hertz]

546.45TB. 7408 reallocated sectors. Erase fail at 31.

[Christopher]

Mushkin Chronos Deluxe 60 Update, Day 50
3.3.2FW

05 10 <--Increase by 2, happened today
Retired Block Count

B1 11
Wear Range Delta

F1 486700
Host Writes

E9 375521
NAND Writes

E6 100
Life Curve

E7 10
Life Left

Average 130.24MB/s Avg
Intel RST drivers, Celeron G530 Biostar TH67+

1139 Hours Work
Time 1 month 17 days 11 hours

11 GiB Minimum Free Space

[Christopher]

The 320 might not be doing it with style, but it's getting the job done admirably, if not beautifully.

[Anvil]

For some odd reason the computer rebooted last night, nothing in the Event Log that tells anything useful. (I noticed so there was no idle time)
I did check the TEST folder and on the Force 3 the folder was empty, I'm pretty sure it means that there was an issue related to all deletes. (most likely TRIM related)

Kingston SSDNow 40GB (X25-V)

465.12TB Host writes
Reallocated sectors : 05 12
Available Reserved Space : E8 99 (it has been 99 for a long time, it's just time to include this attribute)

MD5 OK

35.75MiB/s on avg (~13 hours)

--

Corsair Force 3 120GB

01 94/50 (Raw read error rate)
05 2 (Retired Block count)
B1 65 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 340714 (Raw writes)
F1 453508 (Host writes)

MD5 OK

106.70MiB/s on avg (~13 hours)

power on hours : 1325

B1 is yet again decreasing.

CDI 4.1.3 now shows F1 + F2 in TB

[Christopher]

Anvil,

That's pretty unusual now... That problem drove me crazy even after I fixed the 'random' crashes. ASU will still pause -- lets say around 5000 files deleted -- for several seconds during which the whole system freezes even though the Mushkin isn't the boot drive. Since 3.3.2 the crashes seems to be gone, but there are other factors at work that might not manifest with the current paradigm of ASU, static data, and files generated.

[Anvil]

Very unusual, it must be 30+ days since last time I had issues.

As I cant find anything in the Event log I'm assuming it was the F3, it is the most likely component and coupled with the 0 files I'm almost 100% confident in my conclusion

[Christopher]

I will say that the Mushkin was extremely sensitive to that particular issue and with the 3.2.0FW I had considerably worse luck with that and Beta 9 together. I'm still running Beta8 at the moment, so maybe I'll try it again now that the 3.3.2. seems to have worked it's magic. There are still a few configurations I could try to coax the issues out, but I'm actually liking just having the system running like it should to the tune of 10.7GB a day.


If anyone out there knows anything about the new revised Plextor drives beyond what I see in the retail product listings, let me know.




UPDATE
Wow, I really should not have said any of that. I just logged into my system and the Mushkin has disconnected. ASU was set for 11GiB min free space, and it crashed with 11.01GiB free... It most likely happened in the past hour. Why did I have to go and open my big mouth? I have a screen shot I'll get posted up later.

UPDATE 2

I think the Mushkin just died.......

It didn't disconnect. It died, and no method will restore it to life at the moment.

[Christopher]

I'm trying to figure out what happened and if there's anything I can do about it.


OK, so I've tried a couple of systems and the Mushkin can't get detected in any of them.

Here is a screen cap of the most recent update: 12 hours old from yesterday, day 50.

[Anvil]

Wow, that really is disturbing news.

Are there any LEDs?

[Christopher]

There seems to be one red LED inside the chassis, one that stays solid. It's so hard to tell though. Its very difficult to see as well as you have to look for it through the space around the SATA connectors.

I did try it in a USB enclosure too, but to no avail. I'm going to leave it disconnected for a few hours and then try it again.


Annoyingly, I've had my first two dead SSDs in two days and neither one was what I expected. The Mushkin has just perished mysteriously, but not from exhaustion of PE cycles. The Agility died two days ago as well while running Windows XP on a Dell laptop. I'm having the Agility sent back to me so I can try to D-flash it before RMAing it.

[Christopher]

I can't tell if the red LED is coming from inside the drive or not.

[Ao1]

lol, so not one of the SF based SSD has managed to get past the finishing line. That failure sounds just like what occured to SymbiosVyse' drive. It’s all up to you now Anvil.

[Christopher]

lol, so not one of the SF based SSD has managed to get past the finishing line. That failure sounds just like what occured to SymbiosVyse' drive. It’s all up to you now Anvil.

Except that mine had a WRD of 11, and only 11 reallocated sectors. Maybe there's something someone, somewhere, can do to save it.