![]() |
|||||||||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
#2
|
||||
|
||||
SuperDuper! is reliable, germ, but in this case the problem is that the image was somehow corrupted at a low level. We don't operate at a low level -- so, this must have happened because something in the OS or drive failed. What that is, I'm not sure: I just don't have any information to work with.
Did you have any problems when you performed the operation, on the drive, ejecting, etc? Something must have happened to it. Perhaps it's the FireWire enclosure, since everything worked properly until you placed the drive into it?
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
alternating backup | snoopy67 | General | 11 | 04-04-2009 05:14 PM |
Bootable step required for data backup only? | hattorihanzo | General | 2 | 03-14-2006 07:17 PM |
Scheduled backup problem | macWish | General | 3 | 01-30-2006 07:57 PM |
(Zero-length) File caused SuperDuper to abort backup | alancfrancis | General | 7 | 08-31-2005 10:42 AM |
Security of SuperDuper Backup Data? | Zeigh | General | 1 | 08-08-2004 12:29 PM |