Time Machine backup to my Time Capsule worked great until I installed 10.5.8. My TC is connected to Mac via ethernet cable, and I use tc as my router as well. Now I would consistently get the error message: the volume cannot be mounted. Here's what I've tried so far:
- reboot the system and the time capsule
- repair the sparsebundle via disk utility- it was unrepairable
- repaired permissions
- used airport utility to erase the time capsule
- turned off time machine and reselected the time capsule as the backup volume
- trashed the timemachine .plist and rebooted again
Now when I start time machine a backup volume mounts but is stuck in "preparing mode." When time machine is active, my computer goes haywire- multiple processes and applications begin "not responding" and won't force quit, and I end up having to do a hard restart. I have been browsing threads regarding this issue and can't find any more suggestions other than what I've already tried. any ideas?
EDIT: somehow I missed the whole interaction with Mozy. As per threads in the apple forums, uninstall mozy, deleted the corrupted sparse bundle and restart time machine-- now it works. Hopefully mozy figures out a solution!
- reboot the system and the time capsule
- repair the sparsebundle via disk utility- it was unrepairable
- repaired permissions
- used airport utility to erase the time capsule
- turned off time machine and reselected the time capsule as the backup volume
- trashed the timemachine .plist and rebooted again
Now when I start time machine a backup volume mounts but is stuck in "preparing mode." When time machine is active, my computer goes haywire- multiple processes and applications begin "not responding" and won't force quit, and I end up having to do a hard restart. I have been browsing threads regarding this issue and can't find any more suggestions other than what I've already tried. any ideas?
EDIT: somehow I missed the whole interaction with Mozy. As per threads in the apple forums, uninstall mozy, deleted the corrupted sparse bundle and restart time machine-- now it works. Hopefully mozy figures out a solution!