This isn’t a new problem. This has been a firmware bug since at least the beginning of this year. I’m theorizing that something in the update is precipitating it to happen more frequently on upgrade. Drobo have known about this for a while, and the workaround and fix (I know because I’ve told them), but have yet to fix it or post anything about the workaround.
Here’s how you get your data back and the ability to connect to the share:
- Enable SSH access, to do this:
a) Enable Drobo Apps in the Dashboard (checkbox under Settings / Admin)
b) Restart Drobo
c) From here: http://www.drobo.com/droboapps/ download DropBear ssh
d) Under your shares, you’ll have a new folder called “DroboApps”, drag
the .tgz from c) into this share
e) Reboot drobo and wait a while for everything (including ssh) to start up
f) ssh to your drobo with: ssh root@IP_ADDRESS (where IP_ADDRESS is the ip address of your drobo)
- Zapping the corrupt database. First make sure no machines are using your drobo.
a) cd Shares
b) ls (look for your TimeMachine partition, lets call this “MyTimeMachine”
c) cd MyTimeMachine (note if you want to be reassured your files are still there, type ls. If you don’t see them, then a corrupt database isn’t your issue.)
d) mv .AppleDB .AppleDB2
mv .AppleDesktop .AppleDesktop2
mv .AppleDouble .AppleDouble2
(you can delete them if you prefer)
e) /sbin/reboot (restarts your drobo)
f) ssh into your drobo again
g) Use “ps” to see if a process is running (/sbin/cnid_dbd), this process indexes your drive. It should NOT be running at this stage.
h) Login to your share in the Finder. You will still see no files, and you may get the pizza wheel after a while, don’t to anything. Eventually this connection will prompt the drobo to reindex.
i) Be real patient and wait. At some point, ps will show cnid_dbd running, and you’ll see that the Share/MyTimeMachine will now populate .AppleDB. After potentially a long time (on mine it took 20mins for 1.46TB Time Machine), you’ll see the finder get populated with your Time Machine files.
At this point, you should now be able to use Time machine again.
- Finally, switch of “DroboApps”, unless you don’t care about the security risk.
I’ve only seen this happen on TimeMachine volumes, but if you’re having the same issue of other shares the same procedure should work on those too.
Note you have to login to the share and have it displayed for the .AppleDB to be recreated and the list of file to be displayed.
Above fixed the login immediately logout problem on the drobo dashboard and my Time Machine Backup missing.
However the extremely long wait time for the share to mount still occurs and looks like a problem with the latest netatalk.