Full sector access with sector edit but none with DE task

[Scorpion]

Hi all,

I have a very weired case.
I got the following usb only drive
Model : WDC WD5000LMVW-11VEDS0
Firmware : 01.01A01
Capacity : 465.76 GB (976 773 168)

The drive have 2 heads (0,1).
I converted the usb to sata and successfully read all the data from head 0 BUT noting from head 1.
I got full data access (head 0 & 1) from the utility by using sector edit but noting (head 1) from DE task.
When tring to read the data (head 1) inside the task using DE I got errors and noise clicks from the drive.
How it could be that I have easy and full data access without any noise from head 0 & 1 using the utility but nothing (head 1) from DE task?

How can I use the fact that the utility gives me full data access (from head 1) and recover the lost data ?
Heads test run successfully over head 0 & 1 without any errors.

Best Regards,

[labtech]

Head 1 is likely damaged. Needs replacement.

[Scorpion]

Head 1 is likely damaged. Needs replacement.

How it could be that the utility gives me full access to the data but nothing with the DE task?

[labtech]

Define "full access" in this context, please?

[Lylor]

Are you sure that you read thru UDMA66 mode? Not thru Active utility in DE?

[labtech]

I would.recommend building heads map in DE. Find the LBAs of a few different areas assigned to head 1. Open those same LBAs in the utility and confirm being able to read.

[Scorpion]

I would.recommend building heads map in DE. Find the LBAs of a few different areas assigned to head 1. Open those same LBAs in the utility and confirm being able to read.

This is exactly what I did and this is way it is so weired.
I have full LBA access (head 0&1) through WD Marvel utility but can't read the same sectors in the DE task

[ddrecovery]

Are you sure your destination drive (if using one) is writing data? Or did your PC grab it at some point?

[Scorpion]

Are you sure your destination drive (if using one) is writing data? Or did your PC grab it at some point?

Sure the destination drive writing data.

[ddrecovery]

How do you know if all sector access in PC3000 errors?

[data-medics]

Try hotstarting the drive by subbing one head at a time in RAM and soft resetting it. See if you can get sector access for that particular head in DE, then try turning the other head back on in RAM. I've seen an odd issue like this a couple times, but always managed to get it reading.

[ddrecovery]

You may also want to close the DE task down and restart it just to make sure you are picking up the destination drive. Also make sure you don't get a log message saying 'catastrophic failure', this is also an indication that the destination drive is not being written to.

[Scorpion]

Hi all

Thank you for your help!
I digged over the drive and after I didn't find any solution to that weired case I replaced the heads and get full access to data in the DE too.

[labtech]

Fairly common behavior on that family drive, hence the suggestion from the beginning.

[Amarbir[CDR-Labs]]

Fairly common behavior on that family drive, hence the suggestion from the beginning.

Labtech ,
Awesome Observation Sir ,Thank you

[ddrecovery]

Fairly common behavior on that family drive, hence the suggestion from the beginning.

Labtech ,
Awesome Observation Sir ,Thank you

+1