Error 36 with time machine

When importing Aperture Library from time machine, error 36 appears, and only part of the library copies to my computer. How can I get around this?

Are you trying to restore from or to a disk, that is not formatted Mac OS X Extended journaled, formatted MS-DOS (FAT)? Then you may encounter "error 36", when transferring files with Time Machine due to capitalization errors.
See Pondini's FAQ: TM won't restore some files: names / capitalization in http://pondini.org/TM/Troubleshooting.html
Regards
Léonie

Similar Messages

-6584 error with time machine

I just re-installed OSX Lion from scratch. As instructed by a person from the Genius bar, I made sure to back everything up with time machine before doing this. I didn't automatically rebuild from time machine as I was having problems with the computer that I didn't want to import. There are things in time machine that I need, however, and I do want to import them from time machine.
When I try to "enter" time machine I get a -6584 error. I have searched Mac support for this error code and get no results. The sparse bundle is intact, as I can open it from another machine. When I try to open it from the machine I have installed Lion on, I get the message "Resource temporarily unavailable."
The Time Capsule I am accessing is a brand new Time Capsule.
Can someone help me solve this problem???
Thanks,
--Kenoli

stevenfromsa wrote:
Im having exactly the same issues.
Really? You're getting a -6584 error?
If so, try Repairing your backups, per #A5 in Time Machine - Troubleshooting
Ive also had problems with the Time Machine filling up unreasonably quickly. It seems to be backing up the same files over and over again!
See #D4 in the same article.

Errors with Time Machine (not completing backup, and needing to erase the ".inProgress" package)

I have in a previous discussion been talking about errors with my Time Machine backup. The errors were with a problem with Indexing a file, it fails and stops the whole backup. Each time it attemps another backup, it fills my ".inProgress" package with a (nearly) whole backup, filling my Time Machine hard drive, and thus errasing my previous good backups. The error occurs after about 95% completion.
In my last post of a similar disscussion, the problem was indexing the Preference Pane files and this caused the whole backup to fail. This was my last post there: (below in some additional info of my situation)
I did exclude the MobileMe.prefPane. And I got:
12/16/11 9:24:50.468 PM com.apple.backupd: Starting standard backup
12/16/11 9:24:50.556 PM com.apple.backupd: Backing up to: /Volumes/3 TB GoFlex Drive/Backups.backupdb
12/16/11 9:25:14.418 PM com.apple.backupd: Waiting for index to be ready (101)
12/16/11 9:27:02.366 PM com.apple.backupd: Deep event scan at path:/ reason:must scan subdirs|
12/16/11 9:27:02.366 PM com.apple.backupd: Finished scan
12/16/11 9:33:37.119 PM com.apple.backupd: Deep event scan at path:/Volumes/Mac OS Lion GM reason:must scan subdirs|
12/16/11 9:33:37.119 PM com.apple.backupd: Finished scan
12/16/11 9:36:15.650 PM com.apple.backupd: 758.92 GB required (including padding), 830.32 GB available
12/16/11 10:25:14.873 PM com.apple.backupd: Copied 22.8 GB of 630.5 GB, 782749 of 2357620 items
12/16/11 11:25:15.335 PM com.apple.backupd: Copied 86.6 GB of 630.5 GB, 1167675 of 2357620 items
12/17/11 12:25:16.227 AM com.apple.backupd: Copied 152.2 GB of 630.5 GB, 1393795 of 2357620 items
Dec 17 01:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 305.2 GB of 630.5 GB, 1413946 of 2357620 items
Dec 17 02:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 457.1 GB of 630.5 GB, 1419190 of 2357620 items
Dec 17 03:19:07 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 1736865 files (568.3 GB) from volume Macintosh HD.
Dec 17 03:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 572.1 GB of 630.5 GB, 1848939 of 2357620 items
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Indexing a file failed. Returned 200 for: /Volumes/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane, /Volumes/3 TB GoFlex Drive/Backups.backupdb/Tom iMac/2011-12-14-171406.inProgress/7DB524DD-EFB9-42A6-8A21-0A2A312EDA6D/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Aborting backup because indexing a file failed.
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Stopping backup.
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 2164998 files (581.1 GB) from volume Mac OS Lion GM.
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copy stage failed with error:11
Dec 17 03:40:50 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Backup failed with error: 11
This time it was the Mouse.prefPane that caused the error. I'd like to exclude the entire PreferencePanes directory.
This was my error message this time:
I just realized this was on my small Developers partition. Perhaps there is an error with the build, OR an error with the initial restore. I'd like to perhaps exclude the entire /Volumes/Mac OS Lion GM. I expect that Time Machine is working fine with my main partition and the error happens when it's almost done with the Mac OS Lion GM partition.
The problem now is that I only have 265 GB of 3 TB available on my Time Machine HDD. If attempt another backup, it'll surely erase about 410 GB of my past saved backups. I've already lost 6 months, and I only have two months left of backups. I need to erase the ".inProgress" package again. That'll take time, and it's impossible to do from this main partition, even at root access. This ".inProgress" has a total of two (nearly) full backups; it didn't cleanup the first full backup attempt while starting the second,perhaps it would have had it finished. But I fear even if I exclude the whole "Mac OS Lion GM" partition, It'll create a third full backup before cleanup and erase ~400 GB of previous good backups. Then, I'll have a total of 4 (nearly) full backups! 3 TB is just enough without any past backups.
Maybe I'll just copy my documentations of my 'errasing the ".inProgress" package' last time (from the Mac OS Lion GM partition) and do a full restore of just that partition. Thus erasing the errors all together. If it doesn't fix the errors then this could be a bug in the build that doesn't allow Time Machine to work. I've always included this partition in Time Machine before, even with other Lion builds, so I suspect that it was an error in the initial restore. (I may be answering my own questions, and that the inital restore (of the small partition) is the problem, and I just need to re-restore the small partition)
Again, I'm going to have to erase the ".inProgress" file to regain 1.53 TB of space before proceeding.
Also, I gave myself permission to read the ".Backup.345781513.887697.log", the log that was created last night when I first started Time Machine this last time. It was interesting, but didn't show the error I could see from the console.
Right now, mds and mdworker appear to be going crazy even after I just now turned off Time Machine. I think I'll let it go for the rest of the night. Then I'll work on erasing the ".inProgress" package from the other partition boot up.
That was my entire last post. To add some information, I have two OS X partitons, both Mac OS X Lion. One is my large main partition, the other is one I don't mind testing with. I recently replaced my internal hard drive in my iMac and restored from Time Machine both partitions. This appeared to go smoothly. But I have yet to create a single successful Time Machine backup since. At first it was doing a Full Backup, which I didn't like, but now it just aborts around 95% completion. Each, time, it tries it fills the Time Machine hard drive with duplicate (nearly) full backups errasing my older good backups. I would like to erase the ".inProgress" file to save space.
My main question in this new discussion is does anyone know of a good way of erasing the ".inProgress" file? This is so I can preseerve my previous backups. ACLs and other permissions seem to make it impossible to erase from this startup partition, the one I'm running Time Machine from. Even at root level, if I give myself permission to change permissions or delete a file, it'll say Operation not Permitted instead of Permission Denied. I have been able to delete this ".inProgress" package before when booting from the other partition, but with great difficulty. I have had much help from another Member in this Support Community when it comes to solving my Time Machine problems. I think I have found the problem (indexing files in my small OS X partition), as stated in my copy& pasted post above, but I really need to delete this inProgress package first to save space before continuing!

