Time Machine Error cannot write to sparse bundle -- file in use.

We're having trouble with a Time Machine backup. Twice in the last three days, the backups failed with the error message that the backup disk image is already in use. I noticed that the partition containing the backup sparse bundle is mounted twice in /Volumes -- /Volumes/X and /Volumes/X-1. The error message refers to /Volumes/X-2.
The icon that appears on the desktop has not cleared as if it's still doing a backup.
Looking at the sparsebundle directly gives me the "verificationstate" as 1 -- I recall reading that this is supposed to 0. Other values:
verificationdate == 2012-06-05, and VerificationExtendedSkip == false.
Note that the backup drive is attached to another Mac still running Leopard. This is run fine for years over a gigabit network.
Any ideas?

OK, we fixed this for now with the simple, but common Mac way of
throwing something in the trash.
In this case it seems to be a temporary network connection to the remote Time Machine partition. When Time Machine balks, the icon for the temporary mount gets stuck on the Desktop. We threw it in the trash (unmounting it) and then Time Machine can resume.
Apple networking is annoying, but then on the other, it's easy. We lose printing in a similar way.
Anyway, although we seem to be OK, I'd like to understand this a bit better. I can see in the "/Volumes" folder (in Terminal) three Time Machine mounts, not one as I would have expected, and they all appear to point to the same place:
drwx------   9 root                   wheel 264   Jun 22 10:23 TM-2
drwx------   9 root                   wheel 264 Jun 22 10:23 TM-1
drwx------   9 MYUSERNAME staff   264 Jun 22 10:23 TM
On the remote machine, the disc TM appears only once.
If you look at the listing of all three, they are identical. What gives?
Is this a consequence of the fact that we are putting the time machine backups on a remote machine (that is not a Mac OS server). We have to mount the remote disc before Time Machine will run, but from that point it works perfectly -- or as perfectly as any mac networking thing seems to work.

Similar Messages

Time machine cannot complete backup sparse bundle already in use

I'm getting an error message: time machine unable to complete backup, sparse bundle already in use?
Please advise, I need to find the "yellow brick road", guess it wouldn't be cool for a guy to click red slipper heels together?
Help? Much appreciated....
Macmanusider

What constructive purpose do these smart mouth answere provide? I have been through the "more like this" discussions and the mostly have answers referring you to "more like this". The troubleshooting links refer to old and outdated systems. After all these years, doesn't anyone have an intellrgent suggestion? Is there any way to make the Time Machine backups dependible? It's not worth the trouble to have to reconnect by USB, reboot the time machine, etc. every couple of weeks.

Time machine has created a new sparse bundle

I have booted my new Macbook from my time machine back up. Time machine has created a new sparse bundle and I cannot access the previous backups. Is there any way to make time machine to use the previous sparse bundle? Thanks, Karl

Use the old backups to continue backups or use them for migration etc..
If you have a new Mac then continuing to use the same backup is not recommended..
Info you can see here..
B5 and B6 http://pondini.org/TM/Troubleshooting.html
I do not think it is good idea.. however you can access the old backup to get files if you need them.
See Q17 here.
http://pondini.org/TM/FAQ.html

Time machine backup blocked; disc image sparse bundle needs ejecting

Team, I cannot backup to 2Tb time machine; error message as above. How do I 'eject' this disc image and what exactly is it?
Thanks
Nick B

OK, we fixed this for now with the simple, but common Mac way of
throwing something in the trash.
In this case it seems to be a temporary network connection to the remote Time Machine partition. When Time Machine balks, the icon for the temporary mount gets stuck on the Desktop. We threw it in the trash (unmounting it) and then Time Machine can resume.
Apple networking is annoying, but then on the other, it's easy. We lose printing in a similar way.
Anyway, although we seem to be OK, I'd like to understand this a bit better. I can see in the "/Volumes" folder (in Terminal) three Time Machine mounts, not one as I would have expected, and they all appear to point to the same place:
drwx------   9 root                   wheel 264   Jun 22 10:23 TM-2
drwx------   9 root                   wheel 264 Jun 22 10:23 TM-1
drwx------   9 MYUSERNAME staff   264 Jun 22 10:23 TM
On the remote machine, the disc TM appears only once.
If you look at the listing of all three, they are identical. What gives?
Is this a consequence of the fact that we are putting the time machine backups on a remote machine (that is not a Mac OS server). We have to mount the remote disc before Time Machine will run, but from that point it works perfectly -- or as perfectly as any mac networking thing seems to work.

