#1
|
|||
|
|||
You were right -- the first time
Originally you thought the files were bad on my Mac. Then it looked like the NAS wasn't working right. I always wondered how with an error called "I/O" anyone could tell if it was a read or a write error.
Now I'm getting Error #36 errors from the same files that could not be copied by SD. I'm getting strange sounds from my Mac's drive so I expect it is going bad slowly. IMHO there is no reason to abort a backup because there is an error reading a file. Simply skip the file upon a read error and continue. Is there anyway to tell SD to keep working even if it encounters errors while backing-up a /USER directory? I can use the log to see what files are bad. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Future of SuperDuper? (in light of Leopard Time Machine) | backerupper3160 | General | 10 | 10-20-2007 10:18 PM |
SD! & HDD copy speed fun | DaleMeyn | General | 3 | 03-20-2006 04:24 PM |
Big error fails every time! | skumancer | General | 5 | 02-28-2006 07:00 AM |
Could not disable Ignore Permissions - each time I backup | Tricia Henwood | General | 3 | 08-08-2005 07:57 AM |
1st backup clone to ext dr estimated time ?? | esuebrown | General | 3 | 07-24-2004 04:31 PM |