OCZ Vertex 2 240GB SSD for recovery

[hhddrec]

hhddrec, do you have another (similar to it) SSD OCZ drive?
If you do, then what voltage for NAND chips it is provide? Can you measure it?

And, what exactly written on U5 chip? Is it SPI flash?
If it is, then, do you have a SPI programmer to read it?
If you do, then it is possible to try to analize a dump from it.

But again, chances to get data are low, it is difficult case.

Thanks to all people helping in this case.

sorry for delay

No similar SSD, but i am speaking with customer and maybe will be one, if yes better, we can compare info betwen.
Another news from customer, hi said me that the notebook where was instaled this SSD was failed by heat.
Lot of heat that seems came form VGA.

I think this is a important news because makes stronger the view from fzabkar. Hi said:

the MLCC article I alluded to earlier suggests that heating to 200 degC can sometimes "self-heal" a leaky MLCC

Thaks to all People who helps here.

[hhddrec]

Even if U5 is just a some kind of configuration storage, because of power failure (if), it may contain now a "garbage".
Make sure also, that U5 is also powered with correct voltage.

U5 Volt.
U5 Pin5 t g = 2.81V


download/file.php?id=6405&mode=view

[hhddrec]

Hi HaQue,

Your diferent way is welcomed. This is other way, ill test to to close contacts 2-3 on ATMLH008, but i need tech info about mine IC

[fzabkar]

U5 has a working voltage range of 1.7V - 5.5V, so 2.8V is OK.

The number "ATMLH008" is not the actual part number. See the "Part Marking" section of the AT24C256C datasheet (page 14).

ATML = Atmel
H = Industrial/NiPdAu Grade/Lead Finish Material
008 = YWW date code (week 08 of 2010)

The marking code is on the next line (2ECL).

By shorting pins 2 and 3, the EEPROM's address pins are shorted, which means that the controller will not be able to detect it. Therefore the controller would power up in kernel (?) mode.

[hhddrec]

BlackST, your feelings was not lying.
hhddrec Do it on your own risk. If you feel you skilled enough.
Here is what you need to do. Be ready to spend some time and hold your nerves. Result is not guaranteed.

Preparation:

Find a separate good working PSU for usual desktop computer. 300-350 watt will good. On it's connector for mother board, locate a green wire. Short it with a black wire (near it) with any piece of wire, or metal clip.
Load PSU with any HDD and plug it in to the powerline. Your HDD should spin up and recalibrate. With a multimeter check +5v(red), +12v(yellow) and 3,3v(orange) against a ground wire (any black). They should be ok. Switch it off with it's power switch.
On computer stand, where you doing your hdd repair and data recovery, locate any, free Molex connector, and connect it's ground wire (black) with the same, Molex connector's ground wire (black) on just tested PSU. With any suitable wire. Ensure, that contact is good enough. Be careful not to short anything.
Now we have combined a grounds of bouth PSU by these way.
Connect computer's stand SATA data cable to the hdd, which powered from a separate PSU. Boot computer stand to a DOS and load MHDD.
Switch on separate PSU with it's power switch and wait, until hdd recalibrate.
In mhdd select appropriate port and check with "eid" command, is that drive visible or not. If it visible, then you can run a surface test for a couple of seconds, to make sure, that everything is ok.

Now the Voodoo magic:

Switch off bouth computer stand and separate PSU.
Replace HDD with faulty OCZ drive.
Switch on computer stand again. Load mhdd. Select appropriate port.

1. Switch on a separate PSU with it's power switch.
2. Wait a bit.
3. Give mhdd "eid" command.
4. Does OCZ detected?

If not, switch off separate psu with it's power switch, wait couple of seconds to allow PSU shut down, and go to the step 1.
(You can vary the time on a step 2.)
If yes, then with any cloning software, avaiable to you, make a clone of OCZ drive.

These can take a while, so i warned you.

Hi Randy

I try this waiting diferent amount of time (1 sec, 2 sec, 3 sec, 4 sec, ... ) about 10 times but not SSD is not recognized. by MHDD.

[Doomer]

I try this waiting diferent amount of time (1 sec, 2 sec, 3 sec, 4 sec, ... ) about 10 times but not SSD is not recognized. by MHDD.

It's because Voodoo works only on SSDs made in Africa

[hhddrec]

Hi Doommer; is welcome your joke. Thanks for making me laugh.
Hahahaa.


but continuing with the case

Hi Randy

