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

WD10JPVX-22J3T0

August 25th, 2018, 13:50

Hello,
Drive in topic was dropped and after replacing heads it takes some time to get ready with full model, capacity, SN and FW but no user area access.
SA checked and there's bad sectors in critical tracks (Translator 31, P-List 33 and S.M.A.R.T).
I have managed to get full backup by tracks (composite reading).
MRT not supported module redirection with this FBlite.

Any suggestions?

Thanks in advance.

Re: WD10JPVX-22J3T0

August 25th, 2018, 16:10

Test a non important module to write to...if its write, you can write back the read ones thats were bad...try one head at the time.

Re: WD10JPVX-22J3T0

August 25th, 2018, 17:21

mr_spokk wrote:Test a non important module to write to...if its write, you can write back the read ones thats were bad...try one head at the time.

Already tried this, sir.
Heads are perfectly reading and writing. Tried to write to module then re-read to see the changes and it already write.
Thanks for trying to help. I appreciated

Re: WD10JPVX-22J3T0

August 26th, 2018, 3:30

Ok, so you can write modules back...and confirmed they write good?
And you know that you got the critical modules to 100% when you read them?

Re: WD10JPVX-22J3T0

August 26th, 2018, 5:25

Yes.
Yes by both ID and composite by tracks. 31 and 33 backed up with 3 bad sectors in tracks 255 and 256.
I see that almost every track has the same bad sectors in the same location ( sectors 972,1154, 1155 and 1156 )
The drive was dropped, I believe it's scratches to the surface because of the defective heads. I'm sure that the customer tried to power on the drive several times.

Re: WD10JPVX-22J3T0

August 26th, 2018, 7:29

Go to sector edit and check different location to reach different Lba's.
If not reached any lba and you got 100% of p-list, then try to regenerate translator.

Re: WD10JPVX-22J3T0

August 26th, 2018, 7:37

mr_spokk wrote:Go to sector edit and check different location to reach different Lba's.
If not reached any lba and you got 100% of p-list, then try to regenerate translator.

No user area access.
I will try and post the results.
I remember I had a similar case that I figured out to access user area, but I can not remember what I have done to solve the issue. :D

Re: WD10JPVX-22J3T0

August 26th, 2018, 9:40

unknown wrote:
mr_spokk wrote:Go to sector edit and check different location to reach different Lba's.
If not reached any lba and you got 100% of p-list, then try to regenerate translator.

No user area access.
I will try and post the results.
I remember I had a similar case that I figured out to access user area, but I can not remember what I have done to solve the issue. :D


Always document your findings and what you do, memory can a pain sometimes.

Re: WD10JPVX-22J3T0

August 26th, 2018, 10:16

LoboX wrote:
unknown wrote:
mr_spokk wrote:Go to sector edit and check different location to reach different Lba's.
If not reached any lba and you got 100% of p-list, then try to regenerate translator.

No user area access.
I will try and post the results.
I remember I had a similar case that I figured out to access user area, but I can not remember what I have done to solve the issue. :D


Always document your findings and what you do, memory can a pain sometimes.

Agree.
But sometimes for hard cases when I try several methods to workaround the problem and figure out to access the user data, the only thing I think of, is to hurry to take an image then I forget all I have done to solve the issue. :)

Re: WD10JPVX-22J3T0

August 26th, 2018, 11:52

:lol: ohh yes i have been there.

Re: WD10JPVX-22J3T0

August 26th, 2018, 15:46

Have you tried to record the translator selecting by RAM and try to see if you have access through the sector viewer?

Re: WD10JPVX-22J3T0

August 26th, 2018, 16:28

I have a HDD just like yours. I have broken the mod 0x31 and then after several attempts I have managed to record in RAM and I have access. I do not know if it will work for your particular case.

Re: WD10JPVX-22J3T0

August 26th, 2018, 16:42

Can you upload modules 01, 31 and 33? I believe that most modules have 4 copies.

Re: WD10JPVX-22J3T0

August 26th, 2018, 16:58

mhp666 wrote:I have a HDD just like yours. I have broken the mod 0x31 and then after several attempts I have managed to record in RAM and I have access. I do not know if it will work for your particular case.
fzabkar wrote:Can you upload modules 01, 31 and 33? I believe that most modules have 4 copies.

The problem is not with modules. The problem is with scratches to the surface ( too many bad sectors in SA in several positions)
Also hot swap is not working with this family.

Thanks for your inputs.
Attachments
Modules.rar
(12.4 KiB) Downloaded 71 times

Re: WD10JPVX-22J3T0

August 26th, 2018, 17:12

Have you checked if the mod 0x31 in RAM matches the one you have saved?
A greeting.

Re: WD10JPVX-22J3T0

August 26th, 2018, 17:18

ISTM that all the bad sectors are in the zero-filled area at the end of each module. Therefore modules 31h and 33h should be easy to repair. I was wrong about the number of copies, though -- there are 2, not 4.

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
000003DC  3100 A505 0318 8800 E40D 0000 E40D 0000 0800 401D 1080 0880

As for module redirection, I think it might be possible to do this manually, if necessary.

:idea: Would the drive still operate correctly if you were to truncate the sizes of modules 31h and 33h? You would need to edit the corresponding directory records in module 01h as well.

Re: WD10JPVX-22J3T0

August 26th, 2018, 17:28

Can you corroborate something?
If I turn on the HDD and it has bad 0x33 and 0x31, it starts but does not have access, but if we load the 0x31 in RAM when I want to read sectors I already have access, because the firmware no longer reads these modules from the SA and works with the copy in RAM. Then I do not care as this 0x33 if I have the 0x31 well.

Re: WD10JPVX-22J3T0

August 26th, 2018, 17:32

mhp666 wrote:Have you checked if the mod 0x31 in RAM matches the one you have saved?
A greeting.

Too many modules loaded to RAM are gives errors ( 33,31..etc)

fzabkar wrote:ISTM that all the bad sectors are in the zero-filled area at the end of each module. Therefore modules 31h and 33h should be easy to repair. I was wrong about the number of copies, though -- there are 2, not 4.

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
000003DC 3100 A505 0318 8800 E40D 0000 E40D 0000 0800 401D 1080 0880

As for module redirection, I think it might be possible to do this manually, if necessary.

:idea: Would the drive still operate correctly if you were to truncate the sizes of modules 31h and 33h? You would need to edit the corresponding directory records in module 01h as well.

I know that the damaged sectors are in zero filled sectors. But MRT neither relocate or downsize modules.
Also I have checked several tracks to relocate translator and P-list, but almost all tracks have bad sectors in the same place (0,1)
Sectors (972,1154,1155 and 1156) are damaged in all critical tracks.
Thanks for trying to help

Re: WD10JPVX-22J3T0

August 26th, 2018, 18:04

Try this if you want.
Boot the disk in kernel mode to free memory from RAM.
Read the module 0x11. You must read 0x01 from the disk.
Select read / write RAM.
You must let the translator write in RAM. And if the translator is fine, you should have access.

It's just a suggestion.

I'm going to break the module 0x01 to also do the test.

Re: WD10JPVX-22J3T0

August 26th, 2018, 20:00

mhp666 wrote:I'm going to break the module 0x01 to also do the test.

Would you be interested in testing my ideas? If yes, then could you upload your 01, 31 and 33 modules?
Post a reply