NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
glashoppah
Apr 10, 2012Aspirant
TimeMachine sparsebundle corruption fix
Dear Colleagues, Ever since upgrading my Mac to Lion I have had a curious problem which I've been working (for months) with Apple. Basically once every week or two, always on a Monday morning, the...
dmwarren
Jun 28, 2012Aspirant
Hello! (first post here after my first year with my immensely satisfying Ultra 6...)
I'm running Mountain Lion DP4 and ran into the same problem with Time Machine. :-( I absolutely refused to believe that netatalk was somehow incapable of talking to Mountain Lion, so I dug a little deeper.
Long story short, I think I can point to mDNS/Bonjour discovery as the problem. backupd seems to insist on using Bonjour to find, then mount the TM volume.
Once I mounted the Time Machine volume manually and specified the manually-mounted AFP share as a backup disk, voilà: Time Machine works again! I didn't even need to start a fresh backup; it just picked up as though nothing had ever happened. There's no need to keep the Time Machine share mounted—backupd will mount it just fine on its own now. Of course, Netgear's patches to netatalk prevent you from mounting /c/.timemachine directory, so you'll have to specify it yourself in your AppleVolumes.default file.
I'm not going to post a step-by-step tutorial on how to do this because ... if you don't already know how to administer netatalk, you should cut your teeth somewhere else and not void your warranty by editing random unfamiliar config files. ;)
I can't say it often enough: I love this unit because it's Just A Unix Box(tm) and I didn't have to build it. When I need to get under the hood, I can. Thanks, Netgear. :-)
(Edit: added my theory about what's failing)
I'm running Mountain Lion DP4 and ran into the same problem with Time Machine. :-( I absolutely refused to believe that netatalk was somehow incapable of talking to Mountain Lion, so I dug a little deeper.
Long story short, I think I can point to mDNS/Bonjour discovery as the problem. backupd seems to insist on using Bonjour to find, then mount the TM volume.
Once I mounted the Time Machine volume manually and specified the manually-mounted AFP share as a backup disk, voilà: Time Machine works again! I didn't even need to start a fresh backup; it just picked up as though nothing had ever happened. There's no need to keep the Time Machine share mounted—backupd will mount it just fine on its own now. Of course, Netgear's patches to netatalk prevent you from mounting /c/.timemachine directory, so you'll have to specify it yourself in your AppleVolumes.default file.
I'm not going to post a step-by-step tutorial on how to do this because ... if you don't already know how to administer netatalk, you should cut your teeth somewhere else and not void your warranty by editing random unfamiliar config files. ;)
I can't say it often enough: I love this unit because it's Just A Unix Box(tm) and I didn't have to build it. When I need to get under the hood, I can. Thanks, Netgear. :-)
(Edit: added my theory about what's failing)
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!