Pondini wrote:
Gator TPK wrote:
Now I'll have to fix the small partition? How's the best way to do this? There could be thousands of files that won't index fine.
See if there's anything you haven't done, that applies, in the pink box of #C3 in Time Machine - Troubleshooting
Otherwise, since most (or all?) of the indexing errors are in OSX, you might want to just reinstall it. Something may have gone wrong sometime, that damaged those files.
I reviewed #C3 in Time Machine - Troubleshooting and I have already done most of those things. I have just learned something new though:
When I included my Main OS X partition again, I got an indexing error for the first time for that partition. I might be interesting to note that the _spotlight process was running, and it's running again (the magnifying glass has a dot and it generically says "Indexing Tom's iMac"). mdworker, mds and backupd processes really are working hard, one moment they used over 500% of my CPU. It's nice to know for once quad core is good for something other than video encoding. (Now if they could just get the Finder to do more than 100.1%, only 1 thread is doing 100%, I'd like to see file size calculations 8 times quicker!)
I never got an indexing error once in the past 2 weeks for that large Mac OS X v10.7.2 main volume, and it had appeared to finish that partition backup before running into problems with my smaller test partition. Also, I had just updated the smaller test partition with a later build of Mac OS X. But It appears that the beta builds are clearly not the problem. I thought I could just restore again (from the December 4th backup) the small partition and both would be fine.
I'll finish reviewing all the suggestions on Time Machine - Troubleshooting and go from there. Hopefully, the _spotlight indexing simutaniously was the only problem. It's strange that the indexing hasn't happened since the original restore last week untill I finally got a good clean complete partial Time Machine backup. Why would the first Time Machine backup trigger indexing again?
For now, I'm going to exclude the Main Partition again, and let another good backup run. And try your suggestions. (And wait till mds, mdworker, etc. to finish!)
I have the logs of the first two sucsessful backups and the last two failed backups from the last 3 hours, if that would help.?

I'm having errors with time machine

I checked other discussions and downlaoded a time machine log. The message that comes up is, "Starting standard backup Backing up to: /Volumes/Time Machine Backups/Backups.backupdb Error: (22) setxattr for key:com". Any help?

