Spildit wrote:
Question would be if a damaged drive would handle that "mapping" process at all or if it wouldn't even be slower to map heads on a drive with damaged heads ....
Well ... I guess more testing would be required....
At this time I have no idea what would happen if it had damaged heads.
I would also like to point out that the rebuild assist feature on this drive is wonky. I have to use soft resets on it when it gets “confused” and does not abort head reads when the head is disabled. This is even in addition to the ghost head. That area where it skips heads definitely confuses it in brute force mode. The confusion seems to happen when disabling a different head. I would say that either the rebuild assist feature on this drive is either just buggy from the factory, or maybe this drive was refurbished which screwed it up.
And I have absolutely no idea what would happen if this drive were to disable a head on its own. My code currently does not have any sort of provision for that. Plus I don’t know how the drive would react with an actual bad head (with this drive it is a guessing game, anything could happen). I will need more R&D before being able to produce a working feature. I will probably need to test with a few different drives, which I don’t have, and don’t really have the money for.
_________________
http://www.sdcomputingservice.comHome of HDDSuperClone and HDDSuperTool