When marking badblocks in the destination is enabled, safecopy reads the next block number from the include file to see where it is allowed to write.
This leads to a situation where safecopy treats all blocks between the last attempted read block and the next include block as include blocks, too, even while they are not.
an include file with two sets of blocks.
badblock marking enabled.
the last block of the first set of include blocks fails to read, getting marked as bad.
bad block gets marked, then safecopy skips to the first block in the second group of include blocks and continues there.
bad block gets marked, then safecopy copies ALL the blocks towards and including the second group of include blocks!
This bug will be permanently fixed in safecopy 1.6
a hotfix patch will be provided beforehand asap.