Posts by Mic2024

  • AdGuard Home / Pi-hole DNS with Docker MacVLAN works instabile

    Hello everyone,


    Sorry for my late reply. Too much work, too less time. Thanks again for your advice. It looks like mapping the MacVLAN to the LAN bridge br0 wasn't the right solution after all. However, the problem originated from a different source. The host PC can't establish a direct connection to the MacVLAN, which means it can't access DNS (which runs in the MacVLAN). My idea was to assign the host PC an IP address in the MacVLAN. This gives it direct access to the DNS, which worked well. Unfortunately, it seems as if OMV7 repeatedly pushed itself to the forefront via this IP address and blocked the necessary ports of AdGuard (or Pi-hole). I always assumed it was an instability in the Docker container, because it worked again after a restart.


    My old configuration of /etc/network/interfaces.d/macvlan_host:

    (Please don't use this idea.)


    My new idea was to remove this host IP address from the MacVLAN and grant the host PC access to the DNS via my router. Unfortunately, it's not possible to establish such an IP route via the same LAN port that the host PC is connected to the router via. Therefore, I removed one of my four LAN ports from the LAN bridge br0 and assigned it exclusively to the MacVLAN for AdGuard. This allows me to establish an IP route from the host PC via the router to the DNS. The ping is slightly slower this way, but that's not a problem.


    Since this change, AdGuard's DNS and WebGUI have been permanently and reliably accessible. This makes it the best solution for me. (Note: If you don't have a free LAN port, you can also use a USB-to-LAN adapter. I tested this as a first attempt (because it was the easiest).)


    In OMV7, you also have to set up the additional LAN port as DHCP. All other options didn't work for me. It's important that the LAN port doesn't have the same IP address nor MAC address as the MacVLAN. (This would cause a complete network crash.) In the Docker Compose I entered the name of the LAN adapter directly (not just eth3) as parent. You can check your LAN configuration by ip a in the command line to find the adapter names.


    MacVLAN part of the Docker Compose:


    Code
    [...]
networks:
  macvlan_adguard:
    driver: macvlan
    enable_ipv6: true
    driver_opts:
      parent: enp8s0 # LAN port 4 (eth3) as parent
[...]


    There used to be a menu in the OMV web GUI that allowed you to create a static IP route. This apparently no longer exists. Therefore, I created a systemd service that establishes the static route from the host PC via the router to the MacVLAN (with DNS) every time the PC is rebooted. This has worked flawlessly so far.


    My system Service /etc/systemd/system/static-routes.service to enable the IP routing:


    The disadvantages of this solution are that you have to sacrifice one LAN port each on the PC and one on the router, and that Linux now establishes two parallel routes for IP traffic via the router. In my case, however, this doesn't cause any conflicts, as both LAN cables run directly from the router to the PC, so there's no difference in the path data packets take.


    The following image illustrates the situation once again:


    Perhaps this will help other users who encounter similar problems with a complex network configuration.


    Best regards,

    Mic.

  • Problems with S.M.A.R.T. on SATA SSDs in OMV7

    Hello everyone,


    I have five m.2 NVMe SSDs installed in my mini PC for OMV7. I also have two m.2 SATA SSDs with an m.2 SSD-to-USB3 adapter. The temperatures for the NVMe SSDs are displayed in the OMV Dashboard. For the two SATA SSDs, they are usually not displayed. This isn't a permanent situation. Sometimes it works, sometimes it doesn't.



    I'm using the current version of the Proxmox kernel, installed via the kernel plugin.


    When I run SMART on the SATA SSDs from the command line, I see all the values, but I have to specify that it's a SATA SSD. Perhaps there's an additional setting missing in OMV7?


    Thanks and regards,

    Mic.

  • Kernel Plugin, failure with Proxmox 6.14 and Proxmox 6.13 missing

    Hello ryecoaaron ,


    I needed to restore an old installation of OMV7 on my PC and I did the same steps as described above but now I am not able to update the Kernel Plugin. I always get the error:

    Code
    (Reading database ... 121026 files and directories currently installed.)
Preparing to unpack .../pve-firmware_3.15-3_all.deb ...
Unpacking pve-firmware (3.15-3) over (3.14-3) ...
dpkg: error processing archive /var/cache/apt/archives/pve-firmware_3.15-3_all.deb (--unpack):
 trying to overwrite '/lib/firmware/intel/avs/apl/dsp_basefw.bin', which is also in package firmware-intel-sound 20240709-2~bpo12+1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/pve-firmware_3.15-3_all.deb

