Time machine suddenly failed to do a backup!

Time Machine has been working fine ever since setting up in 2011. Running Snow Leopard on iMac 10.6.8. Today it has failed to do the last backup, and the error screen as shown came up. It is scheduled to do backups every hour. All fine apart from now. I am using a Western Digital My Passport Studio 1TB, with available 600 GB space left. Has been working fine until today. Anyone out there got any ideas why this has just suddenly stopped working? What can I do to resolve it? Any help would be greatly appreciated. Thank you.

Welcome to the Apple Support Communities
See > http://pondini.org/TM/C10.html

Similar Messages

  • Time Machine Suddenly Failing Caused By Aperture Library

    Starting about 3 days ago - my ever-faithful Time Machine backups started failing. The error was concerning running out of disk space. Ilet it try several more times and it failed every time. I started doing some research at this great resource http://pondini.org/TM/Troubleshooting.html and tried several things from the suggestions:
    1. Disk Utility repair
    2. Spotlight Re-index
    3. Manually deleting the "inprogress"
    4. Manually deleting a few older backups.
    None of them worked. Looking at the logs I could see it was choking on the Aperture library. I fired up Aperture and let it do it's thing - hoping it would repair whatever issue it had. Tried backing up again. Still  the same error.
    Next up - I excluded the Aperture Library from the Time Machine backups - and BOOM.... successful backup.
    My only problem now though is I REALLY want that Aperture library backed up  to Time Machine,
    Does anyone have any suggestions for fixing this issue?
    - thx

    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. Clear the text field and scroll back in the log to that time. 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 search box.
    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.

  • I recently upgraded to Mavericks and the time machine is failing to backup.  Time Machine began only backing up twice a day and now has stopped.

    I recently upgraded to Mavericks and the time machine is failing to backup.  Time Machine began only backing up twice a day and now has stopped.

    This is the error message I got:
    2014-03-18 17:02:30 -0400 com.apple.backupd[4971]: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TOSHIBA EXT/Backups.backupdb/Quincy’s iMac size:37
    2014-03-18 17:02:30 -0400 com.apple.backupd[4971]: Backup failed with error 2: 2

  • Time Machine suddenly no longer backs up

    After backing up with the the time machine for over a week successful (on two computers using a common time machine), the time machine keeps failing when attempting a back up - I get the error message "unable to complete backup; an error occurred while creating the backup directory." Any ideas?

    Thanks for the comment, I also have an external drive but it is connected through a firewire port. I'll try disconnecting the external drive, but I suspect your situation going through the TC was different.
    I erased the TC and started all over with an ethernet cable to do the initial backup, then switched back to wireless backups. It backed up for a day or so and then quit. When I hit "back up now" it starts up and begins "preparing" and then just hangs - never starts the actual backup. It will hang all night with no error messages.
    I also take the laptop to work so I manually stop and start the TC - this may be contributing to my problem but I don't think it should.

  • Time Machine ejecting internal hard drive during backup

    I originally posted this in the Time Machine group. It was suggested I post to the Xserve group.
    We have an XSERVE running 10.6.4 server. It has 2 internal 1TB drives. The plan is to use one as the main drive and the second as a Time Machine backup. This used to work in 10.5, but since about 10.6.2 or so, it has not worked correctly.
    Time machine will come on, begin the backup, and then error off with a message that the drive has been ejected. I have erased the drive, but still no joy. I have partitioned the drive, still no joy. I have verified the drive repeatedly, and all is fine. I can copy files to and from the drive until the cows come home, and all works fine, which means I do not think it is the drive itself. Activate TM, however, and it will fail before the first backup is completed. The only way to get the drive back is to do a complete power down and then power up. Needless to say, that is not a good thing for a server that we rely on.
    Any ideas?
    10/14/10 10:41:27 AM com.apple.backupd1230 Backup content size: 542.8 GB excluded items size: 474.1 GB for volume Server HD
10/14/10 10:41:27 AM com.apple.backupd1230 No pre-backup thinning needed: 82.46 GB requested (including padding), 930.13 GB available
10/14/10 10:41:27 AM com.apple.backupd1230 Waiting for index to be ready (101)
10/14/10 10:41:27 AM mds70 (Normal) DiskStore: Creating index for /Volumes/backup/Backups.backupdb
    10/14/10 10:47:38 AM kernel FusionMPT: Notification = 22 (SAS Discovery) for SCSI Domain = 0
