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)
Printable View
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)
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
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.
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.
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.
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
Attachment 120682
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.
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.
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
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.
well i think that alot of manufacturers have been bending the rules a bit with the SF issue. From what i have read many are allowing it.
If there was some kind of assurance that one or two out of every ten SF22xx drives were subject to the error, trying to get a new one wouldn't be a bad idea -- but if data like that exists, no one is talking. I have a few weeks left to make a decision like that, and I know there are many, many SF2281's out there happily working with 1155 boards without incident. There just isn't much real information about it since everyone with inside knowledge is bound by iron clad NDA, but if it's some SF incompatibility with my hardware then drive swapping won't matter. I'm going to roll with it for a while longer before making any decisions, but if it keeps up like this I'll invoke the nuclear option.
EDIT
It finally crashed again, so I tried it in my AMD system. I couldn't even get the system to boot with the drive in the machine, even as a secondary. I don't know what the hell's going on, so I put it in my laptop.
I just read AnandTech's review on the Intel 710 HET MLC. On the second page I read this:
I looked at the Smart data for my Intel drives and it looks like it works. I don't know how to reset the attribute with Smartmontools, but I'm working on it. This could be a useful tool for Anvil and OneHertz.Quote:
Thankfully we don't need to just take Intel's word, we can measure ourselves. For the past couple of years Intel has included a couple of counters in the SMART data of its SSDs. SMART attribute E2h gives you an accurate count of how much wear your current workload is putting on the drive's NAND. To measure all you need to do is reset the workload timer (E4h) and run your workload on the drive for at least 60 minutes. Afterwards, take the raw value in E2h, divide by 1024 and you get the percentage of wear your workload put on the drive's NAND. I used smartmontools to reset E4h before running a 60 minute loop of our SQL benchmarks on the drive, simulating about a day of our stats DB workload.
Once the workloads finished looping I measured 0.0145% wear on the drive for a day of our stats DB workload. That works out to be 5.3% of wear per year or around 18.9 years before the NAND is done for. I'd be able to find more storage in my pocket before the 710 died due to NAND wear running our stats DB.
For comparison I ran the same test on an Intel SSD 320 and ended up with a much shorter 4.6 year lifespan. Our stats DB does much more than just these two tasks however - chances are we'd see failure much sooner than 4.6 years on the 320. An even heavier workload would quickly favor the 710's MLC-HET NAND.
http://www.anandtech.com/show/4902/i...200gb-review/3
Nice find! Very interesting :)
I've never used smartmontools, but somehow you can reset certain smart attributes with it. I'm trying to figure that part out now, or whether just disconnecting the drive resets the counter. I did some cross checking and I think its in the data sheet for one of the series of drives (it works for all of them)
^ Intel talked about this at IDF 2010. The web seminar can be found here. (How do you measure endurance)
Kingston SSDNow 40GB (X25-V)
358.91TB Host writes
Reallocated sectors : 9
MD5 OK
36.45MiB/s on avg (~12 hours)
--
I've moved the Corsair to an ASUS M4E-Z68 and it can't keep up the same pace as the ASRock MB.
It'll have to do for this weekend though, the Marvell controller on the ASRock was terrible and resulted in an avg of <70MiB/s.
I managed getting it stable though by downloading a new driver and just as important, changing the SATA cable.
(the one I started off with was bad, never used it before though)
Corsair Force 3 120GB
01 90/50 (Raw read error rate)
05 2 (Retired Block count)
B1 47 (Wear range delta)
E6 100 (Life curve status)
E7 80 (SSD Life left)
E9 85962 (Raw writes)
F1 114552 (Host writes)
94.81MiB/s on avg (~11 hours), so, down more than 10MiB/s on avg.
power on hours : 328
The Force 3 disconnected 30minutes ago. (in the middle of a loop)
In 12 hours it wrote 4026 GiB, avg MiB/s 94.64.
So, no improvement on the other Z68 rig, will be moving it to a X58.
Well Christopher, at least we now firmly know that SF2 has not been fixed. 10% failure due to incompatibility alone sounds ridiculously high to me. Lesson to learn : avoid SF drives until a major vendor jumps onto it. Avoid for now unless you like to RMA all day long back and forth ( one guy on OCZ forums RMA his drive 3 times and it still failed LOL ).
The Force 3 is now up and running on my super-rig :)
(X58, 3Gb/s ICH10R, iaStor 9.6.0.1014)
Speed looks to be on par or better than the M4E-Z 68 rig but let's give it a few loops...
Avoid is too harsh to say considering that for each drive with issues there are 9 drive that are working. A better advice would be "Evaluate carefully your options! If you cannot afford to risk, then consider SSDs with other controllers". I know Sandforce based SSDs deployed in desktops that are used as servers (24/24 usage) and in 3 months there was only one restart having root cause an unstable overclocking during which one drive was temporary not recognized.
Update with a milestone
m4:
574.7837 TiB
2117 hours
Avg speed 88.77 MiB/s.
AD gone from 27 to 22.
P/E 10044.
MD5 OK.
Still no reallocated sectors
Attachment 120702Attachment 120703
Kingston V+100
92.3074 TiB
367 hours
Avg speed 76.74 MiB/s.
AD gone from 114 to 105.
P/E ?.
MD5 OK.
Attachment 120700Attachment 120701
My Mushkin has run without incident on my C2D laptop (I think it's the ICH8M). Speeds drop from 123MBs Avg on my 1155 system to 94MBs Avg. I'm using the RST drivers as well.
The Sata II ports on the 1155 rig were good for just as much speed as the Sata III ports, so maybe the much slower laptop helps stability. I couldn't even get my AMD system to boot with the drive attached to a controller... which is strange (it's the 710 SB).
I certainly don't think it's every SF2281 drive, but I think some hardware just doesn't work with the drives due to defect, or of out of spec hardware, or one of twenty other reasons. Until and unless this drive doesn't work with any hardware I have, I won't be giving up on it. So if it's not stable in this laptop, then I get a PCIe Marvel 6G controller. If that doesn't work, then I start thinking about more extreme options.