All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 38 posts ]  Go to page Previous  1, 2
Author Message
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 26th, 2018, 20:41 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 11990
Location: Australia
unknown wrote:
I know that the damaged sectors are in zero filled sectors. But MRT neither relocate or downsize modules.

You could truncate modules 31h and 33h by editing mod 01h as follows:

Code:
Offset(h) 00   02   04   06   08   0A   0C   0E   10   12   14   16   18

000003A8                                                              1A02
000003C2  3300 5C09 0318 8800 8804 0000 8804 0000 2000 0000 0600 0081 1A02
               ^^^^ change this to 2B00 (new size of mod 33h = 002Bh)

000003DC  3100 A505 0318 8800 E40D 0000 E40D 0000 0800 401D 1080 0880
               ^^^^ change this to 0600 (new size of mod 31h = 0006h)

You would need to recalculate the checksum for mod 01h. I suspect that you may not need to change the size word in each module, but that's easily done as well.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 27th, 2018, 10:20 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1355
The drive has killed my second set of heads.
I will try with my last donor. If failed, I will refuse the case.
As the customer won't pay anything until I get his data back.

Thank you all for all your inputs.


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 27th, 2018, 13:21 
Offline
User avatar

Joined: June 17th, 2018, 11:43
Posts: 427
Location: spain
fzabkar wrote:
Would you be interested in testing my ideas? If yes, then could you upload your 01, 31 and 33 modules?

I put the modules.
The option to write directly to RAM is very powerful in my opinion. I wish they had it for the other HDD, you could do very interesting things.


Attachments:
Modules.zip [13.79 KiB]
Downloaded 40 times

_________________
Is Earth an intelligent being?
Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 27th, 2018, 15:54 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 11990
Location: Australia
@mhp666, ISTM that modules 31h and 33h can be truncated to 2 and 21h sectors, respectively. I believe you would need to disable reallocations (slow fix) to ensure that the defect lists do not grow in size.

I would start by editing module 01h only (and recompute checksum). If this doesn't work, then I would edit the headers of modules 31h and 33h to correspond to their new, truncated sizes (and recompute their checksums).

module 31h (translator)

Code:
Offset(h) 00       04

00000000  524F594C 01003000  ROYL..0.
00000008  3100A505 18302698   module ID / size = 0x31 / 0x5A5
00000010  30303430 30303030  00400000
00000018  08143100 00000000
00000020  00000000 00000000
00000028  00000000 00000000
00000030  50000000 35690100   0x50 = offset of first defect
00000038  51000000 00000000   0x51 = total defects
00000040  00000000 00000000
00000048  00000100 A28D0800   0x88DA2 = last defect
00000050  00006000 60150000
00000058  B81F6100 70420000
........
000002C8  E0A3EC0E C5650800
000002D0  6F98ED0E A28D0800   0x88DA2 = last defect
000002D8  FFFF0000 0000FFFF   0x50 + (0x51 x 8) = 0x2D8
000002E0  00000000 00000000

module 33h (P-List)

Code:
Offset(h) 00       04

00000000  524F594C 01003000  ROYL..0.
00000008  33005C09 D3AD4F56   module ID / size = 0x33 / 0x95C
00000010  30303135 30303030  00150000
00000018  07070700 00000000
00000020  00000000 00000000
00000028  00000000 00000000
00000030  0B080000 00000000   0x80B = total defects
00000038  FFFFFFFF 00000001   0x38 = offset of first defect
00000040  FFFFFFFF 00000002
00000048  FFFFFFFF 00000003
........
00004078  FFFFFFFF 21BD0300
00004080  FFFFFFFF 22BD0300   last defect
00004088  FFFFFFFF 00000000   0x38 + (0x80B x 8) = 0x4090
00004090  00000000 00000000

module 01h (directory)

Code:
Offset(h) 00   02   04   06   08   0A   0C   0E   10   12   14   16   18

0000038E                                                              1A02
000003A8  3300 5C09 0318 8800 8802 0000 8802 0000 0100 0010 0000 0000 1A02
               ^^^^ change this to 2100 (size = 0021h)

000003C2  3100 A505 0318 8800 E40B 0000 E40B 0000 8000 004A 4408 0010
               ^^^^ change this to 0200 (size = 0002h)

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 27th, 2018, 17:17 
Offline
User avatar

Joined: June 17th, 2018, 11:43
Posts: 427
Location: spain
I modified the module 0x01. When switching off and on, it returned with the same values.
I modified the module 0x01. Leo 0x11 and load the new 0x01.
I open the modules 0x31 and 0x33 and they open with the new size.
Modify the value of the size in the modules and now if you let me record the mod 0x31 that before could not in the copy 0 for errors in the SA.
I turn the disk off and on and read the modules as I modified them.
I check the information but strange things come out (it may be normal because it was a disk with many defects). Disk access is correct.

I think your idea is very good, because at the moment in my case it has allowed me to record a module (0x31) that I could not before.

Greetings.


Attachments:
Capture.jpg
Capture.jpg [ 303.78 KiB | Viewed 2798 times ]
Modules.zip [11.66 KiB]
Downloaded 36 times

_________________
Is Earth an intelligent being?
Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 27th, 2018, 17:19 
Offline
User avatar

Joined: June 17th, 2018, 11:43
Posts: 427
Location: spain
The modules read by RAM appear with the new size.

