Truly Mysterious Case

[DataMedics]

I've got a case here which has me truly baffled. I've handled a lot of similar cases, but this one I just can't figure out.

Drive came in it was head stuck. I freed the heads up carefully.
On power up the drive fully ID's shows capacity everything. I backed up all modules and tracks without any issue.
When I try to read a sector it gets ABR error instantly.
Tried editing head map in RAM but it would go unstable as soon as I soft reset it.
Checked all modules in directory and all important modules pass check for both head 0 and 1.
Did a heads test and found H5 to be faulty.
Replaced heads with donor ones, and all heads pass test now.
I've confirmed that all heads can both read and write data.
However, I still get ABR error on any attempt to read sectors like there is a translator issue.
I've tried subbing out the service area regions.
I've even completely moved the SA from heads 0 and 1 to heads 2 and 3.
I've tried regenerating the translator
I've tried rebuilding the P-list, then again rgenerating the translating.
I've done the slow responding fix, and tried disabling things in module 02
I've tried pretty much everything I can think of and no matter what I can't get this thing to read a sector.

Any ideas? Any WD masters who'd like to take a quick look remotely? I've already had another tech look at it via TeamViewer and he's stumped too.

I'm certainly willing to throw some hard cash to whoever can solve this one. At this point I care more about figuring this out than I do about the money from the case.

I've also noticed that even just on a fresh restart the drive will go unstable if you do a soft reset to it.

[DataMedics]

OK, I think I figured out what's going on. There is a slight difference in the sliders, perhaps enough that it'll only allow SA access but not user data. I posted some pictures here: https://www.data-medics.com/forum/wd-my ... t1569.html

[Filipp_TS]

Hello,

Thanks for this info.
Yes sliders are different and have a different geometry.
As result heads allow to read a service area data density but not a users area.
Well, as you know the solution is find a matched donor heads.

[DataMedics]

Case solved, data recovered. The donor I finally ended up using was nowhere close to what I'd usually match, though.

Patient:
WD20EARS-00MVWB0
HHRNNTJCH
Jun 2012
Malaysia
Preamp Vendor: 0001
Preamp Revision: 0001

Donor that worked:
WDEARX-00PASB0
DARNHT2MAB
Jul 2012
Thailand
Preamp Vendor: 0000
Preamp Revision: 0005

[Amarbir[CDR-Labs]]

Source of the post I've got a case here which has me truly baffled. I've handled a lot of similar cases, but this one I just can't figure out.

Drive came in it was head stuck. I freed the heads up carefully.
On power up the drive fully ID's shows capacity everything. I backed up all modules and tracks without any issue.
When I try to read a sector it gets ABR error instantly.
Tried editing head map in RAM but it would go unstable as soon as I soft reset it.
Checked all modules in directory and all important modules pass check for both head 0 and 1.
Did a heads test and found H5 to be faulty.
Replaced heads with donor ones, and all heads pass test now.
I've confirmed that all heads can both read and write data.
However, I still get ABR error on any attempt to read sectors like there is a translator issue.
I've tried subbing out the service area regions.
I've even completely moved the SA from heads 0 and 1 to heads 2 and 3.
I've tried regenerating the translator
I've tried rebuilding the P-list, then again rgenerating the translating.
I've done the slow responding fix, and tried disabling things in module 02
I've tried pretty much everything I can think of and no matter what I can't get this thing to read a sector.

Any ideas? Any WD masters who'd like to take a quick look remotely? I've already had another tech look at it via TeamViewer and he's stumped too.

I'm certainly willing to throw some hard cash to whoever can solve this one. At this point I care more about figuring this out than I do about the money from the case.

I've also noticed that even just on a fresh restart the drive will go unstable if you do a soft reset to it.

Jared Boss ,
I have a few questions for you

You Said : I've tried subbing out the service area regions.
My Question : What Do You Guys Do With Regions editing Feature in PC3K ,For Me SA Blocking Is Good Enough To Work ,Whats The Time You Work With This Feature

You Said :I've even completely moved the SA from heads 0 and 1 to heads 2 and 3.
Questions : Can You Let Me Know Briefly How You Do This

[DataMedics]

It's by editing the SA regions and writing the region as read via composite to different SA region addresses.

Got the drive to ID that way, so it definitely was able to load the SA from the other heads. But, as it turned out it was a heads compatibility issue anyway.