The convergence of the mind of Michael Johnson with the World!

Time Machine Error Continued

Thursday, July 10th, 2008

I experienced another Time Machine error exactly like the last one.

Unable to complete backup. An error occurred while copying files to the backup volume.

Console reveals the logs to show “Error: (-36) copying” with a path to the file and closes with an “Error: (-8062) copying” with a path to a file. The difference from my previous trouble is that this file is a JPEG file that I mported last weekend. I copied the file to a new version and deleted the original and the backup completed without error. But this problem still puzzles me.

I have run Disk Utility and find nothing wrong with either the internal hard drive or the external backup drive.

I’ll continue posting my experiences with this error in hopes that it helps someone else. Clearly, Time Machine still has some maturing to do. Hopefully Apple will fix this soon as it will frustrate the less technically inclined that it was designed for.

Tags: , , , , ,

Time Machine Error solved

Wednesday, July 2nd, 2008

\For the last five or six days I have had an error pop up from Time Machine. It turned out to be a file I downloaded last week that Apple didn’t like. Interestingly, Jungle Disk and Carbon Copy Cloner had no problem performing their backup. So with 2 good backups out there I was not overly concerned. Today I took time out to look at the error.

As you can see from the screen capture that the error message that popped up was not informative. Always check Console for better detail on error messages. Console reveals log files very easily. The logs showed two “Error: (-36) copying” with a path to the file. And closes with an “Error: (-8062) copying” with a path to a file. These were MP3 files I had downloaded last week. They played fine and other than a problem with Time Machine appeared to be good files in everyway.

I deleted the files and ran Time Machine again and it completed fine.

I searched for the meaning of the error number but could not find an explanation. I could find others report similar porblems and one person who came to the same solution I did. But no details about why. Is it just an Apple Time Machine thing? I don’t know but I’m functional again.

Tags: , , , , ,