In another thread, regular poster iflyprivate raised an interesting issue: I think we have talked about bad-sector handling, but I do not remember if we ever did get an authoritative answer? I think there is two bad-sector scenarios that needs to be considered: Bad sectors and sector remapping that is handled by the disk and the disk controller. Bad sectors that are marked as unusable by the OS and the file system. Ad 1) Transparent sector remapping is something most modern disk drives can handle. Anyone with a disk that supports S.M.A.R.T. can check this for themselves. One of the S.M.A.R.T. values (I don't remember it name) contains the number of sectors that the disk controller have remapped. It should be in the low 10's to 100 or so. As I said, this is completely transparent to the OS and the filesystem, so whatever True Image does when restoring the image, the controller will handle any bad sectors on the disk. Ad 2) How do True Image handle bad sectors managed by the file system? Can it read the bad cluster table in say NTFS and avoid imaging those clusters (sectors)? That solves the imaging problem, but what happens during the restore. As I see it, True Image must assume that the destination disk is okay and that none of the free sectors are bad. Or do it perform a read-after-write for each sector, and emulate the mark-as-usable process in the same way that the OS/file system would do? Discuss!