10/14/10 10:47:38 AM kernel Discovery condition = 0x000f0001
10/14/10 10:47:38 AM kernel FusionMPT: Notification = 18 (SAS Phy Link Status) for SCSI Domain = 0
10/14/10 10:47:38 AM kernel SAS Phy Link Status: PhyNum = 0, old link rate = 8, new link rate = 0, SASAddress = 50080007002e8c04
    10/14/10 10:48:10 AM kernel SCSIPressurePathManager: Timed out waiting for inactive/error path to become active, loops = 0
10/14/10 10:48:10 AM kernel 
10/14/10 10:48:10 AM kernel disk0s2: media is not present.
    10/14/10 10:48:10 AM com.apple.backupd1230 Stopping backupd because the backup volume was ejected!

10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error
10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error
10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error
10/14/10 10:48:10 AM com.apple.backupd1230 Copied 13416 files (4.0 GB) from volume Server HD.
10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error
10/14/10 10:48:10 AM servermgrd64 servermgr_backup: TimeMachinePostBackupHook called.
10/14/10 10:48:10 AM servermgrd64 servermgr_backup: TimeMachinePostBackupHook done.
10/14/10 10:48:11 AM kernel jnl: disk0s2: close: journal 0xffffff8012b15d20, is invalid. aborting outstanding transactions 


    No, it is not always at the same point/file/bytes transferred. It will vary from a few GB (say 3GB) to quite a few GB (say 30GB). I would add amongst the things I have done was to:
    Perform numerous Disk Utility Checks. Never any errors found.
    Erased the backup drive on multiple occasions. Double checked the GUID and format.
    Partitioned the drive and tried backing up to a new partition. (No joy there either)
    Copied lots and lots of data from the root disk to said partitions to test them. All went fine.
    It really is Time Machine that is causing the issue. I can use the drive all day long as long as TM does not run. When it does, I eventually get a failure message that the drive has been ejected.
    While I have not tried making a partition on the home drive (I'd rather not, lots of data there, make users mad, and since TM is not working, I have no backups at present), I do limit the data that is being backed up to JUST that of the system. /Users is being excluded at the moment. So I doubt there is anything out of the ordinary in the system. And, yes, I did a disk check on the root disk and all is fine there too.

  • Time Machine will not complete a system backup and terminates with "Unable to complete backup. An error occurred while copying files to the backup volume.  This follows a problem when Time machne terminated when the volume was almost full.

    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.

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

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

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

  • HT3275 Time Machine error. Unable to complete backup. An error occurred while copying files to the backup volume. Tried restarting, remounting external WD drive. Still cannot backup.

    Time Machine quit backing up files. Bought a new WD external drive. Worked for awhile, then quit backing up. Tried restarting computer, remounting drive. Message: Time Machine Error. Unable to complete backup. An error occurred when copying files. Suggestions?

    Thanks so very much for your help!! I'm boggled by it and now just about ready to dump the whole idea of Time Machine and backup using a cloning program. Maybe TM is only guaranteed to work well with Time Capsule these days?
    Today there again was no backup. I did as you suggested, looked into Console. It showed many lines of "(Error) DiskStore: No block in wakeup" and also repeatedly "(Warning) DiskStore: Ignored bogus fetch...".
    So I created a marker and attempted to initiate a backup, keeping Console open and refreshed. Here's what I got:
    8/19/13 5:18:40.385 PM Console:  Marker - Aug 19, 2013 5:18:40 PM
    8/19/13 5:19:48.844 PM com.apple.backupd: Starting standard backup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.508 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:38ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.510 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:40ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:20.000 PM kernel: USBF:          58091.976          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:20:51.000 PM kernel: USBF:          58122.985          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:21:22.000 PM kernel: USBF:          58153.992          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:21:53.000 PM kernel: USBF:          58185.  2          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:22:24.000 PM kernel: USBF:          58216. 14          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:22:55.000 PM kernel: USBF:          58247. 25          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:23:26.000 PM kernel: USBF:          58278. 41          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:23:57.000 PM kernel: USBF:          58309. 51          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:24:28.000 PM kernel: USBF:          58340. 59          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:24:59.000 PM kernel: USBF:          58371. 68          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:25:30.275 PM xpchelper: for uid: 501 -- timeout while waiting on FSEvents flush; clearing cache.
    8/19/13 5:25:30.000 PM kernel: USBF:          58402. 82          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:26:01.000 PM kernel: USBF:          58433. 96          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:26:32.027 PM com.apple.backupd: Backing up to: /Volumes/TMBackups/Backups.backupdb
    8/19/13 5:26:32.000 PM kernel: USBF:          58464.112          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:27:02.653 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David’s iMac size:37
    8/19/13 5:27:02.657 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David’s iMac size:37
    8/19/13 5:27:03.000 PM kernel: USBF:          58495.121          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:27:12.668 PM com.apple.backupd: Backup failed with error: 2
    During this 9-minute timeframe Finder also was inoperative - according to Activity Monitor: "Not Responding".
    I'm thinking it's the standalone Buffalo backup drive not waking up, and so everything comes to a screeching halt. Do you also think I should abandon TM and just do manual backups every day using a clone program?

  • Copying Mac App Store Apps may cause Time Machine to fail

    Hey folks,
    My Time Machine backups started failing the other day with the "error occurred while copying files" error (asking me to run Disk Utility). I ran DU and the drive checked out fine. I eventually checked the backupd logs (Console> filter "backupd") and found that TM was stopping with Error: (-41) SrcErr:No Copying /Path/to/a/file/inside/aMacAppStoreApp. Then saying the backup stopped with error:11.
    So I deleted the App and ran the backup again. This time it gave me the same error  on another MacAppStore App that I had installed. So I deleted that one too and then TM backup run successfully.
    Background:
    - There were only two MAS Apps installed (the two referenced above: Quick Note, ARD).
    - Both were installed after being downloaded to a different computer, copied to this one, and then a copy made into the Applications folder. They were working fine.
    - When I "installed" the Apps, I did not do a drag/drop copy, I did a copy/paste.
    - There were two copies of the each App on the filesystem. 1 copy in my "software installers" folder and 1 copy in the Applications folder. Only the copy in the Applications folder failed to backup. The unused copy in the installers folder backed up fine.
    Once the backups were working. I then moved the Apps from the "software installers" folder to the Applications folder. I opened the applications and they worked fine. I then ran the backup and it worked fine as well.
    So I'm not sure if Time Machine was failing because of my unusual way of copying them into the Applications folder or what? Thoughts? Either way, it seems like a strange thing to cause TM to completely fail.

    It's not copy protection issue since after I recopied the App (using drag/drop) the backup worked fine.
    You are allowed to copy MAS Apps from one computer to another and run them as long as the target computer is either authorized for the same MAS account or you login to the account that purchased the App.

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

    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.

  • 365 gig used, 1TB external HD-Time Machine bu fail -claims to need 1.3TB...

    I have an iMac with a 500 gig internal hard drive. We have used close to 365gig of that.
    I originally tried to set Time Machine up with a couple of older/smaller external HD's. Time Machine told me that it needed 800gig to back up.
    I purchased a 1TB LaCie external hard drive.
    Tonight when I tried to set up Time Machine it failed and said it now needed 1.3TB.
    I have now read through various discussions on sizing the drive for backup and generally it is suggested that 2 to 3 times is fine.
    It is also noted that there is no way to restrict this size other than by excluding items. I would prefer to not do this as the point is to back up our entire music, photo and video libraries.
    Also, it appears that once set up Time Machine works with the size of back up drive you have and deletes older backups.
    I am reluctant to now purchase an additional hard drive, to find that it now needs even more space as the space required seems to be growing exponentially.
    I seem to be locked into a catch-22 situation of Time Machine requiring space at a faster rate than I can buy a hard drive.
    Any advice?
    My ideal solution is telling Time Machine to restrict the size of the back up somehow. I realize, based on previous discussions that this does not seem possible.
    1.3TB of back up for a 365gig seems excessive.

    How many disks are connected to the system?
    Is it possible that Time Machine is trying to backup more than
    one disk (if there is more than one)?
    Dave

  • Time machine sometimes fails with no space left

    Hi,
    I'm beginning to notice that sometimes Time Machine is failing to backup saying there is no space left on the Time Machine backup disk.  I'm using OS X 10.9.4 .
    My understanding is that when there is not enough space left, Time Machine will automatically delete older backups to make space? Sometimes this happens, sometimes not.
    For example:
    Aug 10 18:39:49 Barney.local com.apple.backupd[9571]: Starting automatic backup
    Aug 10 18:39:50 Barney.local com.apple.backupd[9571]: Backing up to /dev/disk6s2: /Volumes/TimeMachine/Backups.backupdb
    Aug 10 18:40:04 Barney.local com.apple.backupd[9571]: Will copy (1 MB) from Macintosh HD
    Aug 10 18:40:04 Barney.local com.apple.backupd[9571]: Will copy (Zero KB) from HD5
    Aug 10 18:40:04 Barney.local com.apple.backupd[9571]: Will copy (Zero KB) from HD2
    Aug 10 18:40:04 Barney.local com.apple.backupd[9571]: Found 64 files (1 MB) needing backup
    Aug 10 18:40:04 Barney.local com.apple.backupd[9571]: 1.74 GB required (including padding), 7.41 GB available
    Aug 10 18:40:26 Barney.local com.apple.backupd[9571]: Copied 70 items (1 MB) from volume Macintosh HD. Linked 709.
    Aug 10 18:40:33 Barney.local com.apple.backupd[9571]: Copied 1 items (Zero KB) from volume HD5. Linked 2.
    Aug 10 18:57:34 Barney.local backupd[9571]: Metadata.framework [Error]: server port invalidated for uid 0
    Aug 10 19:01:02 Barney.local com.apple.backupd[9571]: Stopping backup.
    Aug 10 19:01:02 Barney.local com.apple.backupd[9571]: Error: (-34) SrcErr:NO Copying /Volumes/HD2/Users/gj/Documents/2013.partial.mbox/mbox to /Volumes/TimeMachine/Backups.backupdb/Barney/2014-08-10-184001.inProgress/38868 CAA-6167-40B8-8F15-BF798FADF283/HD2/Users/gj/Documents/2013.partial.mbox
    Aug 10 19:01:03 Barney.local com.apple.backupd[9571]: Copied 9 items (16.82 GB) from volume HD2. Linked 21.
    Aug 10 19:01:03 Barney.local backupd[9571]: Metadata.framework [Error]: MDBackupCancel failed:-1 (4) (os/kern) invalid argument
    Aug 10 19:01:03 Barney.local com.apple.backupd[9571]: Copy stage failed with error:28
    Aug 10 19:01:04 Barney.local com.apple.backupd[9571]: Backup failed with error 28: 28
    What I'm interpreting here is that initially TM says there isn't anything to copy from HD2, but then spends about 3.5 minutes copying a very large file from HD2 and then files due to being out of space.
    Why did TM not realise this file existed in the first place?
    Thanks for any help.
    Steve

    About TM "Backup Drive is Full"
    Alert TM only deletes older files if they have been deleted from the source and when TM needs space on the backup drive for a new incremental backup. Time Machine "thins" it's backups; hourly backups over 24 hours old, except the first of the day; those "daily" backups over 30 days old, except the first of the week. The weeklies are kept as long as there's room.
    So, how long a backup file remains depends on how long it was on your Mac before being deleted, assuming you do at least one backup per day. If it was there for at least 24 hours, it will be kept for at least a month. If it was there for at least a week, it will be kept as long as there's room.
    Note, that on a Time Capsule the sparsebundle grows in size as needed, but doesn't shrink. Thus, from the user's view of the TC it appears that no space has been freed, although there may be space in the sparsebundle.
    Once TM has found it cannot free up enough space for a new backup it reports the disk is full. You can either erase the backup drive and start your backups anew or replace the drive with a larger drive.

  • Time Machine error - can't make first backup

    I can't get Time Machine to make the first back up: I tried wirelessly and it reported a "Time Machine Error" after about 112GB of 270GB transfer, so I tried again via ethernet cable and again it failed with the same error message at about the same point.
    So what do I do now? There is no way that I can see to know what is causing the error - there is no error number nor detail in the error message: +Time Machine Error. Unable to complete backup. An error occurred while copying files to the backup volume.+
    Any help gratefully received.

    joecmac wrote:
    How can you search the system log to figure out what is causing the failure?
    Hi joemac
    First open the Utilities folder and then open the Console. You'll see various logs - I took the system log, so that I could see what had happened across the whole system. There's a mass of info, going back in time, so it's very very helpful if you know approximately what time the event took place. I did, because the backup failed before my eyes at 10.02 PM.
    I saw this message - I've edited out my computer's name and highlighted the location and the file name that caused the failure:
    8/28/08 10:02:59 PM /System/Library/CoreServices/backupd[26663] Error: (-36) copying /Users/~/Library/Preferences/IsmTempFile/ns14426860.tmp to /Volumes/Backup of ~ iMac/Backups.backupdb/~ iMac/2008-08-28-164831.inProgress/.../Macintosh HD/Users/~/Library/Preferences/IsmTempFile
    I googled the file name to see what it was - it turns out to be something generated by my scanner and not critical according to posters on various forums.
    I then went to the location (User/~/Library/Preferences), and deleted the file.
    Then I tried another initial backup and it worked.
    Hope this helps.

  • Restore from time machine does not list all my backups.  I know they exist but there dates are not present on the restore list.  Any help appreciated.

    Restore from time machine does not list all my backups.  I know they exist but their dates are not present on the restore list.  Any help appreciated.  If I must use one of these older dates to restore, how do I then get the more current data off time machine?

    Ok, so am i correct in saying that the steps to fix are as follows.
    That's one option, but not what I meant by restoring in the time-travel view. The latter is what you get when you enter Time Machine.
    is the fresh install not going to be able to "see" the time machine backups that I have at the moment.
    It should, but sometimes people report that it fails. I'm not sure why that happens.

  • Time Machine -- can't access parts of backups

    Prior to upgrading my MacBook Air to Yosemite, I made a Time Machine backup, removed temporary stuff I didn't think I'd need any more, and made a bootable clone of Mavericks using SuperDuper!  The upgrade went fine, but after a while I realized one of the things I'd removed (Adobe Lightroom catalog, having transferred all the image files from the MacBook Air to my desktop machine) contained some information I needed.  My attempts to restore it have run into an odd problem, and I'm hoping someone has some ideas that can help me.
    I have the backup disk connected, and when I start up the Time Machine application it shows the expected backups in the "ruler" along the right-hand edge of the screen.  However, for the most part, I cannot "go back in time" to find the files I want from before I deleted them.  What I mean is that, for most locations I select from Finder's sidebar, the "backwards and forwards" buttons are grayed-out and inaccessible.  For a few locations (Desktop, and the system Applications folder) the buttons work as expected and I can access any backup date I wish.  For a few others (e.g. "All My Files") the "backwards" button is available but clicking it takes me to the very first backup stored (8 months old) and "forwards" takes me to "Today (Now)".  None of the intervening backups are available for that location.
    I've used the Terminal app to navigate down the directory hierarchy of the backups on the Time Machine volume.  I can find the files I want there, so it's not like Time Machine had failed to back them up.  However, it refuses to show them.  I tried using the Terminal to copy the files back under my home directory, but the filesystem ACLs and extended attributes were causing problems (Lightroom thought it didn't have write permission).  Deleting the ACSs and xattrs got Lightroom to run, but it's clearly confused (shows blank thumbnails, has exif data but not captions) so something's not right.
    Wondering if this is a Yosemite issue, I rebooted the machine onto the Mavericks clone and tried running Time Machine there.  I get the same results.
    Someone at work suggested that leaving the Time Machine app running for an extended period of time might fix the problem.  I've had it running for 7 hours now and while a few more locations started working, the ones I want aren't.
    Anyone know what's going on and how to fix it?

    Even weirder -- the problem I described above happens only with certain windows. WIth others, I can open the earlier backups.

Maybe you are looking for

  • Problem with repaired neo fis2r

    I am experiencing performance problems with my neo tha t I am not sure where to begin trouble shooting. I had an video card falure(delaminated pin on agp ) which resulted in damage to the agp slot I rma 'd my neo and it returned marked repaired with

  • Read words from text file by delimiter as columns and rows

    Hi All, I need your help as i have a problem with reading string by delimiter. i have used various tech in java, but i can not get the result as expected. Please help me to get the string from text file and write into excel . i have used a text file.

  • Profit Center updates

    Hi, I've got a number of records that have profit centers updated at the G/L account level but not at the customer account type level. How do I allocate these profit centers to the customer accounts in table BSEG ? I understand that there is a normal

  • VBS - Having issues trying to delete duplicate UEFI firmware objects in BCM/NVRAM

    We've been using SCCM 2012 R2 to test deployments of Window 8.1 to UEFI-enabled Lenovo laptops. We found that when you image these laptops over and over again a new "Windows Boot Manager" entry is created as a boot option each time. After much hair p

  • RoboHelp 9 - Enabling the cookie secure flag

    Hello All - Have a question about RoboHelp 9 and a security vulnerability.  We discovered a vulnerability in the webhelp output we produce so I am starting here.  The site requires authentication and then passes it into the page, so we believe that R