sparseimage can no longer be mounted by SD

[rschletty]

Originally Posted by dnanian

Looks like you need to eject the image, open the /Volumes folder (with Finder's "Go to Folder" command) and remove the "SG Mac OS X" folder you'll find there (not a link/alias, but a folder).

Then, restart your Mac and try again.

OK, after re-selecting a grayed out sparseimage in the destination panel, I was able to re-create the backup script. SD mounted the problem sparseimage. Here's the weird thing: The destination sparse image no longer has a matching name. The number 1 is appended to the volume name. It seems that SD is still keeping track of the original sparseimage somehow.

I'll do as you suggested.

I just tried stopping the backup script while in its "preparing the target volume" stage. It gave me the warning "Stopping now will leave [Volume Name] in and unknown state." I am guessing my force-quitting of SuperDuper a couple days ago was the reason that the sparseimage could no longer be mounted by SD. Retrospect does allow one to both pause and quit a back-up session gracefully.