Usually that error indicates a drive malfunction; specifically, the drive is spinning down and not responding to bus signals. Some "Eco" or "green" drives are known for this behavior. The following steps may help:
Select  ▹ System Preferences ▹ Energy Saver ▹ Power Adapter and uncheck the box labeled Put the hard disk(s) to sleep when possible, if it's checked.
If the drive is connected to a hub, connect it to a built-in port on the computer.
If a firmware update is available for the drive, apply it.
Contact the drive manufacturer to see whether there's a firmware setting you can change.
If you installed vendor software for the drive, uninstall it.
If none of the above steps resolves the issue, try another drive.

HT3275 Since updating OS to Mountain Lion from leopard, I get the following error message when trying to backup with time machine on external drive. Could not complete backup to media share. The network backup disk does not support the required AFP feat

Since updating OS to Mountain Lion from leopard, I get the following error message when trying to backup with time machine on external drive. "Could not complete backup to media share. The network backup disk does not support the required AFP features." What are AFP features and how do I get Time Machine to backup to my current external backup?

This means that your NAS does not support the required encryption. Update your NAS to the latest firmware or ditch it and buy a Time Capsule (they are the most reliable when using TM).

I keep getting this error when trying to backup time capsule with time machine. The backup disk image "/Volumes/Data-1/Dan's iMac.sparsebundle" is already in use.

I keep getting this error when trying to backup time capsule with time machine. The backup disk image “/Volumes/Data-1/Dan’s iMac.sparsebundle” is already in use.

Make sure that no other Macs are backing up at the time.
Pull the power cable from the back of the Time Capsule
Count to ten
Plug the power cable back into the back of the Tme Capsule
Wait a few minutes, then try a backup again.

Im using a network drive with time machine and im getting error 45. Time machine will not work now. Why?

I bought a seagate goflex home 2TB network drive. It worked with time machine for a couple of weeks than now it wont. It just says ERROR 45 now and will not back up. Why?

Welcome to Apple Support Communities.
According to several related Time Machine Error 45 threads in these forums, Time Machine is not well suited to backups on most non-Apple network drives.
https://discussions.apple.com/message/10744727#10744727
https://discussions.apple.com/message/15643759#15643759
https://discussions.apple.com/message/11929252#11929252
https://discussions.apple.com/message/13164522#13164522
One of the discussions provides an off-site link to these suggestions:
http://web.me.com/pondini/Time_Machine/Troubleshooting.html

"No such file or directory" errors on Time Machine backup volume

