MacOS – Time Machine fails backup to a time capsule’s attached hard disk

macostime-capsuletime-machine

I've been backing up my Lion OSX system using Time Machine to an second, external drive connected to a time capsule. It has worked but stopped working.

The menu says "Faied" and the time machine prefs says:

"The backup disk image “/Volumes/WD1-1/monster.sparsebundle” could not be created (error 22)"

As far as I can tell the external hard disk is just fine. One really weird thing is that the external drive is called "WD1". However the Volume in the error message is specified as /Volumes/WD1-1. In fact in shall I see this:

monster:~ pitosalas$ mount
/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk1s2 on /Volumes/MonsterHD (hfs, local, journaled)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
afp_0TSQUm1ubQ4400mmYF0Pyetl-1.2d000003 on /Volumes/WD1 (afpfs, nodev, nosuid, mounted by pitosalas)
afp_0TSQUm1ubQ4400mmYF0Pyetl-1.2d00005c on /Volumes/WD1-1 (afpfs, nobrowse)

and

monster:~ pitosalas$ ls /Volumes/
BootHD      MonsterHD   WD1     WD1-1

(notice that MonsterHD and BootHD are both internal drives of the OSX box called monster)

What is that second Volume WD1-1? It has different characteristics in $ mount listing none of which are meaningful to me. Could that be related to the problem?

Best Answer

Time Machine tries to track a UID for the volume and not a name, but it could be confused.

Have you tried setting the backup destination to none and rebooting with no drives connected and no network connection.

At that point /Volumes should be clean and you would be safe to delete any non-local drives at that point. My guess is it's perhaps a second route to the network - do you have a wired connection and WiFi to the AirPort/Time Capsule?

diskutil list will also get you more information about drives than mount in case you want to post more details and can't get Time Machine happy with these steps.