Backups / DroboCapsule failing after adding new drive.

[handyande]

Hi guys,
Thanks for the great software it has been very useful so far.
Unfortunately I have now it a glitch.
Today I upgraded my Drobo by adding a new 2TB drive to the 2*1TB
drives already installed.
The drobo and share (over smb) work fine and were smoothly updated but
I have issues with the bmfu stuff.

Backups either fail to find the disk, fail to mount it or fail after a
little (very very slow) data transfer.
Sometimes when the backups fail it takes down the drobocapsule other
times it takes down the droboshare.
When the DroboCapsule disappears I noticed that my smb "Drobo" share
becomes "Drobo1".
I have also seen the error dialog "The file server "DroboShare" has
closed down.".

I have tried restarting share and computer, removing bmfu and also
installing the latest version as well
as creating new backup volumes (transferring the sparseimage was as
flakey as the failing backups).

Any ideas or tips on finding the problem? currently all backups hang
whilst trying to make the backup disk available.
Thanks in advance,
Andrew

[xtremetoonz]

I had this same problem today! Hopefully your fix is as easy as mine
was. You will need Dropbear SSH on your DroboShare which I assume you
have if you're trying to install BMFU.

SSH to the DroboShare and type:
ls -la /mnt/DroboShares

I suspect you have something there for Drobo and Drobo1. In my case I
had previously created a symlink for Drobo to point to the actual
share name I had created. This made BMFU work at the time. When I
reset my drobo and droboshare the symlink wasn't deleted and the
reference for 'Drobo' was pointing to the wrong place. I don't want to
be held liable for suggesting you delete the 'Drobo' reference if it
exists, but if you feel the reference point is wrong, that is what
needs to happen. The DroboShare is coming online, trying to mount the
Drobo as 'Drobo' but has to change to 'Drobo1' because of the existing
entry.

Dylan