SSD Write Endurance 25nm Vs 34nm

[bulanula]

I think it is very possible that no LTT is present on the Corsair. The same thing happened with one of the retail SF drives here from Corsair too etc.

[Christopher]

Has anyone here used an original OCZ RevoDrive? The 180GB model is on sale for 1$/GB and the Vertex 3 120 is almost as cheap.

The RevoDrive looks kinda unimpressive next to the Mushkin ChronosDeluxe60

I bet it doesn't have LTT.

Too bad I'm boycotting OCZ's awful plastic chassis, because the Vertex3 is pretty impressive.

[Vapor]

I think it is very possible that no LTT is present on the Corsair. The same thing happened with one of the retail SF drives here from Corsair too etc.

There is no lifetime throttling with the Corsairs or the Mushkin. E6 SMART attribute indicates this for SF-2200 drives and the Corsair SF-1200 has been going way too long (MWI is already down to 10) without any indication of LTT.

[Christopher]

The Mushkin has finally hit 90 MWI.

I don't think this drive is going to die anytime this year -- I really wanted a read-only drive for Christmas.

[Vapor]

I do doubt it will die this year, but MWI should get to 1 in 28-29 days of total runtime* and 3.5+ days of runtime have already been completed.


* that's without any weird scaling when MWI gets to 10 and if it maintains ~122MiB/sec.

[Christopher]

I do doubt it will die this year, but MWI should get to 1 in 28-29 days of total runtime* and 3.5+ days of runtime have already been completed.


* that's without any weird scaling when MWI gets to 10 and if it maintains ~122MiB/sec.

I feel confident that it might be getting close by Easter.


Actually, this drive just keeps growing on me... I'll be sad to see it go.

I'm starting to think two of them would be incredible in R0, but by the time this Mushkin wears out there might not be any more 32nm flash hanging around, which in itself is a tragedy.

I can't understand why Mushkin isn't out there screaming "Hey! We have the fastest 60GB in the Universe!" at the top of their lungs.

[SynbiosVyse]

Sorry haven't been able to post much. The MWI is still at 10%, it seems to be stuck for a little while. I'm going to monitor this closely to try to get a good idea of when it will drop below 10%.

561.20 hours
206.30.98 TiB written
40.74 MB/s
MD5 ok

05: 0
B1: 116
E7: 10%
E9: 166656
EA/F1: 212288
F2: 384

[sergiu]

A SSD is considered dead normally only when it has no more spare area. A possible explanation for MWI that is stuck to 10 is that from 100 to 10 is scaling with P/E cycles while from 10 to 0 would scale with available spare area.

[Anvil]

@Ao1
It certainly looks like there is no LTT

Kingston SSDNow 40GB (X25-V)

342.93TB Host writes
Reallocated sectors : 8 (this is the second bump in a week or so)
MD5 OK

34.17MiB/s on avg (~36 hours)

--

Corsair Force 3 120GB

It disconnected again last night, currently running a tweaked clean-up section, will see if it makes a difference.


01 90/50 (Raw read error rate)
05 2 (Retired Block count)
B1 32 (Wear range delta)
E6 100 (Life curve status)
E7 90 (SSD Life left)
E9 50304 (Raw writes)
F1 67050 (Host writes)

107.29MiB/s on avg (~11 hours)
Uptime 190 hours. (power on hours)

SSDLife estimates lifetime to be 1 month 19 days.

[Christopher]

@Ao1
It certainly looks like there is no LTT

Kingston SSDNow 40GB (X25-V)

342.93TB Host writes
Reallocated sectors : 8 (this is the second bump in a week or so)
MD5 OK

34.17MiB/s on avg (~36 hours)

--

Corsair Force 3 120GB

It disconnected again last night, currently running a tweaked clean-up section, will see if it makes a difference.


01 90/50 (Raw read error rate)
05 2 (Retired Block count)
B1 32 (Wear range delta)
E6 100 (Life curve status)
E7 90 (SSD Life left)
E9 50304 (Raw writes)
F1 67050 (Host writes)

107.29MiB/s on avg (~11 hours)
Uptime 190 hours. (power on hours)

SSDLife estimates lifetime to be 1 month 19 days.

I've not had anymore problems with the Mushkin for the past 36 hours. I've even bumped free space down several GB, in hopes that I can goad the drive into crashing under certain circumstances, and I'm considering dropping a few more incrementally in hopes that I can force a hang or disconnect/reboot . With 6GB Min Free, I'm generating about 10400 files per loop, pretty close to what the Force 3 was, so perhaps I'll have something happen during cleanup.

Still no retired blocks, though I'd expect that to start happening in the next few days. I'm actually surprised I don't have any now, but I'm not sure that you can compare these to Indilinx drives that come with bad blocks straight out of the box.

[Christopher]

Morning Update

Mushkin Chronos Deluxe 60
05Retired Block Count0
B1Wear Range Delta16
F1 Host Writes 37985GB
E9 NAND Writes 29256GB
E6 Life Curve 100
E7 Life Left 87Percent

Average 122.13MBs last ~37 hours.
95 Hours Work Time

I've settled on 6GiB Minimum Free Space with 10400+ files per loop.

SSDlife expects 23 days to 0 MWI

[Vapor]

A SSD is considered dead normally only when it has no more spare area. A possible explanation for MWI that is stuck to 10 is that from 100 to 10 is scaling with P/E cycles while from 10 to 0 would scale with available spare area.

