During my first backup, there are hundreds of these messages:
| 05:14:01 PM | Info | WARNING: Caught I/O exception(5): Input/output error
| 05:14:01 PM | Info | WARNING: Source: /Users/adamshopis/Documents/Final Cut Pro Documents/Capture Scratch/Untitled Project 1/Untitled3, lstat(): 0
| 05:14:01 PM | Info | WARNING: Target: /Volumes/Macintish HD Clone/Users/adamshopis/Documents/Final Cut Pro Documents/Capture Scratch/Untitled Project 1/Untitled3, lstat(): 0
Finally, after 6BG have been written, there is an ERROR and not a warning:
| 05:14:01 PM | Info | Attempting to copy file using copyfile().
| 05:14:01 PM | Info | Attempting to copy file using ditto.
| 05:14:02 PM | Error | ditto: /Volumes/Macintish HD Clone/Users/adamshopis/Documents/Final Cut Pro Documents/Capture Scratch/Untitled Project 1/Untitled3: Input/output error
Contrary to what some suggest, THE FILES ARE PERFECTLY FINE! Including the one that caused the ERROR. Or, the files are good enough to be read by applications which really is all one needs.
SD should simply copy all bits on USER files and not halt the copying even on an error. (Just skip the file.) At worse, after a Restore, one would have the same bits that one had before the Backup. If the bits are the same, then if one finds one can't open a file after a Restore, one couldn't do it before the Backup.
A list of the files with "errors" with their path could then be written to the Source and Target. Now you could see and find the problems for yourself.
SD seemed like it was a good program, but there are others reporting the same problem.
How do you get your money back?
