Need firmware for pc3k WDC WD20EARS-00MVWB0 25.12E

[michael chiklis]

I tried 2 more MOD read with WDR.
1: Read with "by ID" ticked, which i already did few days ago, all module are checked as "good" with green mark.
2. Read with "by ID" unticked, all modules are checked ad "bad" with red mark.

In WDR i get this errors log when i try to read with unticked "by ID".

Someone does know if this is due to software bug or to faulty drive?

[michael chiklis]

SA 2nd copy is on head 1?
If i untick "by ID" i get error on head 0 and also head 1

[michael chiklis]

I get this error also with good drive
Mariner (Royl) drive
WDC WD3200BEVT-00A0RT0_01.01A01

Last edited by michael chiklis on April 20th, 2013, 18:17, edited 1 time in total.

[michael chiklis]

In the module window i see only "02" under copy, also with the good drive

i can't access to copy 01 even in the good drive, because it always show me only 02
could be a software bug or i'm doing something wrong?

Last edited by michael chiklis on April 20th, 2013, 18:25, edited 1 time in total.

[michael chiklis]

Are you able to do modules backup from copy 01 with version 6.0?

[michael chiklis]

When you read by id you read all modules ok from COPY 02
Try to untick "by id" and tick "second copy map"

I tried it, i get still same errors on modules reading

[michael chiklis]

I think my only choice is to try the head 0 depop.
One of this days i will try

[michael chiklis]

When you read by id you read all modules ok from COPY 02
Try to untick "by id" and tick "second copy map"

I tried it, i get still same errors on modules reading

Did you try that with good drive to see if it's diferent ?

Yes i just tried few minutes ago on a good drive:
Mariner (Royl) drive
WDC WD3200BEVT-00A0RT0_01.01A01

Exactly the same!!

[michael chiklis]

I really don't know, head test it's alway good, only once time i had bad report on head 1

P.S.
I just did again head test, again head 1 "bad" reported after i tried 10 times.
Then again all good head

[michael chiklis]

Not an option, too expensive (i need to get only some pics, which are not so important to spend hundred $)
Most of the pictures (about 80% I have recovered from my girlfriend's pc)

[michael chiklis]

Because i'm not so sure this is a head issue, my idea was to backup modules from copy 01 and compare all files to copy 02 with hex editor.
Difference modules may be the corrupted one, but i'm not able to backup "copy 01"

[michael chiklis]

Not an option, too expensive (i need to get only some pics, which are not so important to spend hundred $)
Most of the pictures (about 80% I have recovered from my girlfriend's pc)

Did you ty to copy one by one using dos ?
If you can copy a file at a time, can you copy a picture at a time ?

I wasn't able to do this, because when i go deep inside the directorys, the program hangs so i can't input the copy command

[michael chiklis]

Because i'm not so sure this is a head issue, my idea was to backup modules from copy 01 and compare all files to copy 02 with hex editor.
Difference modules may be the corrupted one, but i'm not able to backup "copy 01"

Save ROM depop head 0. If head 1 is bad you will end up with a bricked drive (no SA access). If SA access is possible then you can backup modules. You can restore ROM to have head map back.

If head 1 is bad, i should depop head 1, right?
So head 0 can load SA...

Last edited by michael chiklis on April 20th, 2013, 18:59, edited 2 times in total.

[michael chiklis]

How do i save ROM depop head 0?
Can i save also others head configurations?

[michael chiklis]

How do i save ROM depop head 0?
Can i save also others head configurations?

Flash operations - Read ROM.
It should backup the ROM file. Check if it's ok.

ok the rom backup i've done many days ago

[michael chiklis]

I have other WD drives but not the same model.
The drive is a WD5000AAKX-001CA0 with similar pcb of my faulty drive (pcb 2060-771640-003).
The faulty drive has pcb 2060-771698-002

However you could tell me how you do the hot swap?
I know that you have to attach and detach the pcb from a donor hdd drives without turning off (but doing motor spin up and spin down).
What that i do not know is if you need to do more ...

I found this about hot swap on WD, but i don't understand what must do with modules 31 and 32
http://www.disk-imager.com/data-recovery-blog/?p=2555
http://www.disk-imager.com/data-recovery-blog/?p=2578

[michael chiklis]

I did depop head 1, but the drive was still slow in mhdd scan, so i activeted again head 1.
(to reactivate head 1 was not enough to restore rom from backup, i had to write also SA with modules backup).

After restored head 1, i cleared the "IBI common log" to delete those 4 soft errors but still slow scanning in mhdd...
I restored again SA from backup, now i see again those 4 soft errors in "IBI common log"

[michael chiklis]

As you can see in one of my firt post, Sediv showed at the begin G-list report on head 4.

So I decided to depop head 4, but something went wrong, look to the pic on bottom:

I got "Unknown error 53E4"

Now i'm not able to turn on the head, drives spins down and is shown in WDR as in the pic in bottom:

I guess problem is on head 4, but i don't understand why doesn't load SA now (SA gets read by head 0 and 1, am i right)?

It's game over?

[michael chiklis]

Neither of those did work!

P.S.
I'm able to keep motor running if i do "ATA soft reset" + "ATA Recalibrate"
If i do Road map via enumeration it shows modules but i'm not able to read or write them

[michael chiklis]

No, i can't right them via enumeration...
I also loaded mod from file, but still i can't write them on SA.

Maybe i'm doing something wrong, or WDR bug, or it's just the faulty drive...
Hot swap may work, but need to buy an identical drive (not an option).

What about "loader" created with Sediv?
Can i use it with WDR?