I try this waiting diferent amount of time (1 sec, 2 sec, 3 sec, 4 sec, ... ) about 10 times but not SSD is not recognized. by MHDD.

Note: I plug power to SSD, wait a bit, DRSC (in blue) and DRDY (in blue), and AMNF (in RED). When i execute "eid" commmand always get: BUSY (green), and DRSC (in blue) and DRDY (in blue), and AMNF (in RED)

[fzabkar]

If you short U5's address pins, then this will be one way to verify whether the POWR607 is releasing Power On Reset. If you get output from the serial console, then this will prove that the controller is not brain dead. If not, then this would support the idea that POR is not being released, which would in turn support the idea that Vio (or Vcore ?) is too low.

[fzabkar]

There are similar PCBs in this review:
http://www.storagereview.com/ocz_vertex ... d22vtxe60g

They use Hynix H27UBG8T2ATR MLC NANDs. These are specified for operation over a range of 2.7V to 3.6V.

http://www.szyuda88.com/uploadfile/cfil ... 220663.pdf

[hhddrec]

There are similar PCBs in this review:
http://www.storagereview.com/ocz_vertex ... d22vtxe60g

They use Hynix H27UBG8T2ATR MLC NANDs. These are specified for operation over a range of 2.7V to 3.6V.

http://www.szyuda88.com/uploadfile/cfil ... 220663.pdf

I'll test v NAND chips

See pic

Attachments

[fzabkar]

If you want to probe the NAND voltage, then I suggest you pick a safe spot such as an adjacent filter capacitor. For example, C39 next to U16 on the controller side looks reasonably safe.

[hhddrec]

If you want to probe the NAND voltage, then I suggest you pick a safe spot such as an adjacent filter capacitor. For example, C39 next to U16 on the controller side looks reasonably safe.

I'll Do it.

Thanks Frank

[HaQue]

Did you manage to get a better log output?

[hhddrec]

Did you manage to get a better log output?

sorry i do not untherstand You?
can you explain better.

Thanks

[HaQue]

Did you manage to get a better log output?

sorry i do not untherstand You?
can you explain better.

Thanks

Did you short pins 2-3 on U5 and did this give a terminal output with clear text instead of garbage?

[hhddrec]

Did you manage to get a better log output?

sorry i do not untherstand You?
can you explain better.

Thanks

Did you short pins 2-3 on U5 and did this give a terminal output with clear text instead of garbage?

sort pins is safe to SSD?

[HaQue]

Yes, you would be shorting the pins 2-3 on U5, which is AT24C256C. Read the post by Fzabkar above.


I read on another forum that the poster was able to get a clean text serial output. You got a serial output like this:

Code:

I atach to tx/RX and i get this log:



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 Aug 22 2011 18:55:20 BuildServer:FW_Common_Build_Release:P1_3_6_4_MP4_Patch4_RC1_Drop-333796 ***
IMFT25 Timing EPch
RCPch SAK0
ÿ ýÞÙ °€¤

ýÞýÞýÞ}ýÞýÞþÀþ?}ýÞýÞ}ýÞýÞ}ýÞýÞýÞýÞýÞýÞýÞþ‚ýÞ
ýÞýÞ\º¯ýÞýÞýÞkŸ4R ýÞÙ °€<¤

ýÞýÞýÞ ýÞýÞýÞýÞýÞýÞ
ýÞýÞýÞ}ýÞýÞ}ýÞýÞýÞýÞýÞýÞýÞþ‚ýÞ
ýÞýÞ\º¯ýÞýÞýÞHi(Ò ýÞÙ °€”¤

ýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞ ýÞýÞ}ýÞýÞ}ýÞýÞýÞýÞýÞýÞýÞþ‚ýÞ
ýÞýÞ\º¯ýÞýÞýÞ<W€Í ýÞÙ °€ð¤

ýÞýÞýÞýÞ
ýÞýÞýÞýÞýÞ÷
ýÞýÞ}ýÞýÞ}ýÞýÞýÞýÞýÞýÞýÞþ‚ýÞ
ýÞýÞ\º¯ýÞýÞýÞ:kû ýÞÙ °€H¥

