Latest MiniDLNA is now available for both DroboFS and Drobo5N. This version includes the latest versions of all dependencies, which should fix a number of issues from the previous releases.
Links to both DroboFS and Drobo5N releases: http://www.droboports.com/app-repository/minidlna
Comments, suggestions, and feedback are welcome.
hi I am a noob here, can you help me with the complete guide to edit and load .config file on my drobo fs. i have already reset my drobo twice. but when i install minidlna, the drobo dasboard kereps saying, " starting in a few seconds"
I’m sorry, but for advice on how to configure MiniDLNA you should ask on the MiniDLNA Help forum here: http://sourceforge.net/p/minidlna/discussion/879957/
As for why your Dashboard keeps saying “starting in a few seconds”: are you sure you are not watching water boil? I.e., How long did you wait for it to come up? Remember that, if minidlna did in fact start up, it could well be the case that the delay you are seeing is minidlna indexing your data.
ha ha… thanks for the reply. but i kept it running for over two days…without any media and still unable to get the water to boil. is there anything i might be missing. mediatomb is dead as it does not pause/fwd/rewind. pls help… once again thanks a lot
Second question: did you try to mount the DroboApps share to edit the config file? Sometimes the Dashboard just goes a little bit crazy and does not update the status correctly.
I actually saw the same thing that rohitpsk. The “starting up” message persists even after a few restarts. In the meantime, all the shares work and minidlna even works correctly with all the directories correctly populated. This is the first drobo app that I installed so at first I thought that there was a problem with installing apps but I subsequently installed open ssh and removed minidlna and things went back to normal. I did update the config files to point to my real directories and disabled the tivo option.
I just wanted to add that I too am seeing the same issue described by rohitpsk. After several Drobo FS restarts and also waiting a few hours the “starting in a few seconds” message never went away. The solution was to remove miniDLNA, which was unfortunate because it was one of my essential Drobo FS apps.
Any idea on what the issue might be? I never noticed this behaviour with past versions on miniDLNA. Thanks!
Ok, I placed a new version of minidlna 1.1.4 on github. This version has an improved service.sh script that I think solved the problem. Could you please give it a try?
I gave it a try - no luck.
I cannot remove minidlna either - no permissions.
Please advice!
Are you logging in as root?
Nope, I have no root password, only “admin”.
I’ve installed sudo package for openssh, and cannot connect to ssh now, “Connection refused”
Here’s screenshot: https://yadi.sk/i/zLJuMU8WfPZVT
Yeah, I’m not sure of what’s happening to your Drobo, but I can say this: you have to be root to install apps.
Installing sudo has no impact on openssh. They are completely unrelated. If you installed sudo as non-root, it is completely normal for it not to work.
[quote=“ricardo, post:12, topic:140452”]
Yeah, I’m not sure of what’s happening to your Drobo, but I can say this: you have to be root to install apps.[/quote]
Ok, how can I log in as root if I only have “admin” user/password?
Unfortunately, I have the same behavior on two of my Drobo-FS machines. as soon as i remove minidlna, they go back to normal 
… are there any archive versions prior to 1.1.4 available?
EDIT: After downloading another version off github and fixing openssh, mines working. failed twice for installing as admin, worked as soon as i installed as root.
I’m having a bit of trouble too.
I’ve been running my Drobo FS for years on Windows 7 with no apps at all, just a file server. I have several file shares which work fine.
I logged into my Drobo using Dashboard and upgraded the firmware and Dashboard to the latest (2.7.0). In the course of doing so, I logged in to my admin account, and it worked, so I know I have the right password.
I downloaded minidlna.tgz, put it in the DroboApps share, rebooted the Drobo. It is getting stuck on “Final stages of starting up. This may take up to 5 minutes.” It’s been over an hour.
I can still access most of my shares just fine, except I can’t get into DroboApps. So, I’ve never been able to edit the config file to tell MiniDLNA which folders to index.
I got diagnostics on the drobo, and there are a bunch of errors. At the very end it has a table of the Drobos it found (just one), but just before that it has this:
TM: 00002228 01\09 14:08:19 Error - DNASShareManager::ManageNASDevice - getDNASStatus() failed. Not adding share info for ESA 0db113570462
TM: 00002228 01\09 14:08:51 Error - DNASShareManager::ManageNASDevice - getDNASStatus() failed. Not adding share info for ESA 0db113570462
TM: 00001f3c 01\09 14:09:09 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdGetVersion
TM: 00000a54 01\09 14:09:09 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdIsAutoDiscoveryEnabled
TM: 00002228 01\09 14:09:23 Error - DNASShareManager::ManageNASDevice - getDNASStatus() failed. Not adding share info for ESA 0db113570462
TM: 00001cf4 01\09 14:09:23 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdIsAutoDiscoveryEnabled
TM: 00002f58 01\09 14:09:23 Information - ServiceCmdRouter::RouteCommand - DeviceID = 0db113570462. CmdID = eCmdGetFirmwareInfo
TM: 00000dd8 01\09 14:09:23 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdIsAutoDiscoveryEnabled
TM: 000013fc 01\09 14:09:23 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdIsAutoDiscoveryEnabled
TM: 00001f24 01\09 14:09:23 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdIsAutoDiscoveryEnabled
TM: 00000c60 01\09 14:09:31 Information - ServiceCmdRouter::RouteCommand - DeviceID = 0db113570462. CmdID = eCmdUploadDiags
So, now I’m kinda stuck. I can’t login via Dashboard, because it doesn’t think the drobo is finished booting. My data shares work, but I can’t configure MiniDLNA because I can’t get into the DroboApps share.
Any ideas?
hi dingo,
it may have finished by now though can i check is it still waiting to become ready and boot up?
can you also remember if you succcessfully rebooted the drobo after the firmwre upgrade (before minidlna), and how much data you had on it approximately?
(i have seen some posts where a user logged into the drobo to kill or remove an app and then things worked, but you may not be able to do that currently)[hr]
(don mentioned a suggestion in a past thread on page 3, which also has a lot of info from others too, which can be found here http://www.drobospace.com/forums/showthread.php?tid=142856 and while its good to take things a bit slow, may be useful to read up in the meantime)[hr]
it could also be a memory allocation as per andre’s thread here:
http://www.drobospace.com/forums/showthread.php?tid=144632&page=2&highlight=DLNA
Thanks, Paul.
It still isn’t ready.
Yes, I did successfully reboot the with the new firmware before installing minidlna.
Unfortunately, I don’t have an SSH client installed, so I can’t log into it.
However, all of my data shares are working fine.
I just can’t log in as admin, and I can’t access the DroboApps share.
I have 2 GB used, 3.5 GB free. Once I make some backups, I’ll try that trick with removing the drives.
The strange thing here is that you can access all the shares but the DroboApps one. There are a couple of options to regain control, but none are terribly easy to do:
This is the hardest one, but will certainly fix it: open the Drobo, find the serial ports, connect to a computer. The serial port gives you full root access, and from there it is easy to stop and/or uninstall minidlna.
If you have a couple of spares disks laying around, you can remove your current diskpack, insert the new ones, install SSH, then configure the DroboFS to start an SSH server on boot. Remove the new diskpack, put the old one back in, and use that SSH server to login and stop and/or uninstall minidlna.
How familiar are you with Linux?
thanks for more info dingo,
ok sure you can try and and please have a look at ricardos ideas too as he knows more about the drobo fs than me - but yes, try things after making backups first 
Thanks, Ricardo.
I’ll have a look for the serial port. I am familiar with linux; I could bring a box home from work. Does the serial port access need (or is it easier) under linux than Windows?
I don’t have any spare disks laying around, unfortunately.
And I’m trying to be gentle, since I don’t want to mess up access to my other shares!