PC-3000 Forum

This WD just got new heads.
After I repaired all the bad modules I am left with just module 4 that is still bad. Because of this module, I can't access user area.
I tried to rewrite Copy 0 and 1 of the module but it failed.
Since it can't be repaired, I was going to move it to a different ABA location. The problem is that module 04 is very large..the only spot available has bad blocks....and so I cannot find anywhere to put it.

So what happens if you cant find space? ....or is there a better approach?

You can shrink a non critical module such as E0 down to just 1 sector in size and make enough room for it that way. Maybe even shrink and relocate a few of them that are next to each other.

That's a great idea... I was wondering about the possibility of deleting non critical ones but shrinking them sounds just as good and safer.

04 is the largest module (by size ) on WD passports and its required for user data access. Apparently on drives other its not so important.


Thanks for the suggestion. You're a pretty active forum member!

I just realized that module 04 is 57,603 sectors.
I don't think there are enough non-critical modules to shrink. E0 and others are only around 1500 sectors each. Any other options?

Dear osity, if Service Area is full of bad sectors, it's almost impossible to find the good space for such big module like 04.
In fact, I often get the data even with bad 04 module, if all others were good.
Please try to change the head map in RAM, maybe some head is weak.
Also check if all other modules are good.

The instructions about RAM head map changing and module relocation are in ACE Blog: http://blog.acelab.eu.com/

All critical module have been corrected except 04. Should I correct non critical as well? (D modules ETC.)

Maybe using hot swap can get your problem solved..

pclab, perhaps, I never use that option
......a what point in a recovery do you consider a hotswap for a solution?

osity wrote:Source of the post pclab, perhaps, I never use that option
......a what point in a recovery do you consider a hotswap for a solution?

Usually at the point you're at right now

When you reach a point where it's impossible/impractical to repair the existing SA, read everything by composite, write it all to a compatible donor, and use it to initialize the PCB so it's all ready to read after hot swapping it. Then just pray that you don't have too many bad sectors causing it to stall and need repeated hot swapping. If module 4 is your only issue, then you should be good. It's when the issue is related to defect lists that you'll really be in tough shape hot swapping it.

My understanding is that hotswap is not possible for the, Shrek, Hubble, Hubble LT and FBLite
Can anyone else confirm?

My drive is FBlite.


Surprisingly ...I was just able to access the user data using a simple RAM headmap on this case. There must have been some back blocks in the maintenance under the disabled head.

Thank you for all your help everyone!

I'm pretty sure it is possible on those. Maybe not a dumb hotswap, but definitely can do a smart hotswap.

DataMedics, I have tried to perform a hot-swap on Hubble LT twice. Both times I have got the bricked donor...
I guess it was related to some differences in SA structure, like Dir positions, or something else.
If you have some tips regarding it, let us know

By the way, the smart hot-swap is described here: http://blog.acelab.eu.com/pc-3000-h ... rives.html