ýÞýÞýÞ$ýÞýÞýÞýÞýÞýÞ÷
ýÞýÞ}ýÞýÞ}ýÞýÞýÞýÞýÞýÞýÞþ‚ýÞ
ýÞýÞ\º¯ýÞýÞýÞû§? ýÞÙ °€`y

ýÞýÞýÞ
ýÞýÞýÞÿþ?ýÞýÞýÞýÞÿþ?ýÞýÞ¬ã
€`ÿþ?
ýÞýÞýÞøºþ?ýÞýލ×õ ýÞÙ °€¨y

ýÞýÞýÞýÞýÞýÞýÞÔy
äy
ýÞýÞýÞýÞýÞýÞæýÞÙ °€ýÞýÞýÞýÞäýÞýÞýÞØx ýÞ Ù °€¨y


and if the information is correct, you should get a better output like this:

Code:

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 ...

then you may have a better idea whats wrong.

[hhddrec]

Yes, you would be shorting the pins 2-3 on U5, which is AT24C256C. Read the post by Fzabkar above.


I read on another forum that the poster was able to get a clean text serial output. You got a serial output like this:

Code:

I atach to tx/RX and i get this log:



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 Aug 22 2011 18:55:20 BuildServer:FW_Common_Build_Release:P1_3_6_4_MP4_Patch4_RC1_Drop-333796 ***
IMFT25 Timing EPch
RCPch SAK0
ÿ ýÞÙ °€¤

ýÞýÞýÞ}ýÞýÞþÀþ?}ýÞýÞ}ýÞýÞ}ýÞýÞýÞýÞýÞýÞýÞþ‚ýÞ
ýÞýÞ\º¯ýÞýÞýÞkŸ4R ýÞÙ °€<¤

ýÞýÞýÞ ýÞýÞýÞýÞýÞýÞ
ýÞýÞýÞ}ýÞýÞ}ýÞýÞýÞýÞýÞýÞýÞþ‚ýÞ
ýÞýÞ\º¯ýÞýÞýÞHi(Ò ýÞÙ °€”¤

ýÞýÞýÞýÞýÞýÞýÞýÞýÞýÞ ýÞýÞ}ýÞýÞ}ýÞýÞýÞýÞýÞýÞýÞþ‚ýÞ
ýÞýÞ\º¯ýÞýÞýÞ<W€Í ýÞÙ °€ð¤

ýÞýÞýÞýÞ
ýÞýÞýÞýÞýÞ÷
ýÞýÞ}ýÞýÞ}ýÞýÞýÞýÞýÞýÞýÞþ‚ýÞ
ýÞýÞ\º¯ýÞýÞýÞ:kû ýÞÙ °€H¥

ýÞýÞýÞ$ýÞýÞýÞýÞýÞýÞ÷
ýÞýÞ}ýÞýÞ}ýÞýÞýÞýÞýÞýÞýÞþ‚ýÞ
ýÞýÞ\º¯ýÞýÞýÞû§? ýÞÙ °€`y

ýÞýÞýÞ
ýÞýÞýÞÿþ?ýÞýÞýÞýÞÿþ?ýÞýÞ¬ã
€`ÿþ?
ýÞýÞýÞøºþ?ýÞýލ×õ ýÞÙ °€¨y

ýÞýÞýÞýÞýÞýÞýÞÔy
äy
ýÞýÞýÞýÞýÞýÞæýÞÙ °€ýÞýÞýÞýÞäýÞýÞýÞØx ýÞ Ù °€¨y


and if the information is correct, you should get a better output like this:

Code:

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 ...

then you may have a better idea whats wrong.

Hi HaQue.

Thaks for your help here

First: I must say that in in my first test i get output data via serial, but after i get no data via serial port output (today i get no data neither)


I tried to test serial output shorting pins 2 and 3.
but no response via serial Port.

Note: when i short pins 2-3 and them power up SSD the green diode is ligthing but Red diode not ligthing

Attachments

[hhddrec]

i continue testing to read via serial port:

and when i short pins 2-3 and them power up SSD the green diode is ligthing but Red diode not ligthing
them if i not short SSD only green diode continues ligthing. but and no data via serial port

but if power up SSD and when them short pins 2-3, Green diode is ligthing and Red diode is ligthing
too. and no data via serial port

but if power up SSD wait for a second (red diode ligth for a second and them red diode not ligth for a second too) and just (in that moment when not ligth red diode) short pins 2-3, Green diode is ligthing and Red diode is ligthing, and not get data via serial port too.

[hhddrec]

Continue testing About BIOS:

If power up SSD and when them short pins 2-3, Green diode is ligthing and Red diode is ligthing
too. and no BIOS info

Attachments