On Mar 9, 2008, at 2:13 PM, Scott E Lasley wrote: > I've run into this sort of thing before when a backup script went > haywire. Back2 is a directory in the /Volumes directory, not an > actual volume that would show up in the Finder or disk utilities. > Notice the drwxr-xr-x permissions for Back2 vs the lrwxr-xr-x > permissions for iMac20. If you open the /Volumes directory, e.g. > using the Go->Go to Folder... menu item, you will see Back2 and can > delete it. Or you can delete it from Terminal using sudo rm -r / > Volumes/Back2. Deleting from the Finder is safer in case of a typo > in the sudo rm command. > > In my case, the simple script I used called rsync to back up to a > volume named Backup: rsync -av /Users /Volumes/Backup. When the > script ran once and the Backup volume was not mounted, rsync created > a /Volumes/Backup directory and backed up /Users to that directory. > > > hth, > Scott On Mar 9, 2008, at 2:17 PM, John Baltutis wrote: > On 03/09/08, Richard Hartman <seasoft at west.net> wrote: >> >> This is giving me fits. >> snip >> How do I delete this rogue volume and make it disappear from my >> Volumes listing? And, presumably, recover a bit of disk space in the >> process. > > A classic "false backup/clone" which occurs when using SuperDuper! > or Carbon > Copy Cloner and the app loses connection to the original target HD. > See > <http://forums.bombich.com/viewtopic.php?t=3852> for details. Just > run this in > the Terminal: > > sudo rm -R /Volumes/Back2 You guys are marvelous. I kind of thought something like this was going on, but was too intimidated to try the deletion. Problem Solved; thanks so very much. Richard