Time Machine Error - Help!

Hello everyone. I am having a problem with backing up my time machine in Lion and get the following error message: "The backup was not performed because an error occurred while copying files to the backup disk. The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repair your backup disk."
Here is the context and history. I recently installed Mavericks on my Mac Mini (late 2009), which was causing all sorts of problems and constant computer crashes. About a week later I used TM to restore to the previous OS version and backup (Lion) before the problems began, and the computer is now working normally as before, except for TM. Initially I thought it was a problem with the drive, so I tried a TM back-up on my second back-up disk but got the same above error message. Thinking it had something to do still with the disk or older back-ups there saved, I erased one of the disks (using disk utility), performed disk repair, tried another TM back-up but continue to get the same error message. Any suggestions of next steps to try? I am not great with code or computer speak, so would greatly appreciate easy instructions if possible.
One last thing to note, this problem only began after doing the TM restore mentioned above. TM was still working normally even with Mavericks, so intuitively I am guessing something went wrnong during the restore, but everything seems to be working fine except with TM. I have done disk repairs also on the Mac HD and no errors were found. Please help!
Cheers!

This is happening to me too.
It seems that the HD randomly becomes unavailable.

Similar Messages

HT3275 Time machine error, backup disk image "/volumes/data-1/.sparesbundle " already in use. I don;t know what this means, can someone help?

My Mac mini time capsule is showing an error Time machine error, backup disk image "/volumes/data-1/.sparesbundle " already in use. I don;t know what this means, can someone help?

I had a similar problem and I solved it as follows -
In Time Machine - > I deselected time capsule Data Disk as a destination.
Then I pulled the power plug on the Time Capsule, twiddled my thumbs for 15 secs, plugged the power back in.
Went back t Time Machine -> Re-Added the Time Capsule Data Disk as destination. And then tested by selecting Backup Now.
All went well and the backup picked up from before the problem.
BTW - I also have a USB drive connected to Time Capsule that is an alternate disk for Time Machine to backup.
In Mountain Lion the GUI lets you add more than one Time Machine backup destinations very easily so I think it a good idea to have redundancy.
Hope this helps.

Time Machine Error Messages-HELP!!

I purchased a Time Machine a few months ago and it worked for a little while. Now I just receive error messages: "Time Machine Error The backup disk image could not be mounted" and "The storage location for Time Machine backups can't be found". I can't figure this out. I have restarted the Time Machine, I tried reconfiguring it several times and still it is not accessing the backups or creating backups. It is only allowing me to connect to the internet. Can I fix this problem?

I have exactly the same problem. I'm running the latest firmware from both Time Capsule as well as Time Machine.
Could you please tell me if your problem was resolved and if yes, how?
Thanks.

Time Machine Error: "The backup disk image could not be created." Help.

I have two Macbook Pro's. One is able to backup to the Time Capsule with no problems. The other connects just fine to Airport Utility, but I get the following error after I attempt to backup: Time Machine Error: "The backup disk image could not be created."
I have reset the Time Capsule several times, so that is not the fix.
The first thing I see when attempting to open Time Machine is the following message: :The storage location for Time Machine Backups can't be found." It gives me the option to setup the Time Capsule, which I select. The next thing I select is to Change Disk. The window that opens has the Icon with Three people on it. The name of that Icon is The Moreman Time Capsule. I select it, and enter the password I created. I then choose to Backup. Then I choose to backup now. That is when I get the error: Time Machine Error: "The backup disk image could not be created."
Any ideas? Has anyone encountered this problem?

You have to delete the .dmg file and start over. This happened to me 3 times already, I finally switched to Déjà Vu, works perfect and only once a day instead of 24 times a day.
http://propagandaprod.com/

Time Machine Error Unable to complete backup. An error occurred while ...

