Done with OCZ for good

[GodisanAtheist]

Second Vertex 2 to lock up on wake from sleep then fail to detect at POST. First one (34nm) made it 1.5 years before it ran into this issue. This one (25nm) was the RMA from OCZ, and it had the decency to crap out after a whopping 3 months. Gonna RMA again but I'm not going to purchase anything new from OCZ from here on out; what people say about this company is true. You save a few bucks out the door for hours of headache later.

Too lazy to diligently back-up primary drive so I make sure not to keep anything important on it (Storage drive with all the important stuff gets an external back-up) but man is this frustrating from a down time perspective.

Will try to sell the replacement drive. Probably spend the good money to get an Intel/Samsung/Crucial SSD. Annoying though as my rig is still SATA 2 based.

 

[Obsoleet]

I used to use OCZ drives at first. I had two of them, not bad for an average enthusiast to give something a try. Then I had enough (very quickly) in the Vertex1 era.

Bought 2 Intel G2s almost 4 years ago now, and haven't one one blip on either one- ever. Same original format. I even hibernate them, pull them out, replace them with other drives, then reattach them- NEVER an issue.

Who cares if you have a 3gb rig. So do I. If you want to follow the current trend for fast+leading stability- Get a Samsung 830, those are the new Intel G2s. Fast and the most reliable on the market. I wouldn't touch anything else to replace my G2s.

 

[F1shF4t]

Its not really OCZ that's at fault here but the sandforce gen1 controller.
Those things don't work well with sleep and tend to panic lock. (Well I guess they are at fault for selling a buggy product, but then so is everyone else who has ever used that controller)

I've have a corsair force F115 which did just that and had to RMA

 

[chloros]

you bent over the minute you bought OCZ

 

[E6700]

HAHA i'm done with them since their 1st gen vertex.

 

[jhansman]

Samsung, baby, Samsung. Or, Crucial.

 

[waterjug]

Its not really OCZ that's at fault here but the sandforce gen1 controller.
Those things don't work well with sleep and tend to panic lock. (Well I guess they are at fault for selling a buggy product, but then so is everyone else who has ever used that controller)

I've have a corsair force F115 which did just that and had to RMA

They basically admitted it wasn't the sand-force at some point, but any post referring to this is deleted from their forums or locked.

 

[PowerYoga]

ocz has awesome RMA though. They get a lot of practice.

 

[VirtualLarry]

I thought everyone knew by now, NEVER USE SLEEP MODE, if you have a first-gen Sandforce SSD.

Problem is PEBKAC.

 

[taltamir]

I thought everyone knew by now, NEVER USE SLEEP MODE, if you have a first-gen Sandforce SSD.

Problem is PEBKAC.

this is wrong on so many levels

 

[Coup27]

Problem is PEBKAC.

No. Problem exists because a product was not fully tested before sale.

 

[Topweasel]

I thought everyone knew by now, NEVER USE SLEEP MODE, if you have a first-gen Sandforce SSD.

Problem is PEBKAC.

A.) You can't expect every person in the world to know this unless its printed on the box.
B.) It's like blaming the victim for Rape. Sure he could have avoided this by knowing more about the product and known bugs. But still its a bug that destroyed his data. He should have avoided it one hand because its easy to do. But on the other hand he shouldn't have to and the persons responsible for him doing something he should be allowed to do and having the drive die is the company that produces a product that dies when someone does something they should be allowed to do.

 

[MrWizzard]

A.) You can't expect every person in the world to know this unless its printed on the box.
B.) It's like blaming the victim for Rape. Sure he could have avoided this by knowing more about the product and known bugs. But still its a bug that destroyed his data. He should have avoided it one hand because its easy to do. But on the other hand he shouldn't have to and the persons responsible for him doing something he should be allowed to do and having the drive die is the company that produces a product that dies when someone does something they should be allowed to do.

NO, he shouldn't have been dressed like that walking down that dark alley!.....wait what are we talking about here?

 

[Topweasel]

deleted

 

[VirtualLarry]

Patient: It hurts when I hit my head with a hammer.

Doctor: Stop hitting your head with the hammer, then it won't hurt.

Patient: It never said on the box of the hammer, not to hit my head with it!

 

[Topweasel]

Patient: It hurts when I hit my head with a hammer.

Doctor: Stop hitting your head with the hammer, then it won't hurt.

Patient: It never said on the box of the hammer, not to hit my head with it!

Not hitting yourself should be instinctual self commonsense. Doing something every other computer does fine, with no recall, warning, or an actual announcement about the issue is something else completely.

 

[groberts101]

Not hitting yourself should be instinctual self commonsense. Doing something every other computer does fine, with no recall, warning, or an actual announcement about the issue is something else completely.

Then again.. the same thing could be said about building or customizing computers. Too many who think this stuff is so simple and they can just throw parts together without issue.

