Previous 1 2 3 4 5 Next 71 Replies Latest reply: Jul 1, 2013 2:30 PM by Nuno.Franca Go to original post
  • montcley.jean Level 1 Level 1 (0 points)

    I finally decided to erase my Time Capsule disk and restart a new backup from scratch with Time Machine.

     

    Working fine every hour all night long.

     

    But as soon as I reboot my Imac,

     

    Problem resurface again !!!!!!

     

    Please Apple Help !

     

    This never happened before 10.7.2 Release !!!!!

     

    Jean.

  • softwater Level 5 Level 5 (5,370 points)

    Time machine *****. Use carbon copy cloner. Far more reliable and configurable.

  • montcley.jean Level 1 Level 1 (0 points)

    I finally decided to erase my Time Capsule disk and restart a new backup from scratch with Time Machine.

     

    Working fine every hour all night long.

     

    But as soon as I reboot my Imac,

     

    Problem resurface again !!!!!!

     

    Please Apple Help !

     

    This never happened before 10.7.2 Release !!!!!

     

    Jean.

     

  • phobos Level 1 Level 1 (0 points)

    it worked for me too... for now

  • Joseph Bacon Level 1 Level 1 (45 points)

    Jean:

     

    Every time I start up my Mac Mini, I still have to go through the steps I listed above to reconnect Time Machine. Because of that, I'm also backing up to another USB drive.

     

    I'll keep doing that until the bug is fixed.

  • Douglas S Level 1 Level 1 (5 points)

    So, this morning I fired up the iMac and let it go into Time Machine backup on its own.  It did, and it worked.  I changed nothing.  ???

     

    Yesterday it froze in the middle of a 3gb backup and I had to power off....

     

    I am using Carbon Copy Cloner to make full one time backups on a separate drive just because the TC is freaking me out a bit - it contains everything.  Last year I had the HD crash.  Replaced it and restored from the TC - it took 2 days to complete but amazingly the entire Mac was as before so I am hoping this is just a minor glitch that is soon removed.

  • Marylee@3kd Level 1 Level 1 (0 points)

    I think the key here is to make certain that the name of your Time Capsule disk in AirPort Utility (as Douglas talked about in the steps above from Express Lane)  matches exactly to the name of your Disk image in Time Machine Backups Info.  Look in the Finder window and click on the name of your AirPort device.  Open the data file and then double click on the name of your backup folder.  A "Time Machine Backups" icon will appear on your desktop, right click on it to view file options, then click on Get Info.  The new window that pops open in the upper left of your desktop screen will tell you the name of the Disk Image. This is what must match the name of your Time Capsule Disk.

     

    In my case, the Time capsule disk was named "Data" (just like Douglas), but my sparsebundle disk image was called: /Volumes/Data-1/Mary Lee's iMac (2).sparsebundle.  The extra -1 was the key to my error message.  I think Time machine couldn't find the backup folder because the names didn't match. Duh.

     

    I clicked on Update in the bottom right of Airport Utility, and my sparsebundle lost the -1 from the name in Get Info and now reads /Volumes/Data/Mary Lee's iMac (2).sparsebundle

     

    My time Machine is back to normal, and it is still working after reboots.  Yeah!

  • iburden2 Level 1 Level 1 (0 points)

    Won't work for me unfortunately, although you are on the right track I'm sure.  I did find the -1 addition to the sparsebundle address as you described.  I managed to get rid of it, but I had to rename the Time Capsule Drive to do it.  But after rebooting the problem came back.  The Express Lane solution does work for me, but only until I reboot, then it's back to the same problem.

  • montcley.jean Level 1 Level 1 (0 points)

    Sorry didn't work for me either ---> just like for you iburden2 !

     

    Thanks anyway for sharing your experiments !

     

    The more  entries we make on that topic the more chances we have to be heard by Apple,

     

    don't you think ?

     

    I suggest we should all contact ou support services when possible to !

     

    Jean.

  • Joseph Bacon Level 1 Level 1 (45 points)

    Doesn't work for me, either.

     

    Every time my Mac Mini is rebooted, I have to follow the steps I posted above to access Time Capsule. The fix propsed by Marylee doesn't work.

     

    So unitl it's fixed I have another drive attached to my Mac Mini and it's getting a backup from Carbon Copy Cloner.

  • Richno Level 1 Level 1 (0 points)

    Express Lane solution above worked perfectly for me!

     

    Thx,

     

    Rich

  • Joseph Bacon Level 1 Level 1 (45 points)

    I followed those steps, too, but STILL have the same problem. So each time I boot my Mac Mini, I have to go through the steps above to get Time Capsule to backup.

     

    I tried a reset on Time Capsule with a new backup and it STILL has the same problem.

     

    Until it's fixed, I have another USB drive attached running Carbon Copy Cloner. I have it set to backup every 24 hours.

     

    I tried to use Automator to set up a routine to disconnect Time Machine and reconnect it, but I cannot get that to work. I don't want to put my Mac Mini in constant sleep since I ran into a problem when I wasn't here and my ex roommate used my Mac to go into gamesites and get me into trouble.

  • iburden2 Level 1 Level 1 (0 points)

    I am still having problems so I have installed the dashboard widget "Time Machine Buddy" to try to get more information.  It reported the following:

     

    Starting standard backup

    Attempting to mount network destination URL: afp://Rosemary%20Burden@Time-Capsule.local/Time%20Capsule

    Mounted network destination at mountpoint: /Volumes/Time Capsule using URL: afp://Rosemary%20Burden@Time-Capsule.local/Time%20Capsule

    Failed to eject volume /Volumes/Time Capsule (FSVolumeRefNum: -104; status: -47; dissenting pid: 0)

    Waiting 60 seconds and trying again.

    Network destination already mounted at: /Volumes/Time Capsule

    Failed to eject volume /Volumes/Time Capsule (FSVolumeRefNum: -104; status: -47; dissenting pid: 0)

    Waiting 60 seconds and trying again.

    Network destination already mounted at: /Volumes/Time Capsule

    Failed to eject volume /Volumes/Time Capsule (FSVolumeRefNum: -104; status: -47; dissenting pid: 0)

    Giving up after 3 retries.

    Backup failed with error: 21

     

    I don't understand this information but I'm a little puzzled to see references to my wife's name in there (this is her computer really and I'm trying to ensure her account is backed up) as this is not the name of this computer (it's called "Silver Macbook Pro" and the sparsebundle on the time capsule is called "Silver Macbook Pro.sparsebundle.)

     

    In the middle of writing this, it actually backed up correcly, and now the report from Time Machine buddy says this:

     

    Starting standard backup

    Network destination already mounted at: /Volumes/Time Capsule

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    Disk image /Volumes/Time Capsule/Silver Macbook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups

    Backing up to: /Volumes/Time Machine Backups/Backups.backupdb

    1.40 GB required (including padding), 379.94 GB available

    Copied 3860 files (4.6 MB) from volume Silver MacBook Pro HD.

    1.39 GB required (including padding), 379.94 GB available

    Copied 613 files (1 KB) from volume Silver MacBook Pro HD.

    Starting post-backup thinning

    Deleted /Volumes/Time Machine Backups/Backups.backupdb/Silver Macbook Pro/2011-10-26-215858 (484.0 KB)

    Post-back up thinning complete: 1 expired backups removed

    Backup completed successfully.

    Ejected Time Machine disk image.

    Ejected Time Machine network volume.

     

    Now my wife's name does not appear, and it works.  What caused the change?  I don't know.

  • iburden2 Level 1 Level 1 (0 points)

    AARGH!   Reboot and the problem is back again.

  • Joseph Bacon Level 1 Level 1 (45 points)

    I tried that too, worked fine until I shut down and restarted, then back on square one again!!!!!!!!!