2 Replies Latest reply: Sep 23, 2013 8:47 PM by dsuchter
dsuchter Level 1 Level 1 (0 points)

The title is pretty descriptive. The "crash" is that I get the spinning beach ball of death and over the course of a few seconds my machine becomes completely non-responsive to input (keystokes stop working, then the wiggling the mouse stops working). I have do hold down the power button to reset the machine after that. Although I'm quite familiar with http://pondini.org/OSX/Home.html I don't see that anything readily addresses "Time Machine crashes my whole OS". Any ideas? Thanks!


MacBook Pro, Mac OS X (10.7.2), MacBookPro8,2
  • 1. Re: Why does "enter time machine" crash my computer?
    dsuchter Level 1 Level 1 (0 points)

    Here a log of what happens. I got this same effective log in two different situations: first when I ran an attempted backup, then again basically the same when I changed the computer name and tried again. That second attempt is probably pretty telling since there is no sparsebundle with the new computer name, meaning the error of "diskimagealreadyattached" cannot be true.

     

    Starting standard backup

    Attempting to mount network destination URL: afp://dsuchter@DiskStation.local/timecapsule

    Mounted network destination at mountpoint: /Volumes/timecapsule using URL: afp://dsuchter@DiskStation.local/timecapsule

    Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35

    Running backup verification

    Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35

    Backup verification incomplete!

    Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35

    Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7faf9305d400 {MessageParameters=(

    Ejected Time Machine network volume.

    Waiting 60 seconds and trying again.

    Attempting to mount network destination URL: afp://dsuchter@DiskStation.local/timecapsule

    Mounted network destination at mountpoint: /Volumes/timecapsule using URL: afp://dsuchter@DiskStation.local/timecapsule

    Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35

    Running backup verification

    Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35

    Backup verification incomplete!

    Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35

    Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7faf93507310 {MessageParameters=(

    Ejected Time Machine network volume.

    Waiting 60 seconds and trying again.

    Attempting to mount network destination URL: afp://dsuchter@DiskStation.local/timecapsule

    Mounted network destination at mountpoint: /Volumes/timecapsule using URL: afp://dsuchter@DiskStation.local/timecapsule

    Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35

    Running backup verification

    Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35

    Backup verification incomplete!

    Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35

    Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7faf93060170 {MessageParameters=(

  • 2. Re: Why does "enter time machine" crash my computer?
    dsuchter Level 1 Level 1 (0 points)

    For posterity:

     

    Hrm... I found this post a minute ago that indicates my symptoms may be due to a change in the AFP protocol and the underlying Netatalk libraries that might be causing my problem. To summarize, some updates in my Mac caused a situation where it thought the Synology timemachine share was read-only, which could cause the error message I see. My Synology was running DSM 4.2-3211 and there's a newer version (DSM 4.3-3776) so I decided to upgrade. My Mac is now happily "verifying backup..." from the last time Timemachine rans, so I believe the problem is fixed.

     

    Note: the post I linked referenced the error was corrected in a DSM 4.1.x release candidate, but my DSM was already newer than that. For anyone who's questioning version numbers I'd suggest they read into the changelots for netatalk and DSM, which I'm not going to do right now since I believe my problem is solved.