SSD Write Endurance 25nm Vs 34nm

[Anvil]

Kingston SSDNow 40GB (X25-V)

372.70TB Host writes
Reallocated sectors : 10
MD5 OK

34.33MiB/s on avg (~35 hours)

--

Corsair Force 3 120GB

01 92/50 (Raw read error rate)
05 2 (Retired Block count)
B1 56 (Wear range delta)
E6 100 (Life curve status)
E7 71 (SSD Life left)
E9 117492 (Raw writes)
F1 156526 (Host writes)

110.05MiB/s on avg (~35 hours).

power on hours : 451

[deathman20]

Whether true or not that you signed something saying you could not share information with customers that might help customers to find out FOR YOU why your company's products are defective, such claims are certainly a good reason for people not to buy OCZ products.

While I won't buy any of there new drives at this time or recommended them at least til someone knows what the deal is with it causing issues and that it can be contained to certain products. Though I understand where Tony is coming from. While doing R&D you have NDA's that you have to agree too. Weather its a large flaw that can't be fixed, or something that is testing that might be promising but ends up failing they have to go through the ropes to see if and what will work before releasing to the public. Because if they release something that creates more issues in some other form its a PR nightmare. Sadly its a waiting game hope its gets fixed so people that want a flawless experience from the get go have more options of drives to select.

And more on topic... Common B.A.T where is our M4 fix for us waiting for that drive to fail.

[bluestang]

M225->Vertex Turbo 64GB Update:

433.66 TiB (476.82 TB) total
1176.96 hours
9004 Raw Wear
117.31 MB/s avg for the last 16.48 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count (Realloc Sectors) at 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)

[bulanula]

I am really amazed by the M4. The C300 really has a lot to live up to !

[B.A.T]

And more on topic... Common B.A.T where is our M4 fix for us waiting for that drive to fail.

I can't promise any failure yet, but I can at least help you with the daily fix

m4
610.5414 TiB
2232 hours
Avg speed 91.11 MiB/s.
AD gone from 05 to 02.
P/E 10643.
MD5 OK.
Still no reallocated sectors


Kingston V+100
122.9812 TiB
483 hours
Avg speed 76.15 MiB/s.
AD gone from 80 to 73.
P/E ?.
MD5 OK.


SSDLife shows 2% for the second time with the m4, but I don't know if they know more than the smartvalues shows us.

[johnw]

so people that want a flawless experience from the get go have more options of drives to select

As I said, it is a reason not to buy OCZ products. Better to go with Crucial, Samsung, or Intel, who make no such excuses about NDAs preventing them from helping fix their defective products.

[johnw]

im sorry m8 but i will never get my point over to you...

What point? That OCZ has defective SSDs and OCZ makes nothing but excuses about NDAs and waiting for new chipsets? That point? I got it, surely.

[Anvil]

The Force 3 is still running, > 41 hours w/o disconnects.
(all power savings disabled)

I was hoping it was ready for a test on OROM 11 , if it lasts another 10 hours it will be a new record.

[devsk]

Its very simple to find where the problem is, with the help of little bit of logic.

FACTS:
1. M4 works on a mobo/chipset/firmware/software combo. So does Intel and Samsung.
2. Vertex 3 fails on the same combo.

CONCLUSION:
Vertex 3 has bugs which need to be fixed.

Whether those are hardware/software compatibility bugs or real bugs in the drive's firmware, I don't care! As an end-user, I will buy what works with my system.

For OCZ, it will make business sense to say "Yes, we know there is an issue. We will fix at the earliest time possible." What will destroy the customer base is things like "its to do with power-savings implementation in such and such chipset" or "it happens only less than 10% of the times".

[Anvil]

Sure, there are issues with SF-2281 based drives, not just the Vertex 3.
The question is what is triggering the error and why aren't all drives affected.

We are getting a bit off topic (and that includes configuring our systems for this test) and so I'm thinking of creating a "SandForce" thread.

[Christopher]

Sure, there are issues with SF-2281 based drives, not just the Vertex 3.
The question is what is triggering the error and why aren't all drives affected.

We are getting a bit off topic (and that includes configuring our systems for this test) and so I'm thinking of creating a "SandForce" thread.

As long as we're testing SF 2281 drives, this thread is inexorably tied to at least a couple SandForce drives. What are your intentions for this other thread?

Short of buying some motherboard that the Mushkin likes, it may just be a fact of testing these drives, that they're going to lock up and disconnect or BSoD.

Eventually it won't be noteworthy any more.



Last night I installed my Intel Extreme motherboard back in. I installed the RST Alpha 11 package, and was getting some great speed, but it crashed soon after.

I uninstalled the RST 11 package, and reinstalled 10.6.whatever. I still get the speed boost in Avg MBs.

[Anvil]

