Western Digital WD20EARS-00MVWB0 can i swap PCB rev.P2 w P1?

[blue8]

Hi there!
2 years ago a WD20EARS-00MVWB0 died at boot of system and i left it in shelf till now.
Now i was looking on internet after a identical PCB and i found one but:

Mine hdd is: WD20EARS-00MVWB0 2060-771698-002 REV P2 2061-771698-802 07P
And on internet i found this: WD20EARS-00MVWB0 2060-771698-002 REV P1

So, the difference is that mine is ver. P2 and the donor is ver. P1
If i will swap Bios chip from mine to donor, will be ok, or need to be identical till the last letter?
Thank you so much!

[Amarbir[CDR-Labs]]

Hi there!
2 years ago a WD20EARS-00MVWB0 died at boot of system and i left it in shelf till now.
Now i was looking on internet after a identical PCB and i found one but:

Mine hdd is: WD20EARS-00MVWB0 2060-771698-002 REV P2 2061-771698-802 07P
And on internet i found this: WD20EARS-00MVWB0 2060-771698-002 REV P1

So, the difference is that mine is ver. P2 and the donor is ver. P1
If i will swap Bios chip from mine to donor, will be ok, or need to be identical till the last letter?
Thank you so much!

Hi ,
Does Not Matter buy another one and swap rom .If rom is not external then do get back here .Procedure would be a little different .

[data-medics]

Actually I have seen some cases where going from P1 to a P2 wouldn't work, not sure about this specific PCB though. I'd have to go back in some old notes to see which cases had this issue. Usually I've found that using a later revision PCB will work to replace an older one (e.g. replace REV A with REV C) but not always. A few boards need the exact revision to work even with ROM transfer.

[Amarbir[CDR-Labs]]

Actually I have seen some cases where going from P1 to a P2 wouldn't work, not sure about this specific PCB though. I'd have to go back in some old notes to see which cases had this issue. Usually I've found that using a later revision PCB will work to replace an older one (e.g. replace REV A with REV C) but not always. A few boards need the exact revision to work even with ROM transfer.

Jared ,
Yes in only few cases not all .You know what the reason is [ i have never figured this out BTW ] . from data to usb it really does not matter imho .Last time ordered pcb's from china from a very reputable seller i got several defective once .

[blue8]

Thank you so much to all of you!
Spildit, is not that diode, was the first thing that i checked despite the fact that hdd is start to spin. Actually the hdd start to spin and after... let say 5 sec it do a very slow tick and so on at every cca 5 sec. in an infinite loop.
I lost that donor pcb now, was on ebay but was on a biding of 3 faulted hdds and was too much as price (64 pounds). Now i am looking after another and when i will find a good price one i will take it and give it a try.
Thanks again to all of you!

[unknown]

5% PCB - 95% head/s (Pre-amp)

[pcimage]

Less than 1% chance a clicking drive of this model is down to PCB, you're wasting your time. Sorry to say

[northwind]

Less than 1% chance a clicking drive of this model is down to PCB, you're wasting your time. Sorry to say

+1

[data-medics]

Actually I have seen some cases where going from P1 to a P2 wouldn't work, not sure about this specific PCB though. I'd have to go back in some old notes to see which cases had this issue. Usually I've found that using a later revision PCB will work to replace an older one (e.g. replace REV A with REV C) but not always. A few boards need the exact revision to work even with ROM transfer.

Jared ,
Yes in only few cases not all .You know what the reason is [ i have never figured this out BTW ] . from data to usb it really does not matter imho .Last time ordered pcb's from china from a very reputable seller i got several defective once .

No, I've never figured it out either. They'll have the same MCU, MC, etc. but just don't work. I think the real problem ones are usually a REV A that can't be replaced with anything but another REV A board. The issue I suspect has something to do with the pre-fetch buffer size I think, just based on what I remember from the last time I had this problem.