SSD Write Endurance 25nm Vs 34nm

[Christopher]

After about 40hrs of running with only 6GB of free space on the drive, Wear Range Delta has jumped up to 20. I would expect it to be a little higher by tonight when I post an update. Unfortunately, I need the those extra 6GB to get the file count over 10K, or it will crash during file deletes after a few hours.

With less static data and more free space the wear range delta had been mostly holding steady. Now with the increase in static data and half as much free space, there's not much room left for wear leveling. I think I'll run it like this for a little while and see where it ends up.




Anvil,

Corsair's 1.3.2 is 3.3.0 I believe.
OCZ and Corsair rename their FW to make FW comparisons difficult -- which is silly. In OCZs case though, they throw some other stuff on top for more performance in some areas.

[Anvil]

I'll send you a preview of the next beta, there are some tweaks you could try.
My Force 3 will have to run another 4-6 hours before I'm willing to make any changes.

Also I'm going to reinstall the ASRock Z68 tonight, just to make sure that I'm running a non tweaked installation.
(will be upgrading the old Vertex 1 as well, it's on fw 1.5 and 1.6/1.7 looks to have fixed a lot of issues + better Endurance)

[bulanula]

Nothing seems to be able to stop the M4. Not even 1 reallocated sector !?

[bluestang]

Nothing seems to be able to stop the M4. Not even 1 reallocated sector !?

It's still at 0 reallocated sectors genius

[Christopher]

I'll send you a preview of the next beta, there are some tweaks you could try.
My Force 3 will have to run another 4-6 hours before I'm willing to make any changes.

Also I'm going to reinstall the ASRock Z68 tonight, just to make sure that I'm running a non tweaked installation.
(will be upgrading the old Vertex 1 as well, it's on fw 1.5 and 1.6/1.7 looks to have fixed a lot of issues + better Endurance)

1.7fw for the Vertex looks to have a few problems. Originally it was yanked due to what OCZ calls an installer problem. Subsequently it was released, but some are still having installation issues. Once you get it installed, some have had issues with the drive exhibiting strange behavior. 1.7 is supposed to manage some aspects of drive endurance and wear leveling differently, but I'm using 1.6 on three drives and find it to be pretty good over 1.5's good-but-not-great write amplification. I may try upgrading one of my Agilities to 1.7 to see what the fuss is about. I'd like to try the new Arrowana FW if they ever get their stuff together and get it out, but it doesn't seem to be doing the new VertexPlus drives any favors -- they're far more problematic than any SF2200 drive floating around out there. The Arrowana FW for old school Indilinx drives was supposed to boost random performance by 5x according to OCZ (back in May, in a press release), but I doubt it's ever going to come out now.

I think I'll upgrade the older Agility now -- what's the worst that could happen??

EDIT
There is an AgilityTrb1.7 file in the 1.7 updates for Indy drives... What's up with that?

[Computurd]

wasnt aware there was a 1.7 for the older vertex. interesting. on 1.6 for my drives.

is 1.7 stable?

[Computurd]

wasnt aware there was a 1.7 for the older vertex. interesting. on 1.6 for my drives.

is 1.7 stable?

[Christopher]

wasnt aware there was a 1.7 for the older vertex. interesting. on 1.6 for my drives.

is 1.7 stable?

They had it out a few months ago... but removed it. Back in September they brought it back out. I just flashed my Agility from 1.6 to 1.7 -- I think you should probably stay where you're at for the moment. My Agility seems a fair bit slower, but it could be an optical illusion... or I have a brain tumor. Not sure.

Now I feel extra stupid because I noticed that there was an AgilityTurbo 1.7 in the update .zip files, so I posted about it on the forums, and I got the "we never released it answer"... I was hoping they had developed some kind of faster Agility FW somewhere along the line and were going to hook it up. The 4K randoms on my Agilities are pathetic... like 8GB PATA SSD pathetic, SD or CF pathetic... no where near as good as Bluestang's Franken-tex or my 120GB Vertex Turbo.

[DooRules]

got a buddy that has been using this FW on 4 30 gb vertex turbos in R0 on x58 mobo, has been stable for about a week now, previously he could only go a day or two and drives would start to drop out...we shall see, got 4 of them turbos myself somewhere

[RyderOCZ]

Arowana will only run on 34nm Nand Vertex/Agility/Solid2 drives, so unless you have a drive with 34nm Nand on it, Arowana will not work.
Vertex Plus is not "far worse than SF-2000" is.. already released a firmware update and have another one ready. Should resolve the 2 issues we have seen.

Vertex/Agility have ALWAYS had anemic 4K's in AS-SSD, no Cognac build will change that. Also, the smaller the drive, the slower the 4k with that controller.

[Christopher]

Arowana will only run on 34nm Nand Vertex/Agility/Solid2 drives, so unless you have a drive with 34nm Nand on it, Arowana will not work.
Vertex Plus is not "far worse than SF-2000" is.. already released a firmware update and have another one ready. Should resolve the 2 issues we have seen.

Vertex/Agility have ALWAYS had anemic 4K's in AS-SSD, no Cognac build will change that. Also, the smaller the drive, the slower the 4k with that controller.

In my experience the 2281 issue's gravity really depends on what the hell you're doing with the drive; So I wasn't crestfallen once I spent a couple weeks figuring out what was going on, though some might be more sensitive. Once I figured out that there was only one thing I needed to do for my 2281 endurance drive, I've not had any problems since. It just took a couple weeks of throwing ideas against the wall, trying this and that, to come to a solution that works for me and my system. I guess you could say that I was lucky in that my usage and system resulted in crazy consistent crashes, which makes it easier to work around.

Have you seen how awesome Bluestang's drive is in 4K's? Fantastic for a 64GB... it's a thing of beauty. It's seriously Hall of Fame material.

My one Agility is hamstrung by other factors as well. I knew it wasn't so hot when I bought it, and if I didn't, I sure as hell figured it out when I bought another one last month. I might piss and moan about them, but I sure do have an unreasonable fondness for my Indilinx units -- all of them.

[Anvil]

The drives have been offline while reinstalling and upgrading the boot drive.
(no issues except for PE count spec was halved for some reason, used to be 10K and is now 5K, health 92%->83%)

Kingston SSDNow 40GB (X25-V)

403.95TB Host writes
Reallocated sectors : 12

--

Corsair Force 3 120GB

01 120/50 (Raw read error rate)
05 2 (Retired Block count)
B1 64 (Wear range delta)
E6 100 (Life curve status)
E7 49 (SSD Life left)
E9 195534 (Raw writes)
F1 260392 (Host writes)

power on hours : 770

Both drives restarted the test just minutes ago.

[Christopher]

Anvil,
from 1.6 on, V1/Agility/Core2s only have 5k PEs now. Even if it had 50nm Samsung @10K PEs, it will only be 5K now.

Some people got upset, but if the NAND doesn't fit, you must acquit.

[Christopher]

Mushkin Chronos Deluxe 60 Update, Day 27

05 2
Retired Block Count

B1 12
Wear Range Delta

F1 255227
Host Writes

E9 196853
NAND Writes

E6 100
Life Curve

E7 10
Life Left

Average 126.49MB/s Avg
RST drivers, Asus M4g-z

620 Hours Work (24hrs since the last update)
Time 25 days 20hours

12 GiB Minimum Free Space
The AnvilPro beta9 preview's 500ms/thousand files is working, and I've reduced the pause a few seconds.

If it runs overnight, I can declare victory on the 2281 TRIM/delete problem, but the additional loops per hour might be hurting speed slightly.

Thanks for the preview, Anvil. So far so good.

[Computurd]

but I sure do have an unreasonable fondness for my Indilinx units -- all of them.

couldnt agree more, excerpt the complaining part LOL. seriously LOVE my indys, still have them all. dont even need my 8 member array, but i keep it for sentimental reasons, seriously i love them.

i have 12 of them spread out around here....was going to endurance test one of them for the sake of science, just cant bring myself to do it

[Christopher]

couldnt agree more, excerpt the complaining part LOL. seriously LOVE my indys, still have them all. dont even need my 8 member array, but i keep it for sentimental reasons, seriously i love them.

i have 12 of them spread out around here....was going to endurance test one of them for the sake of science, just cant bring myself to do it

It's not like I didn't know that random performance gets worse as capacity decreases... I didn't necessarily need an expert to testify on that subject, but Eric seems to be a nice guy, and I'm glad he's still sticking his head in the door over here.

I sure as hell didn't need the last two Indy drives I bought. I put my oldest Agility 60 in my Dell D630 laptop, just because I like the drive so much. It sure as hell isn't the fastest Sata II drive I have laying around, but using any of the others just doesn't feel right. Weird, isn't it? I surely don't feel that way about my GPUs. Like I said, it's irrational.

[bulanula]

So then what is the consensus ? Can we not read the Samsung because it genuinely failed or because of the connector damage ?

[Anvil]

Kingston SSDNow 40GB (X25-V)

405.20TB Host writes
Reallocated sectors : 12

MD5 OK

37.56MiB/s on avg (~10 hours)

--

Corsair Force 3 120GB

01 84/50 (Raw read error rate)
05 2 (Retired Block count)
B1 65 (Wear range delta)
E6 100 (Life curve status)
E7 49 (SSD Life left)
E9 198247 (Raw writes)
F1 264008 (Host writes)

106.25MiB/s on avg (~10 hours)

power on hours : 780

WR delta looks to just keep on growing, strange!

[B.A.T]

A little update from me:
I'll be joining in with 2 more ssd from monday. Those will be:
- Intel X25-M G1 80GB
- MTRON Pro SSD 32GB

What makes them interesting is 50nm mlc and G1 controller without trim for the intel and slc nand for the MTRON. I'll post all the usual data before the test is started.
I would like to thank GullLars for selling them to me.

[Christopher]

A little update from me:
I'll be joining in with 2 more ssd from monday. Those will be:
- Intel X25-M G1 80GB
- MTRON Pro SSD 32GB

What makes them interesting is 50nm mlc and G1 controller without trim for the intel and slc nand for the MTRON. I'll post all the usual data before the test is started.
I would like to thank GullLars for selling them to me.

Doesn't the MTRON use the Indilinx controller?

Anvil, I don't think the 500ms helped as much as I thought. It crashed during file deletion again this morning.

[Hopalong X]

Poor Samsung 470

[Anvil]

The MTRON is much older than the Indilinx stuff, iirc it's their own controller and technology.

Strange that it didn't help but I'm not surprised.
The new fw has a fix for TRIM so lets see what it brings, I expect most will make the new firmware available this week.

[bluestang]

M225->Vertex Turbo 64GB Update:

534.69 TiB (587.90 TB) total
1460.48 hours
10847 Raw Wear
118.41 MB/s avg for the last 16.33 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count (Realloc Sectors) from 9 to 10.
(1=Bank 6/Block 2406; 2=Bank 3/Block 3925; 3=Bank 0/Block 1766; 4=Bank 0/Block 829; 5=Bank 4/Block 3191; 6=Bank 7/Block 937; 7=Bank 7/Block 1980; 8=Bank 7/Block 442; 9=Bank 7/Block 700; 10=Bank 2/Block 1066)

[Christopher]

Well, as long as the Mushkin only has about 12GB of static data, it doesn't matter. For some reason, even with the additional delay in beta9, I still have to compensate by lowering minFreeSpace [since I have much more static data now]. I'll be upgrading to the new FW, but Mushkin doesn't want to say that there is a 3.3.2 FW, much less that it's going to be along shortly.

If it's going to crash while deleting files, it will do it rather soonish. I'm back to about 10K+ files per loop, so that should solve the problem in any event, somehow.

[Anvil]

Well, as long as the Mushkin only has about 12GB of static data, it doesn't matter. For some reason, even with the additional delay in beta9, I still have to compensate by lowering minFreeSpace [since I have much more static data now]. I'll be upgrading to the new FW, but Mushkin doesn't want to say that there is a 3.3.2 FW, much less that it's going to be along shortly.
...

Corsair has the same "policy", they won't tell, I think they should make an exception, this is a serious bug for those that are affected.

Patriot has already told that it will be made available this week. (I've got a WildFire 240GB)