A requested portion of Drobo Dashboard is no longer running

Hi, My Drobo Dashboard 2.6.9 on my MacMini running Mac OS 10.7.5 has an error message saying “A requested portion of Drobo Dashboard is no longer running”. It says to relaunch Dashboard and reinstall it to correct the problem, but after doing both, the error message still appears. Finder on my MacMini can still access all files.

hi, this could be a mac firewall / security permissions issue.
there were some other users recently having a similar problem when mac updates were essentially removing the permission for dashboard services, and then when the permissions were granted again, things were ok.

drobo data can still usually be accessed with or without the dashboard, but there are other features that only exist in dashboard.[hr]
here is a link which may help too:
https://myproducts.drobo.com/article/AA-01503

If your computer is 32 bit as opposed to 64 bit this could be the reason.

DroboMod

Hi Paul,
My firewall settings are correct. I haven’t updated my OS either.

[quote=“Paul, post:2, topic:141571”]
hi, this could be a mac firewall / security permissions issue.
there were some other users recently having a similar problem when mac updates were essentially removing the permission for dashboard services, and then when the permissions were granted again, things were ok.

drobo data can still usually be accessed with or without the dashboard, but there are other features that only exist in dashboard.[hr]
here is a link which may help too:
https://myproducts.drobo.com/article/AA-01503
[/quote][hr]
Hi DroboMod,
I’m running a 64bit MacMini. Just to confirm though, my MacMini’s info states: Processor: 2 GHz Intel Core 2 Duo. What options do I have?

Hi redimech,

Try one of these steps and see if it resolves the issue.

Background:

  • The warning message you saw on the Dashboard is related to the “DDService64d” daemon process that is running in the background of OSX.

  • When Dashboard launches, it first look for this DDService64d process and tries to comms it. Without DDService64d, Dashboard will not be able to function or discover any Drobo within the Dashboard.

  • Of cos’ without Dashboard or DDService64d process… OSX will still be able to mount and access the Drobo Volumes or Shares (5N model).

Few reason to why this happen:

  • When Dashboard opens, DDService64d is NOT running or is still in the process of start-up.
  • OSX Firewall blocking DDService64d

Steps:

  1. Make sure OSX Firewall is not blocking DDService64d.
  • Open System Preference > Security > Firewall > Advance and check DDService64d is allowed “Allowed in-coming connection”
  1. Close and Quit Drobo Dashboard. Now open OSX Activity Monitor, make sure to “Show ALL Process”.
  • Look for DDService64d

*If DDService64d did not show up in Activity Monitor, that means it is NOT running at all.

  • If DDService64d is NOT running, Open OSX Terminal app and enter the following command to manually run it and also set it to run on every OSX start-up.

  • In the Terminal app, enter:

sudo launchctl load -w /Library/LaunchDaemons/com.datarobotics.ddservice64d.plist

You will be asked for your OSX password.

Now in Activity Monitor, search for DDService64d again. It should be there, and with a PID number (Process ID).

  • Launch Drobo Dashboard, check if error message still pop out. If NOT, then can the Dashboard discover your Drobo?

If the above works… do a restart of the OSX. After OSX restarts, open Dashboard… everything ok?

**If the initial search on Activity Monitor does show DDService64d running and with a PID. But somehow Dashboard still showing the error message upon launch. This could be that DDService64d process is “dead”.

If this is the case… >

  • CLose Quit Dashboard. In Activity Monitor… Select the DDService64d entry and take note of the PID number. Once selected in Activity Monitor, click the “Force Quit Process” button. This will quit the DDService64d process and it will auto relaunch with a new PID number. So if after quitting, you see a new PID number on the DDService64d in Activity Monitor… that means DDService64d successfully restarted.

  • Now open Dashboard and check if everything is working.

thanks for the update redimech,
maybe dons latest message will help?

I tried this… DDService64d was appearing. Restarted it, but Dashboard still produced the same error.

I am having the same problem, and am very frustrated! I’ve spent hours now trying to get Drobo Dashboard to recognize my Drobo;

[list]
[]Completely uninstalled 2.6.9 and installed the very latest 2.6.10 version
[
]Firewall is not running
[*]Verified that DDService64d was running, and killed and restarted process
[/list]

I am running a Mac Mini (2.0 GHz Core 2 Duo, 64 bit processor, 32 bit EFI, 32 bit kernel) with OSX 10.6.8, and an original 4-bay Drobo.

It has been broken for quite a while (this wasn’t the first time I’ve tried a complete uninstall/reinstall) and while I can access my drive, I am worried about its health without the ability for Drobo Dashboard to work.

Please help!

Thank you

I have the same problem too :frowning:

hi freshcat and beatie,
while it might not be a full fix for you etc ,just to let you know that the main drobo unit (chassis) itself, should still be able to flash a failed drive with 1 blinking/flashing red light if a drive was to fail, even while you might not have dashboard running.

Thanks for the reminder that NAS is after all a hardware solution that should take care of itself :slight_smile:

I’d still like the ability to run Drobo Dashboard though, and would welcome any help from the Drobo team in getting it working again.

hi tcbeatie, yes thats true it should work with dashboard too.
i was wondering if you have a bit more info about your setup that you could provide, such as how the drobo is connected up to the mac, and if there is any other hardware routing or cabling too?

Thanks for responding. It’s connected via Firewire - a 6-pin connector cable from the Mac Mini, with a 6-to-9 pin adapter to the Drobo.

thanks for the info,
(btw while probably not going to affect dashboard from running, sometimes adaptors or usb hubs can cause other problems)

While I can understand that, the setup worked for quite a number of years without issue, both access to the drive and dashboard. As mentioned previously, access still works, but I would very much like to get dashboard running again! I would love any help I can get in helping to make that happen. Something seemed to have happened with some recent dashboard update that seems to make it not work. Would downgrading to a previous version of dashboard help? (and if so, what version and how would I get it?)

hi tc, while i do not have a mac there is a downloads page here with some links for pc and mac:
http://www.drobo.com/drobo-downloads-2/
& some uninstall / reinstall info which may hopefully help you:
http://myproducts.drobo.com/article/AA-01837

(it may of course be a case where the latest dashboard version does not by choice recognise an older drobo model, but i certainly hope that is not the case, and never the case)

So I did a full deinstall, and then installed version 2.6.4 from the link above, and am still getting the same error. Help? I feel like I’ve tried everything!

hmm, can you remember which version of dashboard you had before, when it was working fine?
it may have been a long time ago now, but maybe you found yourselv in one of the following scenarios…

for example:
a) maybe you got your drobo and only ever installed the one that came with the cd, (which was working fine before)
or
b) maybe you also downloaded a new version (and kept the installer dmg or similar) and then that was the version which was working fine before

of course, there might be a c) or d) where you did something else, or did an update via the dashboard software directly, :slight_smile: but am just trying to find a way to see which version did work fine for you… and then the next challenge will be to try and locate that specific installer for you :smiley:

And now it’s February and I’ve had trouble for the last week. I did not recently update Dashboard Software. But now I’ve been through every step outlined in this thread without resolution. Would Drobo Tech Support please send out a fix for this!

hi, if you have a chance could you post back with some more info about your computer and drobo, and we can try and help