 |
 |
 |
 |
 |
 |
 |
 |
|
|||||||||||
|
|
|
|
|
|
|
|
|
#2
06-21-2005, 04:54 PM
|
||||
|
||||
|
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 
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| SuperDuper Backup of AES 128 Encrypted Disk Image | rwg4 | General | 3 | 11-30-2005 10:28 AM |
| i/o error on clone | BKSLDR7 | General | 7 | 11-09-2005 03:35 PM |
| Question regarding backing up to Image | giba | General | 3 | 05-20-2005 05:54 PM |
| "convert failed - image/device is too large" error creating a DMG (Image) | dnanian | Frequently Asked Questions | 2 | 05-05-2005 01:28 PM |
| How do I update an image? | dnanian | Frequently Asked Questions | 0 | 06-12-2004 10:05 AM |
Threaded Mode