Hi, Adam.
This is a known issue, but it's actually an "extra step" we take to restore the original UUID (a low-level identifier) to a drive. The actual drive has been restored properly, as you'll see by looking at it -- only the UUID is different.
This is fixed in v2.0. In the meantime, just ignore the error. (Note that, because the UUID is different, you may have to select the drive as a source or destination in SuperDuper! again.
Hope that helps!
__________________
--Dave Nanian
|