Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

WD10JMVW-11AJGS2 Recovery

December 13th, 2015, 23:19

Problem

1. hdd is not detected via usb
2. PCB 771961(usb)

Steps Taken:

1. PCB 771961(USB) replaced by 771959 (SATA)
2. ROM Chip U12 Transferred

Status

1. Not Detected by bios and windows
2. SPIN and No Clicking Sound
3. In WDR 6.0 detected as
WDC ROM MODEL-FBLITE- FW:16.56H SN:WDC-ROM SN# XYZ---- (ROYL selected) port 0xF0C0
Logical: Cyls 0, Heads 0, Sectors 0, LBA 0, 0Gb
Controller Buffer Size: 0Kb
Family: Unknown


4. Head Write test
Write Test on Track -4, Num Heads :4
---------------------------------------
Head 0 - GOOD
Head 1 - GOOD
Head 2 - GOOD
Head 3 - GOOD


5. All modules can't be read, here attached


Pls advice
Attachments
Modules.rar
read by wdr 6.0
(1.5 MiB) Downloaded 918 times

Re: WD10JMVW-11AJGS2 Recovery

December 14th, 2015, 5:18

Well, I do not know how WDR works, but there are critical modules that are "BAD" and -most importantly- there are critical modules that are missing completely.

Re: WD10JMVW-11AJGS2 Recovery

December 14th, 2015, 8:01

ok thx i will check and post

Re: WD10JMVW-11AJGS2 Recovery

December 14th, 2015, 8:04

WDR has a bug in the way that it parses the SA module directory (module 01). In fact it is very similar to a bug in Atola Insight in the following thread:

http://www.hddoracle.com/viewtopic.php? ... 8&start=40

Your directory has 0x1F6 entries, each of length 0x1A (= 26) bytes. WDR and Atola both assume that the length is fixed at 18 (= 0x12) bytes.

Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  52 4F 59 4C 01 00 30 00 01 00 20 00 06 43 B7 82  ROYL..0... ..C·‚
00000010  30 30 30 32 30 30 30 30 01 02 03 03 05 00 06 00  00020000........
00000020  00 00 07 00 08 00 00 00 09 00 00 00 0A 00 00 00
00000030  F6 01 1A 04 01 00 20 00 0F 18 80 02 22 39 00 00
00000040  22 39 00 00 00 00 00 00 00 00 00 00 1A 02 35 00

Here is how each entry should be parsed:

Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19

00000000  1A 04 01 00 20 00 0F 18 80 02 22 39 00 00 22 39 00 00 00 00 00 00 00 00 00 00
0000001A  1A 02 35 00 0A 00 03 18 80 00 20 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00
00000034  1A 02 2E 01 28 00 03 18 00 00 54 29 04 00 54 29 04 00 00 00 00 00 00 00 00 00
0000004E  1A 02 02 01 01 00 03 18 10 00 2A 00 00 00 2A 00 00 00 00 00 00 00 00 00 00 00
00000068  1A 02 03 01 02 00 03 18 10 00 2B 00 00 00 2B 00 00 00 00 00 00 00 00 00 00 00
00000082  1A 02 04 01 01 00 03 18 10 00 2D 00 00 00 2D 00 00 00 00 00 00 00 00 00 00 00
0000009C  1A 02 05 01 02 00 03 18 10 00 2E 00 00 00 2E 00 00 00 00 00 00 00 00 00 00 00
000000B6  1A 02 06 01 02 00 03 18 10 00 30 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00
000000D0  1A 02 08 01 26 00 03 98 10 00 FC 38 00 00 FC 38 00 00 00 00 00 00 00 00 00 00
000000EA  1A 02 02 00 05 00 03 18 90 02 42 39 00 00 42 39 00 00 00 10 00 58 00 40 00 58
........
000032C8  1A 02 74 80 05 00 03 18 00 00 B7 F5 02 00 B7 F5 02 00 00 02 40 24 90 90 00 00
000032E2  20 00 00 00 0F 00 03 18 00 00 6D 02 00 00 6D 02 00 00 08 02 10 00 10 10 01 20

This is how WDR and Atola see the directory:

Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11

