> You may want to do some additional testing to verify the status of the new > filesystem. In my original message I implied that fsck was sufficient, but as > Tony quite rightly pointed out, it isn't. On my failing disk I knew that the bad > block wasn't part of the active filesystem, so a simple copy/fsck was > sufficient. During the copy there were no errors, and a comparison of the two > filesystems showed no discrepancies. > > When you copied your filesystem, did the system generate any error messages? If > so, you will probably want to investigate which file the bad block belonged to, > and determine the impact that having that file corrupted might cause, and > whether you can restore that file from a backup. > At this point, I have recovered the user data that was lost and committed the entire disk to a backup. Once that is done, it's reinstall time for me. Sean