Posts by dkuhl


    since I run my Plex Server as a Docker Container, I receive messages by the OMV dashboard, I am not used to.
    Even if it is plain streaming within the same LAN (inhouse) without any transcoding (plain 1080p/24p x264 .MKV) I get alerting E-Mails :
    Resource limit succeeded Service rootfs

    Date: Sun, 19 May 2019 20:20:32
    Action: alert
    Host: openmediavault
    Description: space usage test succeeded [current space usage=59.5%]

    Your faithful employee,

    It might be the case, everything is fine and this alert is normal - but it is disturbing me.
    Any idea what the occurance is triggered by and how I can get rid of it?

    Many thanks and nice streaming


    dear all,

    since some days (over a week I think), my Plex desktop reminds me that a new version of Plex is available:
    "Ein Plex Media Server Update für openmediavault steht bereit!"

    Normally, it is available and automatically installed via Docker within some few days. Is there anything I missed to configure or set-up?
    On the other hand, it already updated two or three times since I run Plex on Docker.

    Any idea?

    Many thanks and best regards

    It might still work on amd64 and i386 systems but I'm done maintaining it. I didn't pull it from the repos because I figured people would complain. Docker is the way to go - Installation and Setup Videos - Beginning, Intermediate and Advanced

    OK, I am not an expert in Linux, Debian, Openmediavault or anything else in this particular circumstance.
    I run OMV now in version 4 and recognized this Plex Update issue.
    What does it mean "Docker is the way to go"? Is Docker a replacement for the Repo in OMV-Extras?
    Can I use my "original" Plex database anyhow when moving to the Docker image installation for Plex (new)?
    And: Is there a step-for-step-guide for Dummies (like me)?
    Hope there is...



    I'm thinking /etc/apt/sources.list.d/openmediavault-kernel-backports.list
    should show deb jessie-backports main contrib non-free
    instead of deb jessie-backports main contrib non-free

    But I would like confirmation, so do not just do this without knowing what's going on.

    Don´t think there is anything I can do without a far deeper knowledge of Debian Linux itself - and the Openmediavault port.
    So, if you have any idea how to fix it without deep expert knowledge- it is really appreciated.
    Already thought about upgrading to 4.xx hoping the update error isn´t with that release version.
    Anyway: Is it recommened to upgrade from 3.0.99 to 4.xx?

    best regards and many thanks


    since I while I miss the latest Plex update. So I tried to check manually, but get a very long error message/report beginning:

    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; apt-get update 2>&1' with exit code '100': Ign file: InRelease Ign file: Release.gpg Ign file: Release Ign file: Translation-en Hit erasmus InRelease Hit erasmus/partner amd64 Packages Ign jessie InRelease Hit erasmus/main amd64 Packages Ign jessie-updates InRelease Hit erasmus InRelease Hit jessie Release.gpg Get:1 erasmus/main Translation-en [9339 B] Ign jessie-updates Release.gpg Ign jessie-backports InRelease Hit jessie/updates InRelease Hit erasmus/main amd64 Packages Get:2 jessie InRelease Ign jessie InRelease Get:3

    I attached two text files with the full error message and one with the detailed information.

    I am an amateur in Linux and usage of Openmediavault. Hopefully this is a common error message and you can help.

    Many thanks and best regards


    Built my first NAS last week with OMV as Operation System and especially for Plex Media Server (See my post in the MyNAS section).

    Activated the notification service and now I receive the following E-Mail from my OMV every day:

    Subject: [openmediavault.local] Cron (root@openmediavault> cd / && run-parts --report /etc/cron.hourly

    postsuper: fatal: scan_dir_push: open directory hold: No such file or directory
    run-parts: /etc/cron.hourly/openmediavault-flushmailq exited with return code 1

    I have no idea about it, am an newbie in this Linux stuff.

    Hope you can help.

    Many thanks and best regards


    Mini-ITX case: Sharkoon QB One
    Mainboard: Asrock H110M-ITX Intel Mainboard
    CPU: Intel Pentium Prozessor G4560
    RAM: Corsair CMV4GX4M1A2133C15 4GB DDR4 2133Mhz CL15
    Data-HDD: Seagate IronWolf ST4000VN008 4TB (central storage)
    OS-SSD : SunBow 32GB 2,5''
    CPU-Fan: Alpenfön Silvretta
    PSU: PicoPSU-90 12V 90W power supply

    Only the CPU-Fan is working (820 rpm), the Harddisk is working - even with a load of gum and dampers... working on it ^^

    Here some more views (inside and backside) of my NAS case:

    This is the view on the harddisk bay. Space for two HDD in 3.5 inch plus one 2.5. I used the second 3.5 inch bay for the OS SDD... but the SDD finds also a place in the rear to enable placing a second 3.5 HDD.

    As always: Some troubles with the cables...but at least CPU fan is not disturbed!

    I used a predefined round jack space for the power supply jack to the picoPSU-90.