Many problems after upgrade OMV 3>4

    • Offizieller Beitrag

    No, I was just saying you shouldn’t use the plex plugin. We recommend running plex in docker. The is a video thread pinned to every forum that will show you how to do that.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    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!

  • No, I was just saying you shouldn’t use the plex plugin. We recommend running plex in docker. The is a video thread pinned to every forum that will show you how to do that.

    Thank you.
    I will have a look on it...

  • Be advised that when using any of the Plex dockers, the drive you point the /config container path to must be mounted with the exec option set. This is currently NOT the default for OMV data disks, they are mounted noexec. And although the rootfs drive is mounted exec, it's generally a poor choice to target Plex's /config to it. The smaller the rootfs drive, the poorer the choice.


    I think it's time to either change the default behavior to mount data drives exec, or provide a simple toggle within OMV to do this easily without having to manually edit config.xml and alter an OMV environment variable.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!