Time Capsule hangs at end of full backup, Disk Utility "not responding"

Question

I'm running a Mid 2011 iMac 27" with OSX 10.8.4 and using a WiFi connected 3TB Time Capsule (4th Gen).
I've noticed that the Time Capsule seems to get stuck at the end of a full back-up (let's say 260 GB of 260 GB) and won't end, even after hours of being left alone.
When I mount the Time Capsule Sparse Disk Image Bundle and then try to run Disk Utility, Disk Utility is shown as "Gathering Information," but the Finder and Activity Monitor list Disk Utility as "not responding."  (No disk information is shown in Disk Utility.) This happens both when I connect via WiFi to the Time Capsule and when I connect directly using an Ethernet cable.  If I don't mount the Sparse Disk Image Bundle, Disk Utility works fine, immediately showing my iMac's Hard Drive, so it only happens when the Time Capsule Sparse Disk Image Bundle is mounted.
1.  Is Disk Utility truly "not responding" or is it just taking forever to load because of the 3TB hard drive?
2.  If it truly isn't responding, what can I do to see if the TC needs to be "repaired"?
3.  What's going on with my TC that it hangs up at the end of a full backup?
Thanks.

Answer 1

thefliss wrote:
I see an occasional deep node traversal, but sounds like that can be normal.
Not normal, exactly, but TM's way of handling a problem.  See below.
Aug 17 21:35:50 Erics-iMac.local fseventsd[48]: event logs in /Volumes/Time Machine Backups 1/.fseventsd out of sync with volume.  destroying old logs. (86990 10 86991)
Aug 17 21:35:50 Erics-iMac.local fseventsd[48]: log dir: /Volumes/Time Machine Backups 1/.fseventsd getting new uuid:
Something went wrong with or on the TM drive (Time Capsule in your case), such as a power failure or abnormal disconnection, where OSX was unable to "close it out" properly, so is unsure if all the changes are in the File System Event Store.  If you're not familiar with the Event Store, see the blue box in How Time Machine works its Magic for details (it's talking about the one on your internal HD, but OSX keeps one on every drive/partition and disk image, including your TC backups.)
Aug 17 21:36:07 Erics-iMac.local com.apple.backupd[1728]: Event store UUIDs don't match for volume: Macintosh HD
That's one of the causes of a deep traversal.  The UUID (Universally Unique IDentifier, the long string of numbers and letters) for the Event Store on your internal HD doesn't match the one in TM's records from the previous backup, so it must do a deep traversal instead, comparing everything on your Mac to the latest (completed) backup.
Aug 17 21:42:09 Erics-iMac.local diskarbitrationd[22]: mds [39]:22019 not responding.
Aug 17 21:42:09 Erics-iMac.local diskarbitrationd[22]: fseventsd [48]:17923 not responding.
Aug 17 21:42:15 Erics-iMac.local fseventsd[48]: disk logger: failed to open output file /Volumes/Time Machine Backups 1/.fseventsd/0000000000362fde (No such file or directory). mount point /Volumes/Time Machine Backups 1/.fseventsd
Trouble talking to a disk.  The first two probably involve the TC, the third one definitely does -- it's trying to create the new Event Store.
Aug 17 21:44:03 Erics-iMac.local com.apple.imfoundation.IMRemoteURLConnectionAgent[1789]: [Warning] Denying xpc connection, task does not have entitlement: com.apple.private.imcore.imremoteurlconnection  (IMTransferAgent:1786)
Aug 17 21:44:03 --- last message repeated 1 time ---
Aug 17 21:44:03 Erics-iMac.local com.apple.imtransferservices.IMTransferAgent[1786]: [Warning] Remote loader crashed for request: <NSMutableURLRequest http://init-p01md.apple.com/bag>
Aug 17 21:44:03 Erics-iMac.local com.apple.imtransferservices.IMTransferAgent[1786]: [Warning] Bag loading failed! Error (__kIMRemoteURLConnectionErrorDomain:-1): The operation couldn’t be completed. (__kIMRemoteURLConnectionErrorDomain error -1.) (null)
Out of my comfort zone, but sure looks like some sort of connection problem . . . with something.
Aug 17 21:48:08 Erics-iMac.local com.apple.backupd[1728]: Deleted 3 backups containing 299.76 GB total; 300.65 GB now available, 209.78 GB required
TM did (finally) connect, figured out how much sp it needed, and started deleting old backups to make room.  Since it did, actual copying would have started just after that was sent.
Aug 17 22:07:03 Erics-iMac.local com.apple.SecurityServer[15]: Session 100018 created
Aug 17 22:07:06 Erics-iMac.local ScopedBookmarkAgent[1853]: CFURLCreateByResolvingBookmarkData failed with error [Error Domain=NSCocoaErrorDomain Code=4 "The file doesn’t exist."].
Aug 17 22:07:08 --- last message repeated 7 times ---
Aug 17 22:07:08 Erics-iMac.local QuickTime Player[1845]: It does not make sense to draw an image when [NSGraphicsContext currentContext] is nil.  This is a programming error. Break on void _NSWarnForDrawingImageWithNoCurrentContext() to debug.  This will be logged only once.  This may break in the future.
Aug 17 22:08:37 Erics-iMac.local WebProcess[1866]: objc[1866]: Object 0x7fec4841c8c0 of class NSUserDefaults autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
Aug 19 16:35:11 Erics-iMac.local mds[39]: (/)(Warning) IndexQuery in bool preIterate_FSI(SISearchCtx_FSI *):Throttling inefficient file system query
Most of that is also out of my area, but doesn't seem related to the TC or backups. 
Hard to tell so far, but it looks like problem is on your network, or power, or with the TC.  Trying backups to a directly-connected external HD would be a quick way to confirm that, and especially if these are your only backups, a wise thing to do anyhow. 
It's always prudent to keep "secondary" backups, more so if your main ones are on a network, and especially if there's the slightest doubt about them.  See Time Machine - Frequently Asked Question #27 for more info and some suggestions.
And/or, start through the list in the green box in #D2 of Time Machine - Troubleshooting.