The primary issue is that there will be a lot of noise that relates to why the SF-2xxx drives does not work.
With a separate thread for discussing/trying workarounds (that's really what we are doing) a lot more people can get involved without "littering" this thread.

Sure we will still have to post what changes we have made but not to the same extent.

Wrt your Intel MB, did you get the 11.x option ROM or just the RST Kit?

[Ao1]

+1 for a SF thread to keep this thread on topic.

[Christopher]

The primary issue is that there will be a lot of noise that relates to why the SF-2xxx drives does not work.
With a separate thread for discussing/trying workarounds (that's really what we are doing) a lot more people can get involved without "littering" this thread.

Sure we will still have to post what changes we have made but not to the same extent.

Wrt your Intel MB, did you get the 11.x option ROM or just the RST Kit?

Okay, new thread it is! That works for me.

I just got those alpha RST 11 drivers, it looks like the new ORoms are just for Gigabytes and Asrocks, unless someone knows something that might help otherwise.

But when I uninstalled them and reinstalled 11 I still got the speed... which is why I'm confused. I couldn't even get close to those speeds with the old configuration.

I upgraded the BIOS as well to the rescinded 2053 BIOS I had (which is terrible BTW), but maybe that's the source of the speed. It has a slightly updated (?) 10.6 orom.


EDIT
To make the BIOS work I had to do some re configuring (I had to put in a 4000 series AMD card instead of the nVidia -- but now the system only pulls 43w from the wall while running ASU, down from 49w-51w), and my RAM won't work at higher than 1067MHz at the moment.

[Christopher]

What is the status of the Corsair F40-A?

SymbiosVyse, did you ever get it figured out?

[Anvil]

Kingston SSDNow 40GB (X25-V)

373.98TB Host writes
Reallocated sectors : 10
MD5 OK

33.91MiB/s on avg (~46 hours)

--

Corsair Force 3 120GB

01 92/50 (Raw read error rate)
05 2 (Retired Block count)
B1 57 (Wear range delta)
E6 100 (Life curve status)
E7 70 (SSD Life left)
E9 120830 (Raw writes)
F1 160968 (Host writes)

110.07MiB/s on avg (~46 hours).

power on hours : 463

--

Further discussions on workarounds and suggestions for the SF-22xx based drives will take place in the new thread.
Link

[Christopher]

Mushkin Chronos Deluxe 60 Update, Day 15

05 2
Retired Block Count

B1 10 (Down from 15)
Wear Range Delta

F1 142384
Host Writes

E9 109779
NAND Writes

E6 100
Life Curve

E7 43
Life Left

Average 128.38MB/s Avg
RST drivers, Intel DP67BG P67

356 Hours Work (24hrs since the last update)
Time 14 days 20 hours

12GiB Minimum Free Space 11160 files per loop

SSDlife expects 10 days to 0 MWI


The wear range delta has dropped from the middling 20's back down to 10.
I wonder when it's will start climbing back up?

[Anvil]

Kingston SSDNow 40GB (X25-V)

375.29TB Host writes
Reallocated sectors : 10
MD5 OK

33.65MiB/s on avg (~58 hours)

--

Corsair Force 3 120GB

01 94/50 (Raw read error rate)
05 2 (Retired Block count)
B1 59 (Wear range delta)
E6 100 (Life curve status)
E7 69 (SSD Life left)
E9 124257 (Raw writes)
F1 165531 (Host writes)

110.13MiB/s on avg (~58 hours)

power on hours : 475

58 hours is a new record for this drive!

--

@Christopher
Not sure why my Wear Range Delta is so high vs yours, I've seen it decrease on 2 occations, could be that capacity allows for a higher delta.

[bulanula]

So where is the Sandforce thread then ?

[Anvil]

I linked it a few posts up

SandForce SF-22XX issues and workarounds

[B.A.T]

Todays fix

m4
617.7948 TiB
2255 hours
Avg speed 91.12 MiB/s.
AD gone from 02 to 254. The counter has been started over again from 255. Wonder how far this will go.....
P/E 10763.
MD5 OK.
Still no reallocated sectors


Kingston V+100
129.0186 TiB
506 hours
Avg speed 76.03 MiB/s.
AD gone from 73 to 68.
P/E ?.
MD5 OK.

[bluestang]

M225->Vertex Turbo 64GB Update:

440.37 TiB (484.19 TB) total
1190.79 hours
9126 Raw Wear
118.20 MB/s avg for the last 16.43 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count (Realloc Sectors) at 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)

[deathman20]

Todays fix

m4
617.7948 TiB
2255 hours
Avg speed 91.12 MiB/s.
AD gone from 02 to 254. The counter has been started over again from 255. Wonder how far this will go.....
P/E 10763.
MD5 OK.
Still no reallocated sectors

Wow. Don't think the counter will really help with anything anymore on the drive since its is what the 3rd or 4th time its reset? Im still surprised that not a single cell has failed but im eager for it to show some sign of it. Makes me feel very confident that my drives will last well beyond what I'll have them in my main system for.

[B.A.T]

I think it is the 3rd time it's been reset. One thing is for sure. You will probably throw away you computer because it is old and slow long before you have written too much to the m4

[Christopher]

I think it is the 3rd time it's been reset. One thing is for sure. You will probably throw away you computer because it is old and slow long before you have written too much to the m4

Forget the computer, YOU will be old and slow before you ever write too much to the M4...

600TB over 10 years is 164GB a day. SSDlife reports that the system drive on my system has written .2GB in thirteen hours... it's an X25-E 32GB SLC, so it could last until the next ice age at that glacial pace of writes...