Hi,
I've looked all around the forums for the answer to this one and I'm still unable to get it. So I'm getting this error "Time Machine Error Unable to complete backup. An error occurred while linking files on the backup volume". This started happening after I turned off and on FileVault. I was having a problem with it and turning it on an off got rid of that problem, but created this one. I've noticed that when I shut down the computer and filevault accesses the TM hard drive, it can back up.....but then when I'm logged on, or I want it to back up I get the error. I've tried fixing the drive, removing the in progress file and resetting the PRAM (i think that's what it was called). I'm starting to run out of options and have no other drive to back all this info on to reformat it.
I really don't want to loose all my stuff.
Please help!
Daria

nautical_stars wrote:
Hi,
I've looked all around the forums for the answer to this one and I'm still unable to get it. So I'm getting this error "Time Machine Error Unable to complete backup. An error occurred while linking files on the backup volume". This started happening after I turned off and on FileVault.
Usually this message happens when you replace an external disk that was being backed-up by Time Machine with another one of the same name.
Since File Vault works by making a sparse image of your home folder, and it's treated as a volume just as a HD is, that's probably what's happening here: the new sparse image has the same name as the old one, but isn't the old one.
First, consider whether you really need File Vault. It doesn't work well with Time Machine: you can't see or restore individual items in your home folder, and it only gets backed-up when you log out.
If you have a lot of other things, say photos, videos, and/or music that don't need to be encrypted, perhaps there's an easier way to secure our sensitive data. You can create an encrypted disk image via Disk Utility (in your Applications/Utilities folder), then copy the sensitive documents into it. Then the rest of your home folder is backed-up normally, and individual items can be viewed and restored in the usual fashion.
But if you do continue using FileVault, you may have to use TM to delete all backups of it, via the instructions in item #12 of the Frequently Asked Questions *User Tip* at the top of this forum. That should then allow the new version of your encrypted home folder to be backed-up by TM.

Time Machine Error "Unable to complete backup"

I have not backed up my hard drive for about 30 days. When I plug my external hard drive in, Time Machine "prepares backup" for a while, then gives me the following message:
*Time Machine Error*
Unable to complete backup. An error occurred while copying files to the backup volume.
I tried unplugging and re-plugging, rebooting my computer, trashing the ".inprogress" backup file and restarting. It did not help. While it time machine is preparing the backup, my computer runs crazy slow, with the rainbow pinwheel spinning for about 5-10 seconds just about every time I click the mouse, in any program.
Per someone's suggestion, I put "sudo grep backupd /var/log/system.log" into terminal, and this is what came up:
"No pre-backup thinning needed: 4.98 GB requested (including padding), 70.16 GB available
Waiting for index to be ready (906 > 0)
Unable to rebuild path cache for source item. Partial source path:
Indexing a file failed. Returned -12 for: /Applications/iChat.app, /Volumes/Time Machine Backups 1/Backups.backupdb/My Computer (2)/2011-01-13-113417.inProgress/CB0D491E-EF04-48A0-9AE9-32AE43E9209C/Macintosh HD/Applications/iChat.app
Aborting backup because indexing a file failed.
Stopping backup."
This time, it was apparently iChat, but in each of the three times I've tried to backup and gotten this error message, a different file has been the culprit for the indexing error.
Any suggestions?

orchestr wrote:
Indexing a file failed. Returned -12
see [this_|http://web.me.com/pondini/TimeMachine/C3.html] user tip by Pondini.
JGG

Time Machine Error: The backup was not performed because an error occurred

G'day (from Queensland, Australia)
Not for the first time Time Machine has broken down - originally in September 08 (I just can't recall how I fixed it!!).
Now it has failed after 14 months of faultless performance.
There seems to be little help available, but searching for solutions finds plenty of problems.
I get the message "The backup was not performed because an error occurred while copying to the backup disk.
The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repair you backup disk."
(I have a Time Capsule as my backup disk)
Disk Utility runs and finds-
Verifying volume “Backup of xxxxxx’s iMac”
2010-01-25 12:16:09 +1000: Starting verification tool:
2010-01-25 12:49:21 +1000: The volume Backup of xxxxxx’s iMac appears to be OK.
2010-01-25 12:49:21 +1000: Repair tool completed:
So I search and find "Fix for broken Time Machine backups under Snow Leopard"
(http://www.andrewgrant.org/2009/09/22/fix-for-broken-time-machine-backups-under- snow-leopard.html) - downgrading to 7.4.1 of the Airport Extreme / Time Capsule firmware.
But still have the same Time Machine error!
On to http://forums.macosxhints.com/showthread.php?t=103919&highlight=TimeMachineError
and try-
"... suggesting would be something like renaming the existing TimeMachine file on your backup disk - e.g. add a date to the end of it.
And then go onto Time Machine preferences and set it up as if it were the first time you used it. (Renaming the file on the backup disk should make Time Machine think that you are starting fresh.)"
So, using Finder, I opened my Time Capsule and renamed "xxxxxx’s iMac_00224135e6fb.sparsebundle" as "091222xxxxxx’s iMac_00224135e6fb.sparsebundle091222"
And finally, this worked - I have my backups to 22 December and a complete backup as at today and hopefully for at least another 14 months!

pjh42 wrote:
G'day (from Queensland, Australia)
Not for the first time Time Machine has broken down - originally in September 08 (I just can't recall how I fixed it!!).
Now it has failed after 14 months of faultless performance.
There seems to be little help available, but searching for solutions finds plenty of problems.
On the contrary. At the top of this forum are four *User Contributed Tips,* including one on Troubleshooting that would have saved you a great deal of time.

Time Machine Error. Unable to complete backup. An error occurred while copy

I purchased my iMac 24" in February.
After I had set up the machine I configured an IceCube Firewire 300 GB (Seagate) Hard Drive as a backup volume and flicked the switch in Time Machine. All went as expected. I even restored my whole hard drive from the Time Machine volume about a month ago after I repartitioned the boot volume to set up Boot Camp. No problems.
About a week ago I purchased a 500GB WD HDD and set it up inside the IceCube enclosure (I remembered to make it the "Master" disk too!!). I partitioned it with Disk Utility with a GUID Mac OS X (Journaled) partition for my Leopard boot partition, and as MS-DOS FAT32 for my Boot Camp external partition. I used Carbon Copy Cloner to copy all the Windows files across from Boot Camp to the new FAT32 partition and set up Time Machine to make a backup of the Leopard boot partition.
After several hours Time Machine stopped with the error message above. ("Time Machine Error. Unable to complete backup. An error occurred while copying files to the backup").
I have spent days formatting the new WD drive, repairing permissions on the boot drive, excluding large files and cache files from the backup in Time Machine to no avail. Every time I get the same message. I even set up another 200GB firewire drive to see if it was anything to do with the enclosure of WD HDD. Same result!!
I have searched these forums for any ideas, and have done wide searches with Google but nothing has worked.
I can not understand why my Mac worked perfectly with Time Machine before I installed the new Western Digital Hard Drive.
What have I missed?

I keep getting the Time Machine backup error too, like many others. Was fine until just the other day, now, nothing. Although my husband's backs up just fine. I assume it's the 10.5.3 bug everyone else has. I've tried reselecting the drive, running the disk utility, shutting everything on and off... help!
Here's the console log- anyone know what this means?
Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Starting standard backup
Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Network mountpoint /Volumes/Library not owned by backupd... remounting
Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Network volume mounted at: /Volumes/Library-1
Jun 10 08:37:43 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Disk image /Volumes/Library-1/Tiffany Danko’s Computer (2)_001b63baf698.sparsebundle mounted at: /Volumes/Backup of Tiffany Danko’s Computer (2)
Jun 10 08:37:43 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Backing up to: /Volumes/Backup of Tiffany Danko’s Computer (2)/Backups.backupdb
Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Failed to create progress log file at path:/Volumes/Backup of Tiffany Danko’s Computer (2)/Backups.backupdb/Tiffany Danko's computer (2)/2008-06-09-065427.inProgress/.Backup.234797868.792920.log.
Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Event store UUIDs don't match for volume: Macintosh HD
Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Error: (-36) Creating directory 77B4FA27-3E65-4B81-897C-610DEE7BB187
Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Failed to make snapshot.
Jun 10 08:37:53 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Backup failed with error: 2
Jun 10 08:37:58 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Ejected Time Machine disk image.
Jun 10 08:37:59 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Ejected Time Machine network volume.

Is there a solution for Time Machine error?

I got an error in Time Machine saying backup had failed, a couple of days ago. Spent the next day or two trawling the web and found thousands of postings from people with the same error, but no solution.
(At least, some people had a solution - they were using PC-formatted hard drives.)
I've been using Time Machine for a few weeks, and it has only now taken a dislike to my external hard drive, which is connected by FireWire.
Is there a solution to this problem, or should I revert to using SuperDuper, which I was using successfully before?
I haven't put in lots of information about the apps I'm running, because this is a general query rather than a specific one. If there's a solution, I'll use it; otherwise I'll wipe the drive and go back to using SuperDuper.

OisinOg wrote:
Pondini - Thank you for your slightly hostile reply.
On the contrary. The statement was: +"found thousands of postings from people with the same error, but no solution."+ I don't know where you found thousands of posts -- there are many here, but certainly not thousands. If you're talking about, say, a Google search, if you actually look at them, many are duplicates, unrelated to your problem, or unrelated to Macs at all -- and there are a number of solutions that seem to have fixed many of the real ones.
The error message was the standard one: "Time Machine Error - Unable to complete backup. An error occurred while creating the backup directory."
There's most likely another, better message in your logs. Thus the suggestion about Time Machine Buddy. You can also use the Console app (in your Applications/Utilities folder). Click on Show Log List, then navigate in the sidebar to your system.log (or system.log.0.bz2, etc. for previous ones). You can filter for backupd to get the same TM messages as the widget, but I prefer to view the full log at the date/time in question, as messages from other concurrent processes may have a clue.
I've gone through the suggestions in some of the helpful replies to those thousands of postings, by wiping my drive, erasing it and reformatting it, first in two partitions using the GUID method in Disk Utility, then in a single partition. But Time Machine still doesn't want to back up to it.
Sounds a bit like a problem communicating with the drive. The logs may clarify that.
The hard drive of my computer is 250GB; the external drive is 300GB. Both are SATA drives; the external is connected by FireWire.
How full are they?
Thanks for your suggestion of downloading the Time Machine Buddy widget; I'll give it a last try tonight.
What is the difference between a SuperDuper clone and a Time Machine backup?
The initial backup of both copies almost everything on your HD, excluding only some caches, temp files, etc., although you can exclude other things. This takes quite a while, of course. Thereafter, only the items that changed are backed-up.
SuperDuper (and CarbonCopyCloner, which I use, and other, similar apps) are most often used to make bootable "clones" identical copies of your HD -- if your HD fails, you can boot and run from them immediately. With TM, once your HD is repaired/replaced, you restore your system to it from your TM backup.
Score one for the clones, but TM has it's advantages, too (which is why many of us run both).
First is, CCC and SD look at every file and folder on your HD to see what changed. This is quite time-consuming and CPU-intensive, so most of us run it once a day (or less often), usually automatically at, say, 3 am. TM, however, runs hourly, but uses an internal File System Event Log of changes, so it is far quicker and less intrusive. There are exceptions, but most users rarely even notice the backups unless they see the icon revolving. On my small system, for example, TM rarely runs over 30 seconds; CCC is at least 15 minutes.
Second, not only does TM keep previous versions of changed files, but it manages the space and backups for you. It keeps those hourly backups for 24 hours; except the first of the day becomes a daily backup which is kept for a month; one per week becomes a weekly backup that is kept for as long as there's space (it will fill the drive/partition). But it's smart enough, as it deletes the old weeklies, that it won't delete it's copy of anything that still exists on your HD.
There isn't room to have two 250GB sections on a 300GB drive. I suppose I could get another 250GB drive - I have an IDE enclosure somewhere - but I don't fancy the expense right now.
Your CCC or SD partition only needs to be as large as your HD, although in a pinch it only needs to be somewhat larger than what's actually used on your HD. If you don't have room for both on the one drive, an even better solution might be to get a pair of smaller portable HDs for CCC/SD. Use one daily for, say, a week, then take it to your safe deposit box, workplace, relative's house, etc. and start with the other. Now you're also protected against fire, flood, theft, direct lightning strike on your power lines, etc.

Time machine restore help

I've recently been having issues with my early 2008 black Macbook. I ran the apple HW diagnostics and determined it is a bad hard drive. I went out and bought a new 500GB SATA HD, and attempted to restore my system using a Time Machine backup. I booted into the Leopard Disc that came with my computer, formatted the drive, and ran the Time machine restore. Everything appeared to go fine (took about 2 hours, no error messages). However, after the machine rebooted and attempted to boot into OSX an error similar to this popped up. http://img149.imageshack.us/img149/7792/pict0017lo8.jpg
Any thoughts as to why this is happening? I don't really want to start over with a clean install, that's why I have Time Machine!
Other information:
My computer originally had Leopard, and was upgraded to Snow Leopard.
I have boot camp setup on my mac for Win 7. (I know this isn't backed up or restored as part of a time machine backup, which I'm O.K. with.)
Thanks in advance for all your help.

Any number of possibilities. First, did you prep the drive properly:
Extended Hard Drive Preparation
1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger, Leopard or Snow Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Any brand new drive should be setup per the above because they usually are configured for use on PCs rather than Macs.
Second, depends on how you went about the process of restoring your system. Select Mac Help from the Finder's Help menu and search for "time machine." Look for an article specifically about performing a full system restore. Also, see User Tips for Time Machine for help with TM problems. Also you can select Mac Help from the Finder's Help menu and search for "time machine" to locate articles on how to use TM. See also Mac 101- Time Machine.
What you saw was a kernel panic screen. Panics at startup may be indicative of a hardware problem. You might give this a try:
How to run hardware diagnostics for an Intel Mac
Boot from your original OS X Installer Disc One that came with your computer. After the chime press and hold down the "D" key until the diagnostic screen appears. Run the extended tests for a minimum of two or three hours. If any error messages appear note them down as you will need to report them to the service tech when you take the computer in for repair.
Some "common" error indicators:
SNS - sensor error
MEM - memory error
HDD - hard disk drive error
MOT - fan error
To assure the problem isn't with your backup you might consider installing OS X by itself. If all is OK, then you can complete the TM restore using Migration Assistant.

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?

HT201250 Time Machine Error

Just bought a new 1 TB external hard drive specifically for a Mac and time machine error: unable to complete backup. An error occurred while copying files to the backup volume. messages keeps appearing. Tried to restart and that didn't help. Please advise.

Hello, I don't use TM myself.
Have you looked through Pondini's extensive TM help site?
http://Pondini.org/TM/FAQ.html
http://pondini.org/TM/Troubleshooting.html
I can't imagine anything TMwise not covered.

Time Machine Error: An error occurred while creating the backup directory

Time Machine Error: Unable to complete backup. An error occured while creating the backup directory.
I back up to wirelessly to a Time Capsule. I get these errors often. I'll go for a few days with everything working and then encounter these errors. I've even completely erased the Time Capsule drive and started over. It'll work fine for a few days and then start the errors over again. Interestingly, when the errors occur, the Time Capsule drive can not be unmounted even if clicking the eject button. I am on 10.5.8 but it happened in 10.5.7 as well. I have another Mac that doesn't seem to have any issues with the same Time Capsule.
Here's a log - they all seem to fail with similar errors:
Starting standard backup
Backup destination alias resolved to path: /Volumes/AirPort Disk
Disk image /Volumes/AirPort Disk/Brittney’s Computer_0019e33d4fde.sparsebundle mounted at: /Volumes/Backup of Brittney’s Computer
Backing up to: /Volumes/Backup of Brittney’s Computer/Backups.backupdb
2009-08-27 13:52:48.465 FindSystemFiles[2955:713] Querying receipt database for system packages
2009-08-27 13:52:48.693 FindSystemFiles[2955:713] Using system path cache.
Failed to create progress log file at path:/Volumes/Backup of Brittney’s Computer/Backups.backupdb/Brittney’s Computer/2009-08-26-212437.inProgress/.Backup.273091970.250248.log.
Error: (-50) Creating directory 7CCE60DD-ADCC-4004-A0D9-3EC83D892372
Failed to make snapshot.
Backup failed with error: 2
Failed to eject volume /Volumes/Backup of Brittney’s Computer (FSVolumeRefNum: -114; status: -47; dissenting pid: 0)

Nancy H wrote:
I used it as it came, supposedly formatted for a mac.
It may or may not be right.
I'd be inclined to start over, per #5 in the Frequently Asked Questions *User Tip* at the top of this forum.
If that doesn't help, go on to #C10, etc., in the Troubleshooting Tip, as in the previous post.

Time Machine Error - Backup Requires 2,211,365.5 GB!

Hello - I have searched the posts and nothing seems to touch on this specifically - I have been using Time Machine successfully for months and this has only started to happen in the last few days.
I have a white Macbook, 10.5.6 with an upgraded 150GB hard drive. I do backups sporadically (once or twice a week), as I don't want to keep my Macbook connected to a hard drive and I find using the airdisk feature on my AEBS takes too long and slows down the network. This has been working fine for me for months, but now I get the following message:
Time Machine Error
This backup is too large for the backup volume. The backup requires 2211365.5 GB but only 125.5 GB are available.
I tried reformatting my disk (250GB hard drive) and the problem still arises. There are no external drives or anything connected to the Macbook at the time.
Can anyone help? I don't want to go out and buy a Hard Drive with a 3million GB capacity!
Thanks
Ian

ChunTzu wrote:
If TM is seeing a ridiculous amount of info to backup like that (2 million gigs is probably not a real number I am guessing) it probably means you have file structure problems that are causing TM to count a folder infinitely in some kind of loop... like maybe a file link to itself that kind of thing.
A disk check usually repairs these sorts of problems and should alleviate your issue.
I believe you are correct and I would add that this case might require stronger medicine such as DiskWarrior to repair the directory structure, if that it the issue.

Time Machine error- backup directory

Yet another person with the same error: Time Machine backup has been working just fine for about 2 months to a Time Capsule. Suddenly, all I get is "Time Machine Error. Unable to complete backup. An error occurred while creating the backup directory." No matter what I do, I get the same thing. I've done many of the things listed in other postings:
- turning time machine and laptop on and off (repeatedly!)
- clicking on the Change disk and re-choosing my Time Machine/capsule
- reinstalling the latest 10.5.3 update.
I don't know what else to do- I'd really rather not go nuclear and reinstall the whole dang computer. Help! Any other ideas (not cryptic, please, explain, for me and everyone else out there with this problem)?
Thanks

First make sure that the disk is still good. Use Disk Utility on it. Since I don't have a TC I'm not sure of the exact procedure. You may be able to do it over Ethernet.
If the top level directory checks out, then mount the sparseimage (fire up TM from the dock and then cancel out) and then use Disk Utility to Verify the disk image.
- gws

Time Machine Error - Help!

Similar Messages

Maybe you are looking for