Time Machine Hangs - Help!

I am trying to run Time Machine for the first time on this PowerBook G4.
Three times now backup has gotten to 11.07GB of 36.72GB, then stops progressing.
The backup drive is a 500 GB Maxtor USB drive that I used Disk Utility on to erase and format as Mac OS Extended (Journaled).
The widget "Time Machine Buddy" shows the following:
Starting standard backup
Backing up to: /Volumes/Backup Drive/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Event store UUIDs don't match for volume: HD
Backup content size: 36.8 GB excluded items size: 33.1 MB for volume HD
No pre-backup thinning needed: 44.07 GB requested (including padding), 465.61 GB available
Waiting for index to be ready (909 > 0)
Any help or insight would be appreciated. Thanks.

Very curious. I'd guess your CPU usage is running at or near 100% at all times, no?
Some threads here suspect memory, though, for Bus Errors. Have you added memory, especially 3rd party? You might try running hardware diagnostics. If you're not having any other trouble, this seems doubtful.
Mdworker is associated with Spotlight. First thought here is, have you excluded your TM drive/partition from Spotlight? If no, do so, at least temporarily. (Use System Preferences/Spotlight, then it's Privacy pane.)
If it's trying to index your TM drive and repeatedly crashing, writing crash logs, and restarting, it's likely using-up most of your CPU, slowing the backup to a near halt. Actually, you might want, temporarily, to exclude EVERYTHING from Spotlight -- it's probably completely confused.
You can use the Activity Monitor app (Applications/Utilities) to see how much CPU is being used by mdworker, etc. Select All Processes, then sort by the CPU column.
Once it's under control, start TM again. If your backup then runs normally, that will confirm the problem, and you can begin to remove things from the exclusion list.
You've also probably got a whole passel (technical term) of crash logs and huge system logs. You can clean them out via the Console app, or with OnyX or similar apps.

Similar Messages

  • I have been using time machine to back up my Mac Book Pro 3.1 to my Time Capsule. Now the Time machine hangs up on "calculating time remaining".

    I have been using time machine to back up my Mac Book Pro 3.1 to my Time Capsule. Now the Time machine hangs up on "calculating time remaining".
    Mac Book Pro - 3.1-15-inch  2.4/2.2GHz), Processor 2.2 GHz Intel Core 2 Duo
    Operating system : OS X 10.10.1
    Time Machine Version 1.3, Copyright 2007-2014 Apple Inc., Modified Tuesday, September 9, 2014 at 6:03 PM
    Time Capsule: 500 GB C 2007
    This Time Machine software worked satisfactory until Monday Nov, 10 2014 and I have backups until that time. For several years, the software deleted the oldest back up to save the latest one. This is acceptable to me as I have off site storage that is updated every 3 months. How do I get Time machine working again?

    I have spent a couple of days trying to respond to Linc Davis. Finally I figured it out . The following is a copy of data from my console from the initiation of a time machine backup until it gets stuck trying to calculate the time remaining. There is no indication that anything starts saving.  I copied about 3 minutes of data. This is probably way too much data, but I do not know what is relevant.
    Thanks for the help,
    calcool
    12/22/14 3:16:54.655 PM com.apple.backupd[551]: Starting manual backup
    12/22/14 3:16:55.057 PM com.apple.backupd[551]: Attempting to mount network destination URL: afp://”name”%20”lastname”@Home%20Network%20Time%20Capsule._afpovertcp._tcp.loca l./Time%20Capsule
    12/22/14 3:16:57.262 PM mds[33]: (Volume.Normal:2464) volume:0x7fed5ab54000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Time Capsule
    12/22/14 3:16:57.565 PM com.apple.backupd[551]: Mounted network destination at mount point: /Volumes/Time Capsule using URL: afp://”name”%20”lastname”@Home%20Network%20Time%20Capsule._afpovertcp._tcp.loca l./Time%20Capsule
    12/22/14 3:17:08.000 PM kernel[0]: hfs: mounted Backup of “name” “lastname”’s MacBook Pro on device disk3s2
    12/22/14 3:17:09.625 PM com.apple.backupd[551]: Disk image /Volumes/Time Capsule/”name” “lastname”’s MacBook Pro (2).sparsebundle mounted at: /Volumes/Backup of “name” “lastname”’s MacBook Pro
    12/22/14 3:17:11.112 PM com.apple.backupd[551]: Backing up to /dev/disk3s2: /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb
    12/22/14 3:17:24.931 PM “name”[593]: audit warning: soft /var/audit
    12/22/14 3:17:24.944 PM “name”[594]: audit warning: allsoft
    12/22/14 3:17:24.958 PM “name”[596]: audit warning: closefile /var/audit/20141222201654.20141222201724
    12/22/14 3:17:26.544 PM com.apple.backupd[551]: Event store UUIDs don't match for volume: Macintosh HD
    12/22/14 3:17:34.767 PM com.apple.backupd[551]: Deep event scan at path:/ reason:must scan subdirs|new event db|
    12/22/14 3:17:34.768 PM com.apple.backupd[551]: Reading cached event database from: /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb/”name” “lastname”’s MacBook Pro (2)/2014-12-22-151726.inProgress/F85FEA51-E137-471A-84DA-A2C00E4ECB42/.1BEF88C6 -20C3-3DDC-AE30-05EAB2AFCC15.eventdb
    12/22/14 3:17:38.115 PM com.apple.backupd[551]: Using cached disk scan
    12/22/14 3:17:39.114 PM com.apple.backupd[551]: Saved event cache at /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb/”name” “lastname”’s MacBook Pro (2)/2014-12-22-151726.inProgress/5BC46A53-25E8-4C4A-8947-AFB221D1FA0C/.1BEF88C6 -20C3-3DDC-AE30-05EAB2AFCC15.eventdb
    12/22/14 3:17:39.355 PM com.apple.backupd[551]: Not using file event preflight for Macintosh HD
    12/22/14 3:19:14.782 PM CoreServicesUIAgent[294]: unexpected message <OS_xpc_error: <error: 0x7fff77befc60> { count = 1, contents =
                "XPCErrorDescription" => <string: 0x7fff77beff70> { length = 18, contents = "Connection invalid" }
    }>
    12/22/14 3:20:15.207 PM locationd[182]: Location icon should now be in state 'Active'
    12/22/14 3:20:17.267 PM locationd[182]: Location icon should now be in state 'Inactive'
    12/22/14 3:20:17.884 PM locationd[182]: Location icon should now be in state 'Active'
    12/22/14 3:20:18.483 PM sandboxd[296]: ([310]) com.apple.metada(310) deny mach-lookup com.apple.cfnetwork.cfnetworkagent
    12/22/14 3:20:21.646 PM com.apple.metadata.SpotlightNetHelper[310]: [SLSUGGESTIONS] Location managed failed with error Error Domain=kCLErrorDomain Code=0 "The operation couldn’t be completed. (kCLErrorDomain error 0.)"
    12/22/14 3:20:23.892 PM WindowServer[143]: disable_update_timeout: UI updates were forcibly disabled by application "Spotlight" for over 1.00 seconds. Server has re-enabled them.
    12/22/14 3:20:26.526 PM WindowServer[143]: common_reenable_update: UI updates were finally reenabled by application "Spotlight" after 3.63 seconds (server forcibly re-enabled them after 1.00 seconds)
    12/22/14 3:20:28.298 PM sandboxd[296]: ([310]) com.apple.metada(310) deny mach-lookup com.apple.cfnetwork.cfnetworkagent
    12/22/14 3:20:29.094 PM com.apple.xpc.launchd[1]: (com.apple.quicklook[599]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
    12/22/14 3:20:30.670 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
    12/22/14 3:20:30.670 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
    12/22/14 3:20:32.294 PM com.apple.InputMethodKit.UserDictionary[600]: -[PFUbiquitySwitchboardEntryMetadata setUseLocalStorage:](808): CoreData: Ubiquity:  “name”~00000000-0000-1000-8000-001B63947FCF:UserDictionary
    Using local storage: 1
    12/22/14 3:20:32.317 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
    12/22/14 3:20:32.769 PM locationd[182]: Location icon should now be in state 'Inactive'
    12/22/14 3:20:34.580 PM Console[601]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
    12/22/14 3:20:35.540 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    12/22/14 3:20:36.388 PM com.apple.xpc.launchd[1]: (com.apple.auditd[604]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.auditd
    12/22/14 3:20:36.693 PM “name”[608]: audit warning: soft /var/audit
    12/22/14 3:20:36.718 PM “name”[607]: audit warning: allsoft
    12/22/14 3:20:37.045 PM “name”[610]: audit warning: closefile /var/audit/20141222201724.20141222202036
    12/22/14 3:20:37.438 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
    12/22/14 3:20:42.437 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
    12/22/14 3:20:42.437 PM QuickLookSatellite[611]: Invalid Connection ID 0
    12/22/14 3:20:42.477 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
    12/22/14 3:20:42.477 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
    12/22/14 3:20:42.612 PM QuickLookSatellite[611]: [QL] No sandbox token for request <QLThumbnailRequest stackshot.log>, it will probably fail
    12/22/14 3:20:42.613 PM QuickLookSatellite[611]: [QL] No sandbox token for thumbnail request file:///Library/Logs/stackshot.log, it will probably fail
    12/22/14 3:20:42.615 PM QuickLookSatellite[611]: [QL] No sandbox token for request <QLThumbnailRequest stackshot-syms.log>, it will probably fail
    12/22/14 3:20:42.615 PM QuickLookSatellite[611]: [QL] No sandbox token for thumbnail request file:///Library/Logs/stackshot-syms.log, it will probably fail

  • Time Machine hanging, I/O error

    Hi, I'm having problems with Time Machine hanging partway through a backup to an external Firewire HD. I've tried repartitioning the drive, turning off Spotlight. I tried zeroing out the partition that I'm trying to back up into and ended up with Disk Utility hanging. Does this mean, as I suspect, that the drive is dying?
    A sample of Console output during attempted backup looks like this:
    4/30/14 7:52:30.000 PM kernel[0]: disk1s3: I/O error.
    4/30/14 7:53:00.000 PM kernel[0]: disk1s3: I/O error.
    4/30/14 7:54:22.000 PM kernel[0]: IOSCSIPeripheralDeviceType00::setPowerState(0xdc880163fa41ee73, 3 -> 2) timed out after 102005 ms
    4/30/14 7:56:04.000 PM kernel[0]: IOSCSIPeripheralDeviceType00::setPowerState(0xdc880163fa41ee73, 2 -> 4) timed out after 101973 ms
    4/30/14 7:57:30.000 PM kernel[0]: disk1s3: I/O error.
    4/30/14 7:57:30.151 PM com.apple.backupd[326]: Copied 92.12 GB of 170.2 GB, 879310 of 1029040 items
    4/30/14 8:03:05.000 PM kernel[0]: disk1s3: I/O error.
    4/30/14 8:03:35.000 PM kernel[0]: disk1s3: I/O error.
    While trying to zero out the partition I got similar messages:
    5/1/14 3:32:06.468 AM fseventsd[48]: read_disk_log: problems with history file: /Volumes/Backup Partition/.fseventsd/000000000072fd18 (fd -1, errno 5 ; is_reg 0; uid 0/0 gid 0/0)
    5/1/14 3:40:52.866 AM Google Chrome Helper[638]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd. : LSXPCClient.cp #426 ___ZN26LSClientToServerConnection21setupServerConnectionEiPK14__CFDictionary_bl ock_invoke() q=com.apple.main-thread
    5/1/14 3:40:52.867 AM Google Chrome Helper[638]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd.
    5/1/14 3:40:52.881 AM Google Chrome Helper[638]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
    5/1/14 3:42:02.821 AM ntpd[118]: ntpd: time set -0.525679 s
    5/1/14 3:42:02.858 AM com.apple.time[235]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
    5/1/14 3:57:36.000 AM kernel[0]: disk1s3: I/O error.
    5/1/14 3:58:06.000 AM kernel[0]: disk1s3: I/O error.
    5/1/14 3:58:36.000 AM kernel[0]: disk1s3: I/O error.
    5/1/14 3:59:06.000 AM kernel[0]: disk1s3: I/O error.
    Thanks in advance for any help.

    Hi Tom, Mr. Fore,
    Thanks for your quick replies. I thought since I had the Canon on its own port it would avoid the conflicts noted in the forum, but if there's only one bus that would explain things. Bummer. It's too much of a nuisance to move large files around so capturing to the internal HD isn't a long-term solution even if I got it working (that still produced the timecode problem).
    I guess I have two weeks to search for a fix or a new camera before the store return policy expires.

  • Time Machine Weirdness - HELP!

    Using a mid 2010 MacBook Pro with 10.9.4 installed, all updates present. Attached a WD 750GB My Passport to the Macbook Pro, reformatted the passport to MAC OSX Extended Journaled. Check both MacBook Pro and Passport with Techtool Pro 7 latest version plus Disk Warrier 4.4... Everything seems to check out on both notebook and External HD.
    Opened Time Machine in preferences, chose the WD / HD and began an initial back up on Sunday morning. It's now 12 noon on Monday and I only have 117 GB backed up so far...
    This is when it gets weird. I've turned off the screensaver, put everything to the max in terms of power, clicked the "put the hard disk to sleep" to off etc.etc. and just dimmed the screen thinking the hard disk would stay awake.
    However, every few minutes  Time Machine hangs and stops backing up files... If I walk over and click the arrow on the system preferences box, which is open to the Time Machine box showing progress, then magically, it will start backing up again. I click the box itself not any buttons. Few minutes later, I go back, it's hung, I click on the box, it starts again. This is just not the way it was intended to work... BTW, Don't think it's the My Passport... I use my passports on my iMac (2 of them backing up in tandem) my other brand new MacBook Pro retina and my daughter's macbook.
    My worst nightmare is to have this initial back up go on till Wednesday and then it gives me an error message,
    Anyone seen this before, anyone got any ideas? I'm stumped!

    These instructions must be carried out as an administrator. If you have only one user account, you are the 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.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the word "Starting" (without the quotes.) You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard."
    Each message in the log begins with the date and time when it was entered. Note the timestamp of the last "Starting" message that corresponds to the beginning of an an abnormal backup. Now
    CLEAR THE WORD "Starting" FROM THE TEXT FIELD
    so that all messages are showing, 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 to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    ☞ If all you see are messages that contain the word "Starting," you didn't clear the text field.
    ☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. Don't post more than is requested.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    ☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Time machine restore help

    I've recently been having issues with my early 2008 black Macbook. I ran the apple HW diagnostics and determined it is a bad hard drive. I went out and bought a new 500GB SATA HD, and attempted to restore my system using a Time Machine backup. I booted into the Leopard Disc that came with my computer, formatted the drive, and ran the Time machine restore. Everything appeared to go fine (took about 2 hours, no error messages). However, after the machine rebooted and attempted to boot into OSX an error similar to this popped up. http://img149.imageshack.us/img149/7792/pict0017lo8.jpg
    Any thoughts as to why this is happening? I don't really want to start over with a clean install, that's why I have Time Machine!
    Other information:
    My computer originally had Leopard, and was upgraded to Snow Leopard.
    I have boot camp setup on my mac for Win 7. (I know this isn't backed up or restored as part of a time machine backup, which I'm O.K. with.)
    Thanks in advance for all your help.

    Any number of possibilities. First, did you prep the drive properly:
    Extended Hard Drive Preparation
    1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger, Leopard or Snow Leopard.)
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
    Any brand new drive should be setup per the above because they usually are configured for use on PCs rather than Macs.
    Second, depends on how you went about the process of restoring your system. Select Mac Help from the Finder's Help menu and search for "time machine." Look for an article specifically about performing a full system restore. Also, see User Tips for Time Machine for help with TM problems. Also you can select Mac Help from the Finder's Help menu and search for "time machine" to locate articles on how to use TM. See also Mac 101- Time Machine.
    What you saw was a kernel panic screen. Panics at startup may be indicative of a hardware problem. You might give this a try:
    How to run hardware diagnostics for an Intel Mac
    Boot from your original OS X Installer Disc One that came with your computer. After the chime press and hold down the "D" key until the diagnostic screen appears. Run the extended tests for a minimum of two or three hours. If any error messages appear note them down as you will need to report them to the service tech when you take the computer in for repair.
    Some "common" error indicators:
    SNS - sensor error
    MEM - memory error
    HDD - hard disk drive error
    MOT - fan error
    To assure the problem isn't with your backup you might consider installing OS X by itself. If all is OK, then you can complete the TM restore using Migration Assistant.

  • HT1338 lost word document.  time machine no help.  suggestions?

    lost word document.  time machine no help. suggestions?

    Need more info. How do you think you lost a Word Document?
    Try Easy Find, Search program, and search for *.doc*. That will turn up all Word Docs with both the .DOC and .DOCX extension on your complete hard drive.
    If it is truly lost, Deleted, then you are basically SOL. Unless you do have a recent TM backup that has that file included.
    As for recovering it from TM do a search for Pondini TM FAQs.

  • Backups work, enter time machine "hangs"

    I'm having an issue with Time Machine where the backups appear to be working fine, but if I open a folder in finder, and then "Enter Time Machine", Time Machine starts with that folder "visible" but hangs (no nav buttons work, cancel and restore don't work, and I can't "navigate folders).
    The only way "out" in this case is to hit CMD-OPT-ESC, which weirdly doesn't bring up the terminate applications dialog, but simply exits Time Machine.
    If I make sure that no finder windows are open when I enter Time Machine, it appears to be working fine.
    To duplicate this, open your home folder, have Documents selected and enter time machine. Does your's hang at this point? (Hit CMD-OPT-ESC to leave Time Machine if it does hang).
    TIA for any advice/confirmation.
    Steve

    It appears I may have "misspoken" a little. Time Machine hangs on entry with no default windows too, just "not as much". I can usually move around a little before it hang, but hang it does.
    One side note (and this may cause this thread to be moved to a Leopard issue instead of time machine.
    I recently upgraded to Leopard by buying a brand new drive, installing Leopard from scratch, and gradually adding back my applications as I find I need them (the previous drive had been through 10.1 -> 10.4.11 over a couple years, and had a lot of old apps, etc I just wanted to get rid of.)
    With the new installation, it appears that occasionally (30% of the time?), when I mount/dismount .dmg images or sparseimage/sparsebundle images, the entire Mac will appear to "hang" for about 30-40 seconds, buffering input but otherwise appearing to "lock up". I have iTunes playing, and songs continue uninterrupted, but I can't do anything for this 30-40 seconds, including CMD-OPT-ESC.
    I'm thinking this could be related to the Time Machine issue except for the fact that the OS always recovers and continues normally after 30+ seconds, but Time Machine NEVER comes back.
    Thoughts? Advice?
    Thanks,
    Steve

  • Time Machine hangs at Waiting for index to be ready...help!

    Installed widget, copied messages. Searched forum and google for answers, still can't figure it out.
    Any ideas? - Thanks, Paul
    Starting standard backup
    Attempting to mount network destination using URL: afp://Paul%[email protected]/Time%20Capsule
    Mounted network destination using URL: afp://Paul%[email protected]/Time%20Capsule
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Disk image /Volumes/Time Capsule/Paul's Mac_001f5bf5d5b8.sparsebundle mounted at: /Volumes/Backup of Paul's Mac
    Backing up to: /Volumes/Backup of Paul's Mac/Backups.backupdb
    Event store UUIDs don't match for volume: Macintosh HD
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)

    Okay, still no progress on getting my Time Machine working again. The last backup was 12/2, so I've been trying for 4 days to get it going. Any other ideas?
    Starting standard backup
    Network destination already mounted at: /Volumes/Time Capsule
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Disk image /Volumes/Time Capsule/Paul's Mac_001f5bf5d5b8.sparsebundle mounted at: /Volumes/Backup of Paul's Mac
    Backing up to: /Volumes/Backup of Paul's Mac/Backups.backupdb
    Event store UUIDs don't match for volume: Macintosh HD
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)

  • Time Machine hangs...  Takes hours to do an incremental back up

    Hello All,
    I'm having trouble with Time Machine as of late. It seems to hang and not finish a backup (I'm not talking about the initial back up, I know they take a while).
    I leave my MBP running all the time (fans are on to keep it cool, over heating not an issue) and I've noticed that after the 4th day all bets are off on a reliable backup. Usually it waits till the 2 week mark then freaks out but now it's happening more often and sooner.
    I'll refrain from expressing my opinion as the Apple people don't seem to like freedom of speech as my last post got flagged when I expressed my displeasure with Snow Leopard. I'm having a lot of problems that I didn't have before the upgrade.
    To the Apple people, THIS IS A REAL ISSUE I'M HAVING; note the opening statement explaining my problem. Please don't remove my post again unless you're going to contact me with how to fix it. This should not be considered "Feed Back" as I'm asking my fellow OSX users for help. Thank you!
    Thank you for any advice or tips on how to fix the problem.

    EricB73 wrote:
    I'll refrain from expressing my opinion as the Apple people don't seem to like freedom of speech as my last post got flagged when I expressed my displeasure with Snow Leopard.
    Your best bet is to omit opinions, especially negative ones. Mainly because they don't help us help you. And if they don't get deleted, many of us who try to help people just skip them, as the posters often are more interesting in ranting than working through a problem. And "freedom of speech" doesn't apply here -- this is not a government throwing you in jail, it's Apple saying you agreed to certain terms and conditions when you signed-up to use the forums they provide at no cost. Like it or not, those are the rules.
    That said, you can use the Time Machine Buddy to navigate back a few days in your logs. Use the small navigation arrows after the title "Messages;" the arrow in front will show or drop the message detail. If you can find the most recent backup that was a problem, copy and post the messages here.
    Do the sizes of the backups seem reasonable, considering what you've added or changed since the last one? If they seem too large, that may be part of the problem. See #D4 in the Time Machine - Troubleshooting *User Tip* at the top of this forum.
    You might also try the things in #D2 of that Tip.

  • Time Machine hangs at same point during a full system restore!

    I recently had a complete crash on Mac Book Pro requiring reinstallation of Latest Leopard with Upgrade Disk. Tried to restore full system from time machine backup on time capsule, but the restore stops and does not proceed at around 37-39% complete. No error messages. On the phone with apple care, was told my back up was corrupt! Any ideas. I'm very disappointed right now, as my back ups were automatic via time machine schedule. Please help me get my system back!

    Andre,
    You could, by-pass the Full Restore process and do an Erase & Install and Migrate. Then no 'manual' restore will be necessary. Of course, if the installer is hanging as a certain point with a Full Restore then there is no guarantee that it won't during this process as well. But it's still worth a try.
    Also, if you are dealing with many GBs of user data and multiple accounts, you could have it migrate all this over in stages using Migration Assistant, rather than in one big chunk.
    *Erase, Install, & Migrate*
    A final option, reserved for last resort, is to erase the hard disk, install a fresh copy of the Mac OS, and then use Migration Assistant during the installation to restore your user accounts. This is the Mac equivalent of ‘Slash and Burn’, and really should only be necessary if you require a completely fresh start.
    Procedure:
    Verify that your Mac has uninterrupted AC power.
    For faster migration of user data, Time Capsule/AirDisk users should connect their Macs directly to their Airport device via ethernet.
    Insert your original Mac OS 10.5 Leopard DVD and reboot while holding down the “C” key.
    At the “Welcome” screen click “Continue”.
    Click “Agree” to the user agreement.
    Select you Macs internal hard disk and click “Options”.
    Select “Erase and Install”.
    Select “Mac OS Extended (Journaled)” for disk format. (Avoid selecting “Case-sensitive” unless you know what you are doing.)
    Click “OK”.
    Click “Continue”.
    At “Install Summary” click “Customize” if you would like to eliminate certain Print Drivers, Fonts, or Language packages from being installed. Otherwise, click “Install”.
    If you wish, you can click “Skip” when the DVD integrity check begins.
    After the initial installation completes, your Mac will restart and you will see the video introduction.
    At “Welcome” select your country and then preferred keyboard.
    At “Do You Already Own a Mac?” you are asked “Would you like to transfer your information?”
    +from another Mac+
    +from another volume on this Mac+
    +from a Time Machine backup+
    +Do not transfer my information now+
    Select “from a Time Machine backup” and click “Continue”.
    At “Select a Backup Volume” choose your Time Machine backup disk and click “Continue”. (If you are attempting the migration wirelessly, then click “Join...” and select your network first.)
    At “Transfer Your Information” check all the categories you wish to migrate over. If you wish your Mac to be in the same state as your last backup, then check everything. Give the installer time to calculate sizes.
    Once that is complete, the “Transfer” button will become active and you can click it.
    After the install, verify the registration information, click “Connect” and you are done.
    After logging in, immediately go to System Preferences --> Time Machine, and turn “OFF” backups, even if a backup attempted has begun.
    Next, Launch Disk Utility, select your Macs’ internal disk on the left, and click “Repair Disk Permissions”.
    Interestingly, no Spotlight indexing appears necessary, so, once the permission repair is complete, turn Time Machine back “ON” in the Preferences. Time Machine should continue to backup to the same set of backups that it did prior to the restore. However, due to event logs being out of sync, the first backup will require a lengthy session of “Preparing...” as Time Machine performs a “deep traversal”. Allow this to proceed uninterrupted. Naturally, the first backup after a significant installation like this will be quite large so don’t be alarmed.
    Let us know if this was helpful.
    Cheers!

  • Time Capsule and Time machine hangs my mac

    I read through the first 20 pages to see if anybody else was having similar issues but then gave up so apologies if this is repeated.
    OK here goes. I bought a TC 1 TB plugged it in, worked no problem and did so for ages. None of the problems mentioned by other people.
    Recently I had a backup fail. At the time I had installed time machine editor some time previously and set it to back up once a day which it had been doing with no issues for weeks.
    Reading the help topics I re-selected the TC in TM and off it went preparing - backup failed. Restarted both Mac and TC and tried again. This time it started the backup got to about 70GB and hung my mac - nothing worked had to hold the power button on the mac to get it to restart.
    Plugged my mac directly into the TC to get a GB connection. Deleted the TC drive and reselected it. 70 (ish) GB failed and hung my machine. Checked the logs found the same file failing, excluded it from backups, deleted the drive started again - 70 ish GB failed again hung machine.
    Rand apple support, was asked to do a few things. First hard reset the TC, second check permissions and repair on the mac hard drive. Third re-index the mac HD - then delete the TC drive and start again. 70 GB mac hung - warning server disconnect - backup failed.
    Restarted TC and Mac, deleted TC drive, start again, 70 GB fail.
    Now, the only thing that is going through my mind and im reaching here a bit is that about the time I started having problems was the same time I bought the new expansion to a game - World of Warcraft. I do play this daily and have been during the backups, I have been keeping an eye on the backups while playing and although they do appear to stop incrementing the machine is fine until I try to exit WoW. When I do the machine hangs (only does this when TM is running).
    I am running out of ideas now, seem to have tried everything backups constantly failing at around the 70GB mark no more files needing to be excluded, the errors seem to be losing connection to TC server.

    I ended up with a few days of talking to Apple support about this and here is how it went and this is what we tried.
    Managed to get the TM to backup a full backup. The next backup failed and after that could not mount the bundle.
    Deleted the drive started again, hung around 80% - same problem.
    Deleted and renamed the drive - this seemed to work and full backup completed. Next backup failed.
    Removed all of the 'offending' items from backup - i.e. pretty much anything that had ever been mentioned in a support forum, e.g. parallels drives, Aperture loads of stuff - no difference.
    Complete reset on old time capsule - held reset button for 20 seconds while plugging power in. Deleted and renamed the old drive. Re-installed the firmware.
    I excluded almost everything on the mac hard drive to make for a quick backup. It backed up fine but failed on next backup at which point the sparse bundle could no longer be mounted.
    Apple still thought the problem was not the TC but something it was trying to backup.
    Re-installed OSX. Removed everything from backup - i.e. excluded everything so it had nothing to backup. Then gave it 1 file to backup.
    Backed up fine then failed at next backup.
    Apple sent me a new replacement TC - removed everything (except parallels drive) from exclusions - plugged it in selected it as destination has been working fine ever since.
    Now, Apple sent me the replacement with a not saying do not return old faulty equipment. So I got a new shiny replacement and my problem is solved.... however I am a curious sort and cannot figure out what is wrong with the old one. Its network is fine, I can use the drive as an external drive no problem (i.e. plug it in and mount the drive by connecting to server) but TM fails if I try to use it for TM backups.
    The machine is a NAS, what I am trying to figure out is where is the NAS software held? is this part of the build of the harddrive or part of the firmware?
    The reason I ask is, you cannot reformat a TC, only delete the network drive you create with various setting for secure delete. BUT, if you look at a TC drive it is NOT the full size of the drive within the TC. Also, there are at least 3 partitions on the drive, So I assume that the other 2 are the NAS side of things. My opinion is that one or both of the NAS partitions is corrupt, but we have no method of rebuilding these and no method of reformatting the entire disk.
    I have read that you can remove the TC drive and reformat it using disk utility, but what happens when you put it back in? is it still a TC? does it still have the TC NAS functionality?
    What I think is missing here is something in Airport utility that allows you to rebuild a TC from scratch. I assume the reason it isnt there is to ensure that people can't build their own TC's and have to buy Apple's, but surely Apple could build this into Airport utility so that it recognises a genuine TC and allows a re-build and/or re-format?
    I am going to continue messing with the old one, to see if it can be fixed, if not it will either become the most expensive airport extreme I won or at least a Network attached disk for my PC's.

  • Time Machine hangs here every time

    I am running Leopard 10.5.2 on a new 24 inch iMac. I have prepared a lacie 500 gb disk correctly for TM (Guid, Journaled, partition), but every time TM hangs. All Console is telling me is:
    My-iMac mdworker[411]: Error: image is not of a supported color model
    I have excluded .Trash and even iTunes library. What else can I do???
    Any help appreciated. TM is driving me crazy.
    John

    • Go to the Partition tab. Create two partitions. Under Options, select GUID Partition Table (what you would use to make a Mac OS boot disk) and click OK then Apply.
    • Once your partitions are in place, do it again, reverting back to just one partition, but still keeping the GUID Partition Table option. Click OK and Apply again, and at this point you should be cool.
    • To be safe, you can then go to Erase and set formatting for Mac OS Extended (Journaled), then format it once and for all. But when you get there, you will probably see that your volume is already formatted in the right way.
    http://gizmodo.com/gadgets/apple/leopard-disk-utility-format-issue-screws-with-t ime-machine-but-theres-an-easy-fix-316573.php

  • Time Machine recovery Help!

    Hi forum.
    I have Time Machine setup on a MacBook Pro backing up to a Time Capsule.
    Now the user has lost his iphotos and we want to get them back from the backup.
    When I "enter" timemachine, I cannot navigate, it seems the interface is locked on "today". The Arrows dont work and the timeline on the right shows no other date than today.
    Yet on the timecapsule, there is a sparseimage 500gb with 245GB free. Mounting the sparseimage there is a folder for the computer and a ONE SINGLE file in there called DDMMYY.inprogress . That file is 136MB big and was last modified on the 27th of November (looks good my data must be in there).
    Problem: I cannot access this file. How can I access it?
    If I try to copy the file to another drive it says "cannot copy the file Error -1426"
    Help!
    Is there anyway to view the contents of this file directly?
    Thanks for any tips
    the wumpus
    PS - sofar, Im not impressed with Time Machine. I set it all up to backup, it backs up fine for months, and when you need it it fails you. Sofar 0/10 (given Im doing things corectly...)

    You mean going into the pictures folder and entering time machine?
    As I said, I tried that and I cannot navigate inside timemachine at all (the arrows dont work) nor do I see any dates.
    Or did you mean something else?
    Thanks

  • Time Machine Error - Help!

    Hello everyone. I am having a problem with backing up my time machine in Lion and get the following error message: "The backup was not performed because an error occurred while copying files to the backup disk.  The problem may be temporary.  Try again later to back up.  If the problem persists, use Disk Utility to repair your backup disk."
    Here is the context and history. I recently installed Mavericks on my Mac Mini (late 2009), which was causing all sorts of problems and constant computer crashes. About a week later I used TM to restore to the previous OS version and backup (Lion) before the problems began, and the computer is now working normally as before, except for TM. Initially I thought it was a problem with the drive, so I tried a TM back-up on my second back-up disk but got the same above error message. Thinking it had something to do still with the disk or older back-ups there saved, I erased one of the disks (using disk utility), performed disk repair, tried another TM back-up but continue to get the same error message. Any suggestions of next steps to try? I am not great with code or computer speak, so would greatly appreciate easy instructions if possible.
    One last thing to note, this problem only began after doing the TM restore mentioned above. TM was still working normally even with Mavericks, so intuitively I am guessing something went wrnong during the restore, but everything seems to be working fine except with TM. I have done disk repairs also on the Mac HD and no errors were found. Please help! 
    Cheers!

    This is happening to me too.
    It seems that the HD randomly becomes unavailable.

  • Time Machine / Email help?

    Good morning,
    I am hoping somebody is able to help as I am totally baffled by an issue I am having.
    I purchased a new Macbook Pro today so decided before I formatted my old one, I would make a time machine image so I could transfer the data straight across to my new machine. I thought this would be simple but I have stumbled across an issue.
    I plugged my external HDD into my new Macbook and opened time machine to transfer my files. It advised me it was not set up on the new machine, so I went ahead and set it up, this made a new image of my new Macbook onto my external device.
    When I open time machine it will only open it for this mac and there is no way to choose the time machine backup from my old mac which is extremely frustrating.
    Now, I know you can access files without using time machine by openening the HDD and browsing the files, or browse other time machine disks. I used this method to download all my files with no issues at all but what I really need is my mail folder from my old Macbook.
    I located the library folder but within there is no 'mail' folder. I used terminal to unhide files but this seemed to have no effect on the external HDD.
    If I plug the external HDD back in to the old mac it again tells me no time machine is set up on this product and wants to make a third image.
    Please help as these emails are vital!
    Regards
    Nicola Rutherford

    Today this happened again: lost all the emails on MobileMe account. This time I am sure there was no interference with checking mail from the office or any other computer other than iPod Touch.
    Switched on email. Opening an email it got stuck and after a minute everything in the mobilme inbox disappeared.
    I use the iPod Touch to check email so now and then. Up until now no surprises.
    Start to feel very uncomfortable that this can happen at random. Fortunately I back up on GTech external harddrive, but nevertheless. Any clue?
    (I have posted this message wrongfully under Mac OS X v10.4 Tiger, it should have been Mac OS X v10.5.7 Leopard. Do not know how to move this to the right forum.)

Maybe you are looking for

  • Pacman no longer working...

    I did a pacman-optimize, and pacman -Scc just in case this was an issue local to my computer...? I've also tried using the US mirrors rather than the Great Britain mirrors. None of this has had any effect. [bedtimes@seb ~]$ sudo pacman -Suy :: Synchr

  • HT4847 What will happen if I delete apps off iCloud?

    What will happen if I delete apps off iCloud?

  • Computer keeps shutting off to sleep

    This is by no means a new problem for me. This happened to me before, someone here very helpfully posted that my computer might fall under the RevB warranty - which it did. However, when I took it to an apple care center it was taken and the guy ther

  • Open an Explorer from Java

    How i can open the default explorer from Java and redirect it to an especific URL?

  • Dv6-3050us Battery Dies at 60%

    I've had this problem starting two weeks ago where my laptop would just shut off, not hibernate, automatically at 30%. Now two weeks later it has the same problem but at 65%. I cannot do a full discharge since the laptop automatically shuts off at 65