Time machine stuck on 'caculating changes'

I upgraded to snow leopard with no problems except that I can't get a time machine backup completed. The message is stuck on 'calculating changes'. I have done a reset of time machine etc. but no luck so far. Any advice? Message in my time machine widget is:
Backing up to: /Volumes/Ivisonbackup/Backups.backupdb
Event store UUIDs don't match for volume:....
Waiting for index to be ready (101)
etc.
Thanks

Hi, and welcome to the forums.
What's the "etc." ?
If it's more of the "Waiting for index . . ." messages, that's likely a problem with your TM volume, or communicating with it.
Start by repairing your backups, per #A5 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of the +Time Machine+ forum).
If that doesn't help, post back with details, including all the messages, your setup (especially the destination for the backups), what you've done, and the results.
Message was edited by: Pondini

Similar Messages

  • Time machine stuck on 'calculating changes'

    I have been using Time Machine backups to a 2TB Time Capsule for over a year, and one of my 4 computers has recently stopped backing up. The other 3 are still backing up fine, and I ran disk utility on the Time Capsule which stated that it was working fine as well. Backing up my MacBook Pro is now stuck in an endless (over 24 hrs) 'calculating changes'. I have tried directly connecting it via ethernet to the Time Capsule, but still have the same problem. I'd prefer not to start from scratch as the base backup is around 250GB. Any advice?

    Well, I repaired the disk -- but still having the same problem. Seems to be getting stuck at the same place in the log:
    Starting standard backup
    Attempting to mount network destination using URL: afp://Mark%[email protected]/Data
    Mounted network destination using URL: afp://Mark%[email protected]/Data
    Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin, 262): no suitable image found. Did find:\n /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: mach-o, but wrong architecture
    Cannot find function pointer VRPreviewCFPlugInFactory for factory 20D1C6B2-6A02-11D7-B5A6-000393D45566 in CFBundle/CFPlugIn 0x10050db60 </Library/Plug-ins/DiskImages/NUMPlugin.bundle> (bundle, not loaded)
    Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin, 262): no suitable image found. Did find:\n /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: mach-o, but wrong architecture
    Cannot find function pointer VRPreviewCFPlugInFactory for factory 20D1C6B2-6A02-11D7-B5A6-000393D45566 in CFBundle/CFPlugIn 0x10050db60 </Library/Plug-ins/DiskImages/NUMPlugin.bundle> (bundle, not loaded)
    2010-09-12 18:23:53.015 diskimages-helper[256:2103] Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin, 262): no suitable image found. Did find:
    /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: mach-o, but wrong architecture
    2010-09-12 18:23:53.018 diskimages-helper[256:2103] Cannot find function pointer VRPreviewCFPlugInFactory for factory 20D1C6B2-6A02-11D7-B5A6-000393D45566 in CFBundle/CFPlugIn 0x1003193a0 </Library/Plug-ins/DiskImages/NUMPlugin.bundle> (bundle, not loaded)
    2010-09-12 18:23:53.189 diskimages-helper[256:2103] Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin, 262): no suitable image found. Did find:
    /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: mach-o, but wrong architecture
    2010-09-12 18:23:53.190 diskimages-helper[256:2103] Cannot find function pointer VRPreviewCFPlugInFactory for factory 20D1C6B2-6A02-11D7-B5A6-000393D45566 in CFBundle/CFPlugIn 0x1003193a0 </Library/Plug-ins/DiskImages/NUMPlugin.bundle> (bundle, not loaded)
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    2010-09-12 18:23:55.265 diskimages-helper[263:2103] Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin, 262): no suitable image found. Did find:
    /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: mach-o, but wrong architecture
    2010-09-12 18:23:55.267 diskimages-helper[263:2103] Cannot find function pointer VRPreviewCFPlugInFactory for factory 20D1C6B2-6A02-11D7-B5A6-000393D45566 in CFBundle/CFPlugIn 0x10051bae0 </Library/Plug-ins/DiskImages/NUMPlugin.bundle> (bundle, not loaded)
    2010-09-12 18:23:55.402 diskimages-helper[263:2103] Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPl

  • Time Capsule / Time Machine stuck on 'calculating changes'

    Time Machine has not backed up to my Time Capsule for the last several weeks on my MacBook Pro. It is constantly stuck on 'calculating changes' for hours. I have tried other suggestions I have found in the forum like verify and repair disc on both my internal HDD and on the time capsule drive. No errors were found on either drive. I normally backup via wifi and I have also tried plugging directly into the time capsule with an ethernet cord. It doesn't make any difference either with wifi or ethernet.
    The time capsule drive is full, but I just assumed that Time Machine would erase the oldest backups and continue. I don't know if this is an issue with the problem I am having. I downloaded the time machine widget as suggested in other posts on this topic, the log is posted below. There are errors about the disc being full and an error writing to the backup log. I don't know why it can't right to the log or what could be wrong. After looking at the logs, it appears that what is shown below just continues to repeat about every two hours (time machine seems to give up after about 2 hours and starts over again with the same result).
    I am thinking of erasing the time capsule disc and trying to start over, but would like to figure why this has happened before I erase the disc. I am also worried about erasing my only backups, even if they are three weeks old. Entering time machines still seems to give me all of my older backups like nothing is wrong, but I haven't restored from one so they may not work if I tried.
    Any help would or insight into this would be greatly appreciated.
    Starting standard backup
    Attempting to mount network destination using URL: afp://Kason%[email protected]/Data
    Mounted network destination using URL: afp://Kason%[email protected]/Data
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Disk image /Volumes/Data/MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
    Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    Exception writing exclusions cache. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    Unable to create exclusions cache data.
    Failed to write exclusions cache. Continuing anyway.
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandl

    jaxx323 wrote:
    The time capsule drive is full, but I just assumed that Time Machine would erase the oldest backups and continue.
    Ordinarily it will. Do you have other data on the drive? If so, it appears that other data has completely filled the drive, so much so that Time Machine can't even start the hidden log it keeps there.
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    Usually when that happens, the backup crashes.
    First, cancel the backup. If it won't cancel after a few moments, see #D6 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html].
    Then connect via an Ethernet cable if at all possible. Time Machine needs to do some intensive work, and it will be slow even via Ethernet, but 2-3 times slower via WIFI.
    If there's other stuff on the drive, you could copy some of it elsewhere temporary and delete it. You only need to free up 50 MB or so.
    But your best bet is to delete your oldest backup(s), then "compact" the sparse bundle they're in, to make some space. See #12 of [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html].
    Since it's been several weeks, you may want to delete roughly one old backup for each of those weeks, then "compact" the sparse bundle. If you only delete one, then Time Machine will have to delete more, but it will delete one, dismount the sparse bundle, compact it, then remount it to see if there's enough room. That gets repeated over and over until there's enough space.
    Once this is sorted out, if there is other stuff on your TC's internal HD, see #Q3 in [Using Time Machine with a Time Capsule|http://web.me.com/pondini/TimeMachine/TimeCapsule.html] (or use the link in *User Tips* at the top of this forum).

  • Time Machine stuck in "Calculating Changes"

    I am backing up time machine to a 1 tb Seagate GoFlex Desk. It is formatted to MacOS extended journaled. It works about 80% of the time, but a couple of times a day I check and it is stuck in "calculating changes". The only solution i have found is unplugging it which gives me the message "You need to eject". I just reinstalled the os hoping that would take care of it, but no dice. I did try logging out to see if that reset it, and it got stuck at my blank desktop background. But when I unplugged the harddrive, it finished logging out. Anyone have any solutions to these very annoying problems?

    Hi jtupnsmoke - I have the exact same problems and am also using the Seagate 1TB Flex Drive- have had unplug the drive and have had the improperly ejecting the drive message, etc. I'm stuck in calculating changes once again. It is the only problem I've had that I wasn't able to fix with help from all of the great people on these boards. I'm about ready to plug in my old OWC Neptune external drive and see if it makes a difference.

  • Time machine hung on calculating changes (stuck at 99%)

    Im experiencing a few problems with time machine which is currently set to back up wirelessly to a time capsule. This has been working great for about a year now never any problems with any backup in the past but over the last day i can not get a backup to complete.
    N.B; i have been staying away for the past two weeks as i am at university so i'm aware the first backup will be large with a two week gap. Though this is not usually a problem. The other change is i have recently changed the net work set up, before Time capsule was connected to another router (BT Voyager 205) in bridge mode, now i have a new router (BT home hub 2.0) and have re-configured time capsule to simply join the wireless network for back up and storage purposes.
    Heres what i have tried:
    Powering down the time capsule and my laptop several times
    unselecting the disk in the time machine options, selecting none and then re-selecting the disk
    a full reset of time machine (followed the steps found here; http://discussions.apple.com/thread.jspa?threadID=2057525)
    Heres the console log messages:
    05/03/2010 12:09:02 com.apple.backupd[281] Starting standard backup
    05/03/2010 12:09:02 com.apple.backupd[281] Attempting to mount network destination using URL: afp://James%20Clough@James%20Clough's%20Time%20Capsule.afpovertcp.tcp.local/Data
    05/03/2010 12:09:02 com.apple.backupd[281] Mounted network destination using URL: afp://James%20Clough@James%20Clough's%20Time%20Capsule.afpovertcp.tcp.local/Data
    05/03/2010 12:10:41 com.apple.backupd[281] Disk image /Volumes/Data-1/James MacBook_0023df8f4ff4.sparsebundle mounted at: /Volumes/Backup of James MacBook
    05/03/2010 12:10:47 com.apple.backupd[281] Backing up to: /Volumes/Backup of James MacBook/Backups.backupdb
    05/03/2010 12:10:53 mds[36] (Normal) DiskStore: Rebuilding index for /Volumes/Backup of James MacBook/Backups.backupdb
    05/03/2010 12:13:35 com.apple.backupd[281] Event store UUIDs don't match for volume: Macintosh HD
    05/03/2010 12:16:33 com.apple.backupd[281] Node requires deep traversal:/ reason:must scan subdirs|new event db|
    05/03/2010 12:16:36 mds[36] (Normal) DiskStore: Creating index for /Volumes/Backup of James MacBook/Backups.backupdb
    05/03/2010 12:20:16 com.apple.backupd[281] Node requires deep traversal:/Users/James/Pictures/iPhoto Library reason:contains changes|must scan subdirs|found in deep scan|missed reservation|
    also noticed for the first time that when clicking into spotlight search at the right of the screen i see:
    "Indexing backup of James' Macbook"
    with an estimating time bar below which keeps spinning giving no time, just says estimating??
    thankyou to anyone who can help shed some light on this problem.

    vengenceJC wrote:
    also noticed for the first time that when clicking into spotlight search at the right of the screen i see:
    "Indexing backup of James' Macbook"
    with an estimating time bar below which keeps spinning giving no time, just says estimating??
    The combination of symptoms sounds like your backups may be corrupted. Cancel the backup and Repair them per #A5 in the Troubleshooting Tip.
    You might want to exclude the drive from Spotlight indexing temporarily, until the backup is done, via +System Preferences > Spotlight > Privacy.+
    And since Time Machine has to do a "deep traversal," connect to the Time Capsule via Ethernet if at all possible -- both the "deep traversal" and actual backup will be faster that way.

  • OS 10.7.5 time machine stuck on prepping

    I am running 10.7.5 and my time machine has bee stuck on prepping for weeks.
    I have seen other fixes in the support posts, but they aren't for Lion. Does anybody know if the fix is the same or is there something new?
    Thanks

    It's not for your system but the exerpt regarding third-party anti-virus scanning software remains applicable: Mac OS X 10.5: Time Machine may display "Preparing" for a longer time
    It shoudn't take long for you to rule that out, so following that step read Apple Support Communities contributor Pondini's FAQ regarding that question: Stuck in "Preparing" or "Calculating changes"
    The end of that page leads you right back where you came, so if that's how you arrived here then I'll try to rouse Mr. Pondini for you.

  • Time Machine stuck in Preparing Data Mode

    In the past two days my time Machine has not made a successful back up. It seems to be stuck in "preparing data" and will stay like this all day. Even when I click the time machine preferences and stop it, it never changes. Does anyone have any solutions to this or has experienced it.Any suggestions would be greatly appreciated.
    Thanks!!

    Judith,
    The following might contain an explanation for what you are experiencing.
    *_Time Machine May Report "Preparing..." For a Long Time_*
    First, it’s good to determine WHY Time Machine is "Preparing..." for an extended period of time. Examining the Console logs during this event can reveal what is actually going on behind the scenes. It may be “Preparing…” for a genuinely good reason. How long is 'too long' to wait for Time Machine to finish "Preparing..."? Some times, "Preparing..." is required to perform the normal housekeeping that Time Machine does periodically. Other times, it really is "stuck" and never proceeds after more than 24 hours.
    *”Deep Traversal” (Recent Crash / Forced Restart / System Update / Extended Period Between Backups)*
    According to the following KB article it can sometimes take quite a long time if Time Machine begins a “deep traversal” and has to compare data inventories. This may apply to your situation, particularly if many Gigs of data are involved. [http://support.apple.com/kb/TS1516]
    You see, Time Machine *+does not+* ordinarily perform file-by-file comparisons to determine what has changed and thus determine what needs to be backed up. Rather, Time Machine relies on FSEvents notifications. This is a log that the system uses to keep track of changes to directories. Rather than scan tens of thousands of files for changes each time, Time Machine simply looks at this log and narrows its’ scan to only the directories that have experienced changes since the last backup. Otherwise, Time Machine would have to be running constantly just to catch every change on its own and thus eat up precious CPU.
    Every event that FSEvents records has its’ own ID which includes a time stamp. At the end of every backup, Time Machine stores the last event ID that it processes. When the next backup is initiated, Time Machine looks at this stored ID and determines that it only needs to backup events that have occurred after the time stamp on this last event ID.
    If, due to a system crash, power failure, forced restart, or some other major system event, Time Machine cannot find this last event ID in the system logs then it will consider the FSEvents log “untrustable” and it will go into what’s called “deep traversal”. The Console logs may report +“Event store UUIDs don't match”.+ In this event, Time Machine will by-pass the system log entirely and perform its’ own file-by-file comparison to determine what has changed since its’ last backup. Obviously, if tens or hundreds of Gigs are involved, then this process can take quite some time and should be allowed to proceed.
    Additionally, it appears that if Time Machine has to go back too far to find the last event ID, then it will give up and simply go into “deep traversal” and do the file-by-file scan on its’ own. This can occur if Time Machine has not been able to perform its’ hourly backups for some time, as is the case for users who only backup once a week or so. This is also the case with major Mac OS system updates that change thousands of files at one time. There are simply too many events logged by the system for Time Machine to bother looking for the last known event ID.
    *Consolidation / “Thinning”*
    At the beginning, when Time Machine is first used, incremental backups are relatively quick events. But as time goes on, and backup files grow, Time Machine requires time to perform house-keeping on the backed up data. This maintenance is referred to in the Console logs as "thinning". The larger the backup files become, the more time Time Machine requires.
    To prevent the backup drive from filling up too fast, Time Machine will periodically consolidate, or 'thin', backups to free up space for new data. After a certain period of time, each hourly backup becomes "expired". This occurs about 24-48 hours after the hourly backup took place. At that point Time Machine begins consolidating, or "thinning", all the hourly backups of a given day into one daily backup. Then, after about a month all daily backups for a given week “expire” and are consolidated into a single weekly backup.
    Obviously, since the Time Machine process (backupd) does not run continuously, it has to do this "thinning" during routine backups. That is where "Preparing Backup..." and "Finishing Backup..." come in. It is during these initial and closing phases of a backup that "thinning" occurs. As a result, while not every backup will be accompanied by extended periods of "Preparing..." and "Finishing...", periodically Time Machine will require extra time to perform these space-saving consolidations.
    *Anti-Virus Software*
    Running anti-virus software can interfere with the backup process. Either disable it altogether, or try the suggestion outlined here, “If you use third-party anti-virus scanning software and have issues, make sure your Time Machine back up folder (Backups.backupdb on the Time Machine disk) is excluded from virus scanning.” (http://support.apple.com/kb/TS1516)
    *Software Updates* #
    Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your Macs directories. Time Machine will backup every file that has changed since the installation.
    After an OS update (like 10.5.5) Time Machine realizes the system no longer matches what it looked like during the previous backup. So it has determined that it's earlier catalogue of what-should-be-where is “untrustable”. So it is going to go item-by-item comparing the before and after of your system.
    *Spotlight Keeps Indexing Backup Drive* #
    It may be that Time Machine can’t proceed or complete a backup due to Spotlight indexing. During this period, take a look at the Spotlight icon in the upper right corner of your screen. Is there a tiny dot pulsating in the center of the spyglass? Click on the icon. Is there a progress bar displayed? Generally, Spotlight indexing is a good thing. If it has only been a couple of hours then, stop the backup, turn Time Machine OFF, and let the indexing continue.
    However, at times Spotlight may hang and never progress after many hours, preventing further backups from taking place.
    Go to System Preferences --> Time Machine.
    Using the slider on the left, turn OFF Time Machine backups for now.
    Next, click “Show All” in the toolbar.
    Select the Spotlight Preferences.
    Click the Privacy Tab.
    First, drag your Macs’ internal hard disk from the desktop to the Privacy list.
    Wait 10 seconds, then highlight the Macs’ hard disk in the list and click the tiny “-” button at the bottom to remove it from the list.
    Spotlight will initiate a reindex of the hard disk. If you click on the Spotlight menu icon you may see the message:
    +“Spotlight helps you quickly find things on your computer. Spotlight will be available as soon as the contents of your computer have been indexed.”+
    ...and a progress bar will indicate the time remaining.
    Once completed, drag your Time Machine backup disk into the Privacy list of the Spotlight Preferences.
    Wait 10 seconds, then highlight the Time Machine backup disk in the list and click the tiny “-” button at the bottom to remove it from the list.
    Spotlight will now initiate a reindex of the hard disk.
    Once completed, if you have any other hard disks attached to your Mac that are also being backed using Time Machine, then force a reindex as well using the procedure outlined above.
    Then turn Time Machine back ON and initiate a backup.
    *Run Away System Process*
    It’s possible that Time Machine is stuck “Preparing…” because another process is monopolizing your Macs’ CPU. Launch Activity Monitor and sort the items by “CPU”. Is there a process that is at or near 100% that might be preventing the backupd process from moving forward?
    One poster stated, “I took it to my local Genius Bar and they found a Syslogd daemon running, taking up 100% of my CPU….This resulted in the "Preparing..." mode running forever.” [http://discussions.apple.com/thread.jspa?threadID=1755600&tstart=15]
    You may be able use Activity Monitor to “kill” the offending process. Or you may be able to resolve it simply by rebooting your Mac. Then try backing up again.
    *Verify/Repair Mac Hard Disk & Permissions*
    It may be that your Macs’ internal hard disk has so many file/directory issues that Time Machine simply has trouble making sense of it. Some users have had success using Disk Utility on their Macs’ hard drive.
    Launch Disk Utility and click “Repair Disk Permissions”.
    Once complete, attempt a backup.
    If Time Machine appears to hang at “Preparing…” again, then do the following:
    Insert your Macs’ original install DVD and reboot holding down the “C” key.
    At the Welcome screen go up to the “Utilities” menu and select Disk Utility.
    Select your Macs’ hard disk on the left and click “Verify Disk” on the right.
    If problems are found click “Repair Disk”.
    Reboot to your normal desktop and try backing up again.
    *For Time Capsule Users* #
    If, though, none of the options above have helped and it has been 12 hours or more of “Preparing…”, then the Time Capsule may need to be restarted.
    Stop the backup from the Time Machine menu. (Give if a few minutes while it says “Stopping backup…”)
    When the Time Machine icon stops spinning, unplug the TC from the wall outlet.
    Wait 10-15 seconds.
    Re-plug it in again.
    After it has restarted (30-60 seconds), attempt another backup.
    Time Machine will report “Preparing…” again, but it shouldn’t be lasting more than a couple of hours.
    Let us know if any of the above was helpful in resolving your issue.
    Cheers!

  • Time machine setup - how to change 'wireless network name' and settings?

    I have moved laptop to Mountain Lion.
    This is the first time to backup to Timecapsule.
    I went to Settings then Select Disk and selected existing Time Machine.
    It took more than 30 minutes and seemed stuck on 'Preparing ....".
    I cancelled and tried to 'Setup Time Capsule not  listed"...
    The system recognised the Time Capsule but I see that the network settings is my old 'wireless network' name.
    How do I change this to the correct network name and ensure that the settings are correct? 
    I think if this is corrected, the backup will work.
    Thanks in advance.

    On the Home screen of the product control panel, touch the right arrow ( ) to view more options.
    Touch Setup ( ).
    Touch Network .
    Touch Wi-Fi Protected Setup .
    Touch PIN .
    Touch Start . The product displays a PIN.
    NOTE:The product begins a timer for approximately two minutes to allow you time to enter the PIN on the networking device.
    Enter the PIN on the WPS-enabled router or other networking device.
    I work for HP, IPGHT specialist in Officejet and Photosmart printers.
    --Say "Thanks" by clicking the Kudos Star in the post that helped you.
    --Please mark the post that solves your problem as "Accepted Solution" .....

  • Time Machine stuck in "preparing" endlessly.

    I have been able to successfully back up my MacBook Pro twice in the past two months using Time Machine, but both times I had to monkey with it, and I'm not even sure what exactly I did to make it work.
    Today I've tried several times to back up my machine, but it seems to get stuck "preparing" for hours.
    I don't keep Time Machine plugged into my laptop because I need that USB for my printer. Rather, I periodically plug my Sea Gate FreeAgent external drive in and attempt to manually back up. But it never just works without a lot of clicking around.
    What am I doing wrong??? How can I get it to work??
    Thanks so much!

    xtine,
    Your situation is explained in the first section of the info below:
    *_Time Machine May Report "Preparing..." For a Long Time_*
    Consider these factors regarding an extended period of "Preparing...". Consider each topic separately and do not attempt to act on all of them at once.
    *Recent Crash or Other Major System Event* (Deep Traversal)
    The reasons for this process are described in an article by George Schreyer. “During the preparation step it checks the FSEvents log for consistency. If it determines that something isn't quite right it has to rescan the whole disk. This can take quite awhile. A full rescan is always triggered by a crash, an unplanned shut down event or by booting from some other bootable disk between backups…. After a crash, Time Machine must scan the whole disk to determine what it has to do because it cannot trust the information that it left behind. Connected via an Ethernet connection, this phase would typically take 20 minutes on an older PowerBook. Being connected wirelessly stretches this phase out to over 3 hours.” [http://www.girr.org/mac_stuff/backups.html]
    According to the following KB article it can sometimes take a very long time if Time Machine begins this “deep traversal” and has to compare data inventories. This may apply to your situation, particularly if many Gigs of data are involved. (http://support.apple.com/kb/TS1516) Additionally, if Time Machine has not been able to perform its’ hourly backups for 24 hours or more, then it will perform a “deep traversal” once backups are renewed. This is the case for users who only backup once a week or so.
    *Anti-Virus Software*
    Running anti-virus software can interfere with the backup process. Either disable it altogether, or try the suggestion outlined here, “If you use third-party anti-virus scanning software and have issues, make sure your Time Machine back up folder (Backups.backupdb on the Time Machine disk) is excluded from virus scanning.” (http://support.apple.com/kb/TS1516)
    *Software Updates* #
    Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your Macs directories. Time Machine will backup every file that has changed since the installation.
    If you take a look at the Console logs Time Machine may be reporting that your backups need "deep traversal". That's fine. Time Machine knows what is wrong and how to fix it. If you have a great deal of data, it may take quite awhile.
    After an OS update (like 10.5.5) Time Machine realizes the system no longer matches what it looked like during the previous backup. So it has determined that it's earlier catalogue of what-should-be-where is 'untrustable'. So it is going to go item-by-item comparing the before and after of your system. If you have just performed an OS Update then Time Machine knows what it's doing - let it do it!
    *Spotlight Keeps Indexing Backup Drive* #
    It may be that Time Machine can’t proceed or complete a backup due to a Spotlight indexing error. During this period, take a look at the Spotlight icon in the upper right corner of your screen. Is there a tiny dot pulsating in the center of the spyglass? Click on the icon. Is there a progress bar displayed? Generally, Spotlight indexing is a good thing. If it has only been a couple of hours then let the process contiune.
    However, at times it may hang and never progress after many hours, preventing further backups from taking place.
    Go to System Prefs --> Spotlight --> Privacy Tab.
    Drag your Time Machine disk into the window. It should now be among the items to exclude from indexing.
    Now quit System Prefs.
    Reboot your Mac.
    Reopen System Prefs and remove ("-") the Time Machine disk from the window.
    Now initiate a backup.
    This should clear out Spotlights cache. Naturally, Spotlight should begin indexing again (maybe even for a few hours depending on how much data there is), but it should eventually stop.
    *Reboot Time Capsule* #
    If, though, none of the options above have helped and it has been 12 hours or more of “Preparing…”, then the Time Capsule may need to be restarted.
    Stop the backup from the Time Machine menu. (Give if a few minutes while it says “Stopping backup…”)
    When the Time Machine icon stops spinning, unplug the TC from the wall outlet.
    Wait 10-15 seconds.
    Re-plug it in again.
    After it has restarted (30-60 seconds), attempt another backup.
    Time Machine will report “Preparing…” again, but it shouldn’t be lasting more than a couple of hours.
    Let us know if any of the suggestions above helped in your case.
    Cheers!

  • Time Machine Stuck on Preparing -- Solved

    Info for future Internet searchers:
    Thanks to the great info provided by Pondini (http://pondini.org/TM/Troubleshooting.html) I was able to solve a problem with Time Machine on a sick Macbook Pro.  I may need to reload the Mac from recovery disks, but beforehand I always like to have a good backup.
    First problem: Time Machine to AFP-based NAS fails.  It mounts the drive, looks at the .sparsebundle file and then complains that it's already in use.  This is not on an AirPort so the steps in Pondini's guide don't apply: http://pondini.org/TM/C12.html.  Rebooting the NAS didn't help.  I put this issue on hold for now since my goal was to get a backup by whatever means rather than trying to get the more convenient network-based backups working.
    Second problem: Time Machine to a new USB drive fails.  It would get stuck in "preparing to back up" with this system log message repeated for over 12 hours without change:
    com.apple.backupd: Waiting for index to be ready (101)
    Section D2 (http://pondini.org/TM/D2.html) had a very applicable section, "Repeated Indexing Messages."  Unfortunately, removing the /Volumes/<volume name>/.Spotlight-V100 directory didn't help.  However, deleting /.Spotlight-V100 from the SOURCE drive, rebooting, and letting Spotlight rebuild its index did clear up the error. Backups seem to be running to local media now.

    See Pondini's TM FAQs for starters.

  • Time Machine stuck on preparing backup with in turn breaks internet connectivity.

    Hi all!
    I recently started using Time Machine (on a 1TB USB 2.0 external hard drive) on my MBP (Early 2011, 13") and I've noticed that it constantly gets stuck on the "Preparing backup" stage, which can only be unstuck by pulling the drive or hard rebooting the computer (otherwise it gets stuck on the gray post-logout screen forever). What's more interesting is that while Time Machine is stuck I am unable to use any of my browsers because DNS resolution fails outright (although I can still visit IP addresses and perform manually DNS queries and start SSH sessions in Terminal.app). If I pull the drive or reboot the computer, my internet connectivity is restored. As a relatively new Mac user this behavior is quite puzzling; has anybody else encountered this type of problem?
    Thanks!
    Max

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of this exercise is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login. 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:
    Be sure your Mac is shut down.
    Press the power button.
    Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
    Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
    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.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including your login items.
    Launch the application(s) and test. Same problem(s)?
    After testing, reboot as usual (i.e., not in safe mode.)

  • Time Machine Stuck in Preparing: Can You backup a 1TB Raid

    Hello,
    I have been trying to use time machine on my server to back-up my 1TB Mirrored Raid to an external 1TB firewire drive. Time Machine is stuck in preparing for days and does not back up.
    Does time machine work with RAIDs?
    I have recently reformatted the backup drive with the GUID partition. I also ran disk utility on the RAID set and everything passed.
    I've read on Apple's site not to stop the preparing mode, so I have left it, but it has been 2 days which seems like an extraordinary amount of time.
    Any thoughts? Or is this normal?
    Thanks!

    just let it work. it sometimes can take a very long time if TM goes into deep traversal and scans all the files for changes.
    see this link
    http://support.apple.com/kb/TS1516

  • Time Machine stuck while copying and it ends up blocking the whole mac

    I've a problem with my time machine backup. The backup drive is a partition on an external USB drive. The drive has another partition for data. Everything worked good until yesterday. It gets stuck while copying the files, e.g. 532 MB of 5.45 GB, and it doesn't move even after a couple of hours. The backupd process is constantly using 100 % of one CPU and the other applications are getting stuck as well. I also notice that the USB drive stops spinning at a certain point, as if it goes idle.
    I can't cancel the backup and I have to force shut down the Mac. After the restart, the backup will stop at Zero KB. If I delete the inProgress file nothing changes.
    Here's the log:
    Starting manual backup
    Backing up to: /Volumes/LaCie/Backups.backupdb
    Event store UUIDs don't match for volume: Macintosh HD
    Deep event scan at path:/ reason:must scan subdirs|new event db|
    Finished scan
    Found 44342 files (4.95 GB) needing backup
    7.4 GB required (including padding), 11.79 GB availabe
    Then nothing more.

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

  • Time machine stuck after "Ownership is disabled..."

    Hi,
    I have a problem with Time Machine + Time Capsule on my Mac Pro.
    1 week ago all was working properly, but now I'm not able anymore the complete the initial backup.
    Here is what I have in the log :
    04/10/13 11:23:54,018 com.apple.backupd[1696]: Starting automatic backup
    04/10/13 11:23:54,038 com.apple.backupd[1696]: Attempting to mount network destination URL: afp://jocelyn%20fournier;[email protected]/Time%20Capsule%20 Lia%20_%20Joce
    04/10/13 11:23:54,486 com.apple.backupd[1696]: Mounted network destination at mount point: /Volumes/Time Capsule Lia _ Joce using URL: afp://jocelyn%20fournier;[email protected]/Time%20Capsule%20 Lia%20_%20Joce
    04/10/13 11:23:58,111 com.apple.backupd[1696]: User continued after being warned of changed destination volume identity
    04/10/13 11:23:58,128 com.apple.backupd[1696]: Creating disk image /Volumes/Time Capsule Lia _ Joce/Mac Pro de jocelyn fournier.sparsebundle
    04/10/13 11:24:34,198 com.apple.backupd[1696]: Failed to hide extension on /Volumes/Time Capsule Lia _ Joce/Mac Pro de jocelyn fournier.sparsebundle, error: Error Domain=NSCocoaErrorDomain Code=4 "The file “Mac Pro de jocelyn fournier.sparsebundle” doesn’t exist." UserInfo=0x7fbb91c1a2f0 {NSURL=file://localhost/Volumes/Time%20Capsule%20Lia%20_%20Joce/Mac%20Pro%20de% 20jocelyn%20fournier.sparsebundle/, NSFilePath=/Volumes/Time Capsule Lia _ Joce/Mac Pro de jocelyn fournier.sparsebundle, NSUnderlyingError=0x7fbb91c19970 "The operation couldn’t be completed. No such file or directory"}.
    04/10/13 11:24:40,606 com.apple.backupd[1696]: Disk image /Volumes/Time Capsule Lia _ Joce/Mac Pro de jocelyn fournier.sparsebundle mounted at: /Volumes/Copies de sauvegarde Time machine
    04/10/13 11:24:40,611 com.apple.backupd[1696]: Backing up to: /Volumes/Copies de sauvegarde Time machine/Backups.backupdb
    04/10/13 11:24:40,616 com.apple.backupd[1696]: Ownership is disabled on the backup destination volume.  Enabling.
    Nothing is happening after this point, and Time Machine is stuck in the state 'Preparing backup...'
    The time capsule is connected directly through ethernet.
    I've tried the same setup on an iMac, and all is working perfectly, so I assume there's somework wrong on the Mac Pro.
    Here's what I have already tried :
    - Reformat the time capsule
    - Fix permission on the Mac Pro
    - Start the mac pro in Safe mode
    - Let the time capsule alone on the ethernet port (wifi is disabled)
    - Changing the name of the time capsule partition
    - Reselecting the time capsule through the 'choose disk' button
    - Enabling / Disabling trim on my main SSD disk
    Here is what I can see on the time capsule :
    -rwxrwxrwx@  1 root  wheel    0  4 oct 10:26 .com.apple.timemachine.supported
    drwxrwxrwx@  1 root  wheel  264  4 oct 11:44 Mac Pro de jocelyn fournier.sparsebundle
    drwxrwxrwx@  1 root  wheel  264  4 oct 11:44 iMac de Jocelyn.sparsebundle
    drwxrwxrwx@ 1 root  wheel   264  4 oct 11:44 .
    drwx------  1 root  wheel   264  4 oct 11:24 ..
    -rwxrwxrwx  1 root  wheel   500  4 oct 11:23 Info.bckup
    -rwxrwxrwx  1 root  wheel   500  4 oct 11:23 Info.plist
    drwxrwxrwx  1 root  wheel  3730  4 oct 11:43 bands
    -rwxrwxrwx  1 root  wheel   445  4 oct 11:24 com.apple.TimeMachine.MachineID.bckup
    -rwxrwxrwx  1 root  wheel   445  4 oct 11:24 com.apple.TimeMachine.MachineID.plist
    -rwxrwxrwx  1 root  wheel     0  4 oct 11:23 token
    [root@Mac-Pro-de-jocelyn-fournier] /Volumes/Time Capsule Lia _ Joce/Mac Pro de jocelyn fournier.sparsebundle/bands> l
    total 1705048
    drwxrwxrwx  1 root  wheel     3730  4 oct 11:43 .
    drwxrwxrwx@ 1 root  wheel      264  4 oct 11:44 ..
    -rwxrwxrwx  1 root  wheel  3264512  4 oct 11:23 0
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 19
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1a
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1b
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1c
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1c9
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1ca
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1cb
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1cc
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1cd
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1ce
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1cf
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1d
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1d0
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1d1
    -rwxrwxrwx  1 root  wheel  4775936  4 oct 11:23 1d145
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1d2
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1d3
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1d4
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1d5
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1d6
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1d7
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1d8
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1d9
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1da
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1db
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1dc
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1dd
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1de
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1df
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1e
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1e0
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1e1
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1e2
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1e3
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1e4
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1e5
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1e6
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1e7
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1e8
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1e9
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1ea
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1eb
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1ec
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1ed
    -rwxrwxrwx  1 root  wheel   184320  4 oct 11:24 1ee
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 1f
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 20
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 21
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 22
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 23
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 24
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 25
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 26
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 27
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 28
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 29
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 2a
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 2b
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 2c
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 2d
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 2e
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 2f
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 30
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 31
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 32
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 33
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 34
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 35
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 36
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 37
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 38
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 39
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 3a
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:23 3a271
    -rwxrwxrwx  1 root  wheel  1077248  4 oct 11:24 3a272
    -rwxrwxrwx  1 root  wheel  1097728  4 oct 11:23 3a282
    -rwxrwxrwx  1 root  wheel    24576  4 oct 11:24 3a9
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 3b
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 3c
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 3d
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 3e
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 3f
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 40
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 41
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 42
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 43
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 44
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 45
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 46
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 47
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 48
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 49
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 4a
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 4b
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 4c
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 4d
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 4e
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 4f
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 50
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 51
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 52
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 53
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 54
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 55
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 56
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 57
    -rwxrwxrwx  1 root  wheel  8388608  4 oct 11:24 58
    -rwxrwxrwx  1 root  wheel  6475776  4 oct 11:24 59
    And the mounted backup :
    [root@Mac-Pro-de-jocelyn-fournier] /Volumes/Copies de sauvegarde Time machine> l                                  <11:48:15
    total 0
    drwxr-xr-x   4 root      wheel     272  4 oct 11:24 .
    drwxrwxrwt@ 10 root      admin     340  4 oct 11:39 ..
    d-wx-wx-wt@  2 _unknown  _unknown   68  4 oct 11:24 .Trashes
    drwx------   2 _unknown  _unknown  102  4 oct 11:24 .fseventsd
    Any clues of what could be wrong here ?
    (the mounting seems really strange to me, especially the ownership)
    Thanks,
       Jocelyn

    Well, 2h after trying to launch the backup, mds finally crashed, and it seems this unlocked the backup :
    04/10/13 17:02:41,785 ReportCrash[3841]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
    04/10/13 17:02:42,849 ReportCrash[3841]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    04/10/13 17:02:42,849 ReportCrash[3841]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    04/10/13 17:02:42,849 ReportCrash[3841]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    04/10/13 17:02:42,849 ReportCrash[3841]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    04/10/13 17:02:42,849 ReportCrash[3841]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    04/10/13 17:02:42,849 ReportCrash[3841]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    04/10/13 17:02:42,849 ReportCrash[3841]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    04/10/13 17:02:42,849 ReportCrash[3841]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    04/10/13 17:02:42,850 ReportCrash[3841]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    04/10/13 17:02:42,850 ReportCrash[3841]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    04/10/13 17:02:42,967 com.apple.launchd[1]: (com.apple.metadata.mds[77]) Job appears to have crashed: Segmentation fault: 11
    04/10/13 17:02:43,008 mds[3842]: (Normal) FMW: FMW 0 0
    04/10/13 17:02:43,213 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,214 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,214 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,214 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,215 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,215 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,215 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,216 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,216 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,216 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,216 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,217 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,217 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,217 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,217 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,218 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,218 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,218 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,218 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,219 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,219 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,219 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,219 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,219 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,220 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,220 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,220 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,220 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,221 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,221 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,221 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,221 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,222 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,222 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,222 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,222 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,223 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,223 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,223 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,224 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,224 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,224 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,224 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,225 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,225 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,225 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,225 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,226 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,226 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,226 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,226 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,227 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,227 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,227 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,227 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,228 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,228 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,228 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,228 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,228 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,229 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,229 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,229 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,229 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,230 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,230 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,230 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,230 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,231 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,231 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,231 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,231 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,231 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,232 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
    04/10/13 17:02:43,232 mds[3842]: (Error) Task: Invalid storeTokenID (6b000000) in MDSFetchTask
    04/10/13 17:02:43,232 mds[3842]: (Error) Task: Invalid storeTokenID (6b000000) in MDSFetchTask
    04/10/13 17:02:43,316 com.apple.backupd[2263]: Forcing deep traversal on source: "SSD" (mount: '/' fsUUID: 1ECDA662-9676-3D18-9939-C8D073A15B37 eventDBUUID: 14D09399-8E05-4F8C-993F-2707EF8DEE2D)
    04/10/13 17:02:43,316 com.apple.backupd[2263]: Forcing deep traversal on source: "Macintosh HD" (mount: '/Volumes/Macintosh HD' fsUUID: 8BC39A4B-5D17-3754-9DFF-1F3E456F4F6F eventDBUUID: C40760ED-0381-432B-B1A6-5FD4ECE25CB6)
    04/10/13 17:02:43,472 ReportCrash[3841]: Saved crash report for mds[77] version 707.12 to /Library/Logs/DiagnosticReports/mds_2013-10-04-170243_Mac-Pro-de-jocelyn-fourni er.crash
    04/10/13 17:03:02,774 com.apple.backupd[2263]: Backup content size: 93.67 GB excluded items size: 6.66 GB for volume SSD
    04/10/13 17:08:09,607 com.apple.backupd[2263]: Backup content size: 450.55 GB excluded items size: 11.96 GB for volume Macintosh HD
    04/10/13 17:08:09,623 com.apple.backupd[2263]: Found 5349920 files (525.6 GB) needing backup
    04/10/13 17:08:09,624 com.apple.backupd[2263]: 630.72 GB required (including padding), 2 TB available
    04/10/13 17:08:09,646 com.apple.backupd[2263]: Waiting for index to be ready (100)
    So the backup is now running, and the problem is solved, although I don't really understand what was the problem...

  • Time Machine Stuck (Incremental backup, not Initial)

    Hey...me again.
    I was finally successful yesterday backing up 160GB of data with Time Machine.
    However, this morning, the incremental backup is taking forever. It's been stuck at "3.6MB of 6.7MB" for over 20 minutes. It would seem to me that 6.7MB should be pretty quick to backup.
    I have received these messages from TM Buddy:
    Starting standard backup
    Backing up to: /Volumes/Time Machine/Backups.backupdb
    No pre-backup thinning needed: 100.0 MB requested (including padding), 279.56 GB available
    Unable to rebuild path cache for source item. Partial source path:
    Copied 305079 files (49.1 MB) from volume Macintosh HD.
    No pre-backup thinning needed: 100.0 MB requested (including padding), 279.31 GB available
    And Console shows this:
    Aug 25 10:23:53 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: Backup requested by user
    Aug 25 10:23:53 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: Starting standard backup
    Aug 25 10:23:53 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: Backing up to: /Volumes/Time Machine/Backups.backupdb
    Aug 25 10:26:21 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: No pre-backup thinning needed: 100.0 MB requested (including padding), 279.56 GB available
    Aug 25 10:27:51 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: Unable to rebuild path cache for source item. Partial source path:
    Aug 25 10:41:06 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: Copied 305079 files (49.1 MB) from volume Macintosh HD.
    Aug 25 10:42:21 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: No pre-backup thinning needed: 100.0 MB requested (including padding), 279.31 GB available
    Any idea on how to resolve?
    Thanks,
    K

    kieranroy wrote:
    Hey...me again
    Hi again. You seem to have really angered the god of TM, haven't you!
    However, this morning, the incremental backup is taking forever. It's been stuck at "3.6MB of 6.7MB" for over 20 minutes. It would seem to me that 6.7MB should be pretty quick to backup.
    Unable to rebuild path cache for source item. Partial source path:
    This usually doesn't cause a real problem, as long as it's occasional.
    Copied 305079 files (49.1 MB) from volume Macintosh HD.
    This we see on occasion -- the crazy high file count, and very slow backup.
    Aug 25 10:42:21 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd254: No pre-backup thinning needed: 100.0 MB requested (including padding), 279.31 GB available
    Normally, TM will make a second, "catch-up" pass if changes were made during it's first pass. Usually this is very quick, but since the first one way very slow, this one may be worse.
    Do you have any folders, particularly email mailboxes, with a very large number of files (thousands), that are actively being added-to or changed? There was a similar situation recently where an app named SpamSieve was putting messages into a "spam" folder, and the user never cleared it out. Clearing it out helped, but excluding it from Time Machine solved the problem.
    Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). I think it will only show completed backups, so you may not be able to find anything. But look at what's being backed-up to see if any of the files, even if there's only one, are in extremely large folders. If so, try excluding the folder (TM Preferences > Options).

Maybe you are looking for