Time Machine Error - 2nd Internal HD got unmounted when TM doing backup

Hi:
It has been going on for a couple months since and I had to turn TM off cause when TM starts to back up - it will unmount my 2nd internal 500G HD. If I exclude the 2nd HD then TM back up works fine.
My question is what should I change on the 2nd HD setting to prevent TM unmounting it - error "device removal!" will show up and then the 2nd HD disappear from desktop? I can't reformat the 2nd HD as there are tons of important files in it. Also TM would not let me backup the 2nd HD anyway.
HELP.

Hey - here is the error message from TM buddy
Starting standard backup
Backing up to: /Volumes/IOMEGA TIME MACHINE HDD/Backups.backupdb
Event store UUIDs don't match for volume: Val G5 HD2
Node requires deep traversal:/Volumes/Val G5 HD2 reason:kFSEDBEventFlagMustScanSubDirs|
No pre-backup thinning needed: 149.03 GB requested (including padding), 229.93 GB available
Error: (-36) SrcErr:YES Copying /Volumes/Val G5 HD2/iTunes Music/Podcasts/Amanpour (Video)/Human tsunami.m4v to (null)
Error: (-36) SrcErr:YES Copying /Volumes/Val G5 HD2/iTunes Music/Podcasts/Amanpour (Video)/Obama's world policy challenges.m4v to (null)
Error: (-36) SrcErr:YES Copying /Volumes/Val G5 HD2/iTunes Music/Podcasts/Amanpour (Video)/Reflecting on Nigeria's recent violence.m4v to (null)
Error: (-36) SrcErr:YES Copying (null) to (null)
Unable to rebuild path cache for source item. Partial source path:
Copied 2544 files (18.0 GB) from volume Val G5 HD2.
Copied 3047 files (18.0 GB) from volume Val G5 HD.
Error: (-2111) Unable to get a reference to /. Skipping.
No pre-backup thinning needed: 240.4 MB requested (including padding), 211.98 GB available
Unable to resolve path to source: Val G5 HD2
Copied 0 files (0 bytes) from volume Val G5 HD2.
Copy stage failed with error:2
Backup failed with error: 2

Similar Messages

HT3275 Time Machine error (109). Could not access backup disk image

I keep getting a Time Machine error message that says it can not access the backup disk image "……sparsebundle". I have had issue after issue with Time Machine. I have completely started over twice with setting up Time Capsule. Please help!

For informed suggestions, see #P2 in Pondini's excellent support document.....Using Time Machine with a Time Capsule
http://pondini.org/TM/Time_Capsule.html

Time machine error when backing up iMac with internal flash and sata internal drives.

will appear to be backing up and then as just about done, shows Time Machine Error message and ask you to
try again later, if problem persists, repair backup disk with disc utility. Neither solution works.

Bump for a monday, and hopeful for some replies.

Time Machine error -1, cannot access sparsebundle (but not a NAS or WD problem)

