WD Pinclite module 03 reconstruction

[kibul]

Hello,
is there a way to reconstruct module 03 on WD drive (pinclite WD3200AAKS-00L9A0 FW:000500E0) ?

There is one bad sector in the module i am not able to read (second copy is not readable at all, while other modules are readable). Without this module, or with module borrowed from donor drives the drive does not calibrate or turn it's spindle while trying to read.

0003: 0 : As : 3454: 27:No : : : : :Format Select Data Module

Anyone have any idea?
Thank you
Kib

[fzabkar]

Is it possible that the missing sector may be filled with zeros?

Could we see the MOD?

[kibul]

Thank you for fast reply. I tried to leave the DEAD inside and recalced the checksum, i will try the zeros and let you know.
There is the module attached. Also there is a donor module i found from WD3200AAJS-22L7A0_01.03E01 the same FW(but does not work on patient drive).

Also i incorrectly wrote that only one sector is missing, i mistaken it with other module i was able to reconstruct. There are many bad sectors in this module.

Attachments

03.zip

(3.47 KiB) Downloaded 660 times

[Tomset]

This module is unique.
You can not take from another HDD.
Or change the head and proofread 1 copy.
or search for a copy of the modules within the 80xx

[kibul]

Unfortunately there is no copy of 03 in 80xx.
Seems there is no way for recovery.

[Doomer]

There is a way to reconstruct 03 in some cases(depending on damage location) but this knowledge is very sensitive and secretive, so most of DR guys don't even know it is possible. Your module has a lot of damage, IDK if it would be possible to reconstruct it, it is hard to tell without having the drive in hand.

BTW for those who suggests hot swap or zero filling - this module contains zone tables, so you have to have the original module in order to extract data.

[fzabkar]

BTW for those who suggests hot swap or zero filling - this module contains zone tables, so you have to have the original module in order to extract data.

If you're referring to me, I didn't mean to suggest that at all. I had merely observed that similar modules in other resource dumps had lots of zero sectors, and since the OP has said that only one sector was affected, I was hoping that this bad sector was one of these. Obviously that's not the case.

One thing that did occur to me was whether there was any way to disable ECC and read the bad sectors in raw mode. Perhaps there is a RAM buffer that contains these preprocessed data ???

[pcimage]

This from an email I received from DFL...

* New families of 17XX, 18XX, 19XX are added to support, users can fix firmware failures of them and can also run single SF process on them;
* A big change to the software and operation interface, making it clean and easy to use;
* Reset and Log report are added in the starting interface;
* Independent thread is assigned to ‘AutoGetDetails’, progress bar is added to get the HDD details so that the whole process will be faster and won’t get stuck;
* Optimize the LDR and Cache overlay-13 loading for PCB1698 and newer series;
* Auto generation of module 03 is added;
* Converting modules to tracks is added which is very helpful in some cases which module writing may fail;
* Module extraction from tracks is optimized;
* Removed the bottleneck method to access the SA by only ABA mode after hot swap and now with the new program, even if the tracks cannot be accessed, users can read/write modules;
* Users can customize module loading to RAM and it fixed another bottleneck technology-when writing common fw, users needed to write 01 first, power off/on, write other modules. But with the new program and new solution, users can write common fw at one time. When tracks cannot be read, users can read modules directly;
* New method of generating P-list is added and in the new program, users have two auto P-list generation options to maximize the generation success rate;
* T-list generation is added to fix some SadleG6 hdds whose T-list is damaged and the data area couldn’t be accessed;
* SF script generation is added;
* Single online SF process is added and so far 26 processes are supported;
* Format monitoring is optimized;
* SF monitoring process is optimized;
* Two methods of ROM regeneration are enabled in this new version

[kibul]

Hi. I have the same issue again. Now, only 1 sector in module 03 is damaged (both copies). Due to this only part of the drive (end) can be accessed.
Is there a way for recovery?

Attachments

03.zip

(1.25 KiB) Downloaded 590 times