Skip navigation

"Time Machine could not complete the backup" after 10.7.2 update

15366 Views 71 Replies Latest reply: Jul 1, 2013 2:30 PM by Nuno.Franca RSS
  • montcley.jean Level 1 Level 1 (0 points)

    Today I saw new 7.6 release of Time Capsule inner software was on line.

    I did install it ... hoping it would solve the Time Machine disk access problem ...

    Bad luck ! It didn't !...

    Let's hope it is the first step to a future Lion update fixing that isuue for good !

    Jean.

  • Joseph Bacon Level 1 Level 1 (45 points)

    Same here, Jean!

  • iburden2 Calculating status...

    I think the Time Capsule software update must have been a failed attempt to fix the problem.  Here we are 11 days later and still no progress.  This is getting tiresome.

  • luis2233jr Calculating status...

    I tried every method mentioned in the posts but was unseccusful, I was able to solve the issue by not using Back To My Mac, after i had restarted it i was able to start back up with no errors. Backing up as we speak.

  • Joseph Bacon Level 1 Level 1 (45 points)

    Once again, another failure because iCloud disabled Back to My Mac

     

    Going on 2 1/2 months and it's a major pain to manually shut down and relink Time Capsule. Very frustrating since I cannot get this resolved no matter what I've tried.

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

    Hi Joseph !

     

    Get a look at Time Machine not working after 10.7.2. upgrade last DaManni posts,

    Its giving some hope a new OS release could be on its way soon.

     

    Season Greetings from France,

     

    Jean.

  • mach0u Calculating status...

    TC still not working properly, I've tried alotof things and I've read most topics about these issues. But anyway, if it can help in some way, I ave 2 users on my iMac, and TC works for one of them, and for the other one backups always fail.

     

    backup from last night finished successfully for one of the users, but the other is always failing with the folllowing messages :

     

    Starting standard backup

    Network destination already mounted at: /Volumes/Backup

    Failed to eject volume /Volumes/Backup (FSVolumeRefNum: -129; status: -47; dissenting pid: 0)

    Waiting 60 seconds and trying again.

    Network destination already mounted at: /Volumes/Backup

    Failed to eject volume /Volumes/Backup (FSVolumeRefNum: -129; status: -47; dissenting pid: 0)

    Waiting 60 seconds and trying again.

    Network destination already mounted at: /Volumes/Backup

    Failed to eject volume /Volumes/Backup (FSVolumeRefNum: -129; status: -47; dissenting pid: 0)

    Giving up after 3 retries.

    Backup failed with error: 21

     

    And when I force the unmount and restart a backup pretty much the same :

     

    Starting standard backup

    Attempting to mount network destination URL: afp://Elo%20test@HOME.local/Backup

    Mounted network destination at mountpoint: /Volumes/Backup using URL: afp://Elo%20test@HOME.local/Backup

    Failed to eject volume /Volumes/Backup (FSVolumeRefNum: -129; status: -47; dissenting pid: 0)

    Waiting 60 seconds and trying again.

    Network destination already mounted at: /Volumes/Backup

    Failed to eject volume /Volumes/Backup (FSVolumeRefNum: -129; status: -47; dissenting pid: 0)

    Waiting 60 seconds and trying again.

    Network destination already mounted at: /Volumes/Backup

    Failed to eject volume /Volumes/Backup (FSVolumeRefNum: -129; status: -47; dissenting pid: 0)

    Giving up after 3 retries.

    Backup failed with error: 21

     

    It's really annoying :-/

  • luis2233jr Level 1 Level 1 (0 points)

    I have been having the same issue no matter how many tries I could never successfully run a back up, last night I decided to create a new user a run a new back up for all users. It WORKED I was able to back up everything. I will manually start a back up tomorrow, I will post a follow up and let you know if it works. Usually with other methods the second back up fails. Crossing my fingers!

  • Joseph Bacon Level 1 Level 1 (45 points)

    Appreciate the heads up, Jean!

     

    Right now, the Mac Book Air is working OK with Time Capsule. WHen I first bought my new MacBook Air, I transferred all the files from my old MacBook Pro. I'm thinking that there were some legacy threads in the Mac Book that didn't jibe with the 10.7.2 upgrade.

     

    I keep all my main files on my MacMini. Just wish I could get Time Capsule working with it again. Hopefully something good will come out on Tuesday!

  • amcalp Calculating status...

    Also having this problem. Subscribing.


    The strange thing is that it seems to be a permissions issue, when I try to access /Volumes/Data I get "Permission Denied".

     

    Surprised this hasn't been fixed, seems to me to be a very basic OS level problem with AFP accessing and/or mounting an external disk.

  • Thomas Schaller Level 1 Level 1 (105 points)

    I am experiencing the same problem with mounting issues when Time Machine tries to access my Time Capsule. Have tried all suggestions to no avail.

    Might be interesting for you guys to know that I'm still on Snow Leopard with this problem (10.6.8).

     

    Disconnecting users and starting a Backup does not work for me etiher.

     

    When I select Enter Time Machine it takes quite a while for the system to mount and then all of a sudden it says: Do you still want to start Time Machine? Backup volume is now available.

    During all of this the Finder is somewhat unresponsive - you cannot select anything else in a Finder window, but you can switch to open Applications.

    It takes several more tries and then Time Machine kicks in and takes me to the Stars screen with the backups.

     

    The log only shows the problems and then just stops:

     

    Network destination already mounted at: /Volumes/Toms Time Capsule

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    Mount failed... waiting 60 seconds and trying again.

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

    Network destination already mounted at: /Volumes/Toms Time Capsule

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    Mount failed... waiting 60 seconds and trying again.

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

    Network destination already mounted at: /Volumes/Toms Time Capsule

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    Giving up after 3 retries.

    Network destination already mounted at: /Volumes/Toms Time Capsule

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    Mount failed... waiting 60 seconds and trying again.

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

    Network destination already mounted at: /Volumes/Toms Time Capsule

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    Mount failed... waiting 60 seconds and trying again.

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

    Network destination already mounted at: /Volumes/Toms Time Capsule

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    Giving up after 3 retries.

    Network destination already mounted at: /Volumes/Toms Time Capsule

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    Mount failed... waiting 60 seconds and trying again.

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

    Network destination already mounted at: /Volumes/Toms Time Capsule

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    Mount failed... waiting 60 seconds and trying again.

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

    Network destination already mounted at: /Volumes/Toms Time Capsule

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    Giving up after 3 retries.

    Network destination already mounted at: /Volumes/Toms Time Capsule

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    Mount failed... waiting 60 seconds and tr

  • rodrigomd Calculating status...

    Hello everyone,

     

    I have a similar problem. I recently bought a TC 2TB, I have a MBP mid 2011 with Lion 10.7.2. My MBP can't perform any backup in the TC. When I click on select unit, although I can see the HD it can't be selected.

    When I try to access the TC from the Finder, it says that there is a connection error.

     

    Hope there is a solution.

  • rodrigomd Level 1 Level 1 (0 points)

    I found my solution. I downgrade to Lion 10.7, and it works perfect. Shame on Apple for selling hardware that doesn't work with their own products.

  • DaManni Calculating status...

    Do you have a Western Digital external drive and the software installed on your Mac?

     

    A user in an other post to this topic finally got a solution to this problem and it seems the Western Digital Software is causing it.

     

    Uninstall it and everything should work fine. I am feeling a bit embarassed myself for having blamed Apple and Lion for this error all the time since the update to Lion and all it seems to turn out now is a Western Digital software that does itself work on Lion but accidently disrupts the usage of Time Machine with the Time Capsule.

  • mauriziofromparis Calculating status...

    I actually do (on the MacBook Pro that cannot Time Machine to the server, and not on MacBook Air  that ca).

    I do not event know why i  actually installed the software, pretty useless :->.

    I'll try and i'll report  the results.

     

     

     

    Maurizio

Actions

More Like This

  • Retrieving data ...

Bookmarked By (11)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.