data recovery to a SSD ocz vertex 2 80Gb

[athlesi7]

i have a ocz vertex 2 80gb which seems that doesn't get power. only the green led is on and at DDI seems buzy.
can someone do data recovery to it, how much will it cost and how long will it take.
PM
thank you

[hddguy]

You should note here the controller it uses.

It is not always possible to repair, in such situation it would be useful to know if it can be recovered through its NAND memory.

Most new Vertex use Sandforce controller, which is with encryption. Im pretty sure your case has Indilinx controller, but I am not 100% on that.

[fzabkar]

If it's an issue with the onboard DC-DC converters, then the parts cost should be very low (a few $).

If you would like to identify the power supply test points, upload a detailed photo.

[hddguy]

Common issue I see with Sandforce based Vertex is poor contact on 1 or more NAND chip. somehow legs of NAND can 'lift' and contact is no longer good. You can solve this through a reflow.

In case of bad controller, in my experience, device will show DRDY in status register but ID and capacity is wrong. This is same with Indilinx cases, but for Indilinx recovery is quite straightforward from NAND memory. Sandforce use encryption so repair is your only option.

Franc gives good advice, upload photo of PCB of side with Controller.

[cheadledatarecovery]

Hello there,

I've got a similar OCZ 120GB Vertex 2. When in DDI it is stuck in Busy, & can't ID the drive.

The controller chip is as follows:

Sandforce
SF-1222TA3-SBH
PAC461.00
0411 Taiwan

As such encryption will be on by default so removing the NAND chips is not much use. Does anyone have any suggestions? I'm currently testing the components on the PCB to see if there are any obvious failures.

The quality of the image attached is not great, if need I can take more focussed picture.

All the best,
John

[cheadledatarecovery]

Although I didn't mention it before, I don't get any info from the drive when I have it hooked up by the TX/RX

[fzabkar]

If you would like to verify the onboard supply voltages, then could we see a detailed view of the underside?

Did you measure anything at the Vcc terminal of the Tx/Rx header?

Do any of the three LEDs light up (ACT, FLT, PWR)?

Here are datasheets for the MT29F64G08 NAND Flash:
http://read.pudn.com/downloads160/ebook ... ,128Gb.pdf
http://wiki.laptop.org/images/4/48/CL1_NAND_Micron.pdf

Product brief for SF-1200 processor:
http://www.sandforce.com/userfiles/file ... 060110.pdf

[cheadledatarecovery]

PWR (green) & ACT (blue) lights are on constantly when powered. The FLT (red) light comes on when initially powered for a fraction of a second, then turns off.

Attached is jpg of the underside:

I haven't had chance to check the electronic components as a couple of emergency jobs have come in this morning. Once I have I will post the results.

Thanks for the help,
John

[DR-Kiev]

Read with programmer and show content of ROM chip.
And post terminal log please.

[fzabkar]

ISTM that the supplies are probably OK.

The Vcore and Vio (+3.3V) test points would be the two coils, L10 and L11, in the top left corner. Measure the load side, ie the plated through-holes at C82 and C99.

I can't see the markings on U33 and U38, but they would be the PWM regulators.

[Conair0001]

Hello,

I have similar issue like this.
I have the exact same drive and voltage at L11 / C99 is 0.9V, the voltage on L10 / C82 is 2.8V.
I have a short on D2, but it's not the diode itself, if I remove the diode, the short is still there and the diode itself works fine.

Does anyone have a schematics?

Any idea on how I could recover this?

Thanks and best regards,
Conair.

[Conair0001]

Connected terminal program to UART port, getting this:


CLI> PINRST
*** ROM 106 Mar 12 2009 20:29:35 ***
FW_SRC 0 SHA PASS!
*** EEPROM 207 Jan 3 2011 18:36:47 BuildServer:FW_Common_Critical_Fixes:P1_EEPROM_2_0_7_drop-290232 ***
IMFT25 Timing EPch
*** Patch 1.4.1 Mar 10 2011 16:30:10 BuildServer:P1_3_6_0_MP4_7:P1_3_6_0_MP4_7-300475 ***
IMFT25 Timing EPch
RCPch SAK0
ÿýÞÝÖÃX

Then lot's of strange characters.

[Conair0001]

Hello, can anybody help on this?

Thanks.

[labtech]

Hello, can anybody help on this?

Thanks.

Remotely, likely not.
If the recommendations given so far in the thread are not helpful enough, then send it to a REAL professional.

[Conair0001]

Do you have schematics for this HDD?
Or any information about the power-supply?

Are you sure it is 3.3V on both supplies?

Thanks.

[DR-Kiev]

Connected terminal program to UART port, getting this:


CLI> PINRST
*** ROM 106 Mar 12 2009 20:29:35 ***
FW_SRC 0 SHA PASS!
*** EEPROM 207 Jan 3 2011 18:36:47 BuildServer:FW_Common_Critical_Fixes:P1_EEPROM_2_0_7_drop-290232 ***
IMFT25 Timing EPch
*** Patch 1.4.1 Mar 10 2011 16:30:10 BuildServer:P1_3_6_0_MP4_7:P1_3_6_0_MP4_7-300475 ***
IMFT25 Timing EPch
RCPch SAK0
ÿýÞÝÖÃX

Then lot's of strange characters.

Can you give full terminal log, with this "strange characters" ?

[fayn]

Sure

Can you read that scrambled output?

Attachments

SF_terminal.TXT

Broken drive terminal output

(6.67 KiB) Downloaded 2263 times

[DR-Kiev]

Sure

Can you read that scrambled output?

Why not
Hmm, your drive have been turning on only 14 times . Almost new drive.

[fayn]

Hmm, your drive have been turning on only 14 times .

An unusual way of finding it out

I am curious what the drive tells about itself... Could you post / PM the output in a readable form?

[Conair0001]

Hello, could you send me these details as well?
Also, could you let me know how to decode?

Thanks.

Attachments

HDD_log.txt

(8.76 KiB) Downloaded 2129 times