SSD Write Endurance 25nm Vs 34nm

[Christopher]

Looks like the SATA II ports don't help either; I just got my first disconnect on the P67's SATA II ports.

I've increased PCH voltage... not sure if that'll help...


Anvil, what kind of Z68 board are you using?

[SynbiosVyse]

96.10 hours
228.8066 TiB written
57.86 MB/s
MD5 ok

05: 0
B1: 130
E7: 10%
E9: 186624
EA/F1: 235456
F2: 384

[Anvil]

@christopher
It's currently running of an ASRock Extreme4 Z68, either I will change ports or it will run off an Asus M4E-Z for the weekend only.

@synbiosvyse
96 hours can't be right, that is just 4 days and you've been running for months? (or is it this session only)
Otherwise it looks great, no LTT and no reallocated sectors, one should think there would have been movements on 05 by now.

[bulanula]

Looks like the M4 still has some way to go.

[Anvil]

Kingston SSDNow 40GB (X25-V)

356.41TB Host writes
Reallocated sectors : 9 (from 8)
MD5 OK

35.08MiB/s on avg (~23 hours)

--

Corsair Force 3 120GB

01 95/50 (Raw read error rate)
05 2 (Retired Block count)
B1 44 (Wear range delta)
E6 100 (Life curve status)
E7 81 (SSD Life left)
E9 80407 (Raw writes)
F1 107163 (Host writes)

107.51MiB/s on avg (~23 hours)

power on hours : 304

[B.A.T]

Update
m4:
565.0567 TiB
2085 hours
Avg speed 89.57 MiB/s.
AD gone from 30 to 27.
P/E 9880.
MD5 OK.
Still no reallocated sectors


Kingston V+100
83.8624 TiB
335 hours
Avg speed 77.14 MiB/s.
AD gone from 116 to 114.
P/E ?.
MD5 OK.


There have been no problems since yesterday so I'm crossing my fingers that it will continue.

[SynbiosVyse]

@synbiosvyse
96 hours can't be right, that is just 4 days and you've been running for months? (or is it this session only)
Otherwise it looks great, no LTT and no reallocated sectors, one should think there would have been movements on 05 by now.

Yeah that's since I switched back to 46%. I had been running 0-Fill for a while at the beginning, so I ran 100% to help offset that. Personally I find it a little confusing that the app resets the timer even if you set it to count totals. So if you stop the app, it still continues to carry over the data written, but then it resets the timer. Have you considered changing this? Or perhaps at least have two timers, a global and session only.

Overall I've been very impressed with this drive. The speeds are still almost the same as day one, and no reallocated sectors. The MWI has been stable at 10% for a little while now. I will continue to monitor this and note when it drops.

[bulanula]

WOW, imagine what the results of the C300 will be if the M4 got this far ! Really impressive. and no SF-like bugs of random dissapearances etc.

[deathman20]

Dang she's going to crack 10k on that M4. 650TB no issues I'd say at least before it runs out on SSDLife Pro.
At least hes not testing a 128Gig drive... that thing would be going for months more!

[Christopher]

WOW, imagine what the results of the C300 will be if the M4 got this far ! Really impressive. and no SF-like bugs of random dissapearances etc.

That assumes the 34nm NAND is better, and maybe it is, but from what I've seen so far it might be a moot point -- anything's better than random dropouts.

I'm rapidly starting to lose all the goodwill I feel towards the Mushkin. Not that it's Mushkin's fault -- It's probably Sandforce's, but that doesn't make it any less annoying. It dropped out last night again. I'm not really sure that anything I try is going to help.

[Anvil]

Mine is past 30 hours, I'm sort of expecting it to disconnect within a few hours. (that would fit most of the other disconnects)

[Christopher]

Mine is past 30 hours, I'm sort of expecting it to disconnect within a few hours. (that would fit most of the other disconnects)

Mine was like that for the first few days, but now it's going to happen every night. The way I look at it, if disabling TRIM drops avg speed by 25% but stops disconnects, it will be a net gain. Nothing seems to make any difference.

[SynbiosVyse]

I have seen this problem with the SF-1200's last year (on Corsair's). Disabling TRIM did not help in most cases. Have you tried disabling TRIM? I just don't think it will fix the problem. I think there's a worse underlying problem with the firmware.

[Christopher]

I have seen this problem with the SF-1200's last year (on Corsair's). Disabling TRIM did not help in most cases. Have you tried disabling TRIM? I just don't think it will fix the problem. I think there's a worse underlying problem with the firmware.

I don't think it will either. I tried it for a little while, but from what I've seen with users with the exact same problem, it won't help. What I was saying was, if it did help but dropped avg speed 25%, it would still be a net gain. Every night, at some point after I go to sleep, it drops out. So I'm losing several hours every night. My backup AM3 rig only has SATA II, but I'm considering switching to it as well instead of another 1155 board.

I only started looking into TRIM because the first three crashes happened during the delete section of the loop. Since then it's happened seemingly at random. I'm not going to give up, but I'm thinking RMA. I'm also thinking about trying a Samsung 470 with double the spare area to see if it would last twice as long, but not until I get the SF sorted out.

[SynbiosVyse]

It's not worth it to disable TRIM in my opinion.

You may have mentioned this before but what SATA controller are you using again? If you have an Intel SATA II (like an ICH7-ICH10 or something) then see if that works.

