Stuck "calculating changes."  Again.

This is driving me crazy. It's the only problem I am having with my brand new Intel core i3 iMac. Time Machine chugs along smoothly for anywhere from a day to a week, then gets stuck seemingly forever "calculating changes." It has been calculating changes for four hours now. All the system log in Console shows is:
Apr 3 06:44:36 macintosh-2 com.apple.backupd[5839]: Starting standard backup
Apr 3 06:44:36 macintosh-2 com.apple.backupd[5839]: Backing up to: /Volumes/G-DRIVE Back-Up/Backups.backupdb
Last successful backup was an hour before this. The computer was not even used between the end of the previous successful backup and the beginning of the stuck backup. So I have no idea what changed.
If I try to stop the backup, the computer will freeze (beachball of death) so that only a hard restart will work. If I try to restart without touching the backup the computer will freeze (beachball again) and again, only a hard restart will work. If I leave it alone, the beachball will go for literally hours until I do the reboot. I've restarted this machine more in the last three weeks than I did on the previous machine in the past three years. I've done everything in Pondini's excellent troubleshooting guide. The only thing that seems to work at all is trashing the TM Preferences. Then I'll go along just fine for anywhere from a day to a week before the trouble starts again. I can't pinpoint any particular software or files, and have spent hours trying to do so.
I'm at my wit's end and really don't want to harm the computer with all the hard restarts. I searched the forum but couldn't find anybody with this exact situation. Any thoughts from y'all would be greatly, greatly appreciated. -- Tom

OK. Did everything like Linc said. At the end of verifying/repairing the TM drive in Safe Mode (there was nothing found wrong) the external drive went away. I got an error message stating that I had ejected the drive improperly. I did no such thing; the computer went immediately from the green "appears to be OK" to the "improperly ejected" window. Could not get the drive to appear on the desktop no matter what to try the backup in Safe Mode.
Finally restarted the computer in my usual environment. No drive on the desktop. This time turning it off, reconnecting the cable, and turning the drive back on worked and it reappeared. Reconfigured Time Machine using the backup drive and ran a successful backup.
Now we'll have to wait and see if it continues to back up, or if I hit the "calculating changes" snag again, in a day or six.

