Backup Failed With Error 11 Time Machine
Contents |
10.5: Repair a Time Machine 'Error 11' problem May 19, '09 07:30:00AM • Contributed by: leichter One of the more distressing Time Machine errors is Error 11. This is a "sticky" error; once it occurs, Time Machine will hit it every time it time machine logs runs. All you'll see in the standard Time Machine interface is that Time Machine keeps time machine backup failed with error 19 failing. You need to check the system logs to see the Error 11. The underlying cause of Error 11 appears to be some time machine backup failed with error 2 other error that caused an earlier Time Machine run to terminate without cleaning up after itself. This leaves behind a partial file that indicates to Time Machine that another copy of Time Machine is already producing a backup, so time machine backup failed not enough space it just stops. Colin Charles worked out the basic problem and solution, but his description only seems to apply to locally-attached disks. For network-mounted disks, where you've got an additional level of sparsebundle in the way, things are a bit more complicated. Read on for the solution...Here are the steps needed to recover from the problem: Stop Time Machine in the System Preferences panel. Mount the remote disk for read/write access. Open Terminal and run the following command:
Time Machine Backup Failed Read Only
sudo -s. Enter your admin password when prompted. This will create a root shell for the remaining Terminal commands (even though not all commands need root privileges). Enter these commands: $ cd /Volumes $ ls You should see your remote-mounted disk here. For simplicity, let's say it appears as Backup. Type ls -ls Backup. You should see a .sparsebundle file with a name based on your machine's name and hex MAC address. I'm not sure exactly how these names are constructed, but for simplicity's sake, I'll pretend the name is mymachine.sparsebundle. Check that root has both read and write access to this file. If not, you probably mounted the disk with read-only access. Type hdiutil attach Backup/mymachine.sparsebundle/ -noverify -noautofsck -readwrite. This command, which must be typed on a single line substituting the name for your sparsebundle file, mounts the actual backup image. It will take a bit to finish. (Without the -noverify and -noautofsk options, it can take hours! The -readwrite option is probably the default.) Type ls -ls. There should now be an additional volume visible. Again, I'm not sure the name is always constructed the same way, but it will probably look like TM-backup-of-mymachine. Root should again have read/write access. Type fsaclctl -p TM-backup-of-mymachine/ -d. The backup directory has an access control list (ACL) that prevents any modifications. This command disables ACL enforcement on the file system. Note th
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this
Time Machine Backup Fails Repeatedly
site About Us Learn more about Stack Overflow the company Business Learn more time machine error the backup volume could not be mounted about hiring developers or posting ads with us Ask Different Questions Tags Users Badges Unanswered Ask Question _ Ask Different time capsule backup failed is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody http://hints.macworld.com/article.php?story=20090515063602219 can answer The best answers are voted up and rise to the top Time Machine Backup Failing with Error 11 up vote 1 down vote favorite I've been trying to run a Time Machine backup for the last couple of days (OSX 10.7.5 and Porsche LaCie 2TB); however, it has been constantly failing. Console is producing the following crash messages 16-01-01 3:56:47.345 PM ReportCrash: DebugSymbols http://apple.stackexchange.com/questions/221814/time-machine-backup-failing-with-error-11 was unable to start a spotlight query: spotlight is not responding or disabled. 16-01-01 3:56:49.601 PM com.apple.backupd: Indexing a file failed. Returned 1 for: /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/Resources/zh_CN.lproj/NSProAboutPanel.nib, /Volumes/LaCie/Backups.backupdb/Main’s MacBook Pro/2016-01-01-125749.inProgress/DD6E0FAD-0DB6-45EA-B196-73EAB917DF42/Macintosh HD/System/Library/PrivateFrameworks/ProKit.framework/Versions/A/Resources/zh_CN.lproj/NSProAboutPanel.nib 16-01-01 3:56:49.601 PM com.apple.backupd: Aborting backup because indexing of file failed. 16-01-01 3:56:49.601 PM com.apple.backupd: Stopping backup. 16-01-01 3:56:51.870 PM ReportCrash: Saved crash report for mds[844] version ??? (???) to /Library/Logs/DiagnosticReports/mds_2016-01-01-155651_localhost.crash 16-01-01 3:56:54.817 PM com.apple.launchd: (com.apple.metadata.mds[844]) Job appears to have crashed: Segmentation fault: 11 16-01-01 3:56:55.094 PM mds: (Normal) FMW: FMW 0 0 16-01-01 3:56:55.309 PM com.apple.backupd: Copied 926318 files (32.1 GB) from volume Macintosh HD. 16-01-01 3:56:55.309 PM com.apple.backupd: Copy stage failed with error:11 16-01-01 3:56:55.509 PM mds: (Error) Volume: Could not find requested backup type:2 for volume 16-01-01 3:57:07.134 PM com.apple.backupd: Backup failed with error: 11 I went to Disk Utility to verify/repair my disk, and I encountered the same problems as in this problem with volume bitmap I followed the solution there about restarting in Recovery Mode and repairing with Disk Utility. This solved the issue with the volume bitmap. After this, I started another backup attempt, anticipating success. What was different about this was that the previous failures would tell me
Backup failed with error: 11 Posted on 13/8/2008, 12:11 am, by Colin Charles, under General. Got the dreaded "Backup failed with error: 11" with Time http://www.bytebot.net/blog/archives/2008/08/13/fixing-time-machine-backup-failed-with-error-11 Machine. Actually, I only got the dreaded message from the Console - the application itself, just kept failing silently with no suggestions (Apple, this is your cue to make https://www.reddit.com/r/applehelp/comments/qgmu6/cant_back_up_via_time_machine_backup_failed_with/ Time Machine a little more useful). Nothing in Apple's knowledgebase. Nothing seemingly useful come up in a Google search (i.e. something conclusive) Solution? Delete:
/Time Machine Backups/Backups.backupdb/nameOfComputer/date.inProgress
time machine It'll ask for your password, and be gone with the file. Now the backups should start working again. An example of what the Console showed:
13/08/2008 12:51:57 /System/Library/CoreServices/backupd[4946] Error: (-43) copying /Users/byte/Library/Application Support/Adium 2.0/Users/Default/Logs/AIM.bytebotdotnet to /Volumes/Time Machine Backups/Backups.backupdb/lovegood/2008-08-13-125154.inProgress/424A6617-37A5-4C20-8845-764D9167E317/Macintosh HD/Users/byte/Library/Application Support/Adium 2.0/Users/Default/Logs
13/08/2008 12:51:57 /System/Library/CoreServices/backupd[4946] Copied 702 files (169 KB) from volume Macintosh HD.
13/08/2008 12:51:57 time machine backup /System/Library/CoreServices/backupd[4946] Copy stage failed with error:11
13/08/2008 12:52:03 /System/Library/CoreServices/backupd[4946] Backup failed with error: 11
13/08/2008 12:55:31 com.apple.launchd[73] (0x10dbd0.Locum[4961]) Exited: Terminated
Share this:EmailFacebookLinkedInTwitterGoogle Related Tags: apple, error, knowledgebase, MacOSX/Apple, time machine Michael Fox My wife and I have a 1Tb Time Capsule and its been a pretty good unit. Of course the odd issue after a machine has been rebuilt, but thats the perfect time to start it over again. My wife's MacBook Air has been backing up since the day we got the unit. She has an oldest backup of Apr 11th 2008. Al Look in Activity Monitor and see if ATSServer is grabbing lots of CPU. If it is, your problem is not your respective backup drives; it is a combination of SpotLight not having had your external drives added to exclusion lists and ATSServer trying to do font substitution on PDF documents. Turn both off an you'll be better placed to diagnose the error - but it's usually this. Just poor design, and why they don't fix this long sta
»applehelpcommentsWant to join? Log in or sign up in seconds.|Englishlimit my search to /r/applehelpuse the following search parameters to narrow your results:subreddit:subredditfind submissions in "subreddit"author:usernamefind submissions by "username"site:example.comfind submissions from "example.com"url:textsearch for "text" in urlselftext:textsearch for "text" in self post contentsself:yes (or self:no)include (or exclude) self postsnsfw:yes (or nsfw:no)include (or exclude) results marked as NSFWe.g. subreddit:aww site:imgur.com dogsee the search faq for details.advanced search: by author, subreddit...this post was submitted on 04 Mar 20121 point (100% upvoted)shortlink: remember mereset passwordloginAsk a Question!applehelpsubscribeunsubscribe19,787 readers~36 users here nowCheck our /r/AppleHelp FAQ and basic troubleshooting guide before posting. Guidelines for Askers 1. Follow up after receiving answers! Readers attempting to help you deserve thank-you's and upvotes! Also, after finding a solution, please make sure to mark your post using the "edit solved status" (or "flair") button. 2. Questions must be within the bounds of Apple’s EULA. Certain subjects are not appropriate for /r/AppleHelp, including: Developer Previews and AppleSeed Betas. If you are running a beta or developer preview, head over to /r/AppleHelp_Betas. Jailbroken devices. Hackintoshes. Piracy. Bypassing an Activation Lock or firmware password. 3. Include as many details as possible. Certain information may be crucial for solving issues. Please make sure to include the following: Your model of Mac, iPhone, iPad, iPod, etcetera. Your version of