Time Machine hangs here every time

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

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

Similar Messages

  • Time Machine backup fails every time at around 40GB

    Every time I try to back up my older Unibody Macbook, everything seems to go well, until it reaches about 40GB backed up, at which point it shows an error message that just says "Unable to complete the backup, an error occurred while copying files to the backup volume"
    My Macbook's hard drive is almost full, I think it only has about 10GB free, could this be the cause of the problem?
    Or maybe the cause is the fact that the hard drive is 3.0 even though it says its also compatible with 2.0? Should I maybe try using a hard drive thats 2.0 only?

    Try C3  in the 1st linked article.
    Time Machine Troubleshooting
    Time Machine Troubleshooting Problems

  • Time Machine Backup  fails every time "Backup could not be completed"

    I want to do a new Time Machine Backup on my iMac2007 Snow Leopard 10.6.8 fails every time with message  "Backup could not be completed."
    Console says "Error 11" Some Files allways can not be copied/saved by Time Machine,  i search an exclude them in TM not to save them, try again, new ones po up every time.
    Does anyone know a solution?

    One thing which may help.
    I had similar issues....a few times.
    Have done all the renaming (<8 characters) etc etc as detailed in these forums.
    The first time, I erased TC HD and started again. This fixed things for a few days, and then the same issue came back again.
    The next time, I simply copied the sparsebundle file (so I had two sparsebundles, one called xxxxxxxx.sparsebundle, and the other called xxxxxxxx copy.sparsebundle (luckily I had room on the HD to do this)). Then I deleted the original sparsebundle, and before I could rename the copy back to the original filename, the image mounted and started backing up....to the sparsebundle with " copy" still in its name.......so I left it be.
    A week or so went by, and then I got the same "unable to mount" error message.
    Rather than going thru the whole process again, I simply took the " copy" out of the sparesbundle filename, and all was well again.
    I continue to get "unable to mount" error messages occasionally, so I simply rename the sparsebundle file (either by adding or removing " copy"), and it seems to resolve the problem, at least for a while.
    While not a fix, it seems to be a workaround for me until Apple works out what the issue is, and fixes it.
    Hope this helps someone.
    P.S. One word of caution. I just had the thought, while writing this, that I have not actually gone into Time Machine to check that previous backups (eg, one hour ago, one week ago, original backup) are there and are able to be accessed, should the need arise. Because the back-ups appeared to be working, I assumed, and assume, they were. Won't be able to check this for a few days as I am on the road.

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

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

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

  • Time Machine Hangs - Help!

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

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

  • Backups work, enter time machine "hangs"

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

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

  • HT3275 How can I program the Time Machine to backup every 4-6 hours instead of hourly?

    My Time Machine backs up every hour and when it occurs my Mac operating speed slows down to a crawl.  Is there a way to change the settings so that Time Machine backs up every 4-6 hours or at specific times of the day, e.g. 6AM, Noon and 6PM?
    Many thanks,
    Time Machine Novice

    Sawtooth Prop wrote:
    My Time Machine backs up every hour and when it occurs my Mac operating speed slows down to a crawl. 
    That shouldn't happen, unless you've made lots of changes and have your Mac already pretty well maxed-out.  Changing the backup interval is just addressing the symptoms, not the cause.
    Check the size of your backups;  if they seem much too large considering what you've done since the last backup, see #D4 in Time Machine - Troubleshooting for some common culprits, and ways to find out what's actually getting backed-up.
    If the sizes seem reasonable, see #2 there for things that may be slowing your backups down.

  • Firefox hangs nearly every time I am working in Blackboard.

    I teach on line using Blackboard. Since installing Wndows 7 Firefox hangs nearly every time I am working in Blackboard...and this is every day. Firefox doesn't hang on my home desktop using Vista 64. I have all the latest Java updates and have continually queried Blackboard for a solution with no result.

    Could you describe the new window in more detail? For example, is it an ad for something, or a login page, etc.
    Since this occurs so regularly, I think it would make sense to try browsing for an hour in Firefox's Safe Mode to see whether that makes any difference. This will temporarily disable your extensions, which are the type of add-on most likely to cause mischief.
    You can restart Firefox in Safe Mode using
    Help > Restart with Add-ons Disabled ''(Flash and other plugins still work)''
    In the dialog, click "Start in Safe Mode" (''not'' Reset)
    Any difference?

  • Time Machine hanging, I/O error

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

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

  • Time Machine hangs 'preparing items for backup'

    Time Machine continually spinning 'preparing items for backup'
    TM Logs say:
    Starting standard backup
    Backing up to: /Volumes/MyBook TimeMachine/Backups.backupdb
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100190560 "The file “bzdone_20090128_1stats.xml” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100521200 "The file “bzdone_200901311.bzff” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100521fa0 "The file “bzdone_20090131_1stats.xml” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100521200 "The file “bzdone_200902041.bzff” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001d5530 "The file “bzdone_20090204_1stats.xml” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001d5510 "The file “bzdone_200902051.bzff” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100522610 "The file “bzdone_20090205_1stats.xml” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1005220f0 "The file “bzdone_200902061.bzff” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
    Can't find anything relevant googling the error message - seems to appear on damaged software install CDs so possibly the files are corrupt on my harddrive? I think .bzff file are from 'Backblaze' online backup, but given the date in the file name they have previously backed up successfully.

    chassa wrote:
    I think .bzff file are from 'Backblaze' online backup, but given the date in the file name they have previously backed up successfully.
    Try excluding them from Time Machine, per #10 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum).
    If that doesn't help, it may be something else on your internal HD. Verify it, 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 this forum).

  • Lion 10.7.2 On both mac book pro and iMac, both with Lion 10.7.2, obtain repeated iCal event notifications from calendar or address book.  Cannot turn these off.  They repeat several times per session and every time computer is used.  How to diagnose this

    Lion 10.7.2 On both mac book pro and iMac, both with Lion 10.7.2, obtain repeated iCal event notifications from calendar or address book.  Cannot turn these off.  They repeat several times per session and every time computer is used.  How to diagnose this?

    First, uninstall "SuperTV" (whatever that is) according to the developer's instructions. It isn't working and it's filling the log with noise.
    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application.
    Step 1
    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.
    Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Post the messages logged before the boot, while the system was unresponsive or was failing to shut down. Please include the BOOT_TIME message at the end of the log extract.
    Post the log text, please, not a screenshot. 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. In most cases, a few dozen lines are more than enough.
    PLEASE DO NOT INDISCRIMINATELY DUMP THOUSANDS OF LINES FROM THE LOG INTO A MESSAGE. If you do that, I will not respond.
    Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.
    Step 2
    Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

  • How can I resolve OSStatus Error 13 on Time Machine when connecting to Time Capsule on Lion?

    This is a semi-rhetorical question: I have now resolved this for my own setup, However, there was very little information on this error in the fora, so I thought I would post my experience with getting a Time Capsule (2TB, 3rd edition) to work on OS X Lion after the AFP/NAS debacle.
    Background
    My third party LaCie Big Disk Network* NAS died when Lion came out.
    I could access neither Time Machine nor the drive through Finder.
    The excellent thread on "Lion: Connecting to legacy (pre-Lion) AFP services - and Mac OS X (server)" (https://discussions.apple.com/thread/3258472?start=0&tstart=0) allowed me to access the drive via Finder to save my files but, of course, Time Machine was still broken. That guide showed you how to lift security restrictions on AFP shares.
    For reasons explained below [disclaimer: rant follows] I decided to ditch the LaCie and purchased a Time Capsule.
    The Problem
    Time Capsule connected via DSL to the net and set up a wifi network with a green light.
    The "Data" mount for Time Machine was visible in Time Machine, but trying to access it showed the following error:
              The operation couldn’t be completed. (OSStatus error 13)
    Trying to open the share in Finder using the appropriate credentials showed:
              The operation cannot be completed because the original item for "Data" can't be found
    Things that didn't work
    Turning lots of things on and off
    Resetting the DSL modem, the router (Time Capsule), the computer
    Repairing permissions
    What DID work
    Undoing the modifications made during the process of mounting the old LaCie NAS
    To do this, open Terminal and enter:
    sudo -s
    chmod o+w /Library/Preferences
    cd  /Library/Preferences/
    rm com.apple.AppleShareClient.plist*
    (from https://discussions.apple.com/thread/3258472?start=0&tstart=0)
    Then restart your computer.
    This worked for me. I don't UNDERSTAND any of why this did or didn't affect the computer, so please don't ask me to explain how it worked or what else to try. I thought I would just put this out there for knowledge.
    * LaCie have really got my goat. Unlike other manufacturers who seem to be trying to provide support for their drives (Western Digital MyBook), LaCie have stated outright that they will not be providing any updates for their Big Disk Network. This is a hard drive they describe as a "Professional NAS", though I can't think of many professions where £200 backups need to be replaced every two years to keep abreast of security updates. In their defence, the drive is no longer manufactured… but, IMHO, I don't see that as sufficient reason to abandon all support or updates immediately. Boo! On the upside, loving my shiny new refurb Time Capsule.

    Our true genius died a little while ago.
    But up to Mountain Lion he has tones of info ..
    http://pondini.org/TM/Troubleshooting.html
    Try some of the section C solutions.
    It is more than likely network.
    BUT do the following.
    1. Install the widget A1
    2. Reset TM, A4
    3. Verify the backup, A5
    4. Reboot the whole network and restart it in order.. modem.. TC.. MB Air.
    No luck to this point.
    Tell us exactly what OS you have.
    The worst possible is Mavericks. If you are trying to connect to old backups after an upgrade it is hopeless.
    I recommend you start over.
    Simply wipe the TC and start afresh.
    Manually mount the TC disk in Mavericks so you are sure it is working. Tell us if you run into trouble.
    Most important.. in wireless network preferences are you running ipv6 in link-local mode.

  • Time Machine over AirPort to Time Capsule... maybe a solution

    Like a lot of people on this forum, apparently, I have been suffering from the inability to make reliable Time Machine backups to a Time Capsule over AirPort. Here's what I did to solve the situation.
    Here's my network setup:
    I have an ADSL wireless box with b/g network connected over ethernet to a 1-TB Time Capsule which has a 5 GHz 'n' network. Using 5 GHz 'n' network where I am means no interference. All equipment that is not capable of 'n' is on the wireless box, 'n' equipment (basically, only my MacBook Pro) gets on the Time Capsule. It doesn't make internet faster, but sure makes the Time Capsule accessible. Both networks are hidden and secured with WEP (b/g) or WPA2 (n).
    (the Time Capsule is double-NATted, unfortunately, to cut down on network chatter in the system log)
    After upgrading to 10.5.6, I think I haven't been able to make a reliable Time Machine backup over AirPort. It may have been well before that (possibly with the AirPort Extreme update) but I don't remember. Most of the time, before the wireless box arrived, I have been making far-too-irregular backups over ethernet to the Time Capsule.
    Anyway, I had been trying to get Time Machine to work over AirPort to the backup on the Time Capsule. I had made the original backup over ethernet (all 500 GB worth over a weekend). For the incremental backups, though, I would prefer AirPort because keeping a cable attached really is a pain. Of course, it didn't work right away.
    What I couldn't figure out was why. Time Machine mounted the sparsebundle volume on the Time Capsule, but after that it seemed to do nothing with it. I left it for half a day and found little by way of relevant network activity. I tried the following to no avail:
    * disabled Little Snitch (outgoing firewall) and the OS X firewall (incoming firewall)
    * disabled security on the network
    * disabled and re-enable Time Machine
    * changed the name of the sparsebundle volume (that was dumb!)
    * trash Time Machine preferences and re-select the backup disk
    * reboot, reboot, reboot
    Whatever I did, it sucked. Connecting over ethernet was excellent, and incremental backups went really quick, but AirPort just didn't fly. It would have been worse if it were slow; chances are then it'd be a hardware problem. But nothing was going over AirPort with Time Machine.
    In amongst the surfing, I found somewhere how to downgrade the firmware on the Time Capsule. Worth a try since nothing was working. I opened up the AirPort Utility and checked, but it would only give me 7.3.2 (AirPort Utility 5.3.2). I searched and found the AirPort 5.3.1 software, and using Pacifist extracted the AirPort Utility application. That would let me 'downgrade' the Time Capsule firmware to 7.3.1 (and 7.3). It downloaded the 7.3.1 for me and put it on the Time Capsule without problems.
    I then made a test run with Time Machine over ethernet, that was fine. The I tried over AirPort - and hey presto! it worked! I re-enabled my network setup (firewalls, security) and it's still working fine.
    So, if your Time Capsule is on 7.3.2 firmware and Time Machine over AirPort *****, try downgrading to 7.3.1. The AirPort 5.3.1 software, which can download and install the 7.3.1 software (5.3.2 doesn't) can be found here:
    http://support.apple.com/downloads/TimeCapsule_and_AirPort_Base_Station__802_11n__Firmware_7_31
    Note: you need Pacifist to extract the AirPort Utility application;
    do not install the software over your existing AirPort software

    This may be tough because TM isn't supported over wi-fi unless you're using a Time Capsule. There are a couple of resources available to you and I'd also recommend posting in the Snow Leopard forum because TM is part of OS X the OS X forum would be the right venue. The first thing is I'm guessing you are using a router, if so make sure the firmware on it is up-to-date. You will need to refer to the router's manual. You also should do the same with the modem too. Some written resources are:
    Time Machine FAQs
    Time Machine Troubleshooting
    Pondini Time Machine Tips
    That's about all I can help you out with.
    Good luck!

  • I am trying to delete a Time Machine backup from a Time Capsule.

    I am trying to delete a Time Machine backup from a Time Capsule.  The file is about 400GB and my MacBook has been trying to delete it for 5h now. It still says "deleting" but has not given me a "time remaining" yet. Any idea of what I could do????

    You should not attempt to delete backups using the Finder. The result can be a corrupted backup.
    I recommend you let it complete, no matter how long it takes. That could be days, if your TC is connected via wireless.
    It is not necessary to delete backups, since Time Machine will delete old backups some time after they have been deleted from your source volume. For more information read Apple Support Communities contributor Pondini's explanation here: Should I delete old backups? If so, How?

  • Time machine was not working.  I bought a new time machine and migrated time machine files to new time capsule; not recognized by yosemite

    Time machine was not working after yosemite upgrade on new and old MacBooks in my house.  I bought a new time machine and migrated time machine files to new time capsule. I changed the names of the older sparse bundles to the default values.  Yosemite still does not recognize them. 

    I presume the bought a time machine means a time capsule.
    How did you migrate the Time Machine files?
    From where? A Time Capsule or external drive?
    It is difficult to get TM working with Yosemite.. since it doesn't work after the upgrade on the old TM backup.. it will not work on the migrated files either.
    You simply start a new backup and store the old backups for a few months until you are ready to dump them.
    The instructions for inheriting old backups is B5 and B6 here.
    http://pondini.org/TM/Troubleshooting.html
    However it is just unlikely to work.. TM in Yosemite is very different. Broken even.
    I also strongly recommend people to use Carbon Copy Cloner or some other 3rd party backup until Apple get the bugs fixed. And after several months.. they are still rampant.

Maybe you are looking for

  • HP Envy D411A WIA\TWAIN non-functional in Windows 7 64-bit

    I'm running windows 7 64-bit with a d-link dir-655 and the HP Envy D411A which I just received. I had no issues connecting the printer to the WPA2 network and connecting all the ePrint capabilities, and connecting it as a printer was problem free. Th

  • How to view the progress of an Clientimport via R3TRANS

    Hi together, how can I view the progress of an Import of an Clienttransport. I have done an Client Export via SCC8. This transaction had created about 40 files with 2GB size. Now I am Importing this files with STMS. This transport requests are now im

  • Big problem with Lion...

    I have problems too... My mail box is very slow now and safari also....  And my wifi is not so efficient than before. I think we have to wait for an upgrade but maybe someone has a solution for me. Thanks.

  • 'i tunes has detected an ipod which needs recovery'

    My son has an ipod touch 3g...stopped charging and asked for connection to pc via usb...on connection a message box appears on i tunes on pc 'i tunes has detected an ipod that requires recovery' 2 buttons to press - one 'restore' and one 'cancel'....

  • Jvmx.jar missed

    Can any body please help in solving this problem ? when i start portal server ,In the central instance, SDM and Dispatcher instances are started, but server is not started. In Developer tracktrace, i find the below error. Bootstrap nodes -> [00] boot