2 Replies Latest reply: May 13, 2012 1:22 PM by Alex Johnson2
Alex Johnson2 Level 1 Level 1 (115 points)

Two days ago my Time Capsule stopped backing up, and stopped allowing me to use the Time Machine interface. It reports no errors tying to back up, but self-cancels as soon as it starts. I left it on all day; every hour it does the same. I have restarted the Mac, restarted the Time Capsule, and deleted the prefs file in /Library. I've pointed to the disk several times. In Time Machine, I see the interface, but it doesn't load the disk, so all I see is the data for right now, but the starry background.

 

What does work is manually mounting the disk, and navgating to the sparesfile, and opening it to get files. It seems to be fine and I've restored from it; I just can't do it within the Time Machine UI.

 

I don't recall a particular incident. but I've been running the ML DP so I have retsarts more often than I might otherwise. I've been using it for a couple off months, and the backup for a year. ML itself isn't the cause, but crashes and restarts might be.

 

I've run Disk Utility on the TIme Capsule. It had some minor errors, and fixed those. I did the same on my MacBook Air. Again, minor problems, fixed.

 

I folowed Pondini's excellent FAQ, but there's nothing quite right. I'm using his Dashboard widget.

 

I think what is happening is that Time Machine is not deleting old backups as it wasnts to do one for 6GB and there's about 120MB free. But, it;s not reporting any disk full-type errors - it's just quietly self-cancelling.

 

In Console, this is an illustrative sample. Any thoughts? Of course, I can delete and restart but that's not really the point!

 

08/05/2012 22:26:09.100 SystemUIServer[160]: Error getting disk for path /Volumes/Time Capsule: No underlying device was found (for example, AFP network volumes are not supported)

08/05/2012 22:31:01.000 kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Time Capsule-1 prevTrigger 3 currTrigger 4

08/05/2012 22:31:01.000 kernel[0]: AFP_VFS afpfs_DoReconnect:  doing reconnect on /Volumes/Time Capsule-1

08/05/2012 22:31:01.000 kernel[0]: AFP_VFS afpfs_DoReconnect:  posting to KEA EINPROGRESS for /Volumes/Time Capsule-1

08/05/2012 22:31:01.000 kernel[0]: AFP_VFS afpfs_DoReconnect:  Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Time Capsule-1

08/05/2012 22:31:01.000 kernel[0]: AFP_VFS afpfs_DoReconnect:  connect to the server /Volumes/Time Capsule-1

08/05/2012 22:31:01.081 KernelEventAgent[75]: tid 00000000 type 'afpfs', mounted on '/Volumes/Time Capsule-1', from '//Alex%20Johnson@Time%20Capsule._afpovertcp._tcp.local/Time%20Capsule', not responding

08/05/2012 22:31:01.000 kernel[0]: AFP_VFS afpfs_DoReconnect:  Logging in with uam 13 /Volumes/Time Capsule-1

08/05/2012 22:31:01.000 kernel[0]: AFP_VFS afpfs_DoReconnect:  Restoring session /Volumes/Time Capsule-1

08/05/2012 22:34:38.977 DashboardClient[927]: com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: May  8 22:11:17 (null) DashboardClient[927]: com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: May  8 22:03:13 (null) com.apple.backupd[663]: Mounted network destination at mount point: /Volumes/Time Capsule using URL: afp://Alex%20Johnson@Time-Capsule.local/Time%20Capsule

 


MacBook Air, Mac OS X (10.7.2)
  • 1. Re: No Time Capsule Back-Ups, No Reason…?
    RRFS Level 5 Level 5 (4,430 points)

    I know this will sound brutal, are you able to back up your stuff to another drive and then do an erase/format of your Time Capsule disk? Remount the disk and let Time Machine reestablish itself. You would then know if the backup itself was corrupted in some way.

  • 2. Re: No Time Capsule Back-Ups, No Reason…?
    Alex Johnson2 Level 1 Level 1 (115 points)

    I was about to try this, but the problem was solved - by updating to ML DP3. Time Machine was able to report more specifically a UUID mismatch - which was strange as there had been no hardware changes:

     

    Event store UUIDs don't match for volume: MacBook Air

    Deep event scan at path:/ reason:must scan subdirs|new event db|

    Finished scan

    Found 360330 files (16.14 GB) needing backup

    21.25 GB required (including padding), 17.99 GB available

    Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/MacBook Air/2012-05-06-132701.inProgress/36723EA8-68F9-4519-A71B-426EEEE06222 containing 896.2 MB; 18.88 GB now available, 21.25 GB required

    Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/MacBook Air/2012-05-06-132701.inProgress/73A7127D-0521-46C0-AD8F-F7C6B6621F86 containing 4 KB; 18.88 GB now available, 21.25 GB required

    Removed 2 expired backups so far, more space is needed - deleting oldest backups to make room

    Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/MacBook Air/2011-10-08-102105 containing 10.75 GB; 29.63 GB now available, 21.25 GB required

    Deleted 3 backups containing 11.64 GB total; 29.63 GB now available, 21.25 GB required

    Backup date range was shortened: oldest backup is now 15 Oct 2011

    Copied 2.7 MB of 16.14 GB, 106708 of 360330 items

    Copied 5.6 GB of 16.14 GB, 360849 of 360849 items

    Bulk setting Spotlight attributes failed.

    Copied 394370 files (8.46 GB) from volume

     

    Upshot is that after many hours it's back, and the sparseimage has been verified.

     

    If it's of any use to anyone finding this, I would say that the solution seems to have been a Mac OS reinstall - which is counter-intuitive, but if all else fails, give it a go!