WD30NMVW - issue in the controller of the motor

[ictsec.areait]

We have 2 WD30NMVW HD with the same PCB (2060-800041-000 REVP1).
One of these HDs is working properly while the other have a problem with the motor: when we connect the USB cable the motor does't start.
This problem is related to the PCB because the motor of the HD start again only swapping the board.
To access the user data on the disk can we copy the content of ROM from the original PCB and write it to the donor one using PC3000? (without moving the chip from original to donor PCB)
Thanks...

[Amarbir[CDR-Labs]]

Hi,
I am not sure what your question is ,or are you trying to tell us how you solved the issue

[ictsec.areait]

Hi Amarbir,
It was a question (there was also the question mark at the end... ).

I try to re-explain our problem...

We have 2 WD30NMVW: HD1 and HD2.
-) HD1 is working fine.
-) HD2 is broken: when we connect it to an USB cable the motor doesn't start.

Now we would like to recover the user data of the HD2...

We made some tests with these 2 HDs and we discovered that the motor of the HD2 is not burned: it starts again if we only change the PCB of the HD2 with the PCB of the HD1.
Yes, the HD2 is working again with the PCB of the HD1 but , obviously, the user data are not accessible.

Our question was: is there a way to recovery the user data without desoldering any chips from the PCBs?
Is it possible to use a procedure like this one? http://blog.acelaboratory.com/pc-3000-for-hdd-building-rom-image-from-sa-data-on-wd-marvell-drives-with-external-rom.html

Thanks...

[Amarbir[CDR-Labs]]

Source of the post Hi Amarbir,
It was a question (there was also the question mark at the end... ).

I try to re-explain our problem...

We have 2 WD30NMVW: HD1 and HD2.
-) HD1 is working fine.
-) HD2 is broken: when we connect it to an USB cable the motor doesn't start.

Now we would like to recover the user data of the HD2...

We made some tests with these 2 HDs and we discovered that the motor of the HD2 is not burned: it starts again if we only change the PCB of the HD2 with the PCB of the HD1.
Yes, the HD2 is working again with the PCB of the HD1 but , obviously, the user data are not accessible.

Our question was: is there a way to recovery the user data without desoldering any chips from the PCBs?
Is it possible to use a procedure like this one? http://blog.acelaboratory.com/pc-3000-for-hdd-building-rom-image-from-sa-data-on-wd-marvell-drives-with-external-rom.html

Thanks...

Hi,
You Can Try Reading The Patient PCB's Rom Using PC-3000 And Then Programming It On The Donor Board ,If That Works Voila ,If That Does Not Work You Have a Damaged/Corrupt Rom ,In That Case You Should Build Rom For Your Patient Drive

[Maxim_TS]

ictsec.areait, would like to add: you can also try to read and write the ROM using the COM-port like it described here: http://blog.acelab.eu.com/boot-rom- ... rives.html