I suggest to use the search function first...
Yes. Some are already testing OMV5 on a RPI4.
"Officially supported" - what exactly do you mean? votdev will not provide special hardware support for anything. When it runs Debian, it will run OMV.
Posts by WastlJ
-
-
1. Any reasons why this won't work? Any issues I should be aware of?
I don´t know "Macrium Reflect" but as long as you can use a network drive as location this should work.
2. The series of beginner videos here on the forum look like they're perfect to get me started. I've just glanced at them so far, but one comment stuck out: you need to use powered drives. I'd like to use a single spinning disc (for capacity) and was hoping it could be powered by one of the USB 3 ports on the Pi 4. Has anyone successfully tried this yet (maybe on a Pi 3)? Am I out of luck?
I have an 2,5" external SSD working without separate power source (RPI4) . I´d highly suggest to use 3,5" just with external power.
3. It looks like OMV v5 is supposed to support the Pi 4 and v4 does not. True? I know the v5 beta's available now. Any ETA on the final?
Not true. However I´ve not tested v4 as I directly tested OMV5. For ETA take a look here: ETA for OMV 5.0 - weeks, months, quarters, 2020?
-
Was heißt, du findest die Platte nicht? Du musst den Pfad manuell per Hand eintippen
-
Im Anhang 2 Screenshots. Unter "Volumes" musst du deine lokale Festplatte einbinden. Wenn das keine Anhaltspunkte sind...
Die Pfade müssen natürlich passen. Und der User entsprechend Lese/Schreibrechte. Sprich die PUID und PGID Nummern können bei dir abweichen...
-
Bitte bleib sachlich
Ich denke damit hat ryecoaaron aber recht. Wenn du die einfachsten CLI Befehle nicht beherrschst bzw weißt, wie man sich einloggt, solltest du das mit OMV 5 und OMV-Extras noch lassen. Die Kombination befindet sich einfach noch im BETA Stadium.
Eine einfache Installation über das Webinterface ist garantiert möglich, sobald eine STABLE Version da ist.
-
Ja. Leider kannst du das nicht nachträglich machen! Das musst du beim Erstellen - vor dem ersten Start - machen.
-
und jetzt noch der Rest. Bitte Zeile für Zeile einzeln:
chmod +x plex-claim-server.sh
geh auf https://www.plex.tv/claim/ und ersetze bei dem nächsten Kommando PLEX_CLAIM mit dem, was du im Browser angezeigt bekommst.
./plex-claim-server.sh "PLEX_CLAIM"
chown plex:plex "/config/Library/Application Support/Plex Media Server/Preferences.xml"
exit
docker stop plex
docker start plex
jetzt nochmal auf die IP:32400/web
-
Was hast du denn bei Portainer als Reboot-Verhalten eingestellt?
Dann natürlich vorne weg via Console:
docker start plex
dann sollte er laufen. Wenn nicht, bitte das was die Konsole ausspruckt hier posten
-
What filesystem is on your disks?
-
Das hilft mir nicht. Poste doch bitte immer deinen CLI Output.
NATÜRLICH zuerst das: docker exec -it plex /bin/bash
Dann das: curl -L -o plex-claim-server.sh https://github.com/uglymagoo/plex-claim-server/raw/master/plex-claim-server.shJetzt bitte alles was du an Output erhalten hast.
-
Are plugins coming for OMV5? There's only a couple I really use, and snapraid could be installed easy enough using apt.
Everything that has been ported by ryecoaaron is searchable here: https://bintray.com/openmediavault-plugin-developers/usul
-
I have running OMV5 on a PI4 without any problems, too.
Using the Buster Lite Image is the key - https://downloads.raspberrypi.org/raspbian_lite_latest
-
Tut mir Leid aber was du da gerade machst ist nur blindlinks alle Kommandos zu kopieren und einfügen - ganz so ungefährlich ist das nicht. calin hat lediglich den Output gepostet, dass das Script bei ihm geladen wird.
Was erhältst du denn für eine Fehlermeldung bei folgendem Code:
curl -L -o plex-claim-server.sh https://github.com/uglymagoo/plex-claim-server/raw/master/plex-claim-server.sh
-
-
I´ve read somewhere that the CLAIM Token is just available for a few minutes.
So what you can try:
- Delete the Container as well as the Image.
- Make sure your Docker machine is allowed to connect to the internet.
- Pull and create the PLEX Container with --net=host and start it
- Immediately connect to your IP:32400/web
- Now it should show the right screen
-
NTFS drives are not properly supported by Debian. I highly suggest to use just one of the file systems offered by OMV.
-
Are you able to connect via ssh to your container?
Then you could also try that script, it should claim your server again:
Code# download the script curl -L -o plex-claim-server.sh https://github.com/uglymagoo/plex-claim-server/raw/master/plex-claim-server.sh # make the script executable chmod +x plex-claim-server.sh # go to https://www.plex.tv/claim/ in your browser and get the claim token and replace PLEX_CLAIM with this token in the next command, please use use the double quotes around your claim token ./plex-claim-server.sh "PLEX_CLAIM" # fix permissions chown plex:plex "/config/Library/Application Support/Plex Media Server/Preferences.xml" # leave the container exitRestart the container.
From:
https://forums.plex.tv/t/plex-…d-my-server-help/274370/9 -
It executes the command omv-update.
Behind that command is
Codeapt-get update apt-get --yes --allow-downgrades --allow-change-held-packages --fix-missing \ --auto-remove --allow-unauthenticated \ --show-upgraded --option DPkg::Options::="--force-confold" dist-upgrade -
System->Update Manager? Where do they come from?
Standard Debian Updates + OMV related Updates.
-
If you want to change it to bridged (already got that working, too) you need to specify those ports:
-p 32400:32400/tcp \
this one at least, to make it work within your own network.
Code-p 3005:3005/tcp \ -p 8324:8324/tcp \ -p 32469:32469/tcp \ -p 1900:1900/udp \ -p 32410:32410/udp \ -p 32412:32412/udp \ -p 32413:32413/udp \ -p 32414:32414/udp \those, if you want to reach it from the Internet.
I´ve set up all my Containers just via CLI. Using portainer just to "manage" them.
