My Drobo unit keeps getting renamed from Drobo, to Drobo1, to Drobo2, etc…
What is going on?
I am using the Drobo with Droboshare.
Sounds like windows.
Which firmware are you running?
Could it be actually disconnecting/connecting without you noticing?
Update the firmware.
No, not only windows-related.
During the firmware-update to 1.3.3 my Drobo changed the name to Drobo1 from Drobo from my DrobShare.
For the previous years it have allways only been named “Drobo” and when I updated to 1.3.4 it didn’t change but is still “Drobo1”
Since this changed the share-name to \DroboShare\Drobo1 it was a PITA.
I do not have Windows on my network. Just mac and Linux.
The drobo firmwre version is 1.3.0 and droboshare firmware is 1.1.2
The /Volumes directory on my Mac looks like this:
Drobo – owned by root
Drobo 1 – owned by root
Drobo 2 – owned by root
Drobo 3 – The current Drobo
This is causing file accesses to fail as /Volumes/Drobo/… is not the same as /Volumes/Drobo3/…
Why does the Mac create new volumes for the Drobo?
Answer:
OS X will rename the mounted volume in /Volumes to Drobo-X (where X is a sequential number) if at the point when an application calls the Volume, the volume is not mounted.
A program that wants to write to (or access) your Drobo volume has tried to do this while your Drobo was unmounted, ie the path /Volumes/Drobo/… did not exist at that time, so OS X created it for you.
Normally, /Volumes/Drobo is a mount point that exists only while the Drobo is mounted. The next time Drobo is mounted, the Mac sees the directory /Volumes/Drobo already exists, so it mounts the Drobo in a new location, in this case adding or incrementing a numeric suffix.
As a workaround, you can copy the contents of the /Volume/Drobo folder to a safe location and delete the folder. You will also have to delete the other folders: /Volume/Drobo1, /Volume/Drobo2, etc. Now when you mount your Drobo again, the Mac will create a /Volume/Drobo folder for you.
Can you explain why this could happen on a DroboShare?
Did this not answer the question?
OS X will rename the mounted volume in /Volumes to Drobo-X (where X is a sequential number) if at the point when an application calls the Volume, the volume is not mounted.
A program that wants to write to (or access) your Drobo volume has tried to do this while your Drobo was unmounted, ie the path /Volumes/Drobo/… did not exist at that time, so OS X created it for you.
Normally, /Volumes/Drobo is a mount point that exists only while the Drobo is mounted. The next time Drobo is mounted, the Mac sees the directory /Volumes/Drobo already exists, so it mounts the Drobo in a new location, in this case adding or incrementing a numeric suffix.
I’m not sure what exactly you are asking for Dowser.
Thanks! I will try this and see if it works.
I have Mac with Snow Leopard and my Drobo is attached through FireWire800 connection. Same thing happens on my computer that sometimes my Drobo when I wake up my computer is mounted to /Volumes/Drobo 1, 2 and whatever even though all my programs are to look for /Volumes/Drobo.
Is there a way to force my computer to mount Drobo only to /Volumes/Drobo? Maybe to reserve that mounting point for that purpose only?
Unfortunately I’m new to Mac as it is so I can’t even figure out how to delete /Volumes/Drobo 1 from my system
rm -rf – this command will solve your problem, or amplify it if used incorrectly. be careful.
checkout macosxhints.com, they have articles about ensuring a drive always mounts using the same volume name.
I am having a similar issue, except it’s on the DroboShare. When I ssh into my DroboShare, I see the following:
/mnt/DroboShares $ ls -l
drwxrwxrwx 16 root 0 4096 Dec 12 01:10 Drobo
drwxrwxrwx 16 root 0 4096 Dec 12 01:10 Drobo1
drwxrwxrwx 7 root 0 4096 Oct 1 04:02 Drobo2
drwxrwxrwx 16 root 0 4096 Dec 12 01:10 Drobo3
Drobo3 contains what is normally only under Drobo. The Drobo, Drobo1 and Drobo2 directories are empty. I tried the following
/mnt/DroboShares $ rm -rf Drobo
rm: unable to remove `Drobo’: Device or resource busy
But apparently something is holding a file handle or something else open on one of these. I don’t know what. Can you suggest a troubleshooting tool so I can figure out what is blocking DroboShare from mounting the Drobo volume where it belongs?
A reboot of the DroboShare solves the problem, but I’d like to fix it more permanently.
This is one of the main reasons why I sent my DroboShare back. If you can’t rely on the name then it’s hard to write scripts and difficult to use it with things like iTunes.