Similar Messages

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

  • Stuck on "calculating changes"

    Hi there,
    I have time machine set up on an external USB drive and I'm stuck on "calculating changes" when I try to make a backup. It was normal until a couple of days ago, when the drive suddenly disconnected from the Imac in the middle of a backup (I think it was due to an oscilation on the power supply or something like that, not physically disconnected). Ever since then, I'm not able to make new back ups.
    I already ran a disk test (on disk utility) and it is normal. I also tried to remove and add the disk on the time machine preferences, but still nothing.
    I got a log from Time Machine Buddy:
    *Starting standard backup*
    *Backing up to: /Volumes/Backup e Dados/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 (101)*
    *Waiting for index to be ready (100)*
    *Waiting for index to be ready (101)*
    Any ideas on how to fix this?
    Thanks,

    Edu C wrote:
    Hi there,
    Hi, and welcome to the forums.
    I already ran a disk test (on disk utility) and it is normal
    Do you mean you ran +*Repair Disk+* (not permissions) on the TM drive? If not, try that.
    *Event store UUIDs don't match for volume: Macintosh HD*
    That's normal after a disconnection; it just means Time Machine isn't sure it got everything the last time.
    *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 (101)*
    *Waiting for index to be ready (100)*
    *Waiting for index to be ready (101)*
    These mean Time Machine is indexing your backups (because of the abnormal disconnection). It should complete that and proceed with the backup, which will probably take a lot longer than usual.
    If Disk Utility didn't find a problem with the file system, the drive itself may be damaged. How old is it?
    If you haven't yet, try cancelling the backup, ejecting, disconnecting and powering it off for several minutes. Then Restart your Mac and try again. Make sure all connections are snug and secure; try different ports, cables, and combinations of the two (a plug that works fine in one port may not make good contact in another).

  • Stuck on calculating changes - Waiting for index to be ready

    I've got a Time Machine which had my disk properly backed up (~500 Gigs). Then, I used Entourage Time Machine to save my email database to a set of local XML files (tens of thousands of new files). Since then, it's stuck on Calculating Changes; I tried stopping it, removing the .plist file, stopping/restarting the service, etc. I restarted it again and now it's once again on Calculating Changes for 12 hours now. Time Machine Buddy says "Waiting for index to be ready". Could it possibly really be doing what it needs to do or is it stuck somehow and is there anything else I can do??
    thanks in advance,
    Mike

    Michael Levin wrote:
    Then verify your internal HD and repair your backups, per #A5 in Troubleshooting.
    did that - repaired the disk, no problems found.
    Uh, you need to check your internal, too, if you didn't. It's probably ok, but it's best to be sure. Then Restart your Mac.
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    A few of those may not be a problem, especially after a failed backup. The backups have to be indexed for TM to work right.
    why isn't the index ready - could it have anything to do with Spotlight (which is also going like mad, but at least now gives a time estimate) - is that the index it's talking about??
    Perhaps. Both Spotlight and Time Machine use the mds process to index.
    |
    Ok, so I disabled Spotlight, deleted all the .Spotlight files on all volumes, and restarted Time Machine having excluded the Entourage database and 56 Gigs worth of .xml files of individual messages.
    56 GB? Holy moley!
    Event store UUIDs don't match for volume: Main Internal Drive (Leopard)
    Forcing deep traversal on source: "Main Internal Drive (Leopard)" (mount: '/' fsUUID: 22E61BEA-43E3-3C1C-985D-4589FACE5629 eventDBUUID: D2A7E78E-C39A-46A3-B273-CCEE5048369C), {1, 1, 1, 0}
    Node requires deep traversal:/ reason:must scan subdirs|require scan|
    Normal after a failed backup; Time Machine's not sure what was where when the "lights went out," so has to compare everything on your system to the backups to figure out what needs to be backed-up.
    No pre-backup thinning needed: 24.38 GB requested (including padding), 983.14 GB available
    The deep traversal completed. It found about 20 GB to back up (plus 20% for workspace -- the "padding" in the message).
    Error: Flushing index to disk returned an error: 0
    That's another problem writing the index to the TM drive.
    Try a +*Repair Disk+* on it again, and make sure all connections are snug and secure, and try the backup again.
    If this continues, it's beginning to look like a problem with the disk or connections. Try different ports, cables, and combinations of the two -- cables do deteriorate, and a plug that works fine in one port may not make good contact in another one.

  • 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 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 machine is getting stuck whilst 'calculating changes'

    Updated my external HDD to use for TIme Machine. 3 weeks later and TM is trying to back up but getting stuck on 'calculating changes. I can't access or eject the drive whist that's happening so have to just pull the USB and restart.
    After that it's fine, but I'm worried that not ejecting properly might damage the drive or the content. Any ideas?

    Check this post for advice:
    Time Machine - Troubleshooting

  • Time Machine is stuck at calculating changes

    It will try all day to back up but never gets past calculating changes. I am not sure where to even start. Can you help me?

    kcboy713 wrote:
    Could it be a problem if it says I have 25g of 1000g available and my full back up is 106g?
    Is this Drive used exclusively for TM or do you have other stuff on it... ?
    Also some more Details about the Drive and your Mac would be helpful...

  • Calculating Changes... Besides the great Pondini guide...

    Greetings,
    I have a recent iMac with Snow Leopard. I have two external Firewire 400 G-Tech external Harddrives connected to the iMac. One is daisy chained into the other. Every now and then I get the message "calculating changes" which never goes away until I reboot the mac. It then usually works as normal for a week or so.
    I have read this Pondini guide from start to finish and done most of the upkeep but this message keeps returning. I went so far as to reformat the drive a while back to start fresh but the error message makes its way back.
    I don't think anything is wrong with any of these hard drives so I am looking for other areas of error. If I was to guess I think it has something to do with mount points or even the drive goes into sleep even when it is not supposed to. Can you update firmware on these G-Tech harddrives? Should I change to the USB 2.0 and see if that changes anything?
    I'm going to post a couple of TM Buddy messages so let me know what you see...
    Today at noon:
    Starting standard backup
    Backing up to: /Volumes/Backup/Backups.backupdb
    No pre-backup thinning needed: 837.7 MB requested (including padding), 520.75 GB available
    Copied 1616 files (118.1 MB) from volume Snow Leopard.
    No pre-backup thinning needed: 697.2 MB requested (including padding), 520.63 GB available
    Copied 80 files (33 bytes) from volume Snow Leopard.
    Starting post-backup thinning
    Deleted backup /Volumes/Backup/Backups.backupdb/iMac/2010-12-14-113914: 520.66 GB now available
    Post-back up thinning complete: 1 expired backups removed
    Backup completed successfully.
    Then, it didn't do a backup until 5pm:
    Starting standard backup
    Backing up to: /Volumes/Backup/Backups.backupdb
    Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Backup/Backups.backupdb/iMac size:7
    Detected system migration from: /Volumes/Backup/Backups.backupdb/iMac/2010-11-10-174219/Snow Leopard
    Error: (-36) Creating directory 2010-12-15-170413.inProgress
    Failed to make snapshot container.
    Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Backup/Backups.backupdb/iMac size:7
    Backup failed with error: 2
    Then restarted:
    Starting standard backup
    Backing up to: /Volumes/Backup/Backups.backupdb
    Event store UUIDs don't match for volume: Snow Leopard
    Node requires deep traversal:/ reason:must scan subdirs|new event db|
    No pre-backup thinning needed: 1.15 GB requested (including padding), 520.66 GB available
    Copied 8387 files (385.7 MB) from volume Snow Leopard.
    No pre-backup thinning needed: 697.3 MB requested (including padding), 520.26 GB available
    Copied 663 files (803 bytes) from volume Snow Leopard.
    Starting post-backup thinning
    Deleted backup /Volumes/Backup/Backups.backupdb/iMac/2010-12-14-193911: 520.28 GB now available
    Deleted backup /Volumes/Backup/Backups.backupdb/iMac/2010-12-14-183915: 520.31 GB now available
    Deleted backup /Volumes/Backup/Backups.backupdb/iMac/2010-12-14-181112: 520.34 GB now available
    Deleted backup /Volumes/Backup/Backups.backupdb/iMac/2010-12-14-173921: 520.38 GB now available
    Deleted backup /Volumes/Backup/Backups.backupdb/iMac/2010-12-14-163912: 520.41 GB now available
    Post-back up thinning complete: 5 expired backups removed
    Backup completed successfully.
    Cheers

    The TM drive (Nothing else on there) is around 24 months. It has a FW400 and USB2.0 interface on the back. Try connecting it via USB for a while. If that stops the problem, you'll at least have narrowed it down.
    Will Try tomorrow...
    I don't think I have a situation with OSX, but my mac does freeze once a month or so requiring a forced reboot. This is usually however due to some sort of issue with TM, Handbrake, iTunes or similar.
    That may be related. I don't see that you've posted about that earlier, so some details might help. If you're talking about TM being stuck in Calculating Changes, what messages do you see on the TM Preferences panel when that happens. You should see "Calculating Changes" only briefly, then "Scanning xxxx items" for a while, then "Preparing xxx items." Where does it hang?
    It never changes from Calculating changes... I usually notice it because an icon has popped up on the screen "calculating changes". I usually never see the update. This is why I reboot otherwise it would never backup again.
    Have you Verified your internal HD, and repaired your TM drive and other external, per #A5 in Time Machine - Troubleshooting (or use the link in User Tips at the top of this forum)?
    Repaired, Verified, permissions, all according to your guide. Everything checks out OK...
    Should I try to reinstall OSX or just do the latest Combo update? Any input would help...We don't know enough about your other problems, but this one seems more like hardware. But if you want to go that route, I'd start with the Combo. If that doesn't help, reinstall OSX "in place" (without erasing your HD), then the Combo again.
    Erasing and reinstalling everything is a last resort.

  • Time Machine - Calculating Changes

    Many have suffered from Time Machine getting stuck at 99% after a Time Capsule added to system. I was tortured by the same problem and finally fixed it by reasoning things out. Remember, Time Machine looks to back up everything. When you add a Time Capsule your old Time Machine files remain somewhere. In my case it was on another smaller internal SATA. When I added the TC, I forgot to exclude my old Time Machine drive. I went into TM preferences and excluded it and Voila! No more problems. Calculating 99% went away and the backup through ethernet Time Capsule proceeded quite quickly and without problem. I guess Time Machine does not like to back up it's own files on a non-selected drive.
    I hope this helps others who are suffering. Worked like a charm.
    Ted Stam

    hc2008 wrote:
    Network destination already mounted at: /Volumes/WD External
    Disk image /Volumes/WD External/HCC.sparsebundle mounted at: /Volumes/Time Machine Backups
    Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    It +has found+ the sparse bundle. It's not looking for the previous backups on your other internal HD.
    Backup content size: 157.8 GB excluded items size: 3.5 GB for volume Macintosh HD
    That message is sent when +Calculating Changes+ finishes -- TM has estimated how large the backup will be. The +Copying xx of yy GB+ message should be shown on the TM Preferences panel and the menu when you press the TM icon in your Dock.
    Try all the things in #D2 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
    Be sure the disk is formatted properly -- either GUID or APM *Partition Map Scheme* and +Mac OS Extended (Journaled)+ Format.
    Try all the things in #D2 of the Time Machine - Troubleshooting User Tip, also at the top of this forum.
    Also try connecting via Ethernet if possible, for the first full backup. That will be much faster, of course, and will rule out a bad WIFI connection.
    As a last resort, per your earlier post, try erasing the TM disk.

  • Tools are stuck cannot change tool in adobe illustrator cs6

    tools are stuck cannot change tool in adobe illustrator cs6. when i click on the arrow icons on any of the tools it does not work, I can only use the default tool on the tool bar. Shutting down does not fix the issue. Program has never worked. anyone have this problem? anyone have a solution? Ridiculous that I can't contact tech for support without paying when it's their crappy product that doesn't work.

    Jenna,
    It may be time for the list below (or just to go straight to 6)).
    By the way, what happens if you Alt/OptionClick the default tool, or use a keyboard shortcut such as L for Ellipse?
    The following is a general list of things you may try when the issue is not in a specific file, and when it is not caused by issues with opening a file from external media, see below. You may have tried/done some of them already; 1) and 2) are the easy ones for temporary strangenesses, and 3) and 4) are specifically aimed at possibly corrupt preferences); 5) is a list in itself, and 6) is the last resort.
    If possible/applicable, you should save current artwork first, of course.
    1) Close down Illy and open again;
    2) Restart the computer (you may do that up to at least 5 times);
    3) Close down Illy and press Ctrl+Alt+Shift/Cmd+Option+Shift during startup (easy but irreversible);
    4) Move the folder (follow the link with that name) with Illy closed (more tedious but also more thorough and reversible);
    5) Look through and try out the relevant among the Other options (follow the link with that name, Item 7) is a list of usual suspects among other applications that may disturb and confuse Illy, Item 15) applies to CC, CS6, and maybe CS5);
    Even more seriously, you may:
    6) Uninstall, run the Cleaner Tool (if you have CS3/CS4/CS5/CS6/CC), and reinstall.
    http://www.adobe.com/support/contact/cscleanertool.html

  • Time Machine calculating changes and never stops

    I have a 27" iMac and I have an intermittent problem with Time Machine.
    It will work great and then it will get hung on calculating changes and the only thing I can do is turn off the external drive to make it stop
    I have fixed the permissions on the c:\ drive and run repair disk on the external drive
    I am a Mac newbie so I don't know what else to do.  Any ideas on how to proceed to solve this problem?
    TIA
    Mark

    Error writing to backup log.  NSFileHandleOperationException:***
    -[NSConcreteFileHandle writeData:]: No space left on device
    Check with airport utility.. is there any space left on the TC. if not it cannot work.
    You will need to delete something or erase the drive after an archive..
    The former TM should do itself.. but it is better IMHO to take action yourself.. not to delete files but to archive and start again. Still that is my opinion only.
    Are you plugged in by ethernet? If not it will either take forever or not work.

  • Time machine no longer backing up (sticks on 99% calculating changes)

    Since updating to OS 10.6 time machine is no longer backing up. and it's constantly calculating changes.
    I have a time capsule which is connected via ethernet (as is the mac), I've had the computer on for days and it never gets past calculating changes.
    I've tried restarting the time capsule (on/off) and reselecting the Disk, but to no avail.
    I have yet to reformat the time capsule.
    Any ideas?
    Russell
    Message was edited by: Russell Tudor

    mike5282 wrote:
    several times after the upgrade to SL i've seen backupd die (this is the critical background process that runs the backup to TM).
    A reboot immediately solved the problem. There appears to be a major bug that was not caught in QA with backupd.
    I've also noticed, when I cancel a backup in Snow, and it does seem cancelled, with all the proper messages, backupd does not stop; if you do another backup, the same process wakes up and does it, including a new "Starting standard backup" message!
    That's one reason I recommend a restart.

  • Time Machine Backup Hangs at "Calculating Changes"

    Since upgrading to SL, I am unable to backup. I am using a WD MyBook HD linked to a TC for backing up my MacBook Pro 13" UB. Prior to upgrading all was operating normally.
    The process hangs at "Calculating changes 99%" . It will not progress beyond that point. I have to manually stop the backup.
    Here is the log:
    Sep 1 09:13:25 twnMacBook com.apple.backupd[768]: Starting standard backup
    Sep 1 09:13:25 twnMacBook com.apple.backupd[768]: Attempting to mount network destination using URL: afp://Tod%[email protected]/My%20Book
    Sep 1 09:13:41 twnMacBook com.apple.backupd[768]: Mounted network destination using URL: afp://Tod%[email protected]/My%20Book
    Sep 1 09:13:46 twnMacBook com.apple.backupd[768]: Disk image /Volumes/My Book/twnMacBook_00254bca016c.sparsebundle mounted at: /Volumes/Backup of twnMacBook
    Sep 1 09:13:46 twnMacBook com.apple.backupd[768]: Backing up to: /Volumes/Backup of twnMacBook/Backups.backupdb
    Sep 1 09:13:53 twnMacBook com.apple.backupd[768]: Event store UUIDs don't match for volume: Macintosh HD
    Sep 1 09:13:53 twnMacBook com.apple.backupd[768]: Waiting for index to be ready (101)
    Sep 1 09:14:00 twnMacBook com.apple.backupd[768]: Node requires deep traversal:/ reason:must scan subdirs|new event db|
    Any suggestions?

    Elkins45 wrote:
    I'm having exactly the same problem (hanging at 99%). I have a FW drive connected directly and I did an erase an install because I was having problems with my Leopard install.
    I've restarted a hundred times, erased and reinstalled three times and restarted the drive, all to no avail.
    Try a "full reset" of Time Machine:
    a. Go to TM Preferences, turn TM Off, de-select the drive (select "none"), and click the Options button. Note any exclusions in the +Do Not Back Up+ box, and other option(s) on that panel. Then quit System Preferences.
    b. Eject, disconnect, and power-off the drive for a few moments, then reconnect it.
    c. Delete the file /Library/Preferences/com.apple.TimeMachine.plist (in your top-level Library folder, not your home folder).
    d. Go back to TM Preferences, re-select your drive, re-enter any exclusions and other options.
    e. Do a +*Back Up Now*+ or wait for the next scheduled backup.
    If that doesn't help, try the Console app, as in my previous post, but do not filter for Backupd. See if there's anything else suspicious there. If so, copy and post a reasonable amount here.

  • Why does time machine stall on "calculating changes"?

    I have just purchased a Lacie d2 quadra 2Tb, and have connected Time Machine.
    It has successfully backed up my desktop. However, on about the third incremental backup it stall on calculating changes. I have read that this could be when a deep traversal scan is occuring, so I let it continue for 12 hours before rebooting!
    I have repartitioned and zeroed out the disk, and verified permissions etc, but to no avail.
    I have 2 other external drives, and a Time Capsule that work flawlessly with TM.
    Any other suggestions to remedy this would be most welcome.

    Thanks for your reply Dave. Well, I am on that path with Lacie. The two other drives are theirs also, but who knows. They recommended th zeroing out etc.
    I am also in discussion with Apple, who are tackling it from the Time Machine end, and something that might require a tweak with my system. 

Maybe you are looking for