I would definitely return it and get a refund and get a whole new drive, or at the very least RMA it and get a new drive of the same one to see if there is any difference.

[Christopher]

It's not worth it to disable TRIM in my opinion.

You may have mentioned this before but what SATA controller are you using again? If you have an Intel SATA II (like an ICH7-ICH10 or something) then see if that works.

I would definitely return it and get a refund and get a whole new drive, or at the very least RMA it and get a new drive of the same one to see if there is any difference.

Yeah, I tried it on my P67's SATA II port. While I didn't lose much speed, it didn't help either, and disconnected just the same. Right now none of these drives are in stock and so I wouldn't think of RMAing until I can get another one. Plus, if I RMA it, and the drive gets tested it will work, so then they're going to send me the drive back. I'm not sure how best to work this out, but there is definitely something wrong.

Next time it crashes, I'm putting it in the AM3 SATA II ports on my backup system.


EDIT
If anyone has any ideas of another drive to test, I'm all ears.

[Anvil]

The system frooze almost 2 hours ago, will try the add-on controller next.

edit:
It was within a minute of starting a new loop (1580 files created).

The drive is now connected to a Marvell SE9120 6Gb/s controller. (in raid mode)

[bluestang]

Just to compare speeds...what is everyones Estimated/Current MiB/s min and max for a loop? I'll start with the M225.

bursts to 155-160+ for the first few seconds.
settles down in the low 150's to upper 140's.
about 75% through the loop will fall slowly till each reaches the end of the loop ending in the upper 130's.

Evidently my random writes kill my total Avg MB/s

[Anvil]

The Force 3 does about 115-117MiB/s throughout the loop, that is on the PCH 6Gb/s controller.

The "X25-V" starts off at full speed (40MB/s+) and then gradually slows down during the loop, the biggest falloff is during the last 8-10GB.

I'll restart my system and take notes on the first loop.

edit:

I've been playing a bit with the drivers and they are just awfull.

Using the Marvell drivers I got disconnects in seconds, I have not looked for updated drivers, will do that later.
Using MSAHCI the speed is down from 115-117MiB/s to <90MiB/s (a bit early though as it's based on 1 loop)

If the speed doesn't improve I'm dropping the Marvell controller. (unless I can find an updated driver that works)

Will do some more tests before I decide what to do.

[Christopher]

It starts at 157, but in less than a second it drops to 137,136,135, where it stays until the end (135).

So really you could say it stays within the 135 range for the entirety of the loop - it never drops below that on the P67 SATA III ports (the avg MB/s under total lists the avg now at 121.84, so maybe that includes the randoms and the pause/delete time). On the SATA III ports it averages 124MBs instantaneous estimated speed, and about 116MBs for the Avg MB/s rating.

EDIT
I've also tried something a little different. About 4 hrs ago, I reflashed the 3.20 FW on the Mushkin. I then unistalled the mushkin from the device manager. After a reboot, Windows wants to reinstall the driver, which it did, but then you have to reboot again before it gets active. Maybe this will help in some way -- maybe. I'm really just grasping at straws here.

I originally intended on purchasing another 2281 to run as a regular system drive. I decided against it because the problems keep getting worse. So I bought a used X25-M 80GB. It's the unSandforce.

[B.A.T]

m4:
The loop start at 111 MiB/s and stays around 109 MiB/s the whole loop, but once in a while the speed drops to around 80MiB/s. The speed is better after Anvil adjusted the pause. In the earlier versons the speed dropped to around 50 MiB/s

Kingston V+100:
The loop start at 190 MiB/s but dropps rapidly to around 120 MiB/s and slowly continues down to 89 MiB/s.

[Christopher]

Mushkin Chronos Deluxe 60 Update

05 0
Retired Block Count

B1 20 (Up from 19)
Wear Range Delta

F1 84776
Host Writes

E9 65351
NAND Writes

E6 100
Life Curve

E7 67
Life Left

Average 122.25MBs.
215 Hours Work Time
Last 6hrs on 6gps port

12GiB Minimum Free Space

SSDlife expects 17 days to 0 MWI


EDIT
Notice that the Power Cycle count is now at two -- that looks like the only SMART value that was reset after the FW reflash.

[Computurd]

i hate to hear about your SF issues Chris, but seriously i would advise you to get a refund. From what i have seen this will not get better unfortunately.

[Vapor]

C300 Update

445.58TiB host writes, 1 MWI, 7532 raw wear indicator, 2048/1 reallocations, 62.65MiB/sec, MD5 OK


SF-1200 nLTT

295.563TiB host writes, 220.094TiB NAND writes, 10 MWI, 3521.5 raw wear (equiv.), wear range delta 3, 55.6MiB/sec, MD5 OK

[Christopher]

i hate to hear about your SF issues Chris, but seriously i would advise you to get a refund. From what i have seen this will not get better unfortunately.

I'd really hate to just give up on it though - that's not really my style, and it would be amazing if I could get around these problems. This thing is incredible for a 60GB drive, but I'd seriously reconsider any decision to buy a SF drive at this point, except from OWC -- They have a 30 day no-questions-asked money back policy . The vendor I bought the Mushkin from has an exchange only policy -- but maybe I can sweet talk them if it comes down to it.