Open nglayton opened 8 years ago
Thanks for the heads up. I'll have a look at it.
What's the situation with this one? It does also block the Dashboard to see the free space. It sees the used space right, but total and free space are the same 100% all the time.
Can you fix it? Would be a bit better also to see thing from Dashboard...
Has there been any progress on this?
Hi,
Not that I know about it...
Terveisin,
Mika Vuorinen
@mobile
ernest leitch notifications@github.com kirjoitti 6.7.2016 kello 2.05:
Has there been any progress on this?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Sorry, I've had no free time at all to fix this.
@ricardopadilha hate to bug you, but do you have any time to look at this now?
I'm really sorry, but I'm swamped with work right now. Meanwhile, what could help a lot is to get diagnostics from the Drobo so I can try to figure out what is wrong. You can get diags using Drobo Dashboard, in the "Help and Support" tab.
Thanks for the diags, but unfortunately they do not contain much information about the device, at least not on an unencrypted format.
Maybe you can check my one.
DroboDiag__TDB104170192_20170221_182541.zip
Having a FS runing with the same symptoms.
Gruss
Ralf
Guys, how can I delete the minidlna files from the apps share? The share is NOT displaying - I think it's because it's actually stuck in the start-up sequence..
Any help would be great - thanks! Stas
As a work around, you can SSH to the box and restart the DroboApps after boot to correct the DroboDashboard issue.
Sudo su - DroboApps.sh Stop DroboApps.sh Start
Not ideal, I know, but hey.
Thanks - I'll give it a go, although I'm not sure droboFS accepts ssh to be honest.
On Mon, Jan 1, 2018 at 4:40 PM, femxiii notifications@github.com wrote:
As a work around, you can SSH to the box and restart the DroboApps after boot to correct the DroboDashboard issue.
Sudo su - DroboApps.sh Stop DroboApps.sh Start
Not ideal, I know, but hey.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/droboports/minidlna/issues/1#issuecomment-354659555, or mute the thread https://github.com/notifications/unsubscribe-auth/Aff9hsbi1EHwM2zdz9qEaEtQuFtfd4VGks5tGPxzgaJpZM4HsVYC .
It might be related to how the service/application is started, for instance aria2 and transmission have the same issue: they won't let Drobo Dashboard show all its tabs properly, if the application starts at boot.
Moreover, these apps do not obey their _enable variables in .servicerc (on the contrary, they overwrite their own _enable variable to be always YES when the application is installed/started). They are also using a newer API application_dir/libexec/service.subr
The old behavior of /etc/service.subr (start application only if its _enable variable is YES) is used only in minidlna (and maybe some other apps which are not using/packaging the newer API)
@femxiii there's an easier way, once you're root:
# cd /mnt/DroboFS/Shares/DroboApps
# minidlna/service.sh stop
# minidlna/service.sh start
This version seems to work except for it no longer allows the Drobo dashboard to function correctly. Shares will no longer show giving the message "Your Drobo is in the final stage of starting up. This may take up to 5 minutes. See attached screen grab
Effects Drobo Dashboard for MAC v2.5.4 & v2.7.1 - probably all versions. On the mac you can still mount the shares via finder and logon to the Drobo as admin. Which is good otherwise this would be completely useless.
Deleting minidlna solves the issue and Drobo dashboard functions normally again.