WD20SDRW-11VUUS0

[DRUG]

Looking for a bit of guidance.

Drive came in, powers up and no strange noises at all.

I swap the rom to a unlocked board only to find out that module 02, 25 and 190 can't be read.

I managed to write a pretty close module 02 from other drive and now the device ID's correctly. However 25 and 190 are unique to HDD.

So far I'm dealing with two problems:

1) What can I do about module 25?

2) Neither copy 0 or 1 of 190 can be read, even ignoring errors.
Would PBA reading still be an option if I managed somehow to regen module 25?

Thank you for your inputs.

[DRUG]

Case solved update:

I did move/resize on module 25.

Module 190 was declared as DOA so the information will be read on the original pcb with the sata adaptation via PBA.

Recovery will be raw, but at least client will get the data he was looking for.

[Amarbir[CDR-Labs]]

Hi,
Did you change heads or used same heads

[DRUG]

Hi,
Did you change heads or used same heads

Same heads, I usually outsource Chargers, but this time it was time crucial and had to risk it for the biscuit.

Some more experienced techs told me that usually it's better to have to perform a headswap then to deal with SA damage with bad blocks.

All went well in the end, I'm happy

[Amarbir[CDR-Labs]]

Hi,
Did you change heads or used same heads

Same heads, I usually outsource Chargers, but this time it was time crucial and had to risk it for the biscuit.

Some more experienced techs told me that usually it's better to have to perform a headswap then to deal with SA damage with bad blocks.

All went well in the end, I'm happy

Hello ,
You said all went well ,Can you explain what and how you finished this

[DRUG]

Hi!

I did move resize on modules that were damaged and wrote them again.

Only module damaged was 190. I ignored it and cloned via PBA.

[fzabkar]

I did move resize on modules that were damaged and wrote them again.

Does this mean that some modules are bigger than they need to be, and the fix is then to shrink them in the module directory (mod 01)?

[DRUG]

I did move resize on modules that were damaged and wrote them again.

Does this mean that some modules are bigger than they need to be, and the fix is then to shrink them in the module directory (mod 01)?

Move resize is an option on pc3k, basically you can write the modules on free areas of the SA.

[fzabkar]

I did move resize on modules that were damaged and wrote them again.

Does this mean that some modules are bigger than they need to be, and the fix is then to shrink them in the module directory (mod 01)?

Move resize is an option on pc3k, basically you can write the modules on free areas of the SA.

Thanks.

Spildit and I were able to shrink a critical SA module in a Samsung drive without impairing the drive's function, so I know what resizing means from my point of view. I was just wondering whether PC3K was doing the same thing.

[DRUG]

I did move resize on modules that were damaged and wrote them again.

Does this mean that some modules are bigger than they need to be, and the fix is then to shrink them in the module directory (mod 01)?

Move resize is an option on pc3k, basically you can write the modules on free areas of the SA.

Thanks.

Spildit and I were able to shrink a critical SA module in a Samsung drive without impairing the drive's function, so I know what resizing means from my point of view. I was just wondering whether PC3K was doing the same thing.

I do believe that this function would allow you to shrink it indeed.

By the way, is he still alive?
I've never seen him online again.

[Amarbir[CDR-Labs]]

Frank,
Lets take a example that a module is 4 sectors each 512 bytes and only 1st sector has Data we can resize the module and modify DIR 01 so that it has new module size , We need to do this incase a module has read errors in non critical sections ,Yes this is for WD HDD ,Good to know can be done in other HDD families as well