_________________
Is Earth an intelligent being?


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 27th, 2018, 18:10 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 11990
Location: Australia
The OP also states that the SMART modules are bad. AFAICT, modules 21h and 24h contain current SMART data while module 23h corresponds to the initialised state. I'm wondering whether mod 23h is necessary for normal operation. If not, then its space in the SA could be reassigned to one of the bad SMART modules.

We could switch off module 23h by changing its ID to 0xFF23, say. Does the drive still come ready and ID correctly?

module 01h

Code:
Offset(h) 00   02   04   06   08   0A   0C   0E   10   12   14   16   18

00000186                                                              1A02
000001A0  2100 CA00 0318 1000 2E69 0200 2E69 0200 0000 1408 0000 2200 1A02
000001BA  2300 CA00 0318 1002 F869 0200 F869 0200 0000 0020 0000 0008 1A02
          ^^^^ change this to 23FF

000001D4  2400 CA00 0318 1002 C26A 0200 C26A 0200 2002 0000 0008 0000

If the previous test succeeds, then we could "fix" a bad 24h module by exchanging places with mod 23h, as follows:

Code:
Offset(h) 00   02   04   06   08   0A   0C   0E   10   12   14   16   18

00000186                                                              1A02
000001A0  2100 CA00 0318 1000 2E69 0200 2E69 0200 0000 1408 0000 2200 1A02
000001BA  2400 CA00 0318 1002 F869 0200 F869 0200 0000 0020 0000 0008 1A02
          ^^^^ change this from 2300 to 2400

000001D4  2300 CA00 0318 1002 C26A 0200 C26A 0200 2002 0000 0008 0000
          ^^^^ change this from 2400 to 2300

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 28th, 2018, 11:32 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1355
@ Mr. Frank, I need to relocate Mods. 33 and 31 in 01 If possible.
Thanks in advance.


Attachments:
Modules.rar [12.4 KiB]
Downloaded 38 times
Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 28th, 2018, 17:55 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 11990
Location: Australia
unknown wrote:
@ Mr. Frank, I need to relocate Mods. 33 and 31 in 01 If possible.

The drive has 1437 (= 0x59D) sectors per track, whereas the size of module 0x33h is 0x95C. If the drive has a radial scratch across the SA, then ISTM that relocation would be impossible. The same would apply to module 31h (size 0x5A5).

Why not simply truncate your modules, as explained earlier?

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 28th, 2018, 18:38 
Offline
User avatar

Joined: June 17th, 2018, 11:43
Posts: 427
Location: spain
unknown wrote:
Why not simply truncate your modules, as explained earlier?


Yesterday after editing the modules, I regenerated the translator and I had access to the data and the modules 0x01, 0x31, 0x33 followed as they were edited.
I have the HDD working although it is a defective disk.

_________________
Is Earth an intelligent being?


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 28th, 2018, 20:38 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 11990
Location: Australia
mhp666 wrote:
Yesterday after editing the modules, I regenerated the translator ...

Can you show us what module 31h looks like now?

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 29th, 2018, 16:14 
Offline
User avatar

Joined: June 17th, 2018, 11:43
Posts: 427
Location: spain
mhp666 wrote:
Can you show us what module 31h looks like now?

ok.


Attachments:
0x31.zip [773 Bytes]
Downloaded 38 times

_________________
Is Earth an intelligent being?
Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 29th, 2018, 16:24 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 11990
Location: Australia
I was wondering whether regenerating the translator would affect the size word in the module's header -- apparently not. This would suggest that the firmware does not check the header for consistency. If so, then this would be desirable (because we would not need to update a damaged SA).

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

00000000  524F 594C 0100 3000 3100 A505 1830 2698  ROYL..0.1.¥..0&˜
                                   ^^^^ original size (0x5A5) remains unchanged

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 29th, 2018, 16:53 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1355
@ Mr. Frank
All I can say : you are genius. :good:


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 29th, 2018, 17:04 
Offline
User avatar

Joined: June 17th, 2018, 11:43
Posts: 427
Location: spain
I had not seen the size indicator in the translator module.
I would have liked to have left it in "02 00" because it was as I have it in module 0x01 and it is 2 sectors is the size that I have recorded in SA and that appears in RAM when I read with LA MRTLAB.

I wish we could do all this with the SEAGATE. Or can we?

_________________
Is Earth an intelligent being?


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 29th, 2018, 17:12 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 11990
Location: Australia
mhp666 wrote:
I had not seen the size indicator in the translator module.
I would have liked to have left it in "02 00" because it was as I have it in module 0x01 and it is 2 sectors is the size that I have recorded in SA and that appears in RAM when I read with LA MRTLAB.

Every WD ROYL module has a size indicator at the same position. The reason I avoided editing it was to see whether it was necessary to do so. In the OP's case it would seem that writing to the scratched SA should be avoided, if at all possible.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 29th, 2018, 17:38 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 11990
Location: Australia
ISTM that we should apply the "slow fix" to prevent the number of defects increasing. This is because we have reduced the size of the translator to a bare minimum which accommodates the existing defects but does not allow any extra space for new ones.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: WD10JPVX-22J3T0
PostPosted: August 29th, 2018, 18:10 
Offline
User avatar

Joined: June 17th, 2018, 11:43
Posts: 427
Location: spain
Could it be that they do not affect GList entries to the translator?
I have modified the GList and I have rebooted the disk and the translator is the same. And the GList on disk and memory if it has changed.

_________________
Is Earth an intelligent being?


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 38 posts ]  Go to page Previous  1, 2

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: Google [Bot], MSN [Bot] and 22 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group