** CONNECTION LOST **


    What shall I do this time?

    [UPDATE]

    My solution:
    1. sudo apt remove firmware-intel-sound
    2. Do the Update...
    3. sudo apt install firmware-intel-sound


    Regrads
    Mic.

  • AdGuard Home / Pi-hole DNS with Docker MacVLAN works instabile

    Hello community,


    I'd like to revisit an old problem, which has been partially resolved but is still not satisfactory. I started the following thread about it: Pi-hole läuft in Docker nicht auf OMV-PC.


    I've since replaced the Pi-hole Docker with an AdGuard Home Docker because I thought it might be the Pi-hole issue. For AdGuard Home, I also configured a MacVLAN with its own IPv4 and IPv6 in the Compose YAML.


    In principle, this works now. However, it's not permanently stable. After an indefinite period of time, it may happen that the DNS for AdGuard Home is no longer accessible from my network. Sometimes this only happens for devices that connect to the network exclusively via IPv6. Sometimes it happens for all devices.


    It may also happen that the DNS is accessible, but I can't open the AdGuard Home web GUI in the browser using its IPv4 address. The Open Media Vault 7 web GUI then appears at this IPv4 address with an error message (red text on a black background).


    If I then restart the Docker container with docker restart adguardhome, everything works again... sometimes for hours, but sometimes only for seconds or minutes.


    For monitoring purposes, I have a kind of watchdog script running on the OMV PC that tests the DNS resolution every 15 minutes and, if it fails, restarts the Docker container. Simply put, it ping www.google.de and looks at the response.


    Unfortunately, this watchdog script never finds a problem. (I log its output to a file.) Now I had an idea: What if the problem isn't in Docker, but in the Linux network configuration? (This is just an idea; it doesn't have to be this way.)


    I hope there's a Linux networking expert out there who can help me with this. Thanks in advance!


    Best regards

    Mic.

  • Kernel Plugin, failure with Proxmox 6.14 and Proxmox 6.13 missing

    Hi ryecoaaron .

    Thank you, to remove zfs dkms was the golden hint. Great. I needed to reconfigure a lot of things but now 6.14 works.

    What did I do?

    1. In OMV WebGUI: System > OMV extras click on Disable backports

    2. Continue in command line (SSH connection):

    Now, everything is running again properly but with new Kernel Proxmox 6.14.

    I think, I cannot use the OMV standard Kernel with ZFS anymore, right? (But I don't want ro do it.)

    Regards
    Mic.

  • Kernel Plugin, failure with Proxmox 6.14 and Proxmox 6.13 missing

    Hello ryecoaaron ,


    I got your point. It may be complicated to implement this information and I also understand that it is just a question of time when ZFS support also will be available for 6.14. Maybe you could mark it in the download menu as "proxmox kernel 6.14 (no ZFS support)" until it is available or you do not implement a new kernel in the plugin until all features of OMV (and OMV extras) is supported.


    I have seen there is a proxmox kernel 6.13 available but not in your OMV Kernel plugin. Could you please add it to the download list, so I (or other users) dann install it?


    Thank you.


    Regards
    Michael.

  • Kernel Plugin, failure with Proxmox 6.14 and Proxmox 6.13 missing

    Hello everyone,


    I saw that the OMV kernel plugin offers the Proxmox kernel 6.14 for installation. Unfortunately, this kernel is not compatible with ZFS. Are the developers aware of this? A note would have been helpful.


    Unfortunately, you can't install the Proxmox kernel 6.13 via the plugin. However, it does offer some improvements that I find interesting, and it is compatible with ZFS. Could you please include this kernel in the plugin?


    Thanks and regards,

    Mic.

  • Automated system backups do not performe

    Okay. I found this file. The content is just...

    Code
    # cat userdefined-32664b22-5a9d-11ec-8834-6f00f75b23ee
#!/bin/sh -l
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
/usr/sbin/omv-backup

    ... but the file omv-backup has a lot of content.


    Let's see if it will work tomorrow morning. 😊

  • Automated system backups do not performe

    Hello,


    I can see the job in scheduled tasks in OMV à System à Scheduled Tasks but when ich check the target folder of the backup no new files with the date of “last Friday” are created. If I manually start a backup it works, new files will be there.


    In /etc/crontab I see just the 4 standard entries from OMV. There is nothing added e.g. for my task.


    In general, I understand the idea of /etc/crontab but there is no “Every N minute” or “Every N hour” or “Every N day of the month”. How is this handeled?


    Regards

    Mic.

  • Automated system backups do not performe

    Dear all,


    I have configured the automated backup feature of OMV7 but there are no backups performed. Because the WebGUI for configuration of these backups is not very intuitive. How do I need to setup the automated backups to perfome one system backup each Friday at 2:00 a.m.?


    Here is my current (not working) configuration:



    What do I need to change to get my expected bahavior?


    What is aim of the button [tt]Fix cron[/ff]? When sould I use it?


    Regards

    Mic.

  • Plugin for Web-Radio

    Dear all,


    I have seen this thread and because I had a comparable question I connect to it now. I have installed OMV7 on a Mini-PC with Intel N100 CPU. It has an HDMI output but no other audio connectors. The HDMI displays the command prompt of OMV7 on a connected screen.


    I had the idea to use a web radio player as Docker Container (in the OMV Docker Compose plugin). I saw in the internet; I need to install the Pulsaudio driver on my host system and now I also saw this thread.


    Is it generally possible to use the HDMI output on an OMV7 PC for additional audio output from an installed Docker Container? Can I use Pulsaudio (made for Ubuntu) also on OMV7 (Debian)? Or is there any other way to get the audio signal from a Docker Container to my HDMI port? Is there anything what can cause troubles when I would use Pulseaudio on the PMV7 system?


    Thank you in advance!


    Regards

    Mic.