Time Machine fails with "error while linking files on the backup volume"
One of my drives was nearly full. I moved some folders from that drive to one that had more space.
The next TM backup failed with "error while linking files on the backup volume". A full backup is about 620 GB, although this backup shouldn't have been a complete one. There was 570+ GB free on the drive.
A Disk Verify reported "Drive appears to be okay." Earlier TM backups appeared to be fine (at least accessible). I swapped the TM drive for another, initialized it, and TM used that drive with no complaints.
What does the message mean?
Thanks,
harv47
Pondini wrote:
harv47 wrote:
The Time Machine Buddy widget shows no messages. None of the buttons do anything.
What am I doing wrong?
See #A1 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
Your user account may not have permission to see the logs.
The sentence beginning "If the message area is blank ..." shows how to figure out if that's the problem, and how to fix it.
Post back if it's not clear, or doesn't work.
The Tip had the answer. It was permissions.
What follow are the messages for the last unsuccessful TM backup (on v.3), followed by
the successful TM backup on the replacement drive (v.1). The line
"Copied 11 files (0 bytes) from volume Bay 3 HPFS+." was odd.
Starting standard backup
Backing up to: /Volumes/Time Machine v.3/Backups.backupdb
Event store UUIDs don't match for volume: Bay 3 HPFS+
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/Volumes/Bay 3 HPFS+ reason:kFSEDBEventFlagMustScanSubDirs|
Node requires deep traversal:/ reason:kFSEDBEventFlagMustSc
(Finished May 4, 2010 9:31:21 AM-- Status unknown)
Starting standard backup
Backing up to: /Volumes/TimeMachine v.1/Backups.backupdb
Event store UUIDs don't match for volume: Bay 3 HPFS+
Event store UUIDs don't match for volume: Bay 2 HPFS+
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 169.1 GB excluded items size: 0 bytes for volume Bay 3 HPFS+
Backup content size: 305.5 GB excluded items size: 0 bytes for volume Bay 2 HPFS+
Backup content size: 145.7 GB excluded items size: 7.5 MB for volume Macintosh HD
No pre-backup thinning needed: 744.36 GB requested (including padding), 931.15 GB available
Waiting for index to be ready (909 > 0)
Copied 1951 files (169.0 GB) from volume Bay 3 HPFS+.
Copied 4999 files (474.3 GB) from volume Bay 2 HPFS+.
Copied 410304 files (612.4 GB) from volume Macintosh HD.
No pre-backup thinning needed: 712.2 MB requested (including padding), 315.09 GB available
Copied 11 files (0 bytes) from volume Bay 3 HPFS+.
Copied 20 files (1.1 GB) from volume Bay 2 HPFS+.
Copied 1103 files (1.1 GB) from volume Macintosh HD.
Starting post-backup thinning
No post-back up thinning needed: no expired backups exist
Backup completed successfully.
(Finished May 4, 2010 2:38:17 PM)
I hope this is useful. Thanks for your help.
harv47
Similar Messages
-
TM Error. An error occurred while linking files on the backup volume
I have a 1TB Time Capsule. It's been working great for over a month. I'm now receiving an error.
Time Machine Error
Unable to complete backup. An error occurred while linking files on the backup volume.
I don't know what has happened to cause this error. Does anyone know what has happened and how to fix this? The first time I received this error was when it showed under Available it had over 500 GB and was backing up 89.1 GB. Then the error. The backup scheduled time came up and TM started to backup again. Again with the error. The next time it backed up I made a note of the figures it showed. It starts the backup process "Preparing" and shows under Available 389.1 GB of 929.5 GB. Then Preparing shows that it's backing up, 13.5 GB. Then I get the error pop up. I check Time Machine and under Available it shows 370.3 GB of 929.5 GB. The scheduled time came up again. Available shows 370.3 GB of 929.5 GB and that it's backing up 18.9 GB. I'm trying to see if there is a pattern, for instance 389.1 GB - 370.3 GB = 18.8 GB. It's not 18.9 GB, but it's close. I'm wondering if there is a point which causes the backup to fail and figure out if this can be fixed. I'm stumped. The backups keep getting an error but the Available amount keeps getting lower. Again, any help would be appreciated. Maybe you see something I don't. Thank you.I forgot to state this in my post; what I noticed beside "Latest Backup", is that it states "Failed ! (! is in a red circle)". (So why does the "Available" amount keep going down? Where is the disk storage space going if it's not backing up?). It started the backup again, it initializes "Latest Backup" by showing a blank. I was curious what it showed when I went into Enter Time Machine. I guess the last good backup was Sunday July 27, 2008 11:21 PM. That's what it shows prior to the NOW selection on the right. The Oldest Backup is June 19, 2008. I thought this might be useful to note.
I thought it would be a good idea to see what Time Machine is doing and record the steps. I know it will involve time and patience, but hopefully I'll find out something. It might be of use to someone.
- It's backing up again and it gets to the point showing that it backed up 18.8 GB of 18.9 GB and stays there for 20 minutes or so.
- Then it shows 18.9 GB of 18.9 GB, and stays at that point for a while.
- Available shows 351.5 GB of 929.5 GB.
- The Failed ! comes up again in Latest Backup. and backup stops.
- Again it looks like the disk storage is used up. (So the questions would be; 1. If the backup failed, where is the space going if the backup failed? 2. How can I get back what should be available and have it show the correct available amount?
It came up to the time it backs up again. It shows that the backup amount will be 18.9 GB. I turned Time Machine OFF. It looks like it will do the same thing. Does anyone know what is happening and what needs to be done to correct this and get my available space back with it recording the correct available amount (xxx.x GB of 929.5 GB) -
"an error occurred while linking files on the backup volume"
Was backing up both the computer and an external Seagate drive to a second external drive (Seagate II) via Time Machine. The Seagate failed, and we switched it with a third Seagate drive, then restored from backup to Seagate III.
Immediately after, I started receiving the message "Backup Failed" followed by the message listed in the subject line.
I could try removing the old backup and starting fresh, or reformatting the Seagate II, but that makes me nervous, since this is our only backup. Any advice?
Our total data is about 280 GB, currently using 520 GB on the Maxtor.I just got the same error doing basically the same thing: backing up an external LaCie firewire drive to another LaCie firewire drive via Time Machine. Both drives are formatted HFS+. The first LaCie has my active home directory on it, and was freshly reformatted just prior to copying my home directory over from the internal drive a couple of hours ago.
Mac OS X 10.5.2 (9C31) -
More from the Time Machine Buddy: "Node requires deep traversal:/Volumes/Data" and "reason: kFSEDBEventFlagMustScanSibDirs"
I am using a Mac G5 with Leopard. My LaCie data drive failed and I replaced it with a WD MyPassport drive, at which time the failed backups began. The recent file updates do appear in Time Machine, but it appears to back up everything since the last completed backup.Hi Norm,
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
(Repair both Drives)
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.) -
On 11/1/2011, Time Machine (TM) terminated with an error message I did not record. I noted that the drive was full and decided to do a separate complete bootable system backup using Carbon Copy Clone (CCC), before clearing the TM volume and trying to start it over clean. Part way through the full system backup CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". That was about the time that TM malfunctioned, so I assumed they were related. After starting CCC over a couple of times, and getting the same error message, I let it go through to completion of the backup, which took three or four hours. I then ran tests using Disk Utility and verified that there was nothing physically wrong with both the internal hard drive and the TM volume. I also erased and reformatted the TM volume. However, every time I started Time Machine, it would record a few GB and terminate with "Unable to complete backup. An error occurred while copying files to the backup volume". I restarted the computer with no change in results. Note that prior to starting the CCC backup, I "Repaired Permissions", "zapped the PRAM" and "re-set the SMC", hoping to have a clean bootable system on the backup. I ran Techtool and no problems were found.
I'm running this on an Intel iMac under 10.5.8 and recording to a 500GB My Passport drive. My hard drive is only about half full at 246 GB. My assessment is that something happened at 16-28-16 on 11/1/2001 to screwup the Backup Directory in the file at "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". My question is, how do I fix it?
I had just completed writing everything above here, explaining the problems I had been encountering for the past 24 hours. I had the Time Machine window standing open on the desktop where I could see it, having recentlycleared it after the last termination. As I was proofing what I had written, I looked at the window and noted that the clock had started a new run for a full back up, since all prior efforts had failed and the TM volume was empty. As I watched and waited for it to fail again, as it had been doing at about 13 GB, it kept going and going until it just finished a complete backup, about 4.5 hours later, with my having done nothing. Now my question would have to be - what could possiibly have happened to make it perform this way? It will be interesting to see if it continue to operate normally, or if the problem will return, in a later backup run.jcm21 wrote:
CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16"
You should not keep those files for long, and probably shouldn't back them up (if you need them at all -- since you do regular backups, I'm doubtful just how worthwhile that feature is).
"Unable to complete backup. An error occurred while copying files to the backup volume".
One of Apple's maddeningly incomplete messages. Most likely, there's a problem with a file (quite possibly the one CCC didn't like). See #C3 in Time Machine - Troubleshooting for details and instructions on finding and fixing it.
If you continue running the Directory Protection app, be sure to exclude your Time Machine drive from it (as it will just take up lots of room, and won't help repair your backups if there's a problem); and exclude the folders it creates from being backed-up by Time Machine (as they'll create large backups, and you probably can't use the backed-up folders anyway), per #10 in Time Machine - Frequently Asked Questions. -
My time machine always stops at some point... It always shows this message: "Time Machine Error. Unable to complete backup. An error occurred while copying files to the backup volume. I have tried everything and even did time machine in safe boot as told by an apple suppoprt advisor. still the same error after 16gb
If you have more than one user account, these instructions must be carried out as an administrator.
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.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to a failed backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showning, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting. -
Keep getting this message when trying to back up iMac to time Machine: Unable to complete backup. An error occurred while copying files to the backup volume. tried everything.
Pondini's Time Machine FAQ 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.
Time Machine- Troubleshooting backup issues -
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? -
An error occurred while copying files to the backup volume.
Hi,
after weeks of flawless operation,TimeMachine reports the following problem:
Oct 12 10:08:21 MacBook /System/Library/CoreServices/backupd[2429]: Starting standard backup
Oct 12 10:08:21 MacBook /System/Library/CoreServices/backupd[2429]: Network volume mounted at: /Volumes/timemachine
Oct 12 10:08:34 MacBook /System/Library/CoreServices/backupd[2429]: Disk image /Volumes/timemachine/MacBook_001f5be6da97.sparsebundle mounted at: /Volumes/Backup of MacBookPro
Oct 12 10:08:34 MacBook /System/Library/CoreServices/backupd[2429]: Backing up to: /Volumes/Backup of MacBookPro/Backups.backupdb
Oct 12 10:08:34 MacBook com.apple.backupd[2429]: 2008-10-12 10:08:34.826 FindSystemFiles[2441:713] Querying receipt database for system packages
Oct 12 10:08:35 MacBook com.apple.backupd[2429]: 2008-10-12 10:08:35.113 FindSystemFiles[2441:713] Using system path cache.
Oct 12 10:08:45 MacBook /System/Library/CoreServices/backupd[2429]: No pre-backup thinning needed: 100.0 MB requested (including padding), 162.38 GB available
Oct 12 10:08:45 MacBook /System/Library/CoreServices/backupd[2429]: Waiting for index to be ready (906 > 0)
Oct 12 10:09:02 MacBook /System/Library/CoreServices/backupd[2429]: Indexing a file failed. Returned -1136 for: /Library/Preferences/SystemConfiguration/preferences.plist, /Volumes/Backup of MacBookPro/Backups.backupdb/MacBook/2008-10-12-100839.inProgress/A38E496A-EC40- 4788-A648-D954937F694F/MacBook Pro HD/Library/Preferences/SystemConfiguration/preferences.plist
Oct 12 10:09:02 MacBook /System/Library/CoreServices/backupd[2429]: Aborting backup because indexing a file failed.
Oct 12 10:09:02 MacBook /System/Library/CoreServices/backupd[2429]: Stopping backup.
Oct 12 10:09:02 MacBook /System/Library/CoreServices/backupd[2429]: Copied 60 files (11 KB) from volume MacBook Pro HD.
Oct 12 10:09:02 MacBook /System/Library/CoreServices/backupd[2429]: Copy stage failed with error:11
Oct 12 10:09:08 MacBook /System/Library/CoreServices/backupd[2429]: Backup failed with error: 11
Oct 12 10:09:10 MacBook /System/Library/CoreServices/backupd[2429]: Ejected Time Machine disk image.
Oct 12 10:09:11 MacBook /System/Library/CoreServices/backupd[2429]: Ejected Time Machine network volume.
This failure might have been caused by putting my MacBook to sleep during the backup?
Forcing other backups results in a slightly different logs, like:
Oct 14 13:58:09 MacBook /System/Library/CoreServices/backupd[1395]: Starting standard backup
Oct 14 13:58:09 MacBook /System/Library/CoreServices/backupd[1395]: Network volume mounted at: /Volumes/timemachine
Oct 14 13:58:24 MacBook /System/Library/CoreServices/backupd[1395]: Disk image /Volumes/timemachine/MacBook_001f5be6da97.sparsebundle mounted at: /Volumes/Backup of MacBookPro
Oct 14 13:58:24 MacBook /System/Library/CoreServices/backupd[1395]: Backing up to: /Volumes/Backup of MacBookPro/Backups.backupdb
Oct 14 13:58:24 MacBook com.apple.backupd[1395]: 2008-10-14 13:58:24.853 FindSystemFiles[1418:713] Querying receipt database for system packages
Oct 14 13:58:25 MacBook com.apple.backupd[1395]: 2008-10-14 13:58:25.129 FindSystemFiles[1418:713] Using system path cache.
Oct 14 13:58:29 MacBook /System/Library/CoreServices/backupd[1395]: System files exclusion changed.
Oct 14 13:58:39 MacBook /System/Library/CoreServices/backupd[1395]: No pre-backup thinning needed: 100.0 MB requested (including padding), 162.38 GB available
Oct 14 13:58:39 MacBook /System/Library/CoreServices/backupd[1395]: Waiting for index to be ready (906 > 0)
Oct 14 13:58:48 MacBook /System/Library/CoreServices/backupd[1395]: Indexing a file failed. Returned -1136 for: /Library/Application Support/Apple/ParentalControls, /Volumes/Backup of MacBookPro/Backups.backupdb/MacBook/2008-10-14-130636.inProgress/AB496B63-8AF7- 43B1-A817-7E5539814705/MacBook Pro HD/Library/Application Support/Apple/ParentalControls
Oct 14 13:58:48 MacBook /System/Library/CoreServices/backupd[1395]: Aborting backup because indexing a file failed.
Oct 14 13:58:48 MacBook /System/Library/CoreServices/backupd[1395]: Stopping backup.
Oct 14 13:58:48 MacBook /System/Library/CoreServices/backupd[1395]: Copied 29 files (0 bytes) from volume MacBook Pro HD.
Oct 14 13:58:48 MacBook /System/Library/CoreServices/backupd[1395]: Copy stage failed with error:11
Oct 14 13:58:54 MacBook /System/Library/CoreServices/backupd[1395]: Backup failed with error: 11
Oct 14 13:58:56 MacBook /System/Library/CoreServices/backupd[1395]: Ejected Time Machine disk image.
Oct 14 13:58:59 MacBook /System/Library/CoreServices/backupd[1395]: Ejected Time Machine network volume.
Is this problem known? I couldn't find any thread describing exactly this problem. Thanks.3flyingdog,
Spotlight is having trouble indexing what Time Machine wants to backup. The problem may be the source files on your Mac as opposed to any actual Time Machine problems.
First, use Disk Utility to repair permission on your Macs internal hard disk. Then try backing up again.
Next, failing that, boot from your Macs original install DVDs and go to the Utilities menu and launch Disk Utility and "Verify" your Macs internal hard disk. If problems are found "Repair" them. Then try backing up again.
Otherwise, use Disk Utility on the external backup drive and see if that needs repair.
Cheers! -
"Unable to complete backup. An error occurred while copying files to the backup volume."
I get this message when I try to use time machine to backup my files to an external disk. I tried the restart route, and still same problem. Anyone have any ideas?
Actually this is what is listed after "Starting standard backup". I editted out personal names.
Apr 7 09:59:20-macbook /System/Library/CoreServices/backupd[434]: Starting standard backup
Apr 7 09:59:20 s-macbook /System/Library/CoreServices/backupd[434]: Backing up to: /Volumes/Untitled 1/Backups.backupdb
Apr 7 09:59:20 -macbook /System/Library/CoreServices/backupd[434]: Ownership is disabled on the backup destination volume. Enabling.
Apr 7 09:59:21-macbook /System/Library/CoreServices/backupd[434]: Event store UUIDs don't match for volume: Macintosh HD
Apr 7 09:59:21
-macbook /System/Library/CoreServices/backupd[434]: Backup content size: 142.6 GB excluded items size: 1.0 MB for volume Macintosh HD
Apr 7 09:59:21 -macbook /System/Library/CoreServices/backupd[434]: No pre-backup thinning needed: 171.08 GB requested (including padding), 930.96 GB available
Apr 7 09:59:21 -macbook /System/Library/CoreServices/backupd[434]: Waiting for index to be ready (909 > 0)
Apr 7 10:48:08 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Extensions/zfs.readonly.kext/Contents/MacOS/zfs.readonly to (null)
Apr 7 10:54:31 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/cp949.enc to (null)
Apr 7 10:55:11 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/euc-kr.enc to (null)
Apr 7 10:56:18 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/gb12345.enc to (null)
Apr 7 10:57:28 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/iso8859-13.enc to (null)
Apr 7 10:58:08 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/iso8859-15.enc to (null)
Apr 7 10:59:16 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/iso8859-2.enc to (null)
Apr 7 11:00:23 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/iso8859-3.enc to (null)
Apr 7 11:01:05 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/iso8859-5.enc to (null)
Apr 7 11:02:12 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/iso8859-6.enc to (null)
Apr 7 11:02:52 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/iso8859-7.enc to (null)
Apr 7 11:03:32 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/iso8859-8.enc to (null)
Apr 7 11:04:39 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/iso8859-9.enc to (null)
Apr 7 11:05:19 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/jis0201.enc to (null)
Apr 7 11:06:27 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/jis0208.enc to (null)
Apr 7 11:07:08
-macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/jis0212.enc to (null)
Apr 7 11:07:48 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/koi8-r.enc to (null)
Apr 7 11:08:57 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/ksc5601.enc to (null)
Apr 7 11:09:40 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/macJapan.enc to (null)
Apr 7 11:10:49 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/macTurkish.enc to (null)
Apr 7 11:11:57 -macbook /System/Library/CoreServices/backupd[434]: Stopping backup.
Apr 7 11:11:57 -macbook /System/Library/CoreServices/backupd[434]: Error: (-36) SrcErr:YES Copying /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts/encodin g/macUkraine.enc to (null)
Apr 7 11:11:57 -macbook /System/Library/CoreServices/backupd[434]: Copied 104132 files (32.6 GB) from volume Macintosh HD.
Apr 7 11:11:57 -macbook /System/Library/CoreServices/backupd[434]: Copy stage failed with error:11
Apr 7 11:12:03 -macbook /System/Library/CoreServices/backupd[434]: Backup failed with error: 11 -
It won't give me any more details, how do i find out where the problem is?
I've been doing more research on this, i downloaded the time machine buddy and this is what i got.
Starting standard backup
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
I'm not seeing info on this error anywhere. -
My Time Machine backup is repeatedly failing -- instead I receive a message saying it's unable to complete backup because an error has occured. The only "Help" advice is to restart the computer and try to back up again, but that did not solve the problem. Help, please?
Restart the whole network.. not just the computer.. restart in correct order with everything off.
modem
TC or router
clients
2min gap.
If you still have trouble, give us the whole network layout.. what broadband? what modem? any other router? are you using wireless? what mode is the TC in?
I am assuming you are using a time capsule. -
Time Machine Erroroccured while copying files to the backup volume.
Time Machine Error
Unable to complete backup. An errorWhile I am glad this worked for you, I tried this multiple times and my problem remains.
I think the concept of the timer machine is great, but backup methods that aren't reliable don't do much for me. I have a folder called "Precious" that I drag stuff into and I keep a copy of that folder on an external mirrored drive attached via firewire 800. I am sad to have to manage my files this way in 2009 but being responsible for your own data is and always has been the bottom line.
My Mac Book Pro just died after I updated to 10.5.6. It no longer boots, and AppleCare has asked me to fedex my notebook to them. They have warned me that they may wipe or replace my drive. Because of the failure of time machine, all the critical notes on my desktop are not backed up, and I have lost data I really needed.
You would think by 2009 there would be some kind of usable backup technology to help us safeguard our day to day data. Please Apple, do something about this.
Even with time machine, it is not clear to me how to restore a working operating system if something goes terribly wrong with Leopard. In the DOS days, programs and their data were stored in a directory and if you backed up that directory, you had your software and your data for later, minus of cource config.sys and autoexec.bat mods. These days with the software and data splattered all over in various directories, it is difficult (for me impossible) to assure you have everything you need to get back to where you were should something happen. I am tired of losing my data periodically when the OS tanks and I have to reload. Files I have created or downloaded I can do something about, but software is troublesome. I have multiple application programs that enforce install counts and will not reload more than two times. I am tired of begging vendors to reset my counts, and in the case of WordSearch (bible software), they refused and I lost significant time and money. -
HT3275 "Unable to complete backup. An error occurred while copying files to the backup volume."
I'm running Mountain Lion on a Mac Pro with Time Machine backing up to an exterior volume composed of four 3TB drives. System and TM have been working fine until now. Disk Utility reports the backup drive is fine. I've restarted and run TM again and keep having the same problem. I recently swapped out one of my internal drives for a larger drive, which is working fine but that is when TM started acting up. Any suggestions?
http://pondini.org/TM/B5.html
Pondini's site was out of action but back up now.
A new internal drive has a new UUID.. and should be treated by TM as a new computer. But you can inherit the old backup.. if you have restored to the drive then it hopefully will work but as you say take many hours.
I think it is better to start over.. but up to you. -
I have tried reset, worked last week.
But today got the same message and does not work yet, even with restart.
Please helpIs this Lion or Mountain Lion (ML)?
We were hoping the new OS would fix the issues with ML.. but they got worse.
Read C12, C17 and a brief scan over the rest.
http://pondini.org/TM/Troubleshooting.html
If you upgrade installed ML I would expect issues to abound.
Maybe you are looking for
-
I lost the ability to use wifi after the 8.02 update. Is there a way to fix this? I've already tried resetting network. Turned the phone off and on. Nothing is working and now I have to run on just data.
-
Cannot connect to EM on ODD guest from Windows host
Hello, I cannot connect to the Enterprise Manager in my guest VM from my host. From a IE v8.0 browser, the recommended link https://192.168.56.101:1158/em fails to connect. I installed Oracle VM VirtualBox 4.0.4 on a Windows 7 laptop and imported the
-
Problem when making new connection with user "sys"
Hi, I'm having trouble on making new connection with user sys against local 10g installation, the password is correct and I've tried making new connection with other users which is fine. when I click "test" or "connect", the error msg is strange like
-
Why are ACR PSD files 10-20 percent larger than the same file resaved in PSD?
Why are ACR > PSD files 10-20 percent larger than the same file resaved in PSD? I posted this many years ago and never found an answer. Now that my drives fill up quicker, I thought I might chase this question a little bit further. Same .CR2 saved wi
-
Airport Extreme timeout on MacBook Pro 15
My Airport Extreme suddenly can't be accessed from my Mac Book Pro 5.1 I use 10.5.7 and have reset factory settings on the Extreme from my Ethernet wired iMac, plus Airport is useable by the other Mac at home via Airport. So the hardware/firmware Air