I remotely mounted the Time Machine backup volume onto another Mac and was looking around it in a Terminal window and discovered what appeared to be a funny problem. If I "cd" into some folders (but not all) and do a "ls -la" command, I get a lot of "No such file or directory" errors for all the subfolders, but all the files look fine. Yet if I go log onto the Mac that has the backup volume mounted as a local volume, these errors never appear for the exact same location. Even more weird is that if I do "ls -a" everything appears normal on both systems (no error messages anyway).
It appears to be the case that the folders that have the problem are folders that Time Machine has created as "hard links" to other folders which is something that Time Machine does and is only available as of Mac OS X 10.5 and is the secret behind how it avoids using up disk space for files that are the same in the different backups.
I moved the Time Machine disk to the second Mac and mounted the volume locally onto it (the second Mac that was showing the problems), so that now the volume is local to it instead of a remote mounted volume via AFP and the problem goes away, and if I do a remote mount on the first Mac of the Time Machine volume the problem appears on the first Mac system that was OK - so basically by switching the volume the problem switches also on who shows the "no such file or directory" errors.
Because of the way the problem occurs, ie only when the volume is remote mounted, it would appear to be an issue with AFP mounted volumes that contain these "hard links" to folders.
There is utility program written by Amit Singh, the fella who wrote the "Mac OS X Internals" book, called hfsdebug (you can get it from his website if you want - just do a web search for "Mac OS X Internals hfsdebug" if you want to find it ). If you use it to get a little bit more info on what's going on, it shows a lot of details about one of the problematic folders. Here is what things look like on the first Mac (mac1) with the Time Machine locally mounted:
mac1:xxx me$ pwd
/Volumes/MyBackups/yyy/xxx
mac1:xxx me$ ls -a
. .DS_Store D2
.. Documents D3
mac1:xxx me$ ls -lai
total 48
280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 .
282780 drwxr-xr-x 12 me staff 442 Jan 17 14:03 ..
286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 Documents
729750 drwx------ 104 me staff 7378 Jan 15 14:17 D2
728506 drwx------ 19 me staff 850 Jan 14 09:19 D3
mac1:xxx me$ hfsdebug Documents/ | head
<Catalog B-Tree node = 12589 (sector 0x18837)>
path = MyBackups:/yyy/xxx/Documents
# Catalog File Record
type = file (alias, directory hard link)
indirect folder = MyBackups:/.HFS+ Private Directory Data%000d/dir_135
file ID = 728505
flags = 0000000000100010
. File has a thread record in the catalog.
. File has hardlink chain.
reserved1 = 0 (first link ID)
mac1:xxx me$ cd Documents
mac1:xxx me$ ls -a | head
.DS_Store
.localized
.parallels-vm-directory
.promptCache
ACPI
ActivityMonitor2010-12-1710p32.txt
ActivityMonitor2010-12-179pxx.txt
mac1:Documents me$ ls -lai | head
total 17720
135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 .
280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 ..
144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
146 drwxr-xr-x 2 me staff 68 Feb 17 2009 .parallels-vm-directory
147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
148 drwxr-xr-x 2 me staff 136 Aug 28 2009 ACPI
151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
So you can see from the first few lines of the "ls -a" command, it shows some file/folders but you can't tell which yet. The next "ls -la" command shows which names are files and folders - that there are some folders (like ACPI) and some files (like A.txt and A9.txt) and all looks normal. And the "hfsdebug" info shows some details of what is really happening in the "Documents" folder, but more about that in a bit.
And here are what a "ls -a" and "ls -al" look like for the same locations on the second Mac (mac2) where the Time Machine volume is remote mounted:
mac2:xxx me$ pwd
/Volumes/MyBackups/yyy/xxx
mac2:xxx me$ ls -a
. .DS_Store D2
.. Documents D3
mac2:xxx me$ ls -lai
total 56
280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 .
282780 drwxr-xr-x 13 me staff 398 Jan 17 14:03 ..
286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 Documents
729750 drwx------ 217 me staff 7334 Jan 15 14:17 D2
728506 drwx------ 25 me staff 806 Jan 14 09:19 D3
mac2:xxx me$ cd Documents
mac2:Documents me$ ls -a | head
.DS_Store
.localized
.parallels-vm-directory
.promptCache
ACPI
ActivityMonitor2010-12-1710p32.txt
ActivityMonitor2010-12-179pxx.txt
mac2:Documents me$ ls -lai | head
ls: .parallels-vm-directory: No such file or directory
ls: ACPI: No such file or directory
... many more "ls: ddd: No such file or directory" error messages appear - there is a one-to-one
correspondence between the "ddd" folders and the "no such file or directory" error messages
total 17912
728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 .
280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 ..
144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
If you look very close a hint as to what is going on is obvious - the inode for the Documents folder is 152 on the local mounted case (the first set of code above for mac1), and it's 728505 in the remote mounted case for mac2. So it appears that these "hard links" to folders have an extra level of folder that is hidden from you and that AFP fails to take into account, and that is what the "hfsdebug" shows even better as you can clearly see the REAL location of the Documents folder is in something called "/.HFS+ Private Directory Data%000d/dir_135" that is not even visible to the shell. And if you look closely in the remote mac2 case, when I did the "cd Documents" I don't go into the inode 135, but into the inode 728505 (look close at the "." entry for the "ls -la" commands on both mac1 and mac2) which is the REAL problem, but have no idea how to get AFP to follow the extra level of indirection.
Anyone have any ideas how to fix this so that "ls -l" commands don't generate these "no such file or folder" messages?
I am guessing that the issue is really something to do with AFP (Apple File Protocol) mounted remote volumes. The TimeMachine example is something that I used as an example that anyone could verify the problem. The real problem for me has nothing to do with Time Machine, but has to do with some hard links to folders that I created on another file system totally separate from the Time Machine volume. They exhibit the same problem as these Time Machine created folders, so am pretty sure the problem has nothing to do with how I created hard links to folders which is not doable normally without writing a super simple little 10 line program using the link() system call - do a "man 2 link" if you are curious how it works.
I'm well aware of the issues and the conditions when they can and can't be used and the potential hazards. I have an issue in which they are the best way to solve a problem. And after the problem was solved, is when I noticed this issue that appears to be a by-product of using them.
Do not try these hard links to folders on your own without knowing what they're for and how to use them and not use them. They can cause real problems if not used correctly. So if you decide to try them out and you loose some files or your entire drive, don't say I didn't warn you first.
Thanks ...
-Bob

The problem is Mac to Mac - the volume that I'm having the issue with is not related in any way to Time Machine or to TimeCapsule. The reference to TIme Machine is just to illustrate the problem exists outside of my own personal work with hard links to folders on HFS Extended volumes (case-sensitive in this particular case in case that matters).
I'm not too excited about the idea of snooping AFP protocol to discover anything that might be learned there.
The most significant clue that I've seen so far has to do with the inode numbers for the two folders shown in the Terminal window snippets in the original post. The local mounted case uses the inode=728505 of the problematic folder which is in turn linked to the hidden original inode of 135 via the super-secret /.HFS+... folder that you can't see unless using something like the "hfsdebug" program I mentioned.
The remote mounted case uses the inode=728505 but does not make the additional jump to the inode=135 which is where lower level folders appear to be physically stored.
Hence the behavior that is seen - the local mounted case is happy and shows what would be expected and the remote mounted case shows only files contained in the problem folder but not lower-level folders or their contents.
From my little knowledge of how these inode entries really work, I think that they are some sort of linked list chain of values, so that you have to follow the entire chain to get at what you're looking for. If the chain is broken somewhere along the line or not followed correctly, things like this can happen. I think this is a case of things not being followed correctly, as if it were a broken chain problem then the local mounted case would have problems also.
But the information for this link in the chain is there (from 728505 to the magic-135) but for some reason AFP doesn't make this extra jump.
Yesterday I heard back from Apple tech support and they have confirmed this problem and say that it is a "implementation limitation" with the AFP client. I think it's a bug, but that will have to be up to Apple to decide now that it's been reported. I just finished reporting this as a bug via the Apple Bug Reporter web site -- it's bug id 8926401 if you want to keep track it.
Thanks for the insights...
-Bob

