Posts by erbsenzaehler

    Hey,


    I installed OMV8 from skratch on a Futro s540 as I did before with OMV7. I did the install and some initial configuration in my home network (192.168.178.0/24). Then I moved it to my brothers house (192.168.188.0/24). Our networks are connected via wireguard site-to-site from FritzBox. The new install is set up to get DHCP from the router and the router fixes the IP to a specific one. That works. What is not working is the DNS.


    The NAS keeps having my old routers address as DNS server in its config (192.168.178.1). That adress is pingable but doesnt return domains - the system still uses that one and doesn't switch to another one in the list. I tried setting a DNS in network (8.8.8.8), that only added it to the .178.1 entry and the .178.1 entry still got used. I used static config and not DHCP in the web interface and still .178.1 remains in the DNS entries and got used. Reboots in between. What worked was cutting the wireguard connection so .178.1 was not reachable at all.


    Now I dug deeper with the help of Gemini, as I don't know much about Linux, and it lead me to a file which has the old setting in it.

    -> Can I savely delete /etc/netplan/00-installer-config.yaml so the entry disappears?


    Some output from the machine as I was digging just now.



    One could also split the two functions of keeping the dynamic DNS entry updated and resolving the peers into seperate scripts.

    I have an OMV NAS that is only "client" without open ports and domain entry, basically acting as a proxy for my jdownloader in a different home. For that I use wireguard-tools reresolve-dns.sh script to reresolve the ip of peers with a domain entry (in that case my FritzBoxs wireguard with MyFritz dynamic DNS service). It doesn't need to restart services at all. Might be worth a look.


    wireguard-tools/contrib/reresolve-dns/reresolve-dns.sh at master · WireGuard/wireguard-tools
    Mirror only. Official repository is at https://git.zx2c4.com/wireguard-tools - WireGuard/wireguard-tools
    github.com

    Hey,


    I tried applying changes after adding a new user on the NAS of a friend. I get an error (see below). My guess is that a somewhat failed update (not omv update) destroyed some things.

    As I am not a Linux expert I asked Gemini and would like to know if the steps it suggested are the ones I should try. Wouldn't want to destroy even more.

    It's a Futro 540, OS on USB Stick, data on msata.


    1. delete all compiled python files

    sudo find /usr/lib/python3/ -name "*.pyc" -delete


    2. sudo apt-get update

    sudo apt-get install -f

    sudo dpkg --configure -a


    3. sudo omv-salt deploy run postfix


    4. if above fails

    sudo apt-get install --reinstall salt-common python3-psutil



    I have several diferent PATHs to differenciate on Jellyfin, for that same reason:

    Code
          - /pote-media/TVshows:/data/tvshows
          - /pote-media/Movies:/data/movies
          - /pote-media/Anime:/data/anime
          - /pote-media/Documentaries:/data/documentaries
          - /pote-media/Music:/data/music


    You then probably have 5 different libraries. As you said you use mergerfs to merge multiple disks beforehand. If someone doesn't want to use mergerfs then that is possible as well and that would be easily done in rhodesfreak case, if he would be using Jellyfin. A quick Google search tells me that Plex can do the same as Jellyfin.


    Assuming Jellyfin, the media paths actually containing movies and two different drives I would do the following:

    Add both paths containing movies into container as movies1 and movies2.

    Code
    - /srv/dev-disk-by-uuid-123... /movies:/data/movies1
    - /srv/dev-disk-by-uuid-456... /movies:/data/movies2

    Add both paths in the library management of jellyfin for the movies library(see screenshot for add and remove buttons when managing the library)


    I found a Youtube video with the same settings for Plex. I attach the screenshot as well.

    Jellyfin can have multiple paths per library and I am pretty sure Plex can deal with that too. The problem is that rhodesfreak is trying to use two volumes with the same path in the container.

    Change second one like Soma wrote and edit the libraries settings and that should work.

    From what I see you probably have the following setup:


    Storage (HDD/SSD) <-USB-> Fritz!Box (Router) <-SMB-> Openmediavault <-SMB-> Windows 11


    You could have multiple problems at both SMB stages. Did you look at the guide Macom linked on omv-extras.com? Do you need this kind of setup? Someone with more Linux experience needs to look at this.

    That sound just like what the remote-mount plugin is for. It is part of omv-extras.

    misc_docs:omv_extras [omv-extras.org]


    The documentation is for omv6 but probably still the same in the way you use it.

    omv6:omv6_plugins:remote_mount [omv-extras.org]


    Quote

    Summary

    Remote Mount is a plugin that's designed to mount a remote network share, in a manner which makes the resultant file system appear to be a local filesystem on an OMV6 server. This capability makes makes connections to remote OMV servers, non-OMV servers, and Client network shares possible. When remote shares are mounted locally, many desirable administrative operations are possible.

    The filebrowser config file sits here: "/var/lib/filebrowser/filebrowser.json"

    Is that what you wanted to see?


    There is more stuff happening. Maybe take a look at the source code?

    openmediavault/deb/openmediavault-filebrowser at master · openmediavault/openmediavault
    openmediavault is the next generation network attached storage (NAS) solution based on Debian Linux. Thanks to the modular design of the framework it can be…
    github.com

    Why did I want to use the .env file? For some containers you need to set things like a password or other “confidential” information you can see in clear text in the WebGUI. My idea was to move them in the .env file to give a (small) bit of extra security.

    Why would you not trust the WebUI? That is probably the big question. Change password from the default one and do not make it accessible to the outside world.


    The two omv-extras documentations mention the global and the local env files. They are configured through the plugin and the plugin/omv configuration is the source of truth. If you do something outside of the WebUI that does not conform to the intended way of using the plugin/omv then it might just not work how you would think it does...

    Hey,


    did you take a look into the omv-extras documentation? Environment files/variables are explained there. Read the two sites carefully and then you should know where to put what (Docker in OMV 7, (Docker) Compose Plugin For OMV7). Some of the examples in the plugin have predefined environment files.


    Do not try to configure that stuff besides the UI. In OMV the configuration takes first place and you change the configuration (mostly) in the UI. OMV will overwrite files that are managed by OMV and have been changed outside.

    My guess looking at the compose settings and a quick look at the source code (here) is that what you see is the result of caching. It makes viewing stuff smoother but obviously can have side effects. You could try to reduce caching time in the settings to 0 and try again. Default is only 60 seconds so you probably were very quick with what you did.

    Probably #3: Login as the correct user in the web interface.