Those who don't study up and research these things are running on barrowed time anyways. Not to mention there are plenty of other software and sleep issues going on around us for those who even run good old HDD's.

I always say it like this. If you want an SSD based computer that has been validated to work and survive all "typical" user patterns?.. BUY ONE THAT HAS BEEN VALIDATED AND SETUP BY THE MFGR. You pay them to test and config the hardware/drivers for you.

 

[GodisanAtheist]

Patient: It hurts when I hit my head with a hammer.

Doctor: Stop hitting your head with the hammer, then it won't hurt.

Patient: It never said on the box of the hammer, not to hit my head with it!

Poor Analogy. Using a hammer to hit yourself on the head is not the intended use of the hammer. Your example also doesn't have the hammer critically failing, when being used for its intended purpose. A more apt analogy would be "My hammer snapped in half while I was using the claw to pull out nails". Your logic goes: Of course everyone knows you're not supposed to pull nails out with a claw hammer right?

Using an SSD for its intended purpose causes SSD drives to fail. Seriously, there is something wrong with a product when it cannot even hold up to standard use. Why do I have to modify my usage habits for OCZ's benefit? Have you ever heard of RAM failing on wake from sleep? Or a Videocard? Even other SSD drives don't exhibit this behavior. If you were an early adopter of the Vertex 2, like I was, you wouldn't even know this problem existed until it bit you in the ass. How do you think "Lol everyone knows not to sleep a Gen 1 sandforce" even BECAME common knowledge? A bunch of people played beta tester for OCZ. Then the same thing happened with the Gen 2 2281 sandforce controller, primarily with OCZ drives.

Ultimately you have a point: OCZ sells crap (everyone knew their drives break when slept, apparently) , and I should have done my homework before getting in bed with them. Won't happen again I assure you.

 

[taltamir]

Patient: It hurts when I hit my head with a hammer.

Doctor: Stop hitting your head with the hammer, then it won't hurt.

Patient: It never said on the box of the hammer, not to hit my head with it!

more like
Patient: "I bought an OCZ brand hammer and when I pull out nails the hammer breaks and I need to get it replaced under warranty"
Rude condescending man: "what a moron, everyone knows OCZ brand hammers do that, this is your fault for using an OCZ brand hammer is such a manner, you should have obviously only used an OCZ branded hammer for hammering in nails, if you wanted to take nails out you should have bought a different branded hammer. I have zero sympathy for what is clearly your own fault."

 

[bononos]

Is the hibernate problem an issue with Sandforce controllers and not specifically with OCZ?

 

[mikeymikec]

this is wrong on so many levels

Par for the course on this forum.

 

[nanaki333]

Then again.. the same thing could be said about building or customizing computers. Too many who think this stuff is so simple and they can just throw parts together without issue.

Those who don't study up and research these things are running on barrowed time anyways. Not to mention there are plenty of other software and sleep issues going on around us for those who even run good old HDD's.

I always say it like this. If you want an SSD based computer that has been validated to work and survive all "typical" user patterns?.. BUY ONE THAT HAS BEEN VALIDATED AND SETUP BY THE MFGR. You pay them to test and config the hardware/drivers for you.

but a lot of users want to upgrade 1 component in their computer, but don't want to pay an expert $135 just to put a drive in. we're not talking about picking the right motherboard to match the socket of the CPU you just got.

 

[groberts101]

but a lot of users want to upgrade 1 component in their computer, but don't want to pay an expert $135 just to put a drive in. we're not talking about picking the right motherboard to match the socket of the CPU you just got.

true dat. BUT.. this is first gen Sandforce that we're talking about here. Which of course means that "common sense" or "normal practice" goes right out the window.

And FYI here to anyone interested. Sandforce holds their code pretty tightly to their chest for no one to see and it's highly doubtful that even Intel has access to low level code for these controllers. So, with that being said.. Sandforce gets feedback from all vendors using its chip and revises master firmware which has known workarounds/fixes. When that code is ready to be released?.. all mfgrs will get a firmware package with their specific optimizations and tweaks(within the constraints of the controllers internal requirements/abilities) all rolled into one for release to their customers. Which inevitably means that you will have OCZ derived fixes or workarounds running in you Intel or Corsair drives.. and vice-versa.

So, that really boils things down to the point that OCZ, Corsair, Kingston, Patriot, OWC and all the others.. helped to do much of the dirtiest most time consuming work for Intel(including but not limited to letting Intel know where there drivers were coming up short). Such as pissing customers off and forcing them to give feedback as they ran into issues. The companies that sold drives earliest and in higher quantities obviously took the brunt of that which in turn leads to yet more false assumptions based on problem posts. Purely a perspective thing.

 

[tweakboy]

OCZ used to be popular wtf lol.....