HDD GURU FORUMS

WDC WD30EZRX-00DC0B0 80.00A80 Microcode:00040027


The drive was tried to be recovered elsewhere. Not sure if the other company could do it.

Here we have a mod40 damage. 41 42 43 are ok

Any ways to patch stuff from 41 42 43 and get this boy up and running?

--

Module 0x40 is divided into regions. There is a table of regions (offset + size) at the start of the module. It appears that the first 3 regions are either missing completely (regions 1 and 2) or partially (region 3). IMHO, it would have been better if the bad sectors had been identified with a suitable fill pattern (eg BAD!) rather than zeros.

Code:

Offset(h) 00       04       08       0C

00000050                    58010000 00010000
00000060  58020000 000A0000 580C0000 F01D0100
00000070  482A0100 E0160000 28410100 E02E0000
00000080  08700100 98000000 A0700100 00B70000
00000090  A0270200 D00C0000 90560300 101F0000
000000A0  70340200 DB210100 4C560300 20000000
000000B0  6C560300 24000000 A0750300 20000000
000000C0  C0750300 B8020000 78780300 D0030000

Code:

Offset(h) 00       04

           offset    size
          -------- --------
00000000  58010000 00010000  region #1
00000008  58020000 000A0000  region #2
00000010  580C0000 F01D0100  region #3
00000018  482A0100 E0160000
00000020  28410100 E02E0000
00000028  08700100 98000000
00000030  A0700100 00B70000
00000038  A0270200 D00C0000
00000040  90560300 101F0000
00000048  70340200 DB210100
00000050  4C560300 20000000
00000058  6C560300 24000000
00000060  A0750300 20000000
00000068  C0750300 B8020000
00000070  78780300 D0030000

Region #1 is located at the same offset in modules 0x41, 0x42 and 0x43. Modules 0x41, 0x42 and 0x43 are identical apart from their module IDs and checksums.

The region tables in modules 0x40 and 0x41 are identical. This suggests that the modules have the same structure, but the respective regions do not always contain identical content.

Region #2 is located at the same offset in module 0x66. The data are identical. Region #1 in module 0x66 also matches module 0x40.

In fact, module 0x66 is a full copy of 0x40. It differs only in the ID and checksum.

Hi Franc! Thanks for the excellent information. I have never seen any one who is so proficient, humble and sharing in my life.

Thanks for holding my hand here. It has been 10 years + i have worked on so many WDs but never ever did the 40 reworkings.

Sent you a PM.

sin wrote:Sent you a PM.

I don't do PMs anymore.

If you can't regenerate 0x40 from 0x66, upload 0x66 and I'll do it for you.

sin wrote:Hi Franc! Thanks for the excellent information. I have never seen any one who is so proficient, humble and sharing in my life.

Thanks for holding my hand here. It has been 10 years + i have worked on so many WDs but never ever did the 40 reworkings.

Sent you a PM.

no no..all is done....it worked out great!
i wanted to PM about something else that I really wont discuss on the forum (any part of it)
How do I email you then?

Just send me your email address some how so that I can express something to you totally in person.


--

PS: T-list had checksum errors. Even after fixing checksum the drive would go into err abt.
Clearing it gave data access..But not perfectly as with some diablo 3D/3S drives there is sector misalignment post clearing T-Lists. So now next mission is to try to fix the Tlist so we have boot sector seen on LBA0. Other wise Raw data is available.

This drive was gone into some US lab. I sense some misdoings on it as client declined to pay.

I don't wish to share anyone's secrets, primarily because it creates a dilemma if I were to later uncover those same secrets from a different source, or through my own research.

As for mod 0x40, I understand the structure (that's trivial), but I don't understand the content. In that regard it would be best to consult with your peers.

sure. But the email part was not about DR or tech. Just wanted to mail you and keep that thing off the forum records. Public or PM.

Secretes can get buried with their graves who keep them. I care very less.
--