Error 109 With Time Machine

So I have a FantomDrives 1TB Hard Drive plugged into my airport extreme router through the USB port and me and my family have been using it for backing up our software, with mine going on one partition and my father and mother on the other. This has been working fine for us for a while now but as soon as we updated to Snow Leopard all of our backups stopped being accessible, ie, none of the .sparsebundles could be mounted. Ironically, we only installed Snow Leopard on two of the computers, but the third computer, an older PowerPC, cannot access its backup for the same reason. Any ideas?

alan73 wrote:
I have the same setup with a WD 1TB MyBook and have gotten the same error 109 ever since upgrading to Snow Leopard. I thought I simply had a corrupt mount point so I deleted my backup file and started from scratch. The initial backup went just fine but all subsequent backups failed.
Click here to download the +Time Machine Buddy+ widget. It shows the messages from your logs for one TM backup run at a time, in a small window. There should be a clue; if in doubt, copy and post the messages from that failed backup here.
A few folks have had trouble with the Buddy on Snow; if you do, and are familiar with Console, use it and filter for the backupd process; if not, post back for instructions.

Similar Messages

  • 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

  • Error 12 with time machine

    Hi there,
    after a disk failure of an interal SATA disk of my dual-2GHz-G5 I´ve restored the lost data using time machine, which worked perfectly fine. All data restored and OK.
    But - since the restore to the reformated internal disk (same hardware, same name, same mountpoint I suppose) TimeMachine quits backing up. TM prepares, starts backing up but then stops with "... Link of previous volume failed... ".
    Any ideas?
    Christian

    You can add me for another. I thought I was the only one until I found all of these threads describing the same problem. My system disk crashed so I reformated and restored from a CCC backup yesterday. Now I get the same "can't link (error 12) error". I also do not want to have to delete a years worth of backups just to make TM work again just because I restored a drive.
    For some reason, time machine doesn't seem capable of figuring out that the restored drive with the same name, same files, is the same as before, but it seems to think that it is a different drive and won't merge (link) it with previous backups.

  • 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).

  • After reformatting my 1 Tb WD ext drive and tinkering with the "exclude these items" list, I now get the following error message from Time Machine:Are you sure you want to back up to the same device your original data is on? the WD disk has mounted??

    After reformatting my 1 Tb WD ext drive and tinkering with the "exclude these items" list, I now get the following error message from Time Machine: "Are you sure you want to back up to the same device your original data is on?"  I've reformatted in Disk Utilities...not sure what I did wrong.  Any help would be appreciated.

    Not sure what you mean by "booted" from it.
    If the Mac OS is installed on the external drive, then it's possible to start up from it, just as you do from your internal drive. Please open the Startup Disk preference pane in System Preferences, and verify that your internal drive is selected as the startup disk.
    Assuming that's the case, then it may be that your TM settings have been corrupted. Turn off TM, then move or delete the file /Library/Preferences/com.apple.TimeMachine.plist. Turn TM back on, recreate your settings, and try again.

  • 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.

  • -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. 

  • 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

  • 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.

  • Problems with Time machine caused by removing PKCS11.log?

    I haven't yet found a solution to my Time Machine no longer backing up: "while an error occurred while copying files to the backup disk"
    I requested help before, but so far nobody could help me solve this problem!
    I noticed that I removed, in a file clean up, a log file: PKCS11.log."
    I still have this file in the Trash but can not restore this file from Trash to its original location because I don't know its original location. The command" restore", or "put back" does not figure in the menu of Trash.
    It can be that the removal of this log file causes the back up problem in Time Machine?
    As you will notice from the above, I know very little about software and subjects like this and hope that somebody can help me to get Time Machine backing up again.
    Thanks on beforehand!
    Harry

    I am sorry that my message is presented in this "step-by-step way, but it can be that the following lessage from TM Buddy Widget is important?
    Starting standard backup
    Attempting to mount network destination using URL: afp://Harry%[email protected]/Data
    Mounted network destination using URL: afp://Harry%[email protected]/Data
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Disk image /Volumes/Data/Harry Briels’s iMac.sparsebundle mounted at: /Volumes/Time Machine Backups
    Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    No pre-backup thinning needed: 8.22 GB requested (including padding), 464.29 GB available
    Indexing a file failed. Returned 200 for: /Library/Application Support/Adobe/Adobe PCD/cache/cache.db, /Volumes/Time Machine Backups/Backups.backupdb/HarryBrielsiMac/2013-07-04-181224.inProgress/46F8E230- 1335-4D3C-BA4F-E6A4B2AB0C07/Macintosh HD/Library/Application Support/Adobe/Adobe PCD/cache/cache.db
    Aborting backup because indexing a file failed.
    Stopping backup.
    Copied 86 files (266.0 MB) from volume Macintosh HD.
    Copy stage failed with error:11
    Backup failed with error: 11
    Ejected Time Machine disk image.
    Ejected Time Machine network volume.
    Harry

  • 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

  • Suddenly can't back-up with Time Machine

    Time Machine has finally completely quit. I have followed most of the suggestions on various Apple forums, including reformatting the backup HD (several times), repairing both the back-up and main HD, settting spotlight to private, quitting Finder (using Tinker tool), etc. Followed Pondini's very useful steps repeatedly. I get different error messages from Time Machine Buddy most every time. The most consistent refers to indexing.
    Below are the three most recent Buddy logs, in hopes somebody can help. Or suggest another backup solution.
    Starting standard backup
    Backing up to: /Volumes/Hitachi Orange/Backups.backupdb
    Ownership is disabled on the backup destination volume.  Enabling.
    Detected system migration from: /Volumes/Macintosh HD 1
    Backup content size: 498.4 GB excluded items size: 460.7 GB for volume Macintosh HD
    No pre-backup thinning needed: 45.22 GB requested (including padding), 930.58 GB available
    Waiting for index to be ready (101)
    Indexing a file failed. Returned 200 for: /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/wx-2 .8-mac-unicode/wx/lib/inspection.pyc, /Volumes/Hitachi Orange/Backups.backupdb/Galloway Desktop (3)/2011-07-08-190340.inProgress/F18A8582-E9F7-4D93-9BA0-07DEB1749449/Macintosh HD/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/wx -2.8-mac-unicode/wx/lib/inspection.pyc
    Aborting backup because indexing of file failed.
    Stopping backup.
    Copied 60774 files (16.3 GB) from volume Macintosh HD.
    Copy stage failed with error:11
    Backup failed with error: 11
    The one before
    Starting standard backup
    Backing up to: /Volumes/Hitachi Orange/Backups.backupdb
    Detected system migration from: /Volumes/Macintosh HD 1
    No pre-backup thinning needed: 37.67 GB requested (including padding), 877.17 GB available
    Indexer unavailable (200)
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0a4b0 "The file “classes.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0cf10 "The file “info.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0cf10 "The file “keyedobjects.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1005312b0 "The file “classes.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
    Copied 0 files (35 KB) from volume Macintosh HD.
    Backup canceled.
    And before that
    Starting standard backup
    Backing up to: /Volumes/Hitachi Orange/Backups.backupdb
    Detected system migration from: /Volumes/Macintosh HD 1
    No pre-backup thinning needed: 37.67 GB requested (including padding), 877.17 GB available
    Indexer unavailable (200)
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0a4b0 "The file “classes.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0cf10 "The file “info.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0cf10 "The file “keyedobjects.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1005312b0 "The file “classes.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
    Copied 0 files (35 KB) from volume Macintosh HD.
    Backup canceled.
    Any help would be most appriciated.
    This is my iMac (Late 2010) running OS X 10.6.8, backing up to a 1Tb Hitachi external HD, connected directly (no hub) via usb.

    It's possible that the system was keeping some piece of the I/O error in memory and, after the underlying cause of the I/O error went away, something you did juggled the system's brain back to a non-error condition.
    You are absolutely correct to remain suspicious of your HD. While it's possible that changing USB cables or zeroing out the disk might have solved the underlying I/O problem it's equally possible that you have a failing drive on your hands that may only be showing ugly symptoms sporadically. There is a small risk that you will end up with two sets of damaged data if a drive fails during data transfer so it was very wise of you to order another drive.
    You might want to consider using Carbon Copy Cloner or Super Duper! to make a clone to your new drive. Having a TM backup and one or more clones, all on separate physical drives, is a very effective backup solution. That's the combo I use.
    When my Mini's internal drive failed it took about five minutes to boot from one of my clones, restore a few files from my TM backup, set TM to back up the clone, set SuperDuper to back up to my second clone. After that, I was fully back in business by booting from my clone which allowed me to get the Mini's HD repaired when it was convenient for me.

  • 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.

Maybe you are looking for