Odd Volumes Issue

[securityminded]

I am using super duper on a single mac book pro with one external hard drive (which has three partitions on it)

The cloning seems to work fine as the clone is bootable. But I noticed an issue with /volumes. One of the partitions on the external drive is called "Storage". I don't clone to it, only use for it storage. I have done multiple restores and clones using this set up, and just noticed that on my desktop the volume is mounted as "Storage" which is correct. But, when I go to terminal there is a Storage and Storage 1. When I ls Storage the files aren't there. When I ls Storage 1 the files are there.

On my desktop, there is no volume named Storage 1, just Storage. And the Storage on my desktop has the files.

Any ideas?

[dnanian]

You have a mount point (or folder) in /Volumes named "Storage". This forces "Storage" to mount as "Storage 1". We show that in SD! so you can differentiate between two drives with the same name.

[securityminded]

Is there a way to clear this out? I never actually created a Storage and then Storage 1. I am not sure why when the computer reboots it would keep a Storage and then have to load Storage 1

[dnanian]

Use Finder's "Go To Folder" command to open /Volumes. Once there, you should see the folder -- you can then delete it.

[securityminded]

This didn;'t happen until cloning and booting from clone and restoring. Any ideas on how to keep it from happening? Isn't volumes supposed to be cleared when restarted?

[dnanian]

Since I don't know how it happened in this particular case, I can't tell you how to keep it from happening.

Basically, you can end up with this kind of problem when a mount point converts to a folder during a file copy. This can happen if the destination volume fails and a retry recreates the path due to the nature of the API calls used.

Alternatively, it's possible that if you mounted this "Storage" volume while SD! was actually in the process of copying the Volumes folder, our evaluated list of files in that folder might be inaccurate, so the mount point would be copied. But you don't seem like the kind of person who would mount and unmount volumes -- or run other applications unnecessarily -- while you're copying.