My SO has a Mac, and she was using Time Machine to back it up. As someone who cut his teeth with Amanda backups back in the day, Time Machine is a beautiful, intuitive backup solution. Really, it is.
However, a while ago the backups stopped working. She saw this error message: “Unable to complete backup. An error occurred while copying files to the backup volume”.
I googled around for it and saw this KB article from Apple, which wasn’t too helpful, as the only troubleshooting suggestion was a reboot (hmmm, sounds a bit like Windows). I tried doing that multiple times, and still saw the error message.
So, we tried a different hard drive. That still didn’t seem to work–same error message.
Finally, I did some more googling and ran across this forum post (yes Jeff Atwood, forums are indeed the dark matter of the web), which gave me additional troubleshooting tips.
Basically, if you are seeing this error on time machine:
- connect your time machine disk drive to your Mac
- turn off time machine by opening the time machine prefs and select ‘none’ for the backup disk
- open up your console
- click on ‘system.log’
- click ‘clear display’
- turn on time machine by opening the time machine prefs and selecting your disk drive
- watch the system log for errors that look likeMar 9 12:14:14 computer-name /System/Library/CoreServices/backupd: Error: (-36) SrcErr:YES Copying /path/to/file/file.name to (null)
- remove those files
- restart time machine by repeating steps 2 and 6.
I am not sure how to fix the issue if you can’t remove those files. The files that were causing issues for our Mac were imap mailabox files from Thunderbird, so I just uninstalled Thunderbird and removed the mailbox files.
Lost you so long ago. How do I open my console? I don’t even know what it is lol.
This link can help you open the console: http://mac.tutsplus.com/tutorials/app-training/how-to-use-console-your-macs-diagnostic-diary/
Thank you so much! I was stymied by this error message, and as you mentioned Apple’s suggestion was a) rude and b) did not work. This did. For me it was a directory of 2003 tax forms that I had recently copied from another computer using scp. No idea why backupd barfed on these files.