Problem wd7500bmvw-11ajgs2

[mhp666]

I have the hard drive that I have put in the photo.
I do not know the firmware that it carries nor the family of hard disk that it is.
I have the mrtlab and it does not detect it with a sata card.
I changed the heads and they work well.
Can somebody help me. Thank you.

Attachments

Image of HDD

[applpp22]

is hard disk in busy state ?? in MRT

[mhp666]

No pero cuando intenta detectar el modelo se queda en BUSY

[mhp666]

No but when you try to detect the model it stays in BUSY

[mr_spokk]

Have you applied slow-fix?

[mhp666]

I do not know which HDD family to select, it does not detect anything but the controller is fine.

[ddrecovery]

Isolate the pcb, let it come RDY, start the utility in kernel mode and you can see the family. Block SA access. Restate the drive, us a leader. Start utility in normal mode and see if you can get SA access to solve issues.

[BGman]

It's FBLITE family.

[unknown]

It's FBLITE family.

+1
FBLITE with 4 heads with one isolated head.

@OP: what was the initial problem?

[mhp666]

Thank you very much to all for your help, with which I have verified that the family is fblite as you have told me and I have learned a very important thing isolating the motherboard and detecting in kernel mode the family.
I have obtained the following information with the isolated PCB.

Technology mode key : ..........................: OK

RAM:
Read HDD Info : ................................: OK
Heads number : .................................: 1
Head map : .....................................: 7
SA Cyl Count : .................................: 256
Serials Mark : .................................: 0xFE16
Control version : ..............................: A5C0

ROM:
Read Rom Infos : ...............................: OK
ROM Data Size : ................................: 256 Kb
ROM version : ..................................: 16.56H
ROM generation : ...............................: 16.56H
Link table version : ...........................: N0.38
ROM Firmware version : .........................: 00160056

ROM Modules:
Flash ROM dir reading : ........................: OK
Switched off heads : ...........................: Yes
Heads number : .................................: 0x4
Heads number in use : ..........................: 0x3
heads map : ....................................: 0,1,2

The initial problem of the disc was a blow while it worked. The heads are fine, I've tried them on another disk and they work, but the plates are a little marked just outside.

[colanco]

if you have access to SA--->
Work whith SA> solve slow responding problem ---> Power on/off

It's very likely that you're having problems with sectors

[colanco]

That said, I don't think you should work with client disks (yet).

Switching heads to a disk (WD) when you do not yet know the diagnosis of the disk and have serious problems diagnosing it......

[mhp666]

I agree that it may have been a bad move, but after taking the blow, I had to make sure of the state of the heads, sometimes not having done it has made my heads scratch the disc's plates. In fact this album tried to connect several times the client, and each time it was worse, so I decided to see the state of the heads.

[BGman]

Most likely several zones are damaged/unreadable. You could recover most of the data. Good luck.

[mhp666]

The problem is that when trying to detect the disk, it stays in busy and when trying to load a loader it fails and stays in busy. I will think about something, to try to have access to the SA, which at the moment I have not been able to do so.

Indeed, some damaged areas have, because at the edge of the upper plate the plate is scratched.

[BGman]

The problem is easy to solve. If you use WDMarvel I could help. If you use PC3K - go to PC3K forums.

[mhp666]

I can activate the wdmarvell for a month and so I try it. In the afternoon I buy it and I activate it.

[mhp666]

i have activate wdmarvell and i have mrtlab.

[colanco]

MRT can easily solve the problem, and you will also need DE to deal with the damaged areas.

If you have the latest version, enter again in kernel mode and disable the 411 module ( if you have this model)---> off/on -----> identification in normal mode ----->>(already automatically loads module 11) ------> solve slow responding problem -----> off/on -----> ok.

If the model does not have a 411 module, you will have to load module 11 by hand, you have many options, but believe me, it is simple, it is done daily (1st week of the first DR course).

Then you will have to deal with sectors and encryption (if you have one)....

[colanco]

Previous post would miss a step, after solving the slow problem you should enable the 411 module again.

A tip, do only these steps (or others that indicate you here), your knowledge of DR is very limited, if you do experiments with MRT/WDmarvell, it is possible that your client's data ends up in the trash can.