Problem using a WD hard Drive with Time Machine

A couple weeks ago I bought a 1TB Western Digital "Elements" Hard Drive and configured it with Time Machine on my MacBook Pro (running Mountain Lion OSX version 10.8.3). The drive was working fine until last night, when it was in the process of backing up and it got the following error:
Time Machine Error
Unable to complete backup. An error occurred while creating the backup folder.
Now whenever I try to unlock the drive, it freezes up like this:
I've tried restarting the computer and reconnecting the drive several times, and it always gets stuck in the same place. I know my password is correct, because I've tried incorrect ones, and it shakes and rejects them like it should. It's only when I enter the correct password that it freezes.
I went into the disk utility to try to verify the disk, but it gave me these two popups:
I notice it says the drive is almost full, though last night it was somewhere around a third full. I don't know what to make of that.
I had to eject the disk and reconnect it before I could try to repair it. When I did try to repair it, it worked for several minutes, then gave me this:
I notice here that the disk utility looks to have ejected the disk when it couldn't repair it. After that, I don't know what to try.
The one thing I did differently last night that may have contributed to the problem was that before I got the initial Time Machine error, I added a couple of folders to the WD drive and backed up some pictures and music manually. Does Time Machine not work if you have other things on the external drive you're using?
At any rate, I'd rather not erase the drive and start over. Is there anything else I can do at this point? Thanks.

Sounds like your drive may be failing. Test it on another system first, but if the problem persists, get it replaced under warranty.

I have had a series of Macs. They have been backed up with Time Machine. I am trying to restore TM backup files from the older Macs using my new MacBook Pro. No go. What do I do ?

I have had a series of Macs. They have been backed up with Time Machine. I am trying to restore TM backup files from the older Macs using my new MacBook Pro. No go. What do I do ?

I am trying to restore TM backup files from the older Macs using my new MacBook Pro. No go.
Migration Assistant (Finder > Applications > Utilities > Migration Assistant) is the tool that you would use to restore backups from older Macs to another Mac.
Details are here: http://pondini.org/OSX/MigrateLion.html The same info applies for Mavericks and Yosemite. If you are saying that this is a "no go".....where are you getting stuck? What error messages do you see?

Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." Tried suggestions I've seen on the forum.

Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." I've tried various suggestions I've seen on the forum but nothing has worked. TIme Machine worked fine for the last two years and just suddenly started having this problem every time. The only thing that was a little different is that the computer was off for a week while on vacation and then I added a large amount (20 GB) of photos. Now the requested backup size is 82GB, which is large, and process proceeds very slowly for 2-3 hours before failing with the message mentioned. I have more than enough available backup storage space for it. Before failing, Time Machine has backed up no more than 12GB or so of the backup. It fails during different files each time.
I've turned off the computer sleep feature, and I've checked that the NAS is set to never automatically power down. I normally backup over Wi-Fi, but I've also tried connecting to Ethernet and it still has the same problem. It's odd because I also have a MacBook Pro that is still backing up fine to the same NAS using the MacBook's Time Machine.
I am using an iMac with OS X 10.6.8 and an Iomega StorCenter ix2-200 NAS.
I have system logs that I can share if helpful. The logged messages vary a bit from run to run, but here are some messages that I've been seeing:
I always get this message near the beginning of the backup:
Event store UUIDs don't match for volume: Macintosh HD
I've gotten this messsage a number of times:
Bulk setting Spotlight attributes failed.
One Day
Stopping backupd to allow ejection of backup destination disk!
Another day
1/7/12 10:44:20 AM
mDNSResponder[18]
PenaltyTimeForServer: PenaltyTime negative -112916, (server penaltyTime -1132397006, timenow -1132284090) resetting the penalty
1/7/12 10:46:37 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x1106be94
1/7/12 10:46:37 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
Another Day
1/6/12 8:03:22 AM
Google Chrome[164]
Cannot find function pointer CMPluginInFactory for factory 3487BB5A-3E66-11D5-A64E-003065B300BC in CFBundle/CFPlugIn 0x16f99e20 </Users/smarmer/Library/Contextual Menu Items/Google Notifier Quick Add CM Plugin.plugin> (not loaded)
1/6/12 8:04:02 AM
com.apple.backupd[193]
Copied 7.5 GB of 67.0 GB, 8866 of 8866 items
1/6/12 8:06:58 AM
/System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[1013]
No valid tickets, timing out
1/6/12 8:29:44 AM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -148702, (server penaltyTime 2056822773, timenow 2056971475) resetting the penalty
1/6/12 8:59:22 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa5ac380
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
Another day
1/5/12 3:48:55 PM
mdworker[2128]
CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
1/5/12 4:24:54 PM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -42698, (server penaltyTime 1148718961, timenow 1148761659) resetting the penalty
1/5/12 4:29:58 PM
com.apple.backupd[2074]
Copied 586.4 MB of 67.0 GB, 9891 of 9891 items
1/5/12 4:39:00 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa1c0380

