Error message when accessing DroboCapsule

3 views
Skip to first unread message

cabegoose

unread,
Aug 17, 2010, 10:13:46 PM8/17/10
to backmyfruitup
I've been using BMFU for some time now without a glitch, but recently
I got this error message,
"Something wrong with the volume's CND DB, using temporary CND DB
instead. Check server messages for details. Switching to read-only
mode."
I use BMFU to do TM backups from two Macbooks to the drobo. The first
time I got the error I formatted the drobo and reinstalled BMFU. This
worked, I was able to do a complete backup of my wife's macbook, but
when I went to do my macbook pro it backed up about 6 GB of 150 and
stopped. When I tried to access the DroboCapsule it again flashed the
error message. It is only when I try to mount the DroboCapsule that
the error occurs. I can access the DroboShare no problem.

If anybody could help me I would greatly appreciate it.

Thanks

Alex

unread,
Aug 25, 2010, 2:57:28 PM8/25/10
to backmyfruitup
We have exactly the same problem.

I've just set up a Drobo with latest firmware, I used BMFU 3.0,
everything looked fine, I started a backup of two macs (both of them
running 10.6.4). One client's backup size was 180 GB, the other one's
was about 100 GB. The backup started in the evening, and when I came
in the office in the morning, both of them were still running the
backup process, but without any progress. They had backed up about 50%
of their data, but nothing happened any more.

After I cancelled the backup in order to start it again, the same
error as reported by cabegoose appeared. After starting the time
machine backup via the menu bar, you see the "BMFU donate message",
and after that, the next message shows the error "Something wrong with
the volume's CND DB, using temporary CND DB instead. Check server
messages for details. Switching to read-only mode".

Does anyone know what's the reason for that?

Thanks in advance,
Alex

Jon Stevens

unread,
Aug 26, 2010, 1:53:38 AM8/26/10
to backmy...@googlegroups.com
There is a known bug in the version of netatalk that is with BMFU 3.0 that _could_ be causing this issue, but I'm not sure. I've been planning on doing another release of BMFU with the latest version of netatalk, but I was gone for 3 weeks on my honeymoon and since I've been back, the day job has been beyond insane. Hopefully I'll get to it soon as my backups are not working right now either. Sucky (and scary).

jon

--
You received this message because you are subscribed to the Google Groups "backmyfruitup" group.
To post to this group, send email to backmy...@googlegroups.com.
To unsubscribe from this group, send email to backmyfruitu...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/backmyfruitup?hl=en.


Message has been deleted

William

unread,
Aug 26, 2010, 4:04:29 PM8/26/10
to backmyfruitup
Same problem here...

Also when I tried to delete the old nettalk dir (that I renamed),
some of the files (in the man dir) are reported as still in use and
would lock up Finder
during delete.
I had to SSH in to delete them, must be a permissions thing.

Going back to ver 2 tonight, I hope going back is the same
procedure as updating.
Reply all
Reply to author
Forward
0 new messages