Seems reasonable. For the charts, I'm going to consider 10 MWI as exhausted for the Sandforces.

@SynbiosVyse, you've run the 100% setting long enough that you've undone the skew from the 0% run....you can switch back to 46% compression setting (or even 67% if you want).

[bulanula]

Wonder what the next SSD victim will be etc. Maybe one of the Intels ?

[Christopher]

Seems reasonable. For the charts, I'm going to consider 10 MWI as exhausted for the Sandforces.

@SynbiosVyse, you've run the 100% setting long enough that you've undone the skew from the 0% run....you can switch back to 46% compression setting (or even 67% if you want).

You would think that keeping up with hundreds of TB worth of writes, ECC data, and everything else would really take a toll on SF spare area.

[Anvil]

Kingston SSDNow 40GB (X25-V)

344.23TB Host writes
Reallocated sectors : 8 (this is the second bump in a week or so)
MD5 OK

33.72MiB/s on avg (~48 hours)

--

Corsair Force 3 120GB

01 90/50 (Raw read error rate)
05 2 (Retired Block count)
B1 34 (Wear range delta)
E6 100 (Life curve status)
E7 89 (SSD Life left)
E9 53598 (Raw writes)
F1 71439 (Host writes)

107.35MiB/s on avg (~22 hours)
Uptime 202 hours. (power on hours)

SSDLife estimates lifetime to be 1 month 18 days.

[Christopher]

Tonight's Update

Mushkin Chronos Deluxe 60
05 0
Retired Block Count

B1 14
Wear Range Delta

F1 42724
Host Writes

E9 32912
NAND Writes

E6 100
Life Curve

E7 85
Life Left

Average 122.66MBs.
106 Hours Work Time

5GiB Minimum Free Space

SSDlife expects 22 days to 0 MWI



Of course, as soon as I posted the update and walked away I had another crash. ASU's totals have been reset to much earlier numbers as well. It doesn't seem to have anything to do with, well, anything. It happens to be very close to the same amount of time after the last reboot. Maybe it's just going to happen every 40 hours.

[johnw]

Seems reasonable. For the charts, I'm going to consider 10 MWI as exhausted for the Sandforces.

I think that is correct, since the threshold is clearly labeled as 10 in the SMART attributes. With SMART attributes, a failure is defined as the normalized value reaching the threshold value.

[SynbiosVyse]

This will be my last update at 100%. I will be switching to 46% after this post.

585.77 hours
209.7130 TiB written
40.72 MB/s
MD5 ok

05: 0
B1: 119
E7: 10%
E9: 170816
EA/F1: 215808
F2: 384

[bulanula]

Any news testing an SLC drive ?

[Anvil]

I restarted the process on both SSD's an hour ago, no specific reason I just wanted to get ahead of the SF drive doing it's disappearance act. (It had been running for about 33 hours without any issues)

Kingston SSDNow 40GB (X25-V)

345.41TB Host writes
Reallocated sectors : 8
MD5 OK

35.43MiB/s on avg (~1 hour)

--

Corsair Force 3 120GB

01 94/50 (Raw read error rate)
05 2 (Retired Block count)
B1 35 (Wear range delta)
E6 100 (Life curve status)
E7 88 (SSD Life left)
E9 56554 (Raw writes)
F1 75376 (Host writes)

107.62MiB/s on avg (~1 hours)
Uptime 216 hours. (power on hours)

SSDLife estimates lifetime to be 1 month 17 days. (November 13th)

[bluestang]

M225->Vertex Turbo 64GB Update:

371.99 TiB (411.69 TB) total Another one past the 400 TB mark.
1054.44 hours
7922 Raw Wear
118.41 MB/s avg for the last 64.09 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count (Realloc Sectors) from 4 to 6.
(Bank 6/Block 2406; Bank 3/Block 3925; Bank 0/Block 1766; Bank 0/Block 829; Bank 4/Block 3191; Bank 7/Block 937)

[Anvil]

The SF drive was disconnected when I got home, so, it ran for about 1 hour after restarting the app.
Looks like a proper disconnect is needed not just restarting the app.

[Christopher]

After the crash early last night, it looks like it crashed again probably somewhere around 4am or 5am. The really annoying thing is, the system crashes and reboots, but the BIOS can't find the OS, so it just sits at a black screen with the error message until I get there to to physically turn it off/on again. After a soft reboot it still can't find the OS, so I have to physically turn the system off.

I was running it with 5 min GiB free space, so maybe it's hanging on the delete section. I was kinda trying to get that to happen, but only while I was sitting in front of the system.

The last time I checked before the overnight crash it had crept up to a little over 124MBs. I'm still really liking this drive. OWC makes a 240GB version of this drive but it uses the 2282 SF controller, and is probably the fastest drive out there at the moment.

[Christopher]

I stopped testing for a while, and while the drive was idling just after a reboot, I noticed that Raw Read Error Rate is probably just a timer. It increases at the same pace while idling as it does under endurance loads. If you open CrystalDiskInfo and then just continually refresh the info with F5 you'll see it tick up every second.

[B.A.T]

m4 update:
Here is the last screenshot before the avg restarted the rig and I lost contact with it.
538.0406 TiB
1759 hours
Avg speed 91.11 MiB/s.
AD gone from 46 to 42.
P/E 9430.
MD5 OK.
Still no reallocated sectors

I have restartet ASU and will bring next update tomorrow evening.

Kingston:
I'm gone try a SE and put the SSD on the esata controll to see if the problem goes away.