WD10EZRX 0001005C

[siamak5561]

Hi guys
Drive stay in busy
Need loader for this, thanks.

[siamak5561]

Any compatible loader ?

Using load 01 module into ram

Using load loader

[siamak5561]

Okay I manage find a loader that give me access to SA, but after try to load 02 to ram hard goes to busy...

[siamak5561]

Hey guys still struggling with this case, any tip ?

[Swiftdata]

Block SA access (SA regions, module 0x30 or 0x411)
Upload DIR and Loader from SA (I think is possible on this model, if not get suitable resource from hddsurgery database based on ROM version of your case)
Now check that SA is accessible and write back here - if is accessible then is possible to try find cause of the problem in SA

[siamak5561]

Block SA access (SA regions, module 0x30 or 0x411)
Upload DIR and Loader from SA (I think is possible on this model, if not get suitable resource from hddsurgery database based on ROM version of your case)
Now check that SA is accessible and write back here - if is accessible then is possible to try find cause of the problem in SA

Already do that, and have access to SA, but in most of DR cases after load mod 02 UA become accessible, but in this case not!

[Swiftdata]

User area will not be available with 0x411 blocked but SA should be and need to find what fault is. You need to give more information. right now could be many issues, ROM could be not original, some SA adaptive modules could be bad, relocation table could be full causing relo issue - with some SA blocking mechanism present and loader uploaded you can make proper tests of SA to make backup, find any modules that have errors and check condition of modules like 31, 32, 02, 40 etc

[siamak5561]

ROM is original.
Relocation table has been cleared, and I’ve already tested all SA modules — none of them report any errors.

[siamak5561]

And some modules and Roms

Attachments

Data.rar

(1.2 MiB) Downloaded 11 times

[fzabkar]

Did this drive come out of a Dish/Echostar satellite receiver? If so, then perhaps it has "funny" firmware.

This is SA module 0x2E. Module 0x2D is similar.

Code:

Offset(h) 00   02   04   06   08   0A   0C   0E

00000000  524F 594C 0100 3000 2E00 2902 B793 7571  ROYL..0...).·“uq
00000010  3030 3032 3030 3034 0000 0000 0000 0000  00020004........
........
00000250  0000 0000 0000 0000 0000 0000 0000 0000  ................
00000260  5555 5555 AAAA AAAA 4563 686F 5374 6172  UUUUªªªªEchoStar
00000270  2044 5354 3300 3400 3500 3600 4000 4700   DST3.4.5.6.@.G.
00000280  4900 3201 4A01 4F00 4A00 0000 0100 0000  I.2.J.O.J.......

I think these errors may be benign:

Code:

Parsing directory Modules_ByID\ ...

  IDfil ROYL  IDhdr checksum  size(fil/hdr)   stat  filename
  ----  ----  ----  --------  -------------   ---   --------

     1  ....  ....  ........     18   .....         01.rpm
     2  ....  ....  ........      5   .....         02.rpm
     3  ....  ....  ........     A2   .....         03.rpm
     4  ....  ....  ........   5286   .....         04.rpm
     C  ....  ....  ........      C   .....         0C.rpm
    11  ....  ....  ........    50C   .....         11.rpm
    21  ....  ....  ........     CD   .....         21.rpm
    23  ....  ....  ........     CD   .....         23.rpm
    24  ....  ....  23A234C4     CD   .....   BAD   24.rpm
    25  ....  ....  ........    101   .....         25.rpm
    26  ....  ....  ........     81   .....         26.rpm
    28  ....  ....  ........     10   .....         28.rpm
    29  ....  ....  ........      B   .....         29.rpm
    2A  ....  ....  ........      B   .....         2A.rpm
    2D  ....  ....  ........    320 /   229   BAD   2D.rpm
    2E  ....  ....  ........    320 /   229   BAD   2E.rpm
    2F  ....  ....  ........      2   .....         2F.rpm
    31  ....  ....  ........    334   .....         31.rpm
    32  ....  ....  ........     3C   .....         32.rpm
    33  ....  ....  ........    4EC   .....         33.rpm
    34  ....  ....  ........     30   .....         34.rpm
    35  ....  ....  ........      A   .....         35.rpm
    36  ....  ....  ........      5   .....         36.rpm
    37  ....  ....  ........      2   .....         37.rpm
    38  ....  ....  ........    101   .....         38.rpm
    39  ....  ....  ........     11   .....         39.rpm
    3A  ....  ....  ........      C   .....         3A.rpm
    3B  ....  ....  ........     10   .....         3B.rpm
    3C  ....  ....  ........     10   .....         3C.rpm
    3D  ....  ....  ........     10   .....         3D.rpm
    3E  ....  ....  ........     10   .....         3E.rpm
    3F  ....  ....  ........     10   .....         3F.rpm


  IDfil    -- ID of module as reported in its file name (should be the same as ID in SA module 0x01)
  IDhdr    -- ID of module as reported in module's header, or .... if same as IDfil
  checksum -- actual checksum of module if not 0x00000000, or ........ if 0x00000000
  size     -- size of file in sectors / size as reported in module's header if different, or .... if same
  stat     -- status of module is BAD if inconsistency found
  ****     -- "ROYL" signature was not found in header, or .... if "ROYL" found
  xxxx     -- size of file is not a sector multiple
  !!!!     -- IDfil cannot be inferred from filename, or filespec not supported
  ??????   -- the parameter is not applicable for this case
  ......   -- the parameter's value is as expected

[fzabkar]

Section 2 in module 0x02 has 4 different capacities:

Code:

0x747784E0 = 1953989856  <-- IDEMA standard capacity + 464688
0x74706DB0 = 1953525168  <-- IDEMA standard capacity
0x74706DB0 = 1953525168  <-- IDEMA standard capacity
0x7470656F = 1953523055  <-- IDEMA standard capacity - 2113

Code:

ROYL header found

Module 02 consists of 48 sections


Section 1     Length 25 / 0x19 bytes     Offset 0xF2

Addr  00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

0000  00 01 57 44 2D 57 43 43 34 4A 30 4E 53 55 4B 5A  ..WD-WCC4J0NSUKZ
0010  56 00 00 00 00 00 00 51 00                       V......Q.


Section 2     Length 24 / 0x18 bytes     Offset 0x10B

Addr  00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

0000  00 01 10 3F 00 00 00 00 DF 84 77 74 AF 6D 70 74  ...?......wt.mpt
0010  AF 6D 70 74 6E 65 70 74                          .mptnept

The 4th capacity is what you get when you attach the drive to a Gigabyte mainboard that has an Xpress Recovery BIOS. The BIOS grabs 2113 sectors from the end of the UA and stores a backup copy of itself in the HPA. Whatever was in that HPA has now been overwritten.

This screenshot shows that those 4 capacities are normally identical (you need Firefox to access the image):

https://www.hddoracle.com/download/file.php?id=4718&mode=view

[fzabkar]

The attached 0x02 module has been edited so that all capacities are identical.

Attachments

02_IDEMA_capacities.7z

(1.19 KiB) Downloaded 10 times

[fzabkar]

Sorry, it appears that the extra capacity is a red herring.

Here is a DFL blog showing the same extra capacity (1953989856):

https://www.dolphindatalab.com/wd10ezrx-00l4hb0-full-disk-bad-sector-hdd-data-recovery-steps/

[siamak5561]

Did this drive come out of a Dish/Echostar satellite receiver? If so, then perhaps it has "funny" firmware.

[/code]

Its from a PC, maybe in the past used to be in a receiver

So what should I do in the next? already write your modified 02 mod but no difference.