I updated my drobo5n to firmware 3.3.0. now it’s stuck on initializing. I see my shares without any problem, but none of the app is working and dash board reporting drobo is in the final stage of starting up for the last 3 days. I can’t manually update the firmware. or modify share settings, or even shut down or restart drobo. I need your help.
I really don’t want to erase data on the drobo. Should I try reset to factory setting? would that erase everything? Can I reset the firmware somehow?
hi, i would NOT do any resets etc as that can wipe data.
it may just be the case where the new firmware is reoptimising the existing data, (and if that was to take time, i think allowing about 1 day per 1tb of data that you have would be good to do)
i think the new version changed the way some apps work (framework etc) and that might have something to do with the apps not working (but it might still be optimising files from the firmware)
am not sure how much data you have? but if you can currently access your data, and have spare drives / space available, i would start making a backup before trying resets.
you are right, it would not be good to have to wait 9 days.
how is it at the moment - can you see any activitiy lights or hear/feel any drives chattering and vibrating?
Having the same issue on my 5N. Installed apps, network access etc are all running fine, but the Dashboard never completes with the ‘final stage’ message. Been doing it for about two days now, 5x4TB drives with a mSATA in the Hot Cache.
ok thanks,
it may be that a reboot might get it to start, and possibly the msata had a problem, but i would honestly try to wait a bit more, and before rebooting anything, maybe a full exit of dashboard (including service) and relaunch of it might allow it to see the drobo? also if you have any firewalls or av, maybe you could temporarily disconnect from the internet and try disabling those just in case something is blocking dashboard’s interaction with drobo?
If the Dashboard kept display… please wait final stage of start-up etc…
Try to access any of the Shared Folder in the 5N manually either OSX Finder or Windows Explorer (UNC)
If you can login and access the Shared Folder(s) in the 5N and yet Dashboard for some reason kept displaying “Please wait… final stage…”… it seems like the “comms” link between Dashboard and firmware is “broken” and is not updating the correct info to the dashboard for display. Firmware is already total up and running since you are able to login and access the Shares… either AFP or SMB.
So either…
Totally Exit and QUIT the Dashboard.
Restart Drobo Dashboard Service (Windows)
or
Restart DDService64d (OSX)
Launch Dashboard again and test…
Last resort… if unable to login or access any Shares in 5N, and since we have waited for far too long for Drobo 5N to “start-up” … I think maybe a force power cycle (reboot) of 5N is needed.
tried restart the computer where dash board is installed. didn’t work.
tried forced power cycle. didn’t work.
not impressed by reliability of drobo
[quote=“don, post:7, topic:141650”]
Just this:
If the Dashboard kept display… please wait final stage of start-up etc…
Try to access any of the Shared Folder in the 5N manually either OSX Finder or Windows Explorer (UNC)
If you can login and access the Shared Folder(s) in the 5N and yet Dashboard for some reason kept displaying “Please wait… final stage…”… it seems like the “comms” link between Dashboard and firmware is “broken” and is not updating the correct info to the dashboard for display. Firmware is already total up and running since you are able to login and access the Shares… either AFP or SMB.
So either…
Totally Exit and QUIT the Dashboard.
Restart Drobo Dashboard Service (Windows)
or
Restart DDService64d (OSX)
Launch Dashboard again and test…
Last resort… if unable to login or access any Shares in 5N, and since we have waited for far too long for Drobo 5N to “start-up” … I think maybe a force power cycle (reboot) of 5N is needed.
[/quote][hr]
Thank you so much Paul for following up.
There isn’t any warning or abnormal vibration from the drives.
things have been the same. The only good thing is that I can access the data. I have a lot of music and movie there i don’t want to re-rip. i’d want to wait a bit more. whatever i’m going to do, it’s going to take a lot of time.
hi, just out of curiosity,
if you are on windows, you could maybe try using a tool in admin mode, such as Process Explorer, (only from an info point of view) to see if anything might be accessing (or locking) files that are on the drobo, which might be causing the issue.
for example if your drobo is letter e in windows, then you could try a ‘handle or dll search’ for “e:” or sometimes “e:” without quotes, and you might see some movie player accessing a music folder there for example?
same situation here, on a 5N. Not be able to access some features of the dashboard for the mast 4 months, even with prior firmware than the latest one.
had some hdd issues, 2 drives broke, so after changing them, sitll waiting for the drobo to start up and enable for example Drobo Settings, showing up Capacity and able to access Drobo Apps.
I am able to access on MacOSX while mounting the share.
It’s drobo, not my computer. I have restart the computer with dash board installed multiple times. There is nothing that starts as soon as windows starts and access drobo right away. that’s the whole reason why i bought 5n in the first place.
As far as drobo concerned, all drives are reported healthy. It’s just stuck in “starting up” start after the firmware upgrade. It’s been about a week now. I found out I have about 7 terabytes of data. if it’s 1 terabyte a day to repair, it should be over soon.
Honestly, I’m fairly convinced something is going on with the new firmware. Have anyone tried update to an older version of the firmware?
I’ve opened a support case with Drobo, hoping they can offer some suggestions. If they’re able to help resolve the issue I’ll be sure to post the resolution in here.
I recall having some issues with a previous build of the Drobo Dashboard a few months ago, but it was determined to be a bug in that build, could be something similar.
so i finally got my dashboard working, out of nowhere. This is what i did :
1 . pressed the power button on the Drobo
2. Closed the Drobo Dashboard App on all computers that where accessing the Drobo
3. Killed the Process on all computers
4. Powered up the Drobo
5. Started the Drobo Dashboard on all computers
6. Had to login again on all computers
7. everything went fine
im able now to access everything on the Drobo Dashboard.
Tried this. didn’t work for me though. thanks for posting it here.
[quote=“creative-artworks, post:14, topic:141650”]
Hi there, hope u r doing well.
so i finally got my dashboard working, out of nowhere. This is what i did :
1 . pressed the power button on the Drobo
2. Closed the Drobo Dashboard App on all computers that where accessing the Drobo
3. Killed the Process on all computers
4. Powered up the Drobo
5. Started the Drobo Dashboard on all computers
6. Had to login again on all computers
7. everything went fine
im able now to access everything on the Drobo Dashboard.
hope this helps somebody
Jan
[/quote][hr]
it seems my ssh server isn’t up on drobo, getting connection refused. I really want to remove the app folder and restart the drobo. is there a way other than ssh?
How are you trying to log in to the Drobo? As root or as admin? From what I understand root access was removed as an option to make Drobos more secure in this latest firmware update, but if you can log in as admin (ssh admin@[drobo’s IP address]) you should be able to dig in. I had to do it from there as trying to manually delete from OS X’s Finder ran into permissions errors.
its not ideal waiting but just before you try to perhaps force any services up (which may be down for a particular reason) it may just need a bit more time for you and then work again?
Thanks Paul for following up. It’s been a week now. still initializing. no sshd, no apps. So there isn’t a way for me to fix it. I can access my data without any issue, so that’s a plus. Right now I don’t have any other option. I might wait for a new firmware to see if that fixes it. it’s a long shot.