Take the 2-minute tour ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

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?

share|improve this question
add comment

2 Answers

up vote 2 down vote accepted

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.

share|improve this answer
    
Thanks for the tips. Here are some more data points... (1) I stopped backups and removed the indication in TM that it should use the TC's external disk as a target. I also then disconnected the network (wifi is the only path I have to the TC) –  pitosalas Oct 12 '11 at 2:52
    
Awesome - at this point, can you mount / repair that volume through the network. A direct ethernet connection might be substantially faster. A verify is better if you are not sure it can be completed overnight. (if you have say 500GB of data in the disk image) –  bmike Oct 12 '11 at 3:01
    
sorry, I was typing a full response as a response but could not get it to work because of the text editor here so I posted it as an answer to my own question, but, it's more data to help us solve the problem..... –  pitosalas Oct 12 '11 at 3:08
add comment

Thanks for the tips. Here are some more data points...

  • I stopped backups and removed the indication in TM that it should use the TC's external disk as a target. I also then disconnected the network (wifi is the only path I have to the TC)
  • I rebooted my mac.

Here's terminal output:

monster:~ pitosalas$ ls /Volumes/
BootHD      MonsterHD
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)
monster:~ pitosalas$ diskutil list
/dev/disk0
#:                       TYPE NAME                    SIZE       IDENTIFIER
0:      GUID_partition_scheme                        *115.0 GB   disk0
1:                        EFI                         209.7 MB   disk0s1
2:                  Apple_HFS BootHD                  114.2 GB   disk0s2
3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
#:                       TYPE NAME                    SIZE       IDENTIFIER
0:      GUID_partition_scheme                        *640.1 GB   disk1
1:                        EFI                         209.7 MB   disk1s1
2:                  Apple_HFS MonsterHD               639.3 GB   disk1s2
3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3

So you can see, no sign of WD1 or WD1-1 (the name of the external disk attached to the TC is WD1 and its shadow is WD1-1.

Now I assign WD1 to be the backup disk for TC and try to run a backup.

It says that it cannot find the external disk. So I go to finder, open the Share for TimeCapsule which shows two disks, it's own (TimeCap) and the external disk.

When I try use Finder to see the contents of the external disk, it hangs and eventually says "the operation cannot be completed because the original item for "WD1" cannot be found. Wha???

At this point, TM is not yet working. It gives the same error: "The backup disk image “/Volumes/WD1-1/monster.sparsebundle” could not be created (error 22)."

And back on Terminal I see this:

monster:~ pitosalas$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *115.0 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS BootHD                  114.2 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *640.1 GB   disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:                  Apple_HFS MonsterHD               639.3 GB   disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
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.2d000004 on /Volumes/TimeCap (afpfs, nodev, nosuid, mounted by pitosalas)
afp_0TSQUm1ubQ4400mmYF0Pyetl-2.2d000005 on /Volumes/WD1 (afpfs, nodev, nosuid, mounted by pitosalas)
afp_0TSQUm1ubQ4400mmYF0Pyetl-1.2d000006 on /Volumes/WD1-1 (afpfs, nobrowse)
monster:~ pitosalas$ ls /Volumes/
BootHD      MonsterHD   TimeCap     WD1     WD1-1
monster:~ pitosalas$ 

If you can be of any assistance in solving this riddle I would be super grateful!

Pito

share|improve this answer
1  
Excellent! This really helps, but you're not out of the woods. Can disk utility see or verify the WD drive? –  bmike Oct 12 '11 at 3:13
    
DU doesn't see the WD drive because it is connected as follows: Mac Pro "Monster" -> wifi -> TCapsule -> WD and I think that DU doesn't see drives not directly connected to the Mac Pro. Thanks for your continue help, I am feeling lost, but guardedly optimistic due to your help! –  pitosalas Oct 12 '11 at 13:02
    
It might be simpler to temporarily connect the WD drive to the mac with USB to do the checking of the volume and then again the sparse disk image. Do use AirPort Utility to shut down connections to the shared drives before disconnecting. –  bmike Oct 12 '11 at 14:22
    
I connected directly, and did the DU - check volume and check disk image. Neither generated errors but in any event I am now doing a backup successfully to the drive, connected directly. So the conclusion might be that there was an error on the disk or that doing Time Machine backups to a hard disk connected to a Time Capsule via Wifi is not reliable... Not sure which is the case but for now I will leave it connected directly. Thanks much for your help. –  pitosalas Oct 12 '11 at 21:09
    
This is exactly why (i would guess) Apple doesn't support this - TimeCapsule and AirPort can't Disk Utility check an external drive when it fails to get things back verified. I'm happy this all helped! Someone will surely come around again to learn what to do. Why don't you edit my answer above to read just what you ended up so people can get the complete answer in one place rather than reading down to these comments? –  bmike Oct 12 '11 at 21:38
show 1 more comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.