Good afternoon. help cure OCZ Vertex2 40gb. After rebooting the SSD is not visible in the BIOS. I found the information that you can run a jumper it in safe mode and flash fails, the utility did not see SSD. The board has 3 LEDs. When the light is turned green and when you try to access the SSD light up red. On experience with flash drives, short contacts on the chip on a hot b tossed to SATA SSD determined and immediately disappeared from the system, blue LED lights up and is now with the lights green and blue. Plug your terminal:

CLI> PINRST
*** ROM 106 Mar 12 2009 20:29:35 ***
FW_SRC 0 SHA PASS!
*** EEPROM 202 Apr 30 2010 16:53:54 BuildServer:FW_Common_Critical_Fixes:FW_Comm
on_Build_Release-247324 ***
Micron Timing EPch
*** Patch 1.4.1 Sep 20 2010 13:33:48 BuildServer:FW_Common_Critical_Fixes:P1_3_3
_L_Drop-270756 ***
Micron Timing EPch
RCPch SAK0
ÿÿÿÿÿ\_ýÞýÞýÞø^(_ýÞýÞýÞm—ŒýÞÿÿÿÿìcýÞýÞýÞýÞýÞýÞÂvÄ1ýÞUdP‡
ýÞýÞýÞÿÿÿÕýÞýÞÕýÞýÞ
ýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞþ‚ýÞþ€ýÞýÞýÞ ‹IàýÞUdp‡
ýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞ
ýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞþ‚ýÞþ€ýÞýÞýÞXŠ&ýÞUdȇ
ýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞý

on a lot of garbage. If you turn not to consider him the information from the flash (SPI) in the terminal gives

CLI> PINRST
*** ROM 106 Mar 12 2009 20:29:35 ***
*** Patch 1.4.1 Sep 20 2010 13:33:48 BuildServer:FW_Common_Critical_Fixes:P1_3_3
_L_Drop-270756 ***
RCPch SAK0
Failed to read EPA=20038060, using ByteLaneMask=2, ByteLaneTable[0]=1
Failed to read EPA=20038060, using ByteLaneMask=1, ByteLaneTable[1]=0
Failed to read EPA=20038060, using ByteLaneMask=4, ByteLaneTable[2]=2
RCPch SHI
sysclk 150 MHz
JTAG En 0
Link ...

in this case if you connect it to your computer after long reflection, it appears in the BIOS, but SandForce 25gb. OS does not boot (even with the Linux boot loader office site is loaded but the utility does not see SSD). On hot in Windows is defined as the SandForce drive. Tell me how or where to read how to pick it up. Maybe someone can merge dump of SPI?

P.S. Sorry for the bad English.

Get this professionally diagnosed.

Sandforce use Encryption so the only option to save your data is to have the device professionally repaired, if it is possible.

Thanks for the advice, but I do not need information. I want to repair it yourself

PM sent.

_________________
Angel Data Recovery

@loiren, I would very much like to explore the voltage test points on the PCB. Do you have a multimeter, and would you be prepared to make some measurements?

If so, then please upload detailed photos of both sides of the PCB.

_________________
A backup a day keeps DR away.

DR-Kiev,
Здравствуйте, у меня такая же проблема с SSD диском, можно и мне подсказать рецепт исцеления данной железки?

a big mistake in embedded systems is assuming that output that is not human readable is "garbage"

read here on that "garbage" http://www.eevblog.com/forum/repair/ocz-vertex-2-ssd-firmware/

for what its worth, in this situation googling for should have been in the top 3 things to do.

this is Sandforce, the bane of DR engineers.

another link that may be of interest, though not 100% related to the thread:
http://www.overclock.net/t/1330730/ocz-firmware-2-25-trim-doesnt-work-bug-regression-bad-ocz-experience

on another note, this is interesting from the link I posted earlier..:


in particular:
would this turn JTAG functionality off? and would it be pssible to re-enable it in Terminal or by hacking the firmware and editing a start-up script?