bokon0n wrote:
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support TM Lock Stealing
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support Server Reply Cache
Those indicate that your NAS is not fully compatible with Snow Leopard.
1/11/12 8:53:35 AM
kernel
jnl: disk2s2: replay_journal: from: 67182592 to: 78680064 (joffset 0xa7b8000)
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: examining extra transactions starting @ 78680064 / 0x4b09000
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: Extra txn replay stopped @ 79056896 / 0x4b65000
1/11/12 8:53:49 AM
kernel
jnl: disk2s2: journal replay done.
1/11/12 8:53:49 AM
fseventsd[41]
event logs in /Volumes/Time Machine/.fseventsd out of sync with volume. destroying old logs. (253512 14 253512)
1/11/12 8:53:50 AM
kernel
hfs: Removed 1 orphaned / unlinked files and 0 directories
That looks like a problem was found with the file system (data) on the TM disk. I don't know the details, but OSX tried to recover it from the journal, and found extra data on the drive. Likely a result of the incompatibility mentioned above.
1/11/12 9:47:40 AM
com.apple.backupd[1169]
Bulk setting Spotlight attributes failed.
That's a problem writing to the NAS drive.
But the backup continued after all this.
1/11/12 1:25:07 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x9d00b44
Something caused a disconnect. Can't tell from the log what it was.
I doubt it's a problem with something in OSX being damaged or corrupted, but reinstalling OSX isn't a major hassle, so might be worth a try.
To be incompatible with Snow Leopard, this NAS must be at least a couple of years old. It may be beginning to fail.
Contact the maker. See if there's an update to make it compatible with Snow Leopard. If so, that might fix it.
If not, or if that doesn't fix it, see if they have any diagnostics that will shed any light.

Freezing/crash of iMac under Snow Leopard when backup with Time Machine

Hi!
The backup on my external hard drive with Time Machine cannot be completed.
After few ten Go out of 360Go the backup stops suddenly and the computer freezes/crashes.
I have got an iMac Intel Core 2 Duo with Snow Leopard 10.6.8 − 64 bit. The external hard drive is a LaCie 500Go.
Also, backups for another Apple computer can be done with this LaCie external drive. So, it is not the cause of the freezing/crash of the iMac.
I tried to solve this problem applying the following steps:
1- I started with the installation disk.
2- I repaired the internal iMac drive and the permissions with the Disk Utilities soft on the installation disk. All was OK.
3- The LaCie drive was erased, formatted again with one GUID partition (500Go) and the disk verified. All was OK.
4- I re-install the OS with the installation disk -> 10.6 Snow Leopard
5- Updates to 10.6.8, etc… security update 2012-004 and the 13th Java update to v1.6.
6- I deleted in the folder /Library/Preferences the file com.apple.TimeMachine.plist
7- I deleted the file com.apple.finder.plist in the administrator account Preferences folder.
8- The iMac was shutdowned as well as the external LaCie drive.
9- I restarted and changed the name of the external LaCie drive.
10- I choose the LaCie backup drive with Preferences System > Time Machine with right exclusions.
Unfortunately, the problem remained and the backup was again unsuccessful followed by another freezing/crash of the iMac.
So how to solve this problem?
Here is what I obtained from the system.log with the Console utility (crash/freezing at: 10:48):
=============================================================================== ==============================
Tue 4 09:58:24 imac com.apple.backupd[233]: Starting standard backup
Tue 4 09:58:24 imac com.apple.backupd[233]: Backing up to: /Volumes/LaCie/Backups.backupdb
Tue 4 09:58:24 imac com.apple.backupd[233]: Ownership is disabled on the backup destination volume. Enabling.
Tue 4 09:58:25 imac com.apple.backupd[233]: Backup content size: 343.5 GB excluded items size: 2.3 GB for volume iMac
Tue 4 09:58:25 imac com.apple.backupd[233]: No pre-backup thinning needed: 409.52 GB requested (including padding), 465.02 GB available
Tue 4 09:58:25 imac com.apple.backupd[233]: Waiting for index to be ready (101)
Tue 4 09:58:25 imac mds[40]: (Normal) DiskStore: Creating index for /Volumes/LaCie/Backups.backupdb
Tue 4 10:00:32 imac com.apple.backupd[233]: SystemFlippers: didn't consume all data for vers ID 1 (pBase = 0x10083f704, p = 0x10083f70c, pEnd = 0x10083f70d)
Tue 4 10:00:32 imac com.apple.backupd[233]: SystemFlippers: didn't consume all data for vers ID 1 (pBase = 0x10101b304, p = 0x10101b30c, pEnd = 0x10101b30d)
Tue 4 10:00:33 imac com.apple.backupd[233]: SystemFlippers: didn't consume all data for vers ID 1 (pBase = 0x1007c6f94, p = 0x1007c6f9c, pEnd = 0x1007c6f9d)
Tue 4 10:07:49 imac /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[202]: No valid tickets, timing out
Tue 4 10:14:53 imac mdworker[242]: multibyte IDs are unsupported.
Tue 4 10:17:05 imac backupd[233]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
Tue 4 10:17:05 imac mdworker[243]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
Tue 4 10:22:00 imac com.apple.backupd[233]: SystemFlippers: didn't consume all data for vers ID 1 (pBase = 0x10377e518, p = 0x10377e556, pEnd = 0x10377e557)
Tue 4 10:22:01 imac com.apple.backupd[233]: SystemFlippers: didn't consume all data for vers ID 1 (pBase = 0x10393e518, p = 0x10393e556, pEnd = 0x10393e557)
Tue 4 10:30:38 imac mdworker[242]: Corrupt JPEG data: 1 extraneous bytes before marker 0xd9
Tue 4 10:30:38 imac mdworker[242]: JPEG datastream contains no image
Tue 4 10:30:39 imac mdworker[242]: Corrupt JPEG data: 1 extraneous bytes before marker 0xd9
Tue 4 10:30:39 imac mdworker[242]: JPEG datastream contains no image
Tue 4 10:32:10 imac mdworker32[452]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Tue 4 10:38:16 imac mdworker[243]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
Tue 4 10:38:16 imac mdworker[243]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
=============================================================================== ==============================
Waiting for a solution....
Bye
JacRb

