Problem starting miniDLNA Plugin

  • after a reboot, miniDLNA has problems starting.


    systemctl status minidlna.service shows:



    indicating, that is has problems accessing any of the paths.


    When I started it manually (after looking into it) with systemctl start minidlna.service, it had no problems at all.


    Again output of systemctl status minidlna.service



    Any ideas what I could do?

    Qnap TS-853A

    Syno DS-1618+

    Qnap TS-451+

    Qnap TS-259 Pro+

    • New
    • Official Post

    Any ideas what I could do?

    It looks like minidlna is starting before your storage is mounted.

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • That seems to solve the topic.


    Nevertheless, I didn't really like the idea of just putting some arbitrary timer in the startup process.

    So I did some further reading on that topic (including the basics of systemd) and I wonder it putting a dependency on multi-user.target would solve that topic.


    Has anybody already tied this?

    Is there anything obvius that I am missing?

    Qnap TS-853A

    Syno DS-1618+

    Qnap TS-451+

    Qnap TS-259 Pro+

    • New
    • Official Post

    Having a dependency on multi-user.target isn't uncommon. There would be little risk with minidlna. I would just try it.

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Adding that dependency also solves that issue (at least for me).

    Tested with one reboot and one real shut down, waiting some time and bringing the system back up.

    Qnap TS-853A

    Syno DS-1618+

    Qnap TS-451+

    Qnap TS-259 Pro+

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!