 |
 |
 |
 |
 |
 |
 |
 |
|
|||||||||||
|
|
|
|
|
|
|
|
|
#9
11-01-2011, 04:56 PM
|
|||
|
|||
|
I had a backup fail with the same error the other night - I reformatted the destination drive, and tried to do a manual drag-drop copy of the folder it choked on.... the same file that stopped SD! stopped the copy, with an error saying the file had data that couldn't be read or written. So I assume a corrupted file can lead to this error too.
Is it possible to make SD! try and continue the clone in this situation - and perhaps show a warning that x files could not be copied?? 
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| '07 MacBook Pro clone to new '11 MacBook Pro (Clone failed) | Cow | General | 10 | 03-31-2011 12:07 AM |
| Problem Booting From a Clone on a Firewire HD | sgmorr | General | 8 | 03-11-2010 11:11 PM |
| Windows equivalent to SuperDuper!? | jreffner | General | 21 | 08-13-2009 05:36 PM |
| Using Disk Utility from Clone gets -9972 error (falsely?) | eagseags | General | 6 | 09-08-2007 09:50 PM |
| Problem getting apps to run on clone volume | ChetA | General | 3 | 09-06-2005 02:19 PM |
Threaded Mode