Last night, I booted up my Mac Pro, logged on to my normal non-Admin account, and was going to rerun the Xbench tests to confirm the radical performance drop-off I reported earlier.
However, the DroboPro never woke up, even after 10 minutes. And obviously the drive never mounted.
Not having any other ideas, I switched to an Admin user account, in hopes that Drobo Dashboard would be able to tell me something. Dashboard came up, said it was waiting to connect, and almost immediate the DroboPro booted up and everything was fine!
This tends to confirm my suspicion that the DHCP connection is being initiated by the Dashboard.
Now, for reasons that I don’t understand, the Drobo Dashboard cannot run in non-Admin mode – it fails immediately, and relaunching doesn’t help.
If the iSCSI connection DEPENDS on the Drobo Dashboard to launch the service, that would be a huge annoyance, because I would have to log on as Admin, start the Dashboard (which comes up automatically they way I’ve set it up), and then log off and log on as a limited user again. What a pain! And in a corporate environment, where most users do not a have admin privileges, this would be a complete deal-breaker.
I thought that perhaps I could get around this by making use of a manually assigned IP address. I tried doing it while the DroboPro was still connected via the LAN, but that didn’t seem to work. So I shut it down, and connected it via USB, and set the IP address to 126.96.36.199.
But after reconnecting the iSCSI link, DroboPro wouldn’t come up at all, and I gave up and went to bed.
So four questions:
- Is Drobo Dashboard in fact required to be running in order to wake up the DroboPro if automatic (DHCP) registration is used?
- Is that also the case if a manually assigned IP address is used?
- What did I do wrong in configuring the manual IP address?
- Is there any way to run Drobo Dashboard as a service, rather than as an application, so that it isn’t necessary to log on as Admin to bring it up? I don’t mind switching to Admin mode in order to actually USE it, but it ought to be possible to have it do its e-mail thing automatically, in the background, with no explicit effort on my part to launch it.