Time machine error - backup fails due to sparsebundle already in use

Since upgrading, Time machine reports backup error:
TIme Machine Error
The backup disk image ...sparsebundle is already in use.
Any thoughts?

Thanks russ. After the initial upgrade to Mt Lion, no backups have been made. Every attempt reports the sparsebundle error. I recently updated to 10.8.1 and a whole new set of problems have shown up which is having me question the wisdom of continuing to invest in Apple product.
I have decided to pack it in with regard to the timecapsule product, as it is just too unreliable, and certainly not worth the continued time and effort it has been taking to try and get it to work. I have instead gone with an online backup service, Crashplan. I have the backup service I am seeing and I am no longer frittering away valuable time on something that ought to just work.
Problem solved.

Time Machine ERROR: Cannot complete FIRST back up

Hello all.
This is my sis's Mac mini, there was apparently a file or system corruption somewhere that it was not able to boot up, so send in for rescue and the tech was able to rescue all the users' data (sis & dad's)
So Mac mini came home, I reformat the hard disk, ran Disk Utility check and everything OK, and install Leopard 10.5 and iLife 08, and updated them all. Newly-installed apps like Messenger and Skype etc, Time Machine was running OK till now.
Then I started to move my sis's data (user) into the new folders - data of Mail, iTunes, iPhoto, Safari, etc. And TM starts to back up also, and here's where the problem begins:
Time Machine fails to complete back up and give this message:
_Time Machine Error_
Unable to complete backup. An error occurred while copying files to the backup volume. (OK button)
Now this is quite obvious one or more files from the old user folder must be corrupted or "simply bad" that creating this problem. I am suspecting it may be the same problem that was preventing me from previously backing up using SuperDuper while the mini was still in Tiger.
Is there a log file somewhere I can examine to find out which file to delete and not back up? Because the only other way is the start the mac afresh, but I am sure my sis wants her data back.
Thanks and cheers

I seem to be experiencing the exact same issue.
1. I wiped my internal and external HDs and formatted them as MacOS X Extended (Journaled), as per instructions on Support Article: TS1550, with the correct partition schemes for a PowerPC processor.
2. I re-installed MacOS X Leopard from DVD onto the internal HD, created a new admin account, ran Software Update to add all the patches. Re-installed all third party software.
3. I re-created my user account using files restored from a DVD backup.
4. Computer works well, just the same as it always did, except Time Machine cannot complete the first backup.
I have added the +Time Machine Buddy+ widget and got the following report log:
Starting standard backup
Backing up to: /Volumes/Iomega HDD/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 136.9 GB excluded items size: 311.7 MB for volume Macintosh HD
No pre-backup thinning needed: 163.95 GB requested (including padding), 931.15 GB available
Waiting for index to be ready (-911 < 0)
Error: (-36) SrcErr:NO Copying /Applications/Address Book.app/Contents/MacOS/Address Book to /Volumes/Iomega HDD/Backups.backupdb/David Bailey’s iMac G5/2009-02-08-194015.inProgress/C9E9C68B-9FD6-474C-A2E0-BD60ADF3C011/Macintosh HD/Applications/Address Book.app/Contents/MacOS
Stopping backup.
Error: (-8062) SrcErr:NO Copying /Applications/Address Book.app/Contents/MacOS/Address Book to /Volumes/Iomega HDD/Backups.backupdb/David Bailey’s iMac G5/2009-02-08-194015.inProgress/C9E9C68B-9FD6-474C-A2E0-BD60ADF3C011/Macintosh HD/Applications/Address Book.app/Contents/MacOS
Copied 0 files (1.2 MB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11
The external HD is an Iomega MiniMax 1TB Firewire/USB Hub HDD.
The computer is an iMac G5 1.8GHz (no iSight) with 1GB RAM.
I'm guessing that there is something weird with the Address Book app that is stopping the backup. The app itself launches and runs fine, and also syncs with MobileMe fine.
Any ideas?

Time Machine Error sparse bundle could not be accessed

Issue: Time Machine Error "the backup disk image "/volumes/data/.sparsebundle" could not be accessed (error -1).
Background: I have an '07 iMac with an external WD 1TB hard drive to store video, pictures and music as well as a 1TB Time Capsule to use for my Time Machine back ups. Once I converted to Lion, I started getting the "sparsebundle...counld not be accessed" error message. The Apple support line directed me to take the issue up with my local Apple store (or else they would have charged me $50). I went to the local Apple store and was directed to erase my sparsebundle and start over. My iMac apparently values the sparsebundle as it would not let me delete it...it would just hang up. I finally had to erase the file from the Time Capsule and start over (based upon some recommendations I found within the Apple Support Communities). I did that two days ago and it looked like I was in the clear. I have about a day's worth of backups and now just started getting the same error message as I did before. I am a casual computer user with limited trouble shooting skills. Does anyone have any ideas, tips or suggestions as to the source of the problem and how to properly trouble shoot the issue?

Dirty of Apple.. this is a bug.. that is caused by your upgrade to Lion.
We see loads of issues. Did you upgrade install? I am not sure that that is some of the issue.
Anyway the solution is to restart the TC.. just pull out the plug and reboot it.
Like windows.. first support question. Did you turn it off and on again??
Read C17
http://pondini.org/TM/Troubleshooting.html
You need to use the 5.6 utility so download and install that.
http://support.apple.com/kb/DL1482
Go to the disk page and disconnect all users.. same thing as pulling the plug really.

Safari won't open. Firefox disappeared, only question mark. Mail doesn't have content. Time Machine won't turn on because sparse bundle is in use. Please help.

I had this issue about a month in a half ago and it was fixed by a local technician. I no longer have access to him and I really need some help. The issues are as follows:
Safari will not open.
Firefox disappeared. No icon, just a question mark in it's place.
When I open mail it shows I have new messages but the content is blank.
Time Machine cannot turn on because sparse bundle is in use.
New files that were made are no longer available. It's almost as if the computer jumped back in time.
The Mac Mini is running Mavericks 10.9.5

I'll assume that you have some way of connecting to this website from the affected machine. If not, ask for other instructions.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen. Click the Clear Display icon in the toolbar. Then try to launch Safari. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

"Time machine error, The disk image cannot be mounted" What can I do??

I ran the time machine. Then, "preparing backup" showed up for a long time. After that, a window pop out: "Time machine error, The disk image cannot be mounted" What is disk image? What can I do (I can't back up anything)
P.S. I use time capsule for backup. there were no problem on connection

I'm having the same issue. I do not have TC as my base station. It says right in the book that if you choose, you do not have to have it run as your router, just as a part of your existing wireless network. All software is up to date and I have already shortened the name of both my TC and TC disc to 6 characters and no spaces! I've already spoken with someone today about this. He really didn't know. Have tried backing up both wirelessly and directly connecting with an Ethernet cord. I had to finally call because when I attempted to register the product to get online support, apple.com didn't recognize the serial number!!! The gentleman on the phone got it registered for me. I bought the TC from an official apple store and for whatever reason when he put in the serial number his computer said that this TC was so "old" I guess that there was technically "no support." That basically means that even though my parents just purchased this for me a week before Christmas, that it was made a year ago and the warranty is not good?? I need to do more research on that. Right now I am very unhappy about this. I am a firm apple user and have been for years, but this is frustrating.
I had read somewhere else (not sure I've been searching apple for what seems like forever now) to make sure that the TC was showing up in "devices" of the Finder. Mine doesn't show up there, but rather in the "Network" window. Is this an issue? If it is, can anyone tell me how to fix that. I have Time Machine backing up to my TC, so I do not see why it would be.
UPDATE: I just opened up my TC on the "Shared" section of the Finder window and deleted the old "sparsebundle" (I had no clue that anything had backed up way back at 3:30pm on Dec 29) and now I get a slightly new message: Time Machine Error: The backup disc image could not be created." So now the word "mounted" is replaced with "created." This error showed up a lot sooner than the original one. Ok, no clue. I am going to try to Change the Disc again, and try again. I will post another update.
Message was edited by: kryzma

Lost all photos on my iPhoto and get the ERROR WRITING TO DISK when trying to reload from Time Machine. iPhoto cannot import your photos because there was a problem writing to the volume containing your iPHOTO LIBRARY . Looking for solution.

Lost all photos on my iPhoto and get the ERROR WRITING TO DISK when trying to reload from Time Machine. iPhoto cannot import your photos because there was a problem writing to the volume containing your iPHOTO LIBRARY . Looking for solution.

Problems such as yours are sometimes caused by files that should belong to you but are locked or have wrong permissions. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.
First, empty the Trash, if possible.
Triple-click anywhere in the line below on this page to select it, then copy the selected text to the Clipboard by pressing the key combination command-C:
find ~ $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $ 2>&- | wc -l | pbcopy
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign ($) to appear.
The output of the command will be a number. It's automatically copied to the Clipboard. Please paste it into a reply.
The Terminal window doesn't show the output. Please don't copy anything from there.

HT3275 Time Machine error. Unable to complete backup. An error occurred while copying files to the backup volume. Tried restarting, remounting external WD drive. Still cannot backup.

Time Machine quit backing up files. Bought a new WD external drive. Worked for awhile, then quit backing up. Tried restarting computer, remounting drive. Message: Time Machine Error. Unable to complete backup. An error occurred when copying files. Suggestions?

Thanks so very much for your help!! I'm boggled by it and now just about ready to dump the whole idea of Time Machine and backup using a cloning program. Maybe TM is only guaranteed to work well with Time Capsule these days?
Today there again was no backup. I did as you suggested, looked into Console. It showed many lines of "(Error) DiskStore: No block in wakeup" and also repeatedly "(Warning) DiskStore: Ignored bogus fetch...".
So I created a marker and attempted to initiate a backup, keeping Console open and refreshed. Here's what I got:
8/19/13 5:18:40.385 PM Console: Marker - Aug 19, 2013 5:18:40 PM
8/19/13 5:19:48.844 PM com.apple.backupd: Starting standard backup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.508 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:38ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.510 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:40ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:20.000 PM kernel: USBF:          58091.976          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:20:51.000 PM kernel: USBF:          58122.985          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:21:22.000 PM kernel: USBF:          58153.992          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:21:53.000 PM kernel: USBF:          58185. 2          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:22:24.000 PM kernel: USBF:          58216. 14          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:22:55.000 PM kernel: USBF:          58247. 25          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:23:26.000 PM kernel: USBF:          58278. 41          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:23:57.000 PM kernel: USBF:          58309. 51          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:24:28.000 PM kernel: USBF:          58340. 59          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:24:59.000 PM kernel: USBF:          58371. 68          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:25:30.275 PM xpchelper: for uid: 501 -- timeout while waiting on FSEvents flush; clearing cache.
8/19/13 5:25:30.000 PM kernel: USBF:          58402. 82          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:26:01.000 PM kernel: USBF:          58433. 96          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:26:32.027 PM com.apple.backupd: Backing up to: /Volumes/TMBackups/Backups.backupdb
8/19/13 5:26:32.000 PM kernel: USBF:          58464.112          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:27:02.653 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David‚Äôs iMac size:37
8/19/13 5:27:02.657 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David‚Äôs iMac size:37
8/19/13 5:27:03.000 PM kernel: USBF:          58495.121          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:27:12.668 PM com.apple.backupd: Backup failed with error: 2
During this 9-minute timeframe Finder also was inoperative - according to Activity Monitor: "Not Responding".
I'm thinking it's the standalone Buffalo backup drive not waking up, and so everything comes to a screeching halt. Do you also think I should abandon TM and just do manual backups every day using a clone program?

Time Machine Error message and Time Machine

Hello,
I use my 1TB Time capsule to back up my MacBook Pro. Just recently, it wouldn't back up, giving the error message "back up failed, Time Capsule 1 is already in use." I renamed my Time Capsule storage, so it actually says "storage1". So, it obviously thinks I have 2 storage drives (I don't). And what is a sparsbundle? And, it seems to be backing up the same stuff over and over, instead just the new info. I say this because my space went from 566GB down to 399GB in a matter of days. Would this have anything to do with the fact that I just switched from Entourage and loaded Microsoft Outlook for email? Please advise and thanks in advance.

jilco wrote:
Hello,
I use my 1TB Time capsule to back up my MacBook Pro. Just recently, it wouldn't back up, giving the error message "back up failed, Time Capsule 1 is already in use." I renamed my Time Capsule storage, so it actually says "storage1".
Do you mean the folder on your Time Capsule that is/was named "Data"? If so, that shouldn't be a problem.
But if you mean the Time Capsule itself, you should be able to re-select it via Time Machine Preferences.
It sounds more like you were using the +Star Wars+ display to look at your backups when a new backup was trying to start. If the backup disk image appears on your desktop, or Finder sidebar, just eject it and try another backup.
It's also not a problem to rename a drive that's being backed-up, since Time Machine keeps track of drives by their UUIDs (Universally Unique IDentifiers).
So, it obviously thinks I have 2 storage drives (I don't). And what is a sparsbundle?
It's actually a +sparse bundle disk image,+ an odd container that Time Machine uses for network backups.
And, it seems to be backing up the same stuff over and over, instead just the new info. I say this because my space went from 566GB down to 399GB in a matter of days. Would this have anything to do with the fact that I just switched from Entourage and loaded Microsoft Outlook for email?
Yes, quite possibly. See #D4 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum), for some common culprits and ways to find out exactly what's getting backed-up.

Time Machine: Error occurred while creating the backup folder

Mac Mini 2.53 GHz, 8 GB DDR3
OS X 10.8.4
Time Capsule 1 TB, connected via ethernet
Airport Utility 6.3.1 (631.4)
"Time Machine Error. Unable to complete backup. An error occurred while creating the backup folder."
I believe my Time Capsule is out of space and isn't removing older backups to create space for itself. Time Machine preferences says only 98 MB available on the 1 TB volume. I have used Pondini's superb troubleshooting page with the following results:
A1: Time Machine Buddy Widget. Partial log from backup attempt:
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Failed to create progress log file at path:/Volumes/Time Machine Backups/Backups.backupdb/Macmini-34159E18D208 (4)/2013-04-04-223516.inProgress/.Backup.400571203.603238.log.
Event store UUIDs don't match for volume: Macintosh HD
Error: (Error Domain=NSCocoaErrorDomain Code=640 "You can’t save the file “598C5622-100E-456A-89AF-DEBC87A6CA89” because the volume “Time Machine Backups” is out of space." UserInfo=0x7f88a330cef0 {NSFilePath=/Volumes/Time Machine Backups/Backups.backupdb/Macmini-34159E18D208 (4)/2013-04-04-223516.inProgress/598C5622-100E-456A-89AF-DEBC87A6CA89, NSUnderlyingError=0x7f88a33056a0 "The operation couldn’t be completed. No space left on device"}) Creating directory 598C5622-100E-456A-89AF-DEBC87A6CA89
Failed to make snapshot.
Backup failed with error: 2
Ejected Time Machine disk image: /Volumes/Data/Macmini-34159E18D208 (4).sparsebundle
Ejected Time Machine network volume.
A4: Full reset of Time Machine. Done, did not change error from occurring on next backup attempt.
A5b: Verify backups on Time Machine. Done, successful (no problems).
C10: Also attempted switching out ethernet cable and tried different ports on the Time Capsule, to no effect.
I have no exceptions listed in Time Machine preferences (under Options) and the box for "notify when deleting old backups" is UNchecked.
Any suggestions would be most appreciated!!

grifftastic wrote:
I believe my Time Capsule is out of space and isn't removing older backups to create space for itself. Time Machine preferences says only 98 MB available on the 1 TB volume.
"You can’t save the file “598C5622-100E-456A-89AF-DEBC87A6CA89” because the volume “Time Machine Backups” is out of space."
Yes, it's so full it can't get started -- not even far enough to start deleting old backups.
If you have other data there (not usually a good idea), move some of it elsewhere temporarily, and try again.
If not, manually delete a couple of old backups, and "compact" the sparse bundle, per Time Machine - Frequently Asked Question #12.

HT4500 Support Apple advice does not work; I followed the instructions; Time Machine backups cannot be found, possibly in use. Right after an installation of OS.

How can I recover my files using Migration Assistant? Time machine backups cannot be found.
I tried recovery by entering time machine and selecting the files, but they don't appear anywhere; they're on the HD somewhere but neither Finder nor Spotlight can 'find' them.

Have you repaired your permissions? This can be a very frustrating situation which I encountred after a logic board replacement.
What I did was start a TM backup, but excluded items too make it a minimal backup. Make sure you select verify in the TM option before you backup. After the current backup I was able to see the sparse bundle and the prior backups in the Finder. (Check and see after this backup if your oldest and current backups are llisted. If not read on) However, it would not remain seen in the Finder after I closed it. Somehow I was able to see my prior backups again in the Finder. This time I deleted the current TM App in the applications and copied the old one from the TM. It now shows me both old and current backups for selection.
I do not profess to be an expert on the TM. This is just how I accidentally solved my problem.
I wish Apple or a Apple Developer would make an App for these problems. Someone could make a lot a money.

Time Capsule (Time Machine) error -1

My 14-month old 1TB TC seems to be having a disk hardware problem. It's been working without issue since I got it in November 2009. The other day, I got an error message (I didn't record it) that stated something to the effect of "TM couldn't validate your backup, so we have to do a complete new backup". I let it do its thing, but it failed with the new error message "The backup disk image “/Volumes/+drive name+ 1.sparsebundle” could not be created (error -1)." In trying to restart the TC, the hard drive was making loud mechanical clicking noises for several minutes before failing again with the error message. At one point I was able to get the drive to mount on the desktop and ran Disk Utility on the sparse bundle file (twice), and it indicated it was fine. However, my backup data was no where to be found. I tried setting up the TC again as the backup drive, but got the same loud clicking noises and error message as above. I tried to archive what data was on the drive from the Airport Utility, but it also crapped out after saving some data (same loud clicking noises for some minutes and no additional progress on saving data). I cancelled the archive and turned off Time Machine for now.
Any clues? By the way, the WiFi network portion of the TC is still working fine. My guess is a hard drive failure. I plan to call Apple tech support to see if the TC is covered by APP (bought the TC with my new iMac). Thanks for any insights or advice.

Woodsman wrote:
By the way, they replaced only the TC unit itself with a new one. It had been shipped in a plain brown box with nothing else, not the retail packaging.
That's probably a refurbished unit.
Both the AppleCare rep and all the employees at the Store were professional and courteous. When you have to use AC, its always a first class experience.
Maybe not always, but most of the time. Apple always gets the highest marks for customer service.
As I type this, Time Machine is creating a new backup.
Great!
I'm thinking rather than set it on auto-pilot, I may make manual backups every couple of days. I really don't need anything more frequent than that. Perhaps the constant churn of the hourly backups (when the iMac is on) is a contributing factor to the TC hard drive's demise. All's well that ends well.
That's really not a good idea. Disk drives are made to be used, and Time Machine backups are less stressful than most other uses of a drive, since it's idle most of the time, and not trying to do several things at once.
The great thing about the hourly backups is, when you accidentally change or delete the wrong file (like doing a "Save" when you should have done "Save As"), or something turns up corrupted, you've got an excellent chance of recovering a previous version.
And it's far too easy to forget to do backups manually, and find yourself 3 or 4 days behind (or worse) when something awful happens to your Mac.
Anyhow, glad it's sorted out, and thanks for the feedback.

Time Machine Error cannot write to sparse bundle -- file in use.

Similar Messages

Maybe you are looking for