00000000  1A 04 01 00 20 00 0F 18 80 02 22 39 00 00 22 39 00 00
00000012  00 00 00 00 00 00 00 00 1A 02 35 00 0A 00 03 18 80 00
00000024  20 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 1A 02
00000036  2E 01 28 00 03 18 00 00 54 29 04 00 54 29 04 00 00 00
00000048  00 00 00 00 00 00 1A 02 02 01 01 00 03 18 10 00 2A 00
0000005A  00 00 2A 00 00 00 00 00 00 00 00 00 00 00 1A 02 03 01
0000006C  02 00 03 18 10 00 2B 00 00 00 2B 00 00 00 00 00 00 00
0000007E  00 00 00 00 1A 02 04 01 01 00 03 18 10 00 2D 00 00 00
00000090  2D 00 00 00 00 00 00 00 00 00 00 00 1A 02 05 01 02 00
000000A2  03 18 10 00 2E 00 00 00 2E 00 00 00 00 00 00 00 00 00
000000B4  00 00 1A 02 06 01 02 00 03 18 10 00 30 00 00 00 30 00
000000C6  00 00 00 00 00 00 00 00 00 00 1A 02 08 01 26 00 03 98
000000D8  10 00 FC 38 00 00 FC 38 00 00 00 00 00 00 00 00 00 00
000000EA  1A 02 02 00 05 00 03 18 90 02 42 39 00 00 42 39 00 00
000000FC  00 10 00 58 00 40 00 58 1A 02 1B 00 81 00 03 18 90 00
0000010E  47 39 00 00 47 39 00 00 00 10 00 54 00 40 00 41 1A 02
00000120  11 04 E3 00 03 18 90 00 C8 39 00 00 C8 39 00 00 20 00
00000132  00 00 00 00 00 50 1A 02 2F 00 03 00 03 18 90 00 AB 3A
00000144  00 00 AB 3A 00 00 00 24 01 00 02 00 00 10 1A 02 2A 00
........


Columns 02-03 are the module ID. As you can see, the bogus table has IDs such as 0x0000, 0x38FC and 0x3AAB. These do not exist in the actual directory.

Try enumerating the modules by ID from 0x0000 to 0xFFFF rather than via the directory (I think I may be using the wrong terminology).

Re: WD10JMVW-11AJGS2 Recovery

December 14th, 2015, 11:38

Interesting...

Re: WD10JMVW-11AJGS2 Recovery

December 15th, 2015, 7:18

[*]WDmarvel beta 7 demo log

15-12-2015 01:42:19 PM: Error reading module ID11, state - 51AD
15-12-2015 01:42:29 PM: Error reading module ID21, state - 51AD
15-12-2015 01:42:47 PM: Error reading module ID2E, state - 51AD
15-12-2015 01:43:06 PM: Error reading module ID40, state - 51AD
15-12-2015 01:43:16 PM: Error reading module ID4E, state - 51AD
15-12-2015 01:43:40 PM: Error reading module IDB5, state - 51AD
15-12-2015 01:43:53 PM: Error reading module IDE0, state - 51AD
15-12-2015 01:44:03 PM: Error reading module IDE1, state - 51AD
15-12-2015 01:44:13 PM: Error reading module IDE2, state - 51AD
15-12-2015 01:44:24 PM: Error reading module IDE3, state - 51AD
15-12-2015 01:44:39 PM: Error reading module ID120, state - 51AD
15-12-2015 01:44:49 PM: Error reading module ID121, state - 51AD
15-12-2015 01:45:35 PM: Error reading module ID250C, state - 51AD
15-12-2015 01:45:45 PM: Error reading module ID2514, state - 51AD
15-12-2015 01:45:56 PM: Error reading module ID2520, state - 51AD
15-12-2015 01:46:06 PM: Error reading module ID2529, state - 51AD
15-12-2015 01:46:16 PM: Error reading module ID252C, state - 51AD
15-12-2015 01:46:26 PM: Error reading module ID252D, state - DISK_ECU_UNSAFE_TA_ERROR
15-12-2015 01:46:37 PM: Error reading module ID2D03, state - DISK_ECU_UNSAFE_TA_ERROR
15-12-2015 01:46:48 PM: Error reading module ID2D04, state - 51AD
15-12-2015 01:46:58 PM: Error reading module ID2D07, state - 51AD
15-12-2015 01:47:08 PM: Error reading module ID2D09, state - 51AD
15-12-2015 01:47:18 PM: Error reading module ID2D0A, state - 51AD
15-12-2015 01:47:28 PM: Error reading module ID2D0B, state - 51AD
15-12-2015 01:47:39 PM: Error reading module ID2D0C, state - 51AD
15-12-2015 01:47:49 PM: Error reading module ID2D0E, state - 51AD
15-12-2015 01:47:59 PM: Error reading module ID2D13, state - 51AD
15-12-2015 01:48:09 PM: Error reading module ID2D14, state - 51AD
15-12-2015 01:48:19 PM: Error reading module ID2D15, state - 51AD
15-12-2015 01:48:29 PM: Error reading module ID2D1E, state - 51AD
15-12-2015 01:48:40 PM: Error reading module ID2D20, state - 51AD
15-12-2015 01:48:50 PM: Error reading module ID2D22, state - 51AD
15-12-2015 01:49:00 PM: Error reading module ID2D27, state - 51AD
15-12-2015 01:49:10 PM: Error reading module ID2D29, state - 51AD
15-12-2015 01:49:20 PM: Error reading module ID2D2A, state - 51AD
15-12-2015 01:49:30 PM: Error reading module ID2D2C, state - 51AD
15-12-2015 01:49:40 PM: Error reading module ID2D2D, state - 51AD
15-12-2015 01:49:50 PM: Error reading module ID2FF0, state - 51AD


