my old system disk almost failed me. I dd_rescued the disk onto a new one (don’t use dd_rhelp, that one took days and seemed to forget what it had scanned more than once). The condition of the disk was not very good. So naturally I expected the subsequent fsck.ext3 to bomb half of the new disk. But obviously only a few inodes were affected and I lost only about 10 files completely (mostly on the root partition and not the home partition - yeay!).
However, I then ran a badblocks and put all the bad blocks into a file. I could use this to run fsck but I fear that
- It could undo or even redo worse than what the first fsck run did, and
- giving the list of bad blocks, fsck might on the one hand rescue/flag damaged files (which is what I want), but I don’t want it to flag the bad blocks on the new disk as well (they are not bad blocks anymore, just copies of bad blocks).
So, how can I single out problematic files using my list of bad blocks (which I can then look at one by one if they could be rescued) without flagging the supposedly bad blocks on the new disk.