RMA OCZ Vertex 2 90GB 3,5"

Rast

Member
Oct 17, 2011
88
0
61
I have since 2010 nov. my vertex 2, i saw everyone has this cold boot problem. I think I have it too, every time i want to boot my pc I need to restart it, because it wont see my ssd or any other boot device.


so my question is can I RMA It? to get another one or how can i fix this problem.
 

groberts101

Golden Member
Mar 17, 2011
1,390
0
0
I would post this same question over at their forums since they are better equipped to answer the question. You'll obviously need to include the mandatory system details to better help anyone help you with the issue, of course.

from here, I'll start you off.

latest bios
latest SSD firmware

if no later bios available(running it on older outdated OROM)?.. look for one that has been modded with newer OROM to improve compatability.

Good luck with it
 

groberts101

Golden Member
Mar 17, 2011
1,390
0
0
"can" is not going to necessarily mean that he "should".

IMHO, there is little to be gained with the OP's problem IF the underlying issues are not remedied first(which remains to be seen without the system spec's). He'll just be out the 10 bucks to send the drive out and end up in the same boat with a lighter wallet in the end.
 

SickBeast

Lifer
Jul 21, 2000
14,377
19
81
In my case the RMA fixed the problem. My SSD was dead. OCZ have been having a ton of problems with the Vertex 2 drives.

What do you think the OP should do? If his drive is dead he can't put on the latest firmware.
 

groberts101

Golden Member
Mar 17, 2011
1,390
0
0
Either I misunderstood?.. or I'm guessing that you misunderstood his actual issue then. He doesn't have panic locked drive that's completely inaccessible. He has a "cold boot detection issue".

Totally different problem entirely.
 

sequoia464

Senior member
Feb 12, 2003
870
0
71
Either I misunderstood?.. or I'm guessing that you misunderstood his actual issue then. He doesn't have panic locked drive that's completely inaccessible. He has a "cold boot detection issue".

Totally different problem entirely.

what exactly is "panic locked"? I have a couple of Vertex 2's that I had in raid0, with the OS on them. About 15 months into using them, out of the blue, no prior indication of any issues, couldn't get into windows. I can see the drives in bios, but not windows. Is this indicative of the panic lock?
 

Elixer

Lifer
May 7, 2002
10,371
762
126
I have since 2010 nov. my vertex 2, i saw everyone has this cold boot problem. I think I have it too, every time i want to boot my pc I need to restart it, because it wont see my ssd or any other boot device.


so my question is can I RMA It? to get another one or how can i fix this problem.

This was my unit, I had to RMA it twice. Both times, I got the dreaded green + red LEDs on at the same time, and there is nothing you can do to fix it, so only option is RMA it. That is what the panic locked SSD does.

Though, I would still post in the OCZ forums.
 

groberts101

Golden Member
Mar 17, 2011
1,390
0
0
what exactly is "panic locked"? I have a couple of Vertex 2's that I had in raid0, with the OS on them. About 15 months into using them, out of the blue, no prior indication of any issues, couldn't get into windows. I can see the drives in bios, but not windows. Is this indicative of the panic lock?

no, bud. "Panic lock" is a totally lost drive. Non-detected no matter where you put it or how you try to access it. Completely gone.

What you speak of is related to data and/or firmware corruption and can be remedied with a secure erase and forced flash/re-flash to return the controller and all nand to a fresh factory state.

Then it would be wise to not sleep/hibernate the drives in any manner that would cut power to the drive(S1 would still be OK to do) and possibly check cabling with an added slight bump in SB/PCH voltage to reduce the loading that can easily occur with fast raids. Many underestimate signaling and voltage fluctuations as possible cause and go right into blaming the controller. Hope that helps. :)
 

sequoia464

Senior member
Feb 12, 2003
870
0
71
no, bud. "Panic lock" is a totally lost drive. Non-detected no matter where you put it or how you try to access it. Completely gone.

What you speak of is related to data and/or firmware corruption and can be remedied with a secure erase and forced flash/re-flash to return the controller and all nand to a fresh factory state.

Then it would be wise to not sleep/hibernate the drives in any manner that would cut power to the drive(S1 would still be OK to do) and possibly check cabling with an added slight bump in SB/PCH voltage to reduce the loading that can easily occur with fast raids. Many underestimate signaling and voltage fluctuations as possible cause and go right into blaming the controller. Hope that helps. :)
Thanks, I will try that. Appreciate the help.