WD5000BEVT Data Rescue

[fabianf]

HI together,

I have a WD5000BEVT. See Details

WED5000BEVT-22A0RT0
2060-771672-004 REV A
PN: XXXXX-XXX

Faileure: Wont recogniced by BIOS and System, doesnt matter if USB, ESATA or SATA

What I tried already:
- I checked the Harddrive on diferent PCs directly on the S-ATA Port, USB and E-Sata Port. -> same Problem
- I cleaned the contacts für the heads on the PCB -> the Disk was recogniced by the PC for 2 hours.
I start the Software for rescue and hat a lot of bad sectors. But before the scan was at the end of the disk, the disk was gone again -> same problem as before and drive shutdown after round about 20 seconds (connected by E-SATA)
- I bought a new PCB from the same model (WD5000BEVT-22A0RT0) with the PCB Board# 2060-771672-004 REV A. (The drive what i ordered spins and was recogniced by Windows). So I changed the PCB to the defektive one -> nothing happen same as before
- I transfered the Firmwarechip U12 to the PCB -> same as before with shutdown the drive by E-Sata, If i put it on the S-ATA Port inside the PC, the drive will be recogniced by the PC but I cant acces the drive. I can see it in the BIOS and diskmanagement.

If i try to RAW Copy the Disk i just get "Read Error occurred at offset ... LBA ... (uncorrectable error)
With Getdataback its the same problem. Error 1117 in HD129...
DDRescue start to copy but give me after 10 seconds an errorsize of 500GB...

Can anybody help me to fix the problem?

best regards
Fabian

[MindMergepk]

your drive seems to have partial bad heads / FW problem or combination of both.
search forum for slow-fix, it might be of some help.

DIY has it owns pros & cons, your data your choice.

[pcn]

Hi fabian,

If you want the data back stop playing with the drive, you have done all you can and it might have made the case worse. the drive has weak heads and/or media damage, that's why you get read errors. With a new pcb or ROM-Swap you can not solve this. With the right tools one might get the data off the drive without head change but one has to check heads / firmware first. This is not a DIY sorry, so if you need the data stop messing with the drive.

[pcimage]

Hi fabian,

If you want the data back stop playing with the drive, you have done all you can and it might have made the case worse. the drive has weak heads and/or media damage, that's why you get read errors. With a new pcb or ROM-Swap you can not solve this. With the right tools one might get the data off the drive without head change but one has to check heads / firmware first. This is not a DIY sorry, so if you need the data stop messing with the drive.

Couldn't have put it better myself

[fzabkar]

viewtopic.php?f=1&t=29187&start=20

http://www.alexsoft.org/viewtopic.php?t ... 4345#p4345

[fabianf]

@mindmergepk

thank u for the information, but theres no workflow how to do it. I just read, that I need sediv. Is that correct?

@pcn
das ist nicht meine erste HDD die ich wiederhergestellt habe. Ich möchte mich in diesem Gebiet eben weiterbilden und ein externer Dienstleister ist mir das daher nicht wert da mir hier dann auch die Erfahrungswerte fehlen. Das einzige was ich davon habe sind dann eben Kosten statt know how.

@pcn
its not my first hdd that i rescue. I will learn it how to do more in this case of Datarescue. If I give the disk out of my hands i dont learn how to rescue different types of defektive HDDs.

@fzabkar
thank u. I read ur posts there.
With MHDD i get an error if i wanna read the VSC

At the moment I try it with DMDE but it looks not good.

0000000000 - 00000001f0 the Blocks are all 00 00 00 00 00 00 00 00 ....
actually its by searching partitions #2 LBA ...
the response is EinError 1117

do u think u can help me to repair it for Datarescue?

best regards
Fabian

[pcn]

@fabian

as said, I think its a heads problem / media damage rather than firmware and slow-init fix alone will not fix the drive. You might also try wdmarvel instead of sediv/mhdd : http://wdmarvel.com/en/. But keep in mind if you need the data that's not the way to go. If you want to learn, get a bunch of bad drives on ebay and try to fix them first.

[fabianf]

@pcn

thx. i know that i wont fix it.
I tried to buy a 1 month licence of wdmarvel but the password wont sent by the system. I already wait for 45 minutes of it.

next week i get a big bunch of more than 20 drives with defekts.

best regards

[MindMergepk]

@mindmergepk

thank u for the information, but theres no workflow how to do it. I just read, that I need sediv. Is that correct?

First of all, are you absolutely sure you want to take the risk of DIY ?

Sediv is not the only option.
In general you need to read two modules from SA:
Module: 02 & 32, need to edit them with hex editor and write them back.

Again, if data is important send it to DR company i

[fabianf]

Thanks for ur help MindMergepk

i got back my Data.

How can i close the Thread?

[MindMergepk]

you are welcome

[pcn]

Its good that you were able to solve the problem and get your data back !
Would be nice if you tell us what the problem was and how you fixed it.