Using SSR 2013, Desktop.
Jobs started failing with an error message to the effect that the job could not copy a bad sector and to set job properties to ignore bad sectors. I did that and jobs no longer failed.
I assumed that the drive had a bad sector so I replaced the drive and restored the most recent image.
Now the new jobs are failing with the same message.
What is happening?
Not sure about SP1. I am however, running version 220.127.116.11662.
I'll do 'CHKDSK /R' tonight.
More to the point of my question. Did SSR include information in the backup image that says that sector 'x' on the original drive was bad and then mark sector 'x' on the new hard drive as also being bad although it probably was not?
I assume you enabled ignore bad sectors during the backup? If so, it's unlikely (not impossible) that a bad sector was captured during the backup.
However, if a bad sector was somehow backed up, SSR will restore it as is. So it's possible.
EDIT: Yes, that is SP1.
If your running Windows 7 or later, chkdsk has a switch "/b" that will retest bad sectors because they can indeed be caried over in a image.
NTFS only: Clears the list of bad clusters on the volume and rescans all allocated and free clusters for errors. /b includes the functionality of /r. Use this parameter after imaging a volume to a new hard disk drive.
Edit- If your running a previous version of windows that does not have the chkdsk /b option then you can use the recovery disk and do it through the command line.