Pls advice
Attachments
Modules.rar
(11.25 MiB) Downloaded 665 times

Re: WD10JMVW-11AJGS2 Recovery

December 15th, 2015, 7:52

gps31 wrote:[*]WDmarvel beta 7 demo log

15-12-2015 01:42:19 PM: Error reading module ID11, state - 51AD


Pls advice


still missing the ATA Module which is the problem i think.
can you put your ear very close to drive and hear is it absolutely 100% normal sound ?

Re: WD10JMVW-11AJGS2 Recovery

December 15th, 2015, 8:07

Sure, There is no strange or Click sound

Re: WD10JMVW-11AJGS2 Recovery

December 16th, 2015, 23:54

gps31 wrote:Problem

1. hdd is not detected via usb
2. PCB 771961(usb)

Steps Taken:

1. PCB 771961(USB) replaced by 771959 (SATA)
2. ROM Chip U12 Transferred


Never saw 771961 is interchangeable with 771959.

1961 (USB) then 1960 or 1933 (SATA)

Re: WD10JMVW-11AJGS2 Recovery

December 17th, 2015, 2:20

Ref: viewtopic.php?f=20&t=28965

Re: WD10JMVW-11AJGS2 Recovery

December 17th, 2015, 3:09

1959 IS compatible with 1961.

Re: WD10JMVW-11AJGS2 Recovery

December 17th, 2015, 3:22

Sorry, but never tried it before. :)

Re: WD10JMVW-11AJGS2 Recovery

December 17th, 2015, 5:20

unknown wrote:Sorry, but never tried it before. :)

No problem :D

Re: WD10JMVW-11AJGS2 Recovery

January 4th, 2016, 5:20

https://www.google.co.in/imgres?imgurl= ... MwgfKAQwBA


chek that

Re: WD10JMVW-11AJGS2 Recovery

January 4th, 2016, 7:25

gps31 wrote:Ref: viewtopic.php?f=20&t=28965


Hi ,
Where Are You From In India ,Which City I Mean .Might Be i Can Talk With You And Help You solve This Issue

Re: WD10JMVW-11AJGS2 Recovery

February 9th, 2016, 8:51

Amarbir wrote:
Hi ,
Where Are You From In India ,Which City I Mean .Might Be i Can Talk With You And Help You solve This Issue


I m From Madurai, Tamil Nadu, India

Re: WD10JMVW-11AJGS2 Recovery

February 18th, 2016, 0:22

When i use dir (Mod 01) from other model i can read mod 11 without problem.

So directory module may be damaged. can anyone provide Firmware backup of 16.56H of WD10JMVW-11AJGS2 ?
Post a reply