See the problem and its solution:
https://discussions.apple.com/message/21491140#21491140

Problem with Time Machine back up

Hello all,
Grateful for anyone's help with this issue.
Firstly, a summary of specs:
Mac OS X 10.7.
Late 2007 Macbook 13inch
External hard drive - LaCie 1TB D2 Quaddra
Issue - When trying to back up my 2007 Macbook it fails! When I back up my 2011 MacBook Pro (to the same external hard disk) it works fine!
I have reviewed a whole load of advice on here, some I am able to understand others that I unable too! Sorry! Now stuck so thought I would post on here in the hope sometime might be able to give me some advice.
I have downloaded a widget which helped me view the error message details (found that advice on the excellent Pondini website).
The error message was:
Starting standard backup
Backing up to: /Volumes/Mike/Backups.backupdb
Backup content size: 136.3 GB excluded items size: 8.2 GB for volume Macintosh HD
153.65 GB required (including padding), 465.32 GB available
Waiting for index to be ready (101)
Stopping backup.
Error: (-47) SrcErr:NO Copying /Applications/Address Book.app/Contents/MacOS/Address Book to /Volumes/Mike/Backups.backupdb/Mike surname removed’s MacBook/2012-12-26-120325.inProgress/560DC4C6-DFCE-48AA-B430-457C461AEA0F/Macin tosh HD/Applications/Address Book.app/Contents/MacOS
Copied 9 files (774 KB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11
To be honest this is pretty much gooblygook to me! But I did try to locate the file that was causing the problem (Address Book) and excluded it from the Time Machine backup, I then received this error message:
Starting standard backup
Backing up to: /Volumes/Mike/Backups.backupdb
Backup content size: 136.3 GB excluded items size: 8.3 GB for volume Macintosh HD
153.62 GB required (including padding), 465.32 GB available
Waiting for index to be ready (101)
Stopping backup.
Error: (-47) SrcErr:NO Copying /Applications/adidas miCoach Manager.app/Contents/Frameworks/QtCore.framework/Versions/4/QtCore to /Volumes/Mike/Backups.backupdb/Mike surname removed’s MacBook/2012-12-26-120325.inProgress/65EE1FE8-D548-4CAD-AEC7-9B6A4C12FAD9/Macin tosh HD/Applications/adidas miCoach Manager.app/Contents/Frameworks/QtCore.framework/Versions/4
Copied 12 files (2.7 MB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11
So I then excluded miCoach, but it failed again! This time with this message:
Starting standard backup
Backing up to: /Volumes/Mike/Backups.backupdb
Backup content size: 136.3 GB excluded items size: 8.3 GB for volume Macintosh HD
153.59 GB required (including padding), 465.32 GB available
Waiting for index to be ready (101)
Stopping backup.
Error: (-47) SrcErr:NO Copying /Applications/Adobe Flash Player 9/Install Flash Player 9 UB.app/Contents/InstallerData/Installer.data to /Volumes/Mike/Backups.backupdb/Mike surname removed’s MacBook/2012-12-26-120325.inProgress/B7A9D12A-B391-4AD7-907D-01828917DF39/Macin tosh HD/Applications/Adobe Flash Player 9/Install Flash Player 9 UB.app/Contents/InstallerData
So I excluded Adobe Flash Player, and....failed again, this time blaming the Calculator
Starting standard backup
Backing up to: /Volumes/Mike/Backups.backupdb
Backup content size: 136.3 GB excluded items size: 8.3 GB for volume Macintosh HD
153.59 GB required (including padding), 465.32 GB available
Waiting for index to be ready (100)
Stopping backup.
Error: (-47) SrcErr:NO Copying /Applications/Calculator.app/Contents/Resources/Calculator.icns to /Volumes/Mike/Backups.backupdb/Mike surname removed’s MacBook/2012-12-26-120325.inProgress/60CC7EAA-FCE7-4FC3-B946-8B999E574797/Macin tosh HD/Applications/Calculator.app/Contents/Resources
Copied 2760 files (27.1 MB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11
The way this is going I will not have any information left to back up!!
Any advice warmly received.
Merry Christmas

miketangokilo wrote:
Error: (-47) SrcErr:NO Copying /Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Files/Steel String Acoustic Guitar/50B-1GA1-B2.aif to /Volumes/Mike/Backups.backupdb/Mike Surname removed’s MacBook/2012-12-26-120325.inProgress/8614198B-1C54-4CF1-8C24-DDD9692FB82C/Macin tosh HD/Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Files/Steel String Acoustic Guitar
We don't know exactly what error (-47) means. Apple used to publish lists of error code, many years ago, before OSX, but very few now. It's clearly something to do with the file named, but just what isn't clear.
But we do know that SrcErr:NO means the error is not on the "source" -- ie, your Mac. It seems to be a problem writing the file to the TM drive.
So first, if you haven't yet, run Repair Disk on that TM partition, just to be sure it's ok.
Also, be sure the disk has either the GUID (preferred) or APM partition map scheme. Click the top line in Disk Utility's sidebar, and that will be shown at the lower right. If it's MBR (Master Boot Record), that's a Windows setup, and sometimes doesn't work well with Time Machine, especially if there are multiple partitions.
Prior to OSX, error -47 meant the file was busy. If that's still true, something may be trying to access it while it's being written. If you're running any anti-virus apps on that Mac, or anything else that might be looking at the backup drive, exclude the TM drive from it, or, better, turn it off. Antivirus apps can interfere with TM backups -- some can even damage them.

Macbook won't recognize external Hard Drive and issues with Time Machine

Hello everyone,
I have just bought a new Macbook Pro with Mountain Lion and I am currently having problems with Time Machine.
The issue begun in Snow Leopard: Time Machine was taking too long to backup, and would often not finish the backup because the external hard drive would be unwillingly ejected.
Now with Mountain Lion I have reformated the drive (Mac OS Journaled) and about a third of the way through had the same issue: the drive was ejected before the backup could be finished. I restarted the machine and it happened again. However, now the computer won't even recognize the external drive when I plug it in. I have also tried to power off/on the drive itself to no progress.
I have tested the USB port with another drive and the port is fine. I have also tested the usb cable and it is fine. And Disk Utility does not recognize the drive (even when I try the >diskutil list command in terminal).
Now, I can hear the drive humming normally when I turn it on, and it is not usb-powered (my electricity current does fluctuate).
Could the interrupted backup procedures have damaged the drive? And if so, wouldn't the computer recognize it anyway?
It is a 4 year old WD 1 TB that is used exclusively for TM and has never left the house.
Thank you for your time reading this and let me know if you need any more information that could help out.
Cheers!

From your description, I'd suspect a failing drive. Maybe time for a new external, especially as you've already re-formatted and it's still playing up.
I had a similar problem with one of my clone backups a few weeks ago - it failed, I erased it, re-cloned, worked a couple of times and then it failed again. Disk Utility didn't throw up any errors after re-formatting. I guess all disks die at some point.

Accessing back-ups on external hard-drive with Time Machine.

Hi guys,
I hope someone can help me with this problem. I am a novice at this so please be patient and forgive my ignorance.
I backed up the internal hard-drive of my '06 iMac onto an external Iomega 500GB hard-drive using Time Machine.
A couple of weeks later the internal hard-drive of my iMac fried and I got the " grey screen of death ".
Now I have the external hard-drive connected to my '06 MacBook.
There is 300GB of data on the external hard-drive. There is only 50GB of space available on my MacBook.
I would like to access my iPhoto on the external hard-drive but when I click on the iPhoto icon in Time Machine, I get "error code 10657 ".
I am NOT trying to do a full restore of the back-up onto the MacBook because :
1. There is not enough space available on the MacBook and
2. I will do a full restore when I have bought and installed a new bigger hard-drive into the iMac.
So, I guess my question is this : Is it possible for me to access my iPhoto on the external hard-drive using my MacBook without doing a complete transfer and if so, how ?
Thanking you in advance,
Sean.

If this is a network device, you can't back it up with Time Machine. If it's directly attached, and in Mac OS format, delete it from the exclusion list in the Time Machine preference pane.

Error 36 with time machine

Similar Messages

Maybe you are looking for