SSD Write Endurance 25nm Vs 34nm

[bluestang]

M225->Vertex Turbo 64GB Update:

170.00 TiB
599.5 hours
MWI 17 (drops by 1 for every 50 raw wear)
4150 Raw Wear
110.77 MB/s avg for the last 65.03 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count(Realloc Sectors) at 2 (Bank 6/Block 2406; Bank 3/Block 3925)

[SynbiosVyse]

100% (Incompressible)
71.30 hours
117.4192 TiB written total
40.88 MB/s
MD5 ok

05: 0
B1: 40
E7: 66%
E9: 57664
EA/F1: 120768
F2: 128

[bluestang]

100% (Incompressible)
71.30 hours
117.4192 TiB written total
40.88 MB/s

71.3 hours?...that's not your total run time so far. Need to put total hours you have ran so far on ASU, no?

[SynbiosVyse]

That's just the runtime since I changed the setting. Is there a total runtime somewhere? I don't remember seeing it.

[Vapor]

Ever since Anvil implemented a running average MiB/sec, there's no need to report any hours...total or recent

[Anvil]

I often report hours (mainly for historic reasons) as my SSD is slow and I need to run the SSD Toolbox from time to time.
So when it dips below 33MiB/s it's time to perform a manual TRIM. (1MiB/s makes quite a difference in my case )

There will be an option for resetting avg MiB/s every 24 hours. (makes it easier to spot changes)

[Vapor]

C300 Update

278.3TIB host writes, 6 MWI, 4700 raw wear, 2048/1 reallocations, 63.15MiB/sec, MD5 OK


SF-1200 nLTT Update

145.875TiB host writes, 102.344TiB NAND writes, 51 MWI, 1637.5 raw wear (equiv), wear range delta 3, 55.9MiB/sec, MD5 OK

[bluestang]

Out of curiousity, for MD5 test what size file are you guys using?

[SynbiosVyse]

The test files I'm using are only several megabytes. I also try to report the hours as much as possible for my own documentation. I would like to report as many SMART characteristics as possible as well, including the lifetime reads from host.

It helps me figure out when I changed a compression setting, too. More info is better than not enough, right?

[bulanula]

Really anxious to see how long the Samsung will keep the data intact. Which drive has a higher WA, the Samsung or the Indilinx controller ?

[B.A.T]

m4 update:
406.8336 TiB
1344 hours
Avg speed 90.19 MiB/s.
AD gone from 134 to 119.
P/E 7135.
MD5 OK.
Still no reallocated sectors



An unexpected turn for the Kingston. When I came back from my weekend trip the drive had dropped out and APU was non responsive.
I'll try a restart and see if that helps.

m4 question: Should I update to the latest firmware or should I wait?

[B.A.T]

And we are back again with the Kingston:

It dropped out 26 of aug.


status now is:

23.6833 TiB
92 hours
Avg speed 84.30 MiB/s.
AD gone from 177 to 175.
P/E ?.
MD5 OK.
Still no reallocated sectors

Strange. ASU is missing around 14 TiB....

Anvil will help me with this.

Problem solved and now the correct number are posted.

[Anvil]

m4 question: Should I update to the latest firmware or should I wait?

In real life I would have updated the M4 and as the test is trying to be as close as possible to real life I'd definitely update the firmware.

There is a new attribute on my M4 256GB (C2) that looks to be missing from your 64GB, not sure what it could be. (mine says Unknown, raw value 0)
(C2 it is most likely introduced in 0009)

[B.A.T]

I'll try updating tomorrow then.

[Anvil]

First reporting using SSDLife Professional.

SSDLife.png SSDLife_SMART.png

Health is BAD is seems
(as expected)

[Vapor]

SF-1200 nLTT Update

148TiB host writes, 104.063TiB NAND writes, 50 MWI, 1665 raw wear (equiv), wear range delta 3, 55.9MiB/sec, MD5 OK

SSDLife Pro predicts 25 days left on the MWI ticker, my tracking says 26.6 days left....not sure how SSDLife calculates it, but SSDLife Pro was started at least an hour after the SSD ticked down to 51MWI and the data so far is very limited, so app's extrapolation is pretty good so far.

[Computurd]

@ct
Wishful thinking?
I bet you won't be booting off that old array unless it's for sentimental reasons

i agree anvil, man i did have some good times with that array...i just cant break them up for some reason.
dammit im getting misty eyed....

[zalbard]

m4 update:
406.8336 TiB
Still no reallocated sectors

That's insane...

And yes, please update the FW!

[Anvil]

274.34TB Host writes
Reallocated sectors : 6
MD5 OK

34.41MiB/s on avg (23.6 hours)

--

I'm including a screenshot from SSDLife but I guess I need to get some answers on how to configure the app for optimal results/readings.
It looks like it needs to run 24/7 in order to get correct results on "Throughput" for Today and Yesterday, "Last 7 days" looks to be correct though. (it started counting when the app was first started, 1.4TB looks to be correct)

It also reports that there is 39.9GB "free size" which is not correct, so a small bug on one of the drives, strange as the other SSD on the system is correctly reported.
Would have been interesting running this app from day 1.

SSDLife_2011-08-30-11-57.png

[bulanula]

It really is impressive that the M4 reached 400 TB so soon. I wonder how the C300 will fare with same controller and better 34nm NAND. Maybe 600 TB ?

[bluestang]

M225->Vertex Turbo 64GB Update:

176.02 TiB
613.9 hours
MWI 15 (drops by 1 for every 50 raw wear)
4266 Raw Wear
110.53 MB/s avg for the last 15.85 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count(Realloc Sectors) at 2 (Bank 6/Block 2406; Bank 3/Block 3925)

[B.A.T]

m4 update:
412.3073 TiB
1350 hours
Avg speed 90.03 MiB/s.
AD gone from 119 to 115.
P/E 7231.
MD5 OK.
Still no reallocated sectors



Kingston update:
The V+100 dropped out again this morning.
It looks like this when that happens.



Last record states:
26.4734 TiB
103 hours
Avg speed 77.37 MiB/s.
AD gone from 175 to ?.
P/E ?
MD5 OK.

[SynbiosVyse]

100% (Incompressible)
102.80 hours
121.8470 TiB written total
40.90 MB/s
MD5 ok

05: 0
B1: 44
E7: 62%
E9: 63040
EA/F1: 125312
F2: 128

[bulanula]

I think the M4 will be the next to follow the Samsung 470 in the "dead" SSD closet.

[B.A.T]

Update:
I'm not able to update my m4 with new firmware. I get this error message:


I've tried IDE with port 1-4, and AHCI on the same ports.

For the time being I'll run with v002 until I find a fix.

The Kingston is also up and running. I changed port on the motherboard and Anvil helped me recontruct the log.