OCZ Vertex PLus 120GB SSD - recovering from Sandforce bug

[dulcificum]

Tried to cold boot PC after disconnecting my UPS.
Windows couldn't boot.
Turns out SSD (boot drive) is not being recognised by UFEI/BIOS.
Have tried alternative SATA ports, power cables and SATA cables.
Blue LED still comes on inside drive.
Further investigation suggests it's the Sandforce bug.
Have tried the following suggested fixes:
a) repeatedly restart
b) boot PC with just SATA power connected, leave running for 30 minutes, connect SATA data, reboot without power off
c) boot PC with just SATA power connected, leave running overnight, connect SATA data, reboot without power off
d) boot into live CD such as PartedMagic and see if that can awaken the SSD.

Running out of options now. Anyone got any other plans?

[satrow]

Try the routine detailed by Crucial here: http://forum.crucial.com/t5/Solid-St...tem/ta-p/65215

[dulcificum]

That's similar to b) but still no dice

Any other way to trick the drive into thinking the power is good?

[dulcificum]

(although instructions are unclear as preliminary blurb refers to connecting only power while numbered points refer to only disconnecting the power)

[dulcificum]

Guess I need to write off my data, wait for an RMA then reinstall everything

[Agent]

Sadly, yep.

There are a few of us on here who warn people about Sandforce drives, as even with the latest firmwares, I still see issues like this fairly often.

There seems to be two separate issues with it vanishing from the BIOS:

The first is 'deep sleep' related, where the drive just won't wake up. The steps you've done above though should have sorted this.
The second is just near instant death. Gone. No BIOS recognition for you. A lot of people seem to think this is controller related and not firmware, but Sandforce have always been very quiet and never confirmed anything.

You need to keep in mind that not even Intel, with their extensive validation program on Cherryville could produce a drive that wasn't subject to BSOD and BIOS vanishing (although not as bad as others) issues on some systems.

[dulcificum]

Waaaah

FWIW, I never had any BSOD issues with the drive (even with sleep being used) but last time I disconnect my UPS I had the disappeared-from-BIOS issue and had no clue what was happening. After about 5 hours it randomly works when I unplugged an unattached USB cable from the front panel. I was bemused.

[John013]

Sadly, yep.

There are a few of us on here who warn people about Sandforce drives, as even with the latest firmwares, I still see issues like this fairly often.

There seems to be two separate issues with it vanishing from the BIOS:

The first is 'deep sleep' related, where the drive just won't wake up. The steps you've done above though should have sorted this.
The second is just near instant death. Gone. No BIOS recognition for you. A lot of people seem to think this is controller related and not firmware, but Sandforce have always been very quiet and never confirmed anything.

You need to keep in mind that not even Intel, with their extensive validation program on Cherryville could produce a drive that wasn't subject to BSOD and BIOS vanishing (although not as bad as others) issues on some systems.

I believe that the way a controller is implemented depends on the manufacturer of the SSD. Its a little stange how this works though. Personally my vertex 3 and intel 530 are still serving me well. wonder why some fail and others dont. Also have read cases of samsung failing as well