27 October

Apple Time Machine is an attractive backup system for OS X, but I had a hard time fixing it after it recently stopped working for me after I accidentally unplugged my firewire backup disk during a backup operation. For subsequent backup attempts, I got the error message that the backup had failed because a "time machine error -- Unable to complete backup" had occurred. Not so helpful. (This is sometimes manifested as a message in the Console like Backup failed with error: 11.)

By running the Console application, I was able to look at the error messages from backupd. In my case, there were some files that could not be inspected leading to messages like this:

10/27/08 10:00:42 PM /System/Library/Frameworks/.../mdworker[13920] tar importer countered an error (512) scanning "/X/1/Scr/private.tar"

but there were not serious. Eventually a crash occurred though, as follows:

10/27/08 10:04:24 PM ReportCrash[14175] Formulating crash report for process backupd[14129]
10/27/08 10:04:25 PM com.apple.launchd[1] (com.apple.backupd[14129]) Exited abnormally: Segmentation fault

but there was no explanation as to why.

Well, I figured it might be attempting to continue the previous malfunctioning (somehow corrupted) backups. This was supported by the presence of a (hidden) directory
of the form


found by typing "ls -ld thatfile" from the terminal.

I figured the solution was to dispose of the directory called 2008-10-27-075904.inProgress by either removing it (and its contents) or moving it elsewhere.

Unfortunately, the files in that directory use extended attributes and cannot be readily deleted. You can turn off these attributes (with xattr), but it needs to be done file-by-file and it's cryptic.

The solution is to use the command fsaclctl which disables extended attributes (and access control lists) for an entire volume at a time.

Thus, I used

cd /Volumes/MyBook/Backups.backupdb/
sudo fsaclctl -p /Volumes/MyBook/ -d
mv 2008-10-27-075904.inProgress ../hideme
sudo fsaclctl -p /Volumes/MyBook/ -e

After that, Time Machine backups worked again!

By Gregory Dudek at | Read (2) or Leave a comment |    
Re: Fixed Errors with Apple's Time Machine Backup System

At least it was mere data and not the essence of an intrepid time traveller :)

[ Yeah, uh... just what I was thinking... Thanks! -gd]

Posted by: Krys at November 25,2008 15:04
Re: Fixed Errors with Apple's Time Machine Backup System

Nothing else worked for me until I found this post. Google, bump this page UP!

Posted by: ilan at January 17,2009 23:30
Please send trackback to:/blog/142/tbping
There are no trackbacks.
Post your own response

Each comment is manually screened for the presence of appropriate and substantive content, due to a constant onslaught of comment-spam. This means there may be a delay before your comment appears.

(Some kind of name is required, will be visible)

Required, whatever you enter will be visible to other users.

(Optional, used for "mailto" link)

Your email address is not required, but if you insert it it will be displayed so people can contact you.

Answer this question correctly to demonstrate that you are not a dumb spambot.

The title for your comment.

Your comment goes here. All relevant comments are welcome, except for those that simply promote an irrelevant product or else are used to fraudulently inflate the link count to an irrelevant web page. They appear after moderation. Don't forget to also fill in the captcha below or your text will be rejected automatically!

You must answer this question to prove you are human
The governator said (when in a movie as T2): 'I'll be ... (pick a number): 1:tuckered, 2:broke, 3:back, 4:broken, 5:swartzneggered, 6:eaten, 7:you?

Answer this question correctly to demonstrate that you are not a dumb spambot.