Hello, this is my first post here, so I'll try to make it a good one!
I've been wrestling with this problem ever since I bought my Core i7 iMac (SSD + 1TB HD) over a year ago. I have not gotten Time Machine to work during that whole time. Well, I got it to work backing up directly to my internal HD, but that was just a test; it's not what I want. So let me describe this in the most clear and consise way I can:
I want the Time Machine disk to be my Synology NAS. I've configured a share on it correctly. I have an older iMac running SnowLeopard backing up to the same share on the NAS with TimeMachine successfully. But, my iMac won't do it. Whether I create the sparsebundle manually, or I let TimeMachine create it, it always gives the same "error -1". I wrote a more detailed account of my symptoms here (my message is the reply), when I thought this was a NAS-specific issue.
New development: This is not a NAS issue. I found that out by trying an experiment:
First, I tried to back up my SSD using Time Machine to my internal 1TB disk - I selected the "1 TB Secondary Disk" as the Time Machine disk. I initiated the backup, and it worked fine, putting the time machine backup in the "Backups.backupsdb" directory structure at the root of the drive. I then turned off Time Machine and "removed" the 1TB as my backup disk.
Then, I created a sparsebundle at the root of the drive using this command:
hdiutil create -size 150g -fs HFS+J -volname "Time Machine" NAME_xxxxxxxxxxxx.sparsebundle
(where the "xxxxxxxxxxxx" is my ethernet MAC address). I then selected the "1 TB Secondary Disk" as the Time Machine disk again. Time Machine found my sparsebundle and started working with it... and got "error -1"! So even on a local drive, when Time Machine tries to use a sparsebundle for backing up, it still doesn't work.
Now, I have the console log entries that were written during the Time Machine backup attempt:
1/1/13 12:53:59.511 PM com.apple.backupd[4460]: Starting manual backup
1/1/13 12:54:00.780 PM com.apple.backupd[4460]: Renaming /Volumes/1 TB Secondary Disk/NAME_3c07540fdd8c.sparsebundle to /Volumes/1 TB Secondary Disk/iMac.sparsebundle
1/1/13 12:54:00.871 PM com.apple.backupd[4460]: detach: could not open /dev/disk4
1/1/13 12:54:01.260 PM com.apple.backupd[4460]: Resizing backup disk image from 161.06 GB to 999.76 GB
1/1/13 12:54:02.940 PM com.apple.backupd[4460]: Waiting 60 seconds and trying again.
1/1/13 12:55:03.378 PM com.apple.backupd[4460]: Resizing backup disk image from 161.06 GB to 999.76 GB
1/1/13 12:55:06.013 PM com.apple.backupd[4460]: Waiting 60 seconds and trying again.
1/1/13 12:56:06.619 PM com.apple.backupd[4460]: Resizing backup disk image from 161.06 GB to 999.76 GB
1/1/13 12:56:09.255 PM com.apple.backupd[4460]: Giving up after 3 retries.
1/1/13 12:56:19.263 PM com.apple.backupd[4460]: Backup failed with error: 21
1/1/13 12:56:19.265 PM com.apple.backupd[4460]: [SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
1/1/13 12:56:19.265 PM com.apple.backupd[4460]: Failed to eject volume (null) (FSVolumeRefNum: 0; status: -35; dissenting pid: -1)
1/1/13 12:56:19.265 PM com.apple.backupd[4460]: Failed to eject Time Machine disk image: /Volumes/1 TB Secondary Disk/iMac.sparsebundle
So, here I see it tries to resize the sparsebundle to the full volume size, and fails. I don't think I want it to do this resize, because I don't want it to fill up my whole NAS share. I searched and found this post, which specifies how to set the permissions in the sparsebundle such that it won't be resized. I followed those instructions with a new sparsebundle, and see the same problem... tries to resize, and fails.
I do not have Western Digital software installed and never have.
I've tried everything on this page.
It seems like the attempt to resize is corrupting the sparsebundle. Before starting the backup, I can mount the sparsebundle and manually copy files to it. After attempting the backup, I can mount the sparsebundle, but I cannot copy anything to it manually. Note that I can mount the sparsebundle that the MacBook Pro uses for Time Machine, and manually copy files to and from it (in other words, the correct SnowLeopard configuration does allow manual copying).
I have tried repairing the sparsebundle using the Disk Utility, which restores the ability to manually copy files to it, but Time Machine once again renders it unwriteable when it attempts to back up.
Anyone know of anything else I can try? Thank you so much!
Dan

Yeah, sorry about the broken link. I noticed that link wasn't working after I replied, then I edited my earlier reply. Also, yes, copying the files was just meant as a test; I created new clean sparsebundles for other tries.
Anyway, I'm not too worried about the resizing for now; first things first, let's just get Time Machine working with a sparsebundle at all.
I don't know how to make Time Machine create its own sparsebundle on my local drive; if there isn't a manually created sparsebundle at the root, it just puts everything in the "Backups.backupsdb" directory structure without a sparsebundle. However, it of course does create its own sparsebundle when I point it to my NAS share (as I understand it, Time Machine knows the NAS filesystem doesn't support everything it needs, so it creates the sparsebundle to emulate the correct filesystem). As I have always gotten the same "error -1" when using the NAS share as I did when using the local sparsebundle, I was assuming the same problem was happening in both cases... but now I've checked the console log after doing a backup attempt on the NAS share, and I see different stuff:
1/2/13 9:21:12.000 PM kernel[0]: AFP_VFS afpfs_mount: /Volumes/TM Backups, pid 9615
1/2/13 9:21:12.000 PM kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff8148d5b008 /Volumes/TM Backups (error = 0, retval = 0)
1/2/13 9:21:13.000 PM kernel[0]: AFP_VFS afpfs_unmount: /Volumes/TM Backups, flags 0, pid 9624
1/2/13 9:21:13.000 PM kernel[0]: AFP_VFS afpfs_unmount : We are the last mnt/sbmnt using volume /Volumes/TM Backups 0xffffff8148d5b008
1/2/13 9:21:13.000 PM kernel[0]: AFP_VFS afpfs_unmount : We are the last volume using socket /Volumes/TM Backups 0xffffff8148d5b008
1/2/13 9:21:49.647 PM com.apple.backupd[9623]: Starting manual backup
1/2/13 9:21:49.737 PM com.apple.backupd[9623]: Attempting to mount network destination URL: afp://[email protected]/TM%20Backups
1/2/13 9:22:00.060 PM com.apple.backupd[9623]: Mounted network destination at mount point: /Volumes/TM Backups using URL: afp://[email protected]/TM%20Backups
1/2/13 9:22:00.000 PM kernel[0]: AFP_VFS afpfs_mount: /Volumes/TM Backups, pid 9630
1/2/13 9:22:00.000 PM kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff8148ffb008 /Volumes/TM Backups (error = 0, retval = 0)
1/2/13 9:22:15.323 PM com.apple.backupd[9623]: Creating disk image /Volumes/TM Backups/iMac.sparsebundle
1/2/13 9:22:46.397 PM com.apple.backupd[9623]: Failed to hide extension on /Volumes/TM Backups/iMac.sparsebundle, error: Error Domain=NSCocoaErrorDomain Code=4 "The file “iMac.sparsebundle” doesn’t exist." UserInfo=0x7fe881407700 {NSURL=file://localhost/Volumes/TM%20Backups/iMac.sparsebundle/, NSFilePath=/Volumes/TM Backups/iMac.sparsebundle, NSUnderlyingError=0x7fe8814073c0 "The operation couldn’t be completed. No such file or directory"}.
1/2/13 9:23:10.209 PM com.apple.backupd[9623]: Failed to eject volume /Volumes/TM Backups (FSVolumeRefNum: -153; status: -47; dissenting pid: 0)
1/2/13 9:23:10.210 PM com.apple.backupd[9623]: Waiting 60 seconds and trying again.
1/2/13 9:24:10.241 PM com.apple.backupd[9623]: Network destination already mounted at: /Volumes/TM Backups
1/2/13 9:24:56.305 PM com.apple.backupd[9623]: Failed to eject volume /Volumes/TM Backups (FSVolumeRefNum: -153; status: -47; dissenting pid: 0)
1/2/13 9:24:56.305 PM com.apple.backupd[9623]: Waiting 60 seconds and trying again.
1/2/13 9:25:56.326 PM com.apple.backupd[9623]: Network destination already mounted at: /Volumes/TM Backups
1/2/13 9:26:40.171 PM com.apple.backupd[9623]: Failed to eject volume /Volumes/TM Backups (FSVolumeRefNum: -153; status: -47; dissenting pid: 0)
1/2/13 9:26:40.171 PM com.apple.backupd[9623]: Giving up after 3 retries.
1/2/13 9:26:50.177 PM com.apple.backupd[9623]: Backup failed with error: 21
1/2/13 9:26:50.178 PM com.apple.backupd[9623]: [SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
1/2/13 9:26:50.178 PM com.apple.backupd[9623]: Failed to eject volume (null) (FSVolumeRefNum: 0; status: -35; dissenting pid: -1)
1/2/13 9:26:50.178 PM com.apple.backupd[9623]: Failed to eject Time Machine disk image: /Volumes/TM Backups/iMac.sparsebundle
So... looking through this, it does some mounting, which all works fine, then it does a create sparsebundle, which appears to work fine, but then it tries to "hide extension", but it can't because it can't find the sparsebundle that it supposedly created. Then it tries three times to eject the NAS share ('TM Backups'), and fails, and gives up. At this time I get the "error -1" pop up on my monitor, and check the NAS share (using the disk utility on the NAS managment page), and sure enough there is the sparsebundle "iMac.sparsebundle". So why does it create it, but then not be able to use it?
Skiing tomorrow, must sleep now. :-)

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 error: The backup disk image could not be mounted

Time Machine worked OK for several months. Now I get this error every 10 minutes or so.
I unplugged Time Machine capsule and "Change Disk" in Time Machine options.
Nothing helps, I continue to get this error.
I cannot Enter Time Machine either. "Connecting to Server, Connecting to backup" does not work.
Help please because I will probably have to archive and reinstall Leopard. I need the backups,
Christine

Christ1ne,
Before you reformat the disk, consider these causes of this error.
*_"The Backup Disk Image Could Not Be Mounted" (Console - “Failed to mount disk image”)_*
First, it is important to distinguish this error message from another, similar Time Machine error that states “The backup volume could not be mounted”. This is important as the causes and cures for these two errors can be very different.
Consider each topic below separately. When one option does not resolve your issue, then move on the next one.
*Unmount the Backup Disk Image* (TC)
If, for some reason, you have manually mounted the Time Machine backup disk image (sparsebundle), or Time Machine failed to eject it after the previous backup, subsequent backups may fail. (Console - “Failed to mount disk image”… “Backup failed with error: 21”)
Eject the backup disk image (white drive icon) by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Click the drive icon on the desktop and select “Eject” from the contextual menu. Now try backing up again or launching Time Machine to view previous backups.
*“Disconnect All Users…”:*
If your Time Machine backup drive (“Backup of Users Computer”) is mounted on your desktop or in the Sidebar of the Finder window. then Time Machine may think the drive is already in use. Alternatively, if the Time Capsule hard disk has been recently accessed by a Windows machine, it may not have fully relinquished control. Do the following:
Open Airport Utility and select the Time Capsule on the left.
Click “Manual Setup”.
Select “Disks” at top of window.
Click “Disconnect All Users…” at bottom of window.
Close the Airport Utility.
Now try Backing up again.
One poster reported: “I got it resolved. Apparently it had to do with one of the files being open on the disk from the drive. I had browsed the disk with one of my windows boxes here and it must have left one of the folders "open". Anyway, I rebooted the TC and we are good to go now.”
*Proper Computer Name* #
Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
According to this article, [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
(0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
# Try removing the apostrophe from the disk images name (sparsebundle).
*A Stalled .inProgress Files:* #
It may be that the previous backup attempt was ungracefully interrupted leaving remains that Time Machine can’t deal with.
Stop any current backup attempt. Choose “Stop Backing Up” from the Time Machine menu.
Open the Time Machine Preferences and turn “OFF” Time Machine.
Open your Time Machine drive.
Open the folder labeled “Backups,backupdb”.
Now open the folder containing backups of the computer in question.
Are there any “.inProgress” files there. Delete them by dragging the file to the Trash. Or Ctrl-Click the file and select "Move to Trash" from the contextual menu. (Give this time as deleting a large file on an external disk can take a while.)
Turn Time Machine back “ON”. Now try backing up again.
NOTE: If the above procedure becomes impossible to perform, try accessing the disk image from another Mac. Some have discovered that attempting a repair from another computer succeeds where the original computer failed.
Let us know if any of the suggestions above helped to resolve your issue.
Cheers!

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, 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

Time Machine error: The backup disk image "/Volumes/----/----MacBook Pro.sparsebundle" is already in use and resource unavailable?

I have a MacBook Pro 13" 2010 model running Mountain Lion. I have always been able to use Time Machine with my Time Capsule. Just today I have been receiving the same error message whenever I would back up my computer:
I removed my name before "MacBook Pro". It takes a long time "Looking for backup disk..." first. The disk I put with the time capsule is called Huge Backup, and in Huge Backup there is my sparsebundle file called "----- MacBook Pro." When I open Finder, open my time capsule, and then open my sparse folder, it should mount a drive where I can see my computer's backups. That doesn't work. Then I get this message:
I once again removed my name before "MacBook Pro" but I can open my sister's sparsebundle who is running Mountain Lion on the same network and her backups work fine. I have researched this topic and have tried to repair the disk in Disk Utility, remount all the drives, remove the drive and restart the backups, and even restart my computer and the Time Capsule. Nothing worked. It just was working yesterday, but now I get this in the settings along with a caution symbol in my menubar:
Is there anything I could do to fix this? Reconnecting it in AirPort Utility (5 or 6) didn't work. Also, for some reason, the error renamed Huge Backup to Huge Backup-1 as you can see above and below in the messages. I downloaded the Time Machine Buddy widget and this is the error report I got. I replaced my names or private info with [-----]. By the way, the network is called NDR Network, and the Time Capsule is alled NDR Time Capsule. Here's the error I keep getting:
Starting manual backup
Attempting to mount network destination URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
Mounted network destination at mount point: /Volumes/Huge Backup using URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
Disk image already attached: /Volumes/Huge Backup/[-----]'s MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a483e6c0 {MessageParameters=(
Ejected Time Machine network volume.
Waiting 60 seconds and trying again.
Attempting to mount network destination URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
Mounted network destination at mount point: /Volumes/Huge Backup using URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
Disk image already attached: /Volumes/Huge Backup/Rohan's MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a343d430 {MessageParameters=(
Ejected Time Machine network volume.
Waiting 60 seconds and trying again.
Attempting to mount network destination URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
Mounted network destination at mount point: /Volumes/Huge Backup-1 using URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
Disk image already attached: /Volumes/Huge Backup-1/Rohan's MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a34410c0 {MessageParameters=(
Ejected Time Machine network volume.
Giving up after 3 retries.
Backup failed with error: 31
[SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
Failed to eject volume (null) (FSVolumeRefNum: 0; status: -35; dissenting pid: -1)
Failed to eject Time Machine disk image: /Volumes/Huge Backup-1/Rohan's MacBook Pro.sparsebundle
Please help!

I didn't remove all of my names, so just ignore that...

After clean install of Snow Leopard, Time Machine did not restore all files. When I try to restore these files I get "Not enough disk space" error. What do I need to do to get these important files back onto my Mac from my external hard drive??

After clean install of Snow Leopard, Time Machine did not restore all files. When I try to restore these files I get "Not enough disk space" error. What do I need to do to get these important files back onto my Mac from my external hard drive??

Janet.b wrote:
About 3 years old...pretty dated now I guess. Am thinking I may just need to have it upgraded by a Mac tech.
For what the Apple Store's charge you can buy almost buy a new computer.
Just for giggles I brought my old laptop in for a drive upgrade and asked, they wanted $600 for a drive that only cost $120 at the time and it was a slow 5,400 RPM drive. The new Mac's of a similar make were going for $1000.
I did the drive replacement myself, got a faster drive of better quality for $300 instead.
Then another time I asked for a RAM upgrade from 4GB to 8GB, they wanted to charge $400 + $35 for the labor.
The same RAM is on Crucial.com for $90 and all I need is a 00 micro phillips screwdriver.
So you see what's going on here.
I think what you should do, if your out of warranty/AppleCare, is to call up the local PC tech guy who also does Mac's and have them fix you right up.
They can offer more personalized care which you need. Clone your old drive to the new and everything.
With Apple they are overworked at the Genius Bar and just place roadblocks so you buy a new machine instead.
For instance, all new iMac's now have proprietary drive software installed on the hard drives for heat monitoring. So now the only choice a user has is to bring their iMac into a Apple Store for a very expensive drive upgrade, which a person then decides the money is better spent buying a new machine.

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: 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 Message. What to do?

Hello,
My G5 has 2 built-in drives, each 160Gb. I have reserved one of these drives exclusively for Time Machine. There is no issue regarding the connection of these drives since they are internal.
I started Time Machine 3 weeks ago, and it has been running successfully. With each backup, the available space has been declining. Tonight the available space reached the megabyte range - insufficient space for the next backup. It is my understanding that when new space is required by TM, old backup(s) are AUTOMATICALLY deleted.
Tonight when a backup starts, the window (System Preferences) shows that the backup is preparing. However, as soon as it starts copying to the TM drive, I receive the following error message:
"TIME MACHINE ERROR
Unable to complete backup. An error occurred while copying files to the backup volume."
No further information is provided for diagnosing the problem. I have no idea about the cause or what to do.
Can anyone identify the problem and a workout? I would appreciate some help. Thank you. Dale

Hello,
I'm back on this thread after having been absent for several weeks. I hope that the original helpers are still subscribed to this issue. I continue to get the message: "Time Machine Error . . . Unable to complete backup. An error occurred while copying files to the backup volume."
Below is the system.log file pertaining to backupd. I am not a technician, so I cannot understand the entries. Can someone help, please? Thank you, Dale
Feb 20 19:23:29 sherborn-g5 /System/Library/CoreServices/backupd[335]: Backup requested by automatic scheduler
Feb 20 19:23:29 sherborn-g5 /System/Library/CoreServices/backupd[335]: Starting standard backup
Feb 20 19:23:36 sherborn-g5 /System/Library/CoreServices/backupd[335]: Backing up to: /Volumes/Time Mach 160Gb HD/Backups.backupdb
Feb 20 19:23:37 sherborn-g5 /System/Library/CoreServices/backupd[335]: Event store UUIDs don't match for volume Leopard HD
Feb 20 19:23:37 sherborn-g5 /System/Library/CoreServices/backupd[335]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
Feb 20 19:27:47 sherborn-g5 /System/Library/CoreServices/backupd[335]: No pre-backup thinning needed: 10.18 GB requested (including padding), 14.37 GB available
Feb 20 19:27:52 sherborn-g5 /System/Library/CoreServices/backupd[335]: MDBackupIndexFile returned -12 for: /Library/Application Support/5221530, /Volumes/Time Mach 160Gb HD/Backups.backupdb/Sherborn G5/2008-01-25-202510.inProgress/0FA23087-5ECE-44FB-8C5D-C089622A374E/Leopard HD/Library/Application Support/5221530
Feb 20 19:27:52 sherborn-g5 /System/Library/CoreServices/backupd[335]: Aborting backup because MDBackupIndexFile failed
Feb 20 19:27:52 sherborn-g5 /System/Library/CoreServices/backupd[335]: Canceling backup.
Feb 20 19:27:54 sherborn-g5 /System/Library/CoreServices/backupd[335]: Copied 2 files (18 KB) from volume Leopard HD.
Feb 20 19:27:54 sherborn-g5 /System/Library/CoreServices/backupd[335]: Copy stage failed with error:11
Feb 20 19:27:55 sherborn-g5 /System/Library/CoreServices/backupd[335]: Backup failed with error: 11

Time Machine Error. Backup is too large for the backup disk. Backup requires 289.28 GB but only 177.01 GB are available.

My Mac has not been backing up for some time. Tried Apple Support, but couldn't figure out problem.
Receive the following error...
Time Machine Error
This backup is too large for the backup disk. The backup requires 289.28 GB but only 177.03 GB are available.

See #C4 in Time Machine - Troubleshooting.
If that doesn't clarify the situation, post back with:
How much data is on your internal HD (and any others being backed-up)?
How large is your Time Capsule?
Is there anything else on the TC besides these backups? If so, what and how large?

Time Machine error: backup disk image could not be created

Iet up my new time capsule day and it's working great. Now that I've got everything sorted out, I'm ready to do the initial time machine back up on it. I went into preferences, changed the backup location to my TC and clicked 'back up now'. Very quickly I get a message that the backup failed: "Time Machine Error - The backup disk image could not be created".
I've searched the apple support area but haven't been able to figure this one out. Can anyone help, please? This is an initial backup. (FYI, it worked great on my old external drive.)
Many thanks

I had the same problem. I installed my Time Capsule, fired up Time Machine and got an error that said "The backup is too large for the backup volume. The backup requires 436.8 GB but only 182.2GB are available."
Coincidently, these are the same sizes as the space used and the space available on my iMac's drive.
I looked in /Volumes and saw that the sparsebundle was being created on the local disk and not on the main disk. Trying to backup again gave me the "Time Machine error: backup disk image could not be created." message.
I poked around the forums, and found a post about the machine name setting in sharing. I decided to give it a look, and lo and behold, I did not have a machine name. So I gave my box a name, kicked off Time Machine again, and it worked.

Time Machine Error - 2nd Internal HD got unmounted when TM doing backup

Similar Messages

Maybe you are looking for