Time Machine Freezes During Backup!

Hi there,
When I back up my computer for the first time using Time Machine, it gets to around 53.2 GB. After that, it sits there with the blue progress bar at the same level. Then, i get a message that says I did not eject the disk properly, and then Time Machine alerts me that it could not finish the backup. NOTE: When it says the disk has not been ejected properly, I still see the disk in both Finder and disk utility. Also, I currently have the disk in 2 partitions, but I'm only using the Mac OS X (Journaled) partition for my Time Machine backups. Please help! Like I said, it seems to eject my external hard drive (Hitachi 250 GB Simple Drive) after freezing up for a while. I am able to use other things on my computer the whole time. The only application that was open during the backup was iTunes. Here is the log from Time Machine buddy:
Starting standard backup
Backing up to: /Volumes/External HD/Backups.backupdb
Backup content size: 142.3 GB excluded items size: 30.7 GB for volume Macintosh HD
No pre-backup thinning needed: 133.85 GB requested (including padding), 213.91 GB available
Waiting for index to be ready (101)
Copied 48.9 GB of 111.5 GB, 250192 of 667394 items
Stopping backupd because the backup volume was ejected!
Stopping backup.
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Error: (-36) SrcErr:NO Copying /Users/********/Library/Mail/IMAP-********@******[email protected]/INBOX.imapmbox/Attachments/3234/2 to /Volumes/External HD/Backups.backupdb/*******’s MacBook/2011-03-12-104926.inProgress/A8B8FCD0-3EA2-4A4D-B313-4A9EE0C56252/Macin tosh HD/Users/********/Library/Mail/IMAP-*********@********[email protected]/INBOX.imapmbox/Attachments/3234
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Copied 259985 files (49.5 GB) from volume Macintosh HD.
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Copy stage failed with error:11
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Backup failed with error: 27
Thank you so much!
Message was edited by: Host

As a first step, launch Disk Utility, select the backup volume, and run "Verify Disk" (NOT "Repair Disk"). It will take a long time to run, maybe hours. If any errors are found, copy all data on the device to another drive, then run "Repair Disk." Be prepared for the possibility that "Repair Disk" may destroy the volume beyond recovery. It may also fail to repair the damage, in which case you should replace the device -- DO NOT erase it and continue to use it.

Similar Messages

  • Time Machine freezes during back up to Passport Ext drive

    Time Machine freezes during first back up to My Passport Ext drive. It is a 1TB, and seems to keep stopping at 6 to 10GB stage so never actually backs up. I have excluded files to limit first backup to about 40GB.

    you sure this is a Mac Pro and not a MacBook Pro first. Most every report  of issues with bus powered like Passport are best solved using a drive case with its own power instead.

  • Time machine freezes during back-up.

    Time machine freezes during back-up. Have to unplug HD before I can regain controll over Time Machine In System Preferences. Tried loading folders the old fachion way—sometimes freezes during that also.
    At first I thought I had a bad exteral HD, but I am on my fourth and still the same problem. My first Time Machine HD (THAT WORKED) now has the same problem.
    I have been working with someone with apple support for weeks. We just replaced the interal HD, and still have the same problem. My iMac is only five months old
    Any ideas ? ? ? .

    you sure this is a Mac Pro and not a MacBook Pro first. Most every report  of issues with bus powered like Passport are best solved using a drive case with its own power instead.

  • Time Machine Freezes During Initial Backup

    I have a 500gb external Western Digital HDD I am trying to use as my Time Machine backup drive. The computer I'm using is a 24" iMac with about 250gb of data on it. The external drive is partitioned as a GUID / Mac OS Extended (Journaled).
    When I try to run the initial backup, it will randomly freeze during the process. Sometimes it gets halfway through the backup and freezes, other times, right away. Sometimes there is an error, other times there isn't.
    I have tried re-partitioning the drive many times, manually starting the backup and also letting the backup start on its own. All of my applications are closed when the backup begins, but no matter what I do, I cannot get the initial backup process to complete.
    Ironically, I had the same problem on ANOTHER iMac of mine, with the same model Western Digital drive. The backup would freeze randomly during the initial process but I would keep manually re-starting the backup until it magically finished the backup. Now that computer seems to be working fine.
    However, I still can't get this other iMac to work. I find it strange that two separate computers with two separate 500gb Western Digital drives would have the same problem with Time Machine, unless the problem is with Time Machine itself.
    Any ideas out there how to resolve this?

    Bruno321 wrote:
    However, I still can't get this other iMac to work. I find it strange that two separate computers with two separate 500gb Western Digital drives would have the same problem with Time Machine, unless the problem is with Time Machine itself.
    Why do you assume it's TM, not WD?
    There are many possibilities.
    Did you completely erase the drive before formatting it? Sometimes the utilities, etc., that come on new drives can interfere with TM.
    Is your iMac an Intel? If it's an older PPC, you need the Apple Partition Map, not GUID.
    Is this USB or FireWire? USB is often much slower and less reliable.
    If it's USB, does it have it's own power, or does it draw from your Mac? Often there's just barely enough to run a drive; if you have another USB peripheral, it can take enough power to interfere with the disk.
    Does it have an automatic "spin down" feature? If so, can you disable it?
    Does it have the latest updates? I thing I saw a post here recently that a WD update fixed, but I can't find it now.
    Are you running any anti-virus scanning? If so, exclude your TM drive from it.
    Sometimes excluding it from Spotlight as well, at least during a large initial backup, can prevent conflicts between TM and Spotlight.

  • Time Machine freezes during automated backups

    I have a Mac Pro running Mac OS 10.6.4 that freezes during incremental time machine backups. The initial backup will run fine, but during a subsequent backup the machine will always lock up and need to be restarted.
    I've tried repairing the permissions looking for trouble in log files, but haven't had any luck.
    Any ideas?

    thatweskid wrote:
    I have a Mac Pro running Mac OS 10.6.4 that freezes during incremental time machine backups. The initial backup will run fine, but during a subsequent backup the machine will always lock up and need to be restarted.
    I've tried repairing the permissions looking for trouble in log files, but haven't had any luck.
    Try verifying your internal HD, per #A5 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum). If that fails, you'll have to use your Install disc to repair it, per the yellow box there.

  • Time Machine Freezes during full backup

    I just got a new MacBook Pro. I am trying to create an initial Time Machine full backup.
    The process freezes after processing 6.39GB out of 462.76GB. Further, Time Machine
    also globally freezes after the following steps:
    Reboot
    Try full backup
    -- it freezes
    Stop backup
    -- backup stops
    Try to start backup again
    TimeMachine is now completely frozen. Further, all the top-right menus seem frozen.
    Try to restart machine
    Machine cannot completely shutdown -- it stays in a zombie state trying to shutdown forever
    Force shutdown (pressing power button continously until the machine shuts down).
    I've tried this process about 10 times.
    Same behavior using 4 different types of backup disks.
    (network attached via afs, direct usb, direct fire-wire).
    Here's the console output is below.
    The "freezing" seems to coincide with the output of:
    "kernel[0]: AppleVTD: waiting space (512)"
    Does anybody have any suggestions on how to fix this problem?
    Thanks!
    Luis.
    ====== Console output======
    10/23/12 12:14:48.677 AM com.apple.backupd[1052]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    10/23/12 12:14:48.700 AM com.apple.backupd[1052]: Ownership is disabled on the backup destination volume.  Enabling.
    10/23/12 12:14:49.283 AM com.apple.backupd[1052]: Forcing deep traversal on source: "Macintosh HD" (mount: '/' fsUUID: 6C558E68-8F4B-337F-8BB6-6721988887F1 eventDBUUID: 54A53EDD-B4AA-4C26-830B-37AE17F0CA69)
    10/23/12 12:14:53.278 AM coreservicesd[24]: Received request to reset fmod watch. Latest received id is 14820719323154. Latest sent id is 14820719323154
    10/23/12 12:14:53.463 AM com.apple.backupd[1052]: Backup content size: 440.85 GB excluded items size: 20.16 GB for volume Macintosh HD
    10/23/12 12:14:53.464 AM com.apple.backupd[1052]: Found 1095112 files (420.69 GB) needing backup
    10/23/12 12:14:53.465 AM com.apple.backupd[1052]: 504.83 GB required (including padding), 7.41 TB available
    10/23/12 12:14:53.471 AM com.apple.backupd[1052]: Waiting for index to be ready (100)
    10/23/12 12:15:31.916 AM mdworker[1136]: Unable to talk to lsboxd
    10/23/12 12:15:31.977 AM sandboxd[1137]: ([1136]) mdworker(1136) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:15:32.000 AM kernel[0]: Sandbox: sandboxd(1137) deny mach-lookup com.apple.coresymbolicationd
    10/23/12 12:16:01.962 AM mdworker[1142]: Unable to talk to lsboxd
    10/23/12 12:16:02.019 AM sandboxd[1143]: ([1142]) mdworker(1142) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:16:02.000 AM kernel[0]: Sandbox: sandboxd(1143) deny mach-lookup com.apple.coresymbolicationd
    10/23/12 12:17:03.350 AM mdworker[1153]: Unable to talk to lsboxd
    10/23/12 12:17:03.355 AM mdworker[1154]: Unable to talk to lsboxd
    10/23/12 12:17:03.433 AM sandboxd[1155]: ([1153]) mdworker(1153) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:17:03.441 AM sandboxd[1155]: ([1154]) mdworker(1154) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:17:03.000 AM kernel[0]: Sandbox: sandboxd(1155) deny mach-lookup com.apple.coresymbolicationd
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (463)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (128)
    10/23/12 12:19:04.717 AM mdworker[1168]: Unable to talk to lsboxd
    10/23/12 12:19:04.721 AM mdworker[1167]: Unable to talk to lsboxd
    10/23/12 12:19:04.782 AM sandboxd[1169]: ([1168]) mdworker(1168) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:19:04.788 AM sandboxd[1169]: ([1167]) mdworker(1167) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:19:04.000 AM kernel[0]: Sandbox: sandboxd(1169) deny mach-lookup com.apple.coresymbolicationd
    =====

    Please read this whole message before doing anything.
    This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
    Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
    When you see the gray Apple logo, release the shift key.
    If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    *Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.
    Test while in safe mode. Same problem?
    After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Time Machine stuck during backup

    From December 28 to January 13 my Time Machine functioned without issue, using an external Seagate Free Agent Drive (300 GB) with a 150 GB partition devoted to TM. For whatever reason I didn't happen to connect the drive from the 13th to the 16th, and now it appears to be freezing during the preparation process or very early in the backup.
    I've looked at some of the non-complete packages to try and ascertain the problem - so far it appears to always hang while backing up the Applications folder. Why it is re-backing up this whole folder at once is beyond me, as I'm only aware of one program I've recently updated - Flip4Mac. Incidentally, this was the program is was halting on initially - so I added that to the exclude list. Next go at it, and its stuck on a different program. Then another. Then another.
    Do I really need to exclude my whole Applications folder? That seems a bit counterintuitive to me.

    I've discovered the culprit after some additional searching here. Apparently Time Machine does not function correctly while the iSight is enabled. In the past I've had no trouble with Time Machine running in the background with a variety of other processes ongoing, but apparently this one is problematic. After quitting Skype I've found that backups completed quickly and painlessly. Hopefully this post is helpful to others as well, and hopefully Apple addresses this - at least through improving Time Machine's dreadfully horrible Help files.

  • Time Machine stalls during backup to external HD

    About a month ago, Time Machine began to stall when attempting to backup to my external HDD. Now when I attempt to backup, the progress will reach ~3 KB/4GB and will stop. I have no idea what the problem is or how to fix it.
    I have tried running repair disk on my external hard drive, i was able to backup to the point of 1.58GB/4.09 GB before the progress stalled. I performed a search in console for "backup" and found an error that occurred 3 hours after the backup was started. This was the error "7/28/12 3:15:00.439 AM com.apple.var-db-shadow-backup: Error adding file shadow". I dont know exactly what it means or what to do about it.

    Jul 30 19:06:13 Users-MacBook-Pro com.apple.backupd[3973]: Starting standard backup
    Jul 30 19:06:13 Users-MacBook-Pro mtmd[2561]: Set snapshot time:1343689575 (current time:1343689573)
    Jul 30 19:06:13 Users-MacBook-Pro com.apple.backupd[3973]: Backing up to: /Volumes/Iomega HDD/Backups.backupdb
    Jul 30 19:06:20 Users-MacBook-Pro com.apple.usbmuxd[21]: _SendDetachNotification (thread 0x7fff72651960): sending detach for device 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
    Jul 30 19:06:20 Users-MacBook-Pro iTunes[2382]: _AMDDeviceDetached (thread 0x10fd75000): Device 'AMDevice 0x7f921e9f66b0 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 214, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' detached.
    Jul 30 19:06:20 Users-MacBook-Pro iTunes[2382]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...
    Jul 30 19:06:20 Users-MacBook-Pro ath[2407]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...
    Jul 30 19:07:06 Users-MacBook-Pro com.apple.usbmuxd[21]: _SendAttachNotification (thread 0x7fff72651960): sending attach for device 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
    Jul 30 19:07:06 Users-MacBook-Pro usbmuxd[21]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
    Jul 30 19:07:06 Users-MacBook-Pro iTunes[2382]: _AMDDeviceAttachedCallbackv3 (thread 0x10fd75000): Device 'AMDevice 0x7f921c9fa7f0 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 215, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
    Jul 30 19:07:06 Users-MacBook-Pro ath[2407]: _AMDDeviceAttachedCallbackv3 (thread 0x7fff72651960): Device 'AMDevice 0x10433b820 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 215, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
    Jul 30 19:07:06 Users-MacBook-Pro ath[2407]: _AMDDeviceAttachedCallbackv3 (thread 0x7fff72651960): Device 'AMDevice 0x104243d30 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 215, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
    Jul 30 19:07:41 Users-MacBook-Pro com.apple.usbmuxd[21]: _SendDetachNotification (thread 0x7fff72651960): sending detach for device 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
    Jul 30 19:07:41 Users-MacBook-Pro iTunes[2382]: _AMDDeviceDetached (thread 0x10fd75000): Device 'AMDevice 0x7f921c9fa7f0 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 215, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' detached.
    Jul 30 19:07:41 Users-MacBook-Pro iTunes[2382]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...
    Jul 30 19:07:41 Users-MacBook-Pro ath[2407]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...
    Jul 30 19:08:23 Users-MacBook-Pro com.apple.backupd[3973]: 4.57 GB required (including padding), 213.21 GB available
    Jul 30 19:10:28 Users-MacBook-Pro com.apple.usbmuxd[21]: _SendAttachNotification (thread 0x7fff72651960): sending attach for device 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
    Jul 30 19:10:28 Users-MacBook-Pro usbmuxd[21]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
    Jul 30 19:10:28 Users-MacBook-Pro ath[2407]: _AMDDeviceAttachedCallbackv3 (thread 0x7fff72651960): Device 'AMDevice 0x104338da0 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 216, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
    Jul 30 19:10:28 Users-MacBook-Pro iTunes[2382]: _AMDDeviceAttachedCallbackv3 (thread 0x10fd75000): Device 'AMDevice 0x7f921ed04060 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 216, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
    Jul 30 19:10:29 Users-MacBook-Pro ath[2407]: _AMDDeviceAttachedCallbackv3 (thread 0x7fff72651960): Device 'AMDevice 0x1040be1e0 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 216, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
    Jul 30 19:11:03 Users-MacBook-Pro com.apple.usbmuxd[21]: _SendDetachNotification (thread 0x7fff72651960): sending detach for device 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
    Jul 30 19:11:03 Users-MacBook-Pro iTunes[2382]: _AMDDeviceDetached (thread 0x10fd75000): Device 'AMDevice 0x7f921ed04060 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 216, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' detached.
    Jul 30 19:11:03 Users-MacBook-Pro iTunes[2382]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...
    Jul 30 19:11:03 Users-MacBook-Pro ath[2407]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...

  • Time Machine Freezes on Backup

    I am trying to back my imac up for the first time using Time Machine (10.9 Mavericks) however it keeps freezing at 15.17gb and won't move on from there.
    I am backing up to a Western Digital My Passport Ultra drive formatted to Mac OS Extended (Journaled) and it's Partition Map Scheme is GUID Partition Table.
    Please Help,
    Harry

    See C1 in the first linked article.
    Time Machine Troubleshooting
    Time Machine Troubleshooting Problems

  • Time Machine crashing during backup

    I have been having issues with TM for the past 2-3 days. It worked fine for the past year and has suddenly stopped working and generating errors after every attempt. I have verified, repaired permissions on both my internal HD and the Lacie 1 TB external drive (partitioned into 2x500G, one for TM and one for media). I have also erased the partition and resetup TM but still no luck. The backup seems to fail after copying 1.8GB of data of 178 GB. I have attached a copy of the log from Time Machine Buddy.
    Thanks for any help.
    Starting standard backup
    Backing up to: /Volumes/Time Machine Backup /Backups.backupdb
    Error parsing SystemMigration.log to determine source volume of system migration.
    No pre-backup thinning needed: 198.26 GB requested (including padding), 431.11 GB available
    Waiting for index to be ready (101)
    backupd(317,0xb0185000) malloc: * mmap(size=2720010240) failed (error code=12)\n* error: can't allocate region\n* set a breakpoint in mallocerrorbreak to debug
    backupd(317,0xb0185000) malloc: * mmap(size=2720010240) failed (error code=12)
    * error: can't allocate region
    * set a breakpoint in mallocerrorbreak to debug
    terminate called after throwing an instance of 'std::bad_alloc'
    what(): std::bad_alloc
    2010-04-21 22:44:23.453 ReportCrash[320:1207] Saved crash report for backupd[317] version ??? (???) to /Library/Logs/DiagnosticReports/backupd2010-04-21-224423localhost.crash

    Going to give the hardware test a run to see what it comes back with. I am quite confused as I am not seeing any other issues with the computer.
    I have been working on computers for years and still do it for a living and can't figure this out for the life of me (The reason I use a mac is because I deal with PC issues all day long). I honestly am considering doing the actual complete wipe and reinstall even though its probably not going to help. I'm at a loss here and its frustrating because I deleted all my old backups as I originally thought it was the HD causing the problem and tried formatting the drive.
    Thanks for all your help...Your assistance here is invaluable and you are great at articulating troubleshooting steps.
    Crash Log:
    Process: backupd [225]
    Path: /System/Library/CoreServices/backupd
    Identifier: backupd
    Version: ??? (???)
    Code Type: X86 (Native)
    Parent Process: launchd [1]
    Date/Time: 2010-04-22 19:16:59.553 -0600
    OS Version: Mac OS X 10.6.3 (10D578)
    Report Version: 6
    Exception Type: EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Crashed Thread: 2
    Application Specific Information:
    abort() called
    Thread 0: Dispatch queue: com.apple.main-thread
    0 libSystem.B.dylib 0x94b632fa machmsgtrap + 10
    1 libSystem.B.dylib 0x94b63a67 mach_msg + 68
    2 com.apple.CoreFoundation 0x968f800f __CFRunLoopRun + 2079
    3 com.apple.CoreFoundation 0x968f70f4 CFRunLoopRunSpecific + 452
    4 com.apple.CoreFoundation 0x968fd034 CFRunLoopRun + 84
    5 backupd 0x0001067d 0x1000 + 63101
    6 backupd 0x00005f59 0x1000 + 20313
    Thread 1: Dispatch queue: com.apple.libdispatch-manager
    0 libSystem.B.dylib 0x94b89b42 kevent + 10
    1 libSystem.B.dylib 0x94b8a25c dispatch_mgrinvoke + 215
    2 libSystem.B.dylib 0x94b89719 dispatch_queueinvoke + 163
    3 libSystem.B.dylib 0x94b894be dispatch_workerthread2 + 240
    4 libSystem.B.dylib 0x94b88f41 pthreadwqthread + 390
    5 libSystem.B.dylib 0x94b88d86 start_wqthread + 30
    Thread 2 Crashed:
    0 libSystem.B.dylib 0x94bd04be _semwait_signalnocancel + 10
    1 libSystem.B.dylib 0x94bd03a2 nanosleep$NOCANCEL$UNIX2003 + 166
    2 libSystem.B.dylib 0x94c4b2f2 usleep$NOCANCEL$UNIX2003 + 61
    3 libSystem.B.dylib 0x94c6c9a8 abort + 105
    4 libstdc++.6.dylib 0x98c8cfda _gnu_cxx::__verbose_terminatehandler() + 433
    5 libstdc++.6.dylib 0x98c8b17a _cxxabiv1::_terminate(void (*)()) + 10
    6 libstdc++.6.dylib 0x98c8b1ba _cxxabiv1::_unexpected(void (*)()) + 0
    7 libstdc++.6.dylib 0x98c8b2b8 _gxx_exception_cleanup(_Unwind_ReasonCode, UnwindException*) + 0
    8 libstdc++.6.dylib 0x98c8b658 operator new(unsigned long) + 101
    9 libstdc++.6.dylib 0x98c8b703 operator new[](unsigned long) + 17
    10 com.apple.DesktopServices 0x903096c4 TCFURLInfo::CopyExtendedAttribute(char const*, __CFString const*, int, __CFData const**) + 430
    11 com.apple.DesktopServices 0x902c965b TCFURLInfo::CopyExtendedAttributes(__CFArray const*&, __CFArray const*&, unsigned long) const + 713
    12 com.apple.DesktopServices 0x902c8e86 TCopyItem::TCopyItem(unsigned long, TCopyQueue*, TCountedPtr<TCFURLInfo>, TCountedPtr<TCFURLInfo>, TCopyBuffer*, unsigned long) + 454
    13 com.apple.DesktopServices 0x902c89d2 TCopyReader::GetNextItem() + 1792
    14 com.apple.DesktopServices 0x902c704a TCopyReader::Read(unsigned long long, TCountedPtr<TCFURLInfo> const&, TCountedPtr<TCFURLInfo> const&) + 166
    15 com.apple.DesktopServices 0x902fd8ff TFSCopyOperation::CopyToTarget() + 613
    16 com.apple.DesktopServices 0x902ffb00 TFSCopyOperation::DoCopy(TCountedPtr<TCFURLInfo> const&) + 780
    17 com.apple.DesktopServices 0x90300170 TFSCopyOperation::Run() + 174
    18 com.apple.DesktopServices 0x902f5a05 _NodeOperation + 438
    19 backupd 0x0001978c 0x1000 + 100236
    20 backupd 0x00018c90 0x1000 + 97424
    21 backupd 0x0001325b 0x1000 + 74331
    22 backupd 0x0000d96e 0x1000 + 51566
    23 backupd 0x000089a3 0x1000 + 31139
    24 com.apple.Foundation 0x934398dc -[NSThread main] + 45
    25 com.apple.Foundation 0x9343988c _NSThread__main_ + 1499
    26 libSystem.B.dylib 0x94b90a19 pthreadstart + 345
    27 libSystem.B.dylib 0x94b9089e thread_start + 34
    Thread 3:
    0 libSystem.B.dylib 0x94b91262 _semwaitsignal + 10
    1 libSystem.B.dylib 0x94b90f1e pthread_condwait + 1191
    2 libSystem.B.dylib 0x94b92bb8 pthreadcondwait$UNIX2003 + 73
    3 ...ple.CoreServices.CarbonCore 0x94598aee TSWaitOnCondition + 126
    4 ...ple.CoreServices.CarbonCore 0x9458443d TSWaitOnConditionTimedRelative + 202
    5 ...ple.CoreServices.CarbonCore 0x9457fe0f MPWaitOnQueue + 250
    6 com.apple.DesktopServices 0x902c7ce1 TCopyQueue::Dequeue() + 69
    7 com.apple.DesktopServices 0x902c7642 TCopyWriter::GetNextItem() + 42
    8 com.apple.DesktopServices 0x902c730f TCopyWriter::Write() + 131
    9 com.apple.DesktopServices 0x902c6c25 TCopyWriter::WriteTaskProc(void*) + 75
    10 ...ple.CoreServices.CarbonCore 0x94563eb6 PrivateMPEntryPoint + 68
    11 libSystem.B.dylib 0x94b90a19 pthreadstart + 345
    12 libSystem.B.dylib 0x94b9089e thread_start + 34
    Thread 2 crashed with X86 Thread State (32-bit):
    eax: 0x0000003c ebx: 0x94bd0309 ecx: 0xb010008c edx: 0x94bd04be
    edi: 0xa0639b10 esi: 0xb01000e8 ebp: 0xb01000c8 esp: 0xb010008c
    ss: 0x0000001f efl: 0x00000247 eip: 0x94bd04be cs: 0x00000007
    ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
    cr2: 0xffe2aa10

  • Time Machine 'growing' during backup.

    I've had this issue before, but has only just become a problem.
    Basically, Time Machine starts, and (in Console) says it needs to backup 28.2MB of files ... here's the console text:
    29/08/2012 18:53:09.181 com.apple.backupd[27535]: Will copy (28.2 MB) from iMac
    29/08/2012 18:53:09.191 com.apple.backupd[27535]: Found 455 files (28.2 MB) needing backup
    29/08/2012 18:53:09.227 com.apple.backupd[27535]: 403.3 MB required (including padding), 16.93 GB available
    However, when it backs up, this size grows (it's currently counting up from about 6.95GB) until it says there's not enough room on the backup disk. If it only needs 28.2MB, why is it appearing to do a full 'first' backup?
    I now cannot backup via Time Machine, as it's saying that I don't have the space. I've tried deleting the 'in.progress' file from the backup disk, and the .plist file from the root Library directory – but no joy: it still gets bigger and BIGGER.
    Any one having the same issue?

    I've heard virtual machines can cause issues, but I don't have any!
    The only solution I've had is to manually (via TM's interface) a handful of my oldest backups. Afterwards, it backed up 58.4Gb and is working okay at the moment.
    As with your backup, it said it was backing up much more than this (around 90-100GB), despite only copying 58.4Gb. I think it's just a case of TM not deleting outdated backups effectively when disk space is tight. My TM disk was rather full – but I hoped TM would deal with that!
    I'll keep an eye on it, as much of what is backed up I wouldn't consider 'new' or altered files (many of my Apps, for instance, in the last big backup. Whether this is a Mountain Lion issue, I can't say, as it's taken two years to fill up my disk, so it's seen a few system migrations in its time.
    Anyway, I'll keep an eye on it and see what happens when my free TM space gets to around 30Gb (which is when the problem occured).

  • Time Machine error during backup

    After using my external USB drive as my backup target for several months I am not getting the following error:
    Unable to complete backup. An error occurred while copying files to the backup volume.
    My backup volume is an external USB formatted Mac OS Extended (Journaled). I've reformatted and verified the external disk. I've also checked the permissions and verified my startup disk.
    The same thing also happens on my firewire 400 external disk. I've tried the same things on that one.
    Any one got any ideas? Thank you in advance.

    You might try looking in the console log. Use the Console application in your Utilities folder. Look for entries related to the backup to see if there is more information that could give you a clue to the cause. In addition to a problem with the backup drive, the error could be caused by a corrupted file you are trying to back up.

  • Time Machine freezes at onset of first backup

    I took one of my external Lace disk drives (250 MB - with 200+ MB available) and designated it as the target drive for Time Machine. I've used this drive for over a year with no issues. Time Machine starts up, does its calculations and starts its initial backup. There is a Backups.backupdb folder created on the drive. In that folder another folder is created bearing the name of my system and within that folder there's a time stamped file (i.e., 2007-10-31-150019.InProgress) of the Kind "package". The file gets to a nominal 38.8 MB in size and that's it. I let this sit for over an hour with no progress. Attempting to stop the back up in the Time Machine System Preferences window results in a "Stopping..." message with the application just spinning its wheels. Any suggestions? Log files I can look at? Etc? Thanks!

    I am not sure what to make of this, but it appears that Time Machine is probably running into a locked file or something. I have had my backup running just fine all day, but it's currently frozen as I type this, trying to backup 20.5 MB or so of changes on my main drive.
    I have no idea how to troubleshoot this. I can see in the Console messages that Backupd started, but just gets stuck (no error) in the middle. Like so:
    10/31/07 11:48:10 PM /System/Library/CoreServices/backupd[689] Backup requested by automatic scheduler
    10/31/07 11:48:10 PM /System/Library/CoreServices/backupd[689] Starting standard backup
    10/31/07 11:48:17 PM /System/Library/CoreServices/backupd[689] Backing up to: /Volumes/Backup/Backups.backupdb
    10/31/07 11:48:19 PM /System/Library/CoreServices/backupd[689] No pre-backup thinning needed: 200.0 MB requested (including padding), 351.60 GB available
    ... and that's it. No further messages.
    What it OUGHT to look like (when working):
    10/31/07 10:48:10 PM /System/Library/CoreServices/backupd[608] Starting standard backup
    10/31/07 10:48:17 PM /System/Library/CoreServices/backupd[608] Backing up to: /Volumes/Backup/Backups.backupdb
    10/31/07 10:48:18 PM /System/Library/CoreServices/backupd[608] No pre-backup thinning needed: 240.3 MB requested (including padding), 351.68 GB available
    10/31/07 10:48:44 PM /System/Library/CoreServices/backupd[608] Copied 2565 files (72.3 MB) from volume Kidd.
    10/31/07 10:48:45 PM /System/Library/CoreServices/backupd[608] No pre-backup thinning needed: 188.7 MB requested (including padding), 351.60 GB available
    10/31/07 10:48:47 PM /System/Library/CoreServices/backupd[608] Copied 1172 files (90 KB) from volume Kidd.
    10/31/07 10:48:49 PM /System/Library/CoreServices/backupd[608] Starting post-backup thinning
    10/31/07 10:48:49 PM /System/Library/CoreServices/backupd[608] No post-back up thinning needed: no expired backups exist
    10/31/07 10:48:49 PM /System/Library/CoreServices/backupd[608] Backup completed successfully.
    When this occurs, I cannot stop the backup from the UI. I can kill backupd the 'hard way' with Activity Monitor and an Administrator force quit, but afterwards Time Machine will not backup again without more drastic measures (minimum reboot).
    I am curious if the condition will eventually fix itself once the file becomes unlocked, but I dunno if it will.

  • My 4th gen ipod won't backup after it froze during a software update to 4.3.5. I had to cancel the backup at the start of the update and now it won't let me backup to my computer, freezes during backup or says my backup is corrupted.

    I pressed 'X' during a backup after it froze during an update to software 4.3.5 and now it won't let me backup on my computer. Does anyone have any ideas? It either freezes during backup or says my 'backup is corrupted' or 'I cannot backup on my computer'. I have had to abort quite a few attempted backups since the initial problem, which I think has made it worse. I have already tried restoring my ipod, deleting the aborted backup from my preferences/devices in itunes and deleting it from my user/appdata/etc on my PC hard drive. Any ideas what to try next?

    After hours of frustration I eventually decided to restore. I lost my apps, but i didn't have many and was able to reinstall them for free. During the restore it updated my ipod to the latest software 4.3.5, which i think may have caused the initial problem, but the backup issue remains. Sometimes it stops me from syncing and other times it allows me to skip the backup, but still says that i can't backup on my computer. I'm worried that it has done something to my computer as it took me six hours to do a Bullguard scan, which only normally takes about an hour. The scan didn't come up with any viruses, but it stalled at system32 for ages. The only other thing that i can think of is that a demo CD I uploaded may have caused a problem. iTunes couldn't find a track listing for it but gave me a few different options. i thought I had to choose one to continue, so did that then changed the track details to the correct tracks. I'm now worried that may have introduced an issue or caused a glitch in iTunes. How paranoid am I sounding?  

  • Time Machine fails to backup HD and stalls computer when backing up to external HD (Western Digital WD5000MT) when using Firewire 800 but works fine using USB

    I have a mid 2012 MBP (MacbookPro9,1) running Mountain Lion 10.8.2.  When I start a Time Machine backup to an external Western Digital HD (WD5000MT) connected using a Firewire 800 cable, my open programs stop responding and in general my computer freezes up not allowing me to open activity monitor or the console utility.  I can't even shut down or restart my computer and must hard boot to reset.  Though removing the firewire cable that goes to the external HD can sometimes get my system working again.  However, the WD external HD also has a usb port and when I connect it to my computer via a USB cable, Time Machine seems to backup my system fine without stalling my computer.  This same external HD worked fine with Firewire 800 using my old late 2007 MBP running snow leopard.  I should note that my brother has the exact same model WD external HD and he also had issues with the firewire port on his MBP running mountain lion.  I have run the disk utility checking for disk/file permission errors and the drive itself seems fine.  I initially formatted that drive as ExFAT but while troubleshooting reformatted to HFS+ and still had the same issue.  I tested using a different firewire 800 cable but still had the same issue.  Can't think of anything else to do.  I don't have another firewire-compatible device to test if it is the HD vs the firewire port.   I would prefer to use the firewire port for quicker transfer speeds but I'm stuck with USB for now.  Any suggestions? 

    Maybe these will help:
    http://pondini.org/TM/Troubleshooting.html
    http://support.apple.com/kb/PH11194
    http://support.apple.com/kb/HT3275 (note - older article)
    Have you tried looking at the Western Digital web site to see if you can find anything?
    http://support.wdc.com

Maybe you are looking for

  • Iphone wont pull emails from exchange

    We are running exchange 2010, i have a iphone 3g. The account verifies fine. but when i got to pull emails it doesnt do anything. and if i try to send a email it says it cant comunicate with the server. I set up a 3gs just like i tried to set mine up

  • Question about Forte...

    Ok, I'm pretty sure this is the wrong forum to ask, but I haven't found a better one. I apologize for that. Now, I've just downloaded and installed Forte for Java CE. It installs fine, when I run it it shows the nice pic where it loads and initialize

  • Deployment analysis error

    We made sure all of addressing was relative and changed the directory name of our code to conform to our ClearCase naming conventions. I load the ws file and the main sequence after which the tests come up and run normally. However we are having buil

  • External Hard Drive Enclosure.

    Hello, I would like to take the hard drive out of my macbook which has a damaged display and put it in a case so I can use it as an external hard drive. Which case should I buy? What other adapters or cables will I need? Thank you.

  • Access Connections 5 and up issues

    Hi, For years our organization has been using Access Connections 4.52 flawlessly.  Recently we purchased a boat load of R500 notebooks.  At this point, we were forced to upgrade to version 5.20 as 4.52 will not recognize the wireless card. With 4.52,