WD5000AAKS-00V1A0 Crash

[drd]

I will try WDR.

[drd]

I'm going to test WDR. Is WDR able to work over USB or do I have to conntect the HDD to SATA?

[drd]

Status quo:
- Old HDD spins up with old PCB
- New HDD works with it's own PCB (with bad soldered EEprom)

- Old HDD didn't spin up with new PCB (with changed EEprom)

Does WDR run with wine and over SATA-USB-Interface?

[drd]

I'm really sure. Nevertheless, I ripped that pad off after I tested this new PCB with the old EEprom. It's now shorted and is still working (new HDD with it's own working PCB and EEprom).

[Keatah]

To be sure of being sure, you need to see the pertinent schematic.

[louis]

God..dammnned! You're just making someone else's repair bill go 2x higher.

When you stop?!! I've read your last 4 posts on this topic. If you can't say anything than..."seed a pro" (perhaps like you) then say it once an go away!! You don't help anybody performing like this. I like to believe that everyone who ask for help here knows that with a software click or a hand shake could ruin forever the data. If that happens at a "pro store" and i'm sure that happens...they would simply tell you..sorry...we've done what we could. there is no malpraxis in this "world"!!

Spildit realty helps around..well... as much it's possible.

[drd]

Thanks for your help.
I was able to read out the flash from the new HDD with the bad soldered EEprom. But I wasn't able to read out the defective one.
Next, I would try to desolder the EEprom and read it out with a Galep, shouldn't I?
Should I try to mount new PCB with wrong EEprom on defective HDD? Should it spin up?

BTW: New HDD seems to work fine. I copied files to it and copied them back.

[drd]

I attached the .bin-files from the new ROM (do you mean the EEprom?). The HDD is spinning all the time, still while reading out the EEprom. "SAFE MODE" was checked.
I'm able to use an external programmer to read out the EEprom on this weekend.
I changed new PCB with it's own ROM to defective HDD and it doesn't make any noise and doesn't spin up.

BTW: Primary failure was the power supply. The person told me, he saw some smoke out of the power supply. Then he shut it off and tried to reboot, but PC fails to boot while recognition of HDD.

Attachments

WDC WD5000AAKS-00V1A0_05.01D05_WD-WMAWF2172998.zip

EEprom Read out from:
WDC WD5000AAKS-00V1A0_05.01D05_WD-WMAWF2172998

(179.59 KiB) Downloaded 475 times

[drd]

I put the old PCB without HDD into my PC and now, the PC was able to boot. Before, with HDD, the PC wasn't able to boot. Nevertheless, I wasn't able to read out EEprom.

Defective HDD with new PCB but without contact to head stack, spins HDD up. It sound like the old PCB, but without clicking. The HDD spins up, stops an tries to spin up, again. After that, it stops.

I thought of swapping old PCB to new HDD. But I thought it wouldn't be a great idea because it could break the new HDD.
I will change the EEproms another time.

[drd]

Do you mean the new PCB from the new working HDD is defective?

[drd]

Thank you very much for your help. I will think about that tomorrow. For now, I have to finish.
But I logged SPI communication on old PCB. For watching it, you need Salea Software: http://www.saleae.com/downloads

Attachments

SPI-Flash.zip

Recorded SPI-communication

(8.8 MiB) Downloaded 579 times

[drd]

New PCB with it's original ROM without drive won't work with WDR. I'm not able to read out the ROM without drive.

[drd]

I could log SPI communication from new PCB to verify.

[drd]

Some news. I tried WDR-4.0 from louis an attached bad PCB to good drive without contact to head stack and was able to read out EEprom. Log and bin files in attachment.
Here is the log from good PCB and drive:

WDC WD5000AAKS-00V1A0 FW:05.01D05 SN:WD-WMAWF2172998 (ROYL selected) port 0xFE00
Logical: Cyls 16383, Heads 16, Sectors 63, LBA 976773168, 500Gb
Controller Buffer Size: 16384Kb
Family: Tahoe_PL (Royl)

ROM Rev: 11.58C
Mod 0D : 00010000 (01.00)
Mod 4F : 00110058 (11.58)
DIR Rev: 00020000 (02.00)
OVL Rev: 00110059 (11.59)

Is it possible to upgrade firmware in good PCB? Is the EEprom from defective PCB corrupted?
Because of logged spi-communication, I would rather say, EEProm is ok.

[louis]

Can't follow you. so, tell us..you have the donor with which ROM soldered now?

You should have had a rom backup/compare before unsoldering the ROMs...and one after...in this way you could have found if the firmware data lies inside the rom or inside mcu.

[drd]

I've got:

- one defective HDD with almost defective PCB with it's own EEprom
- one working HDD with its own PCB and its own EEprom

Status quo:

- defective HDD spins up and you hear some clicking, then it spins down
- working PCB with old EEprom doesn't work on defective drive - it doesn't either spin up
- same with working PCB and its own EEprom
- defective drive spins up withworking PCB and its own EEptom, but without head stack connection
- WDR is able to read out EEprom on working PCB with its own EEprom
- WDR isn't able to read out EEprom on defective HDD with defective PCB
- WDR isn't able to read out EEprom on any PCB without connected drive
- WDR is able to read out EEprom on good drive with goot PCB without connected head stack
- WDR is able to read out EEprom on good drive with bad PCB without connected head stack

Differences:

- Some different assembly on these PCBs
- Obviously different firmware versions

Does anyone have a schematic from this PCB?
So, I will try to reprogram working PCB with old ROM-Image.

Attachments

_12.0MD_.zip

Log and bn-files defective PCB

(179.86 KiB) Downloaded 441 times

[drd]

Hi,
I flashed the bin from old ROM into new ROM and mounted new PCB to old drive - I wont' spin up.
But new drive is still working with old ROM, obviously.
Maybe, I should move R48, R68, R71 and R51 from old PCB to new PCB an remove R10, C48 and R50 from new PCB (all components near pads to heat stack)?!

[Nesa]

As I can see, the problem is in head(s) or preamp so you can do nothing with working on PCB ("flashing", removing or changing components...).

Please, learn how hard drives work.

[Nesa]

Clicking sound in your case is because of the heads can not find servo. Possible reasons can be: damaged servo, bad heads, bad preamp, bad reading channel, bad ROM content etc. In any of those cases you can not do anything without tools, knowledge and experience. Sorry for saying but you have nothing of those.

[Nesa]

...
Can you confirm if you can use the new drive correctly, write and read files from it, using ROM (FLASHED BY WDR) from damaged drive ? If so ROM of the 2 drives are compatible !!!

There is no possibility for this because the fw versions are not the same in both drives:

- Old one: 12000M
- New one: 110058