-
Multiple NIC Setup for Management, VM, Docker
Hmmm.... I did that, despite it is not really the perfect solution because after every redeploy (e.g. updates) you get a new mac-address. But nevertheless I added the mac-address to my OPNsense DHCP config. It was pingable and the DHCP entry showed "active"...but I could not reach it....that's weird.
-
Multiple NIC Setup for Management, VM, Docker
@Veah Ahh yeah, I read about that. But how do you manual assign on the DHCP-Server? U need a least a MAC-Address....are you using a macvlan docker network? Thanks @caplam yes, I know....it is more a relict from an old setup. I deleted the VLANS and set-up Access-Ports on my switch.
-
Multiple NIC Setup for Management, VM, Docker
@Veah thank you for your answer. Yes, eth0 is working fine. I have webgui access. The VM on eth1 uses the virtio Network Model and br1.4. It is reachable and show up on my DHCP-Server. Yes, I tried to assign IPs....the container starts but doesn't show up on my DHCP-Server and is not reachable. I attach my config for the NICs: ETH0 E ETH1: ETH2
-
Multiple NIC Setup for Management, VM, Docker
I know.. I know...but I want to split my traffic. The different VLANS are for different things and I want to segment my network. The eth2 is already a 10G NIC.
-
Multiple NIC Setup for Management, VM, Docker
Hello Community, I want to achieve the following. My goal: NIC 1 / eth0 = WebGUI and system traffic, untagged NIC 2 / eth1 = VMs, tagged VLAN 4, subnet 192.168.4.1 NIC 3 / eth2 = Containers, tagged VLAN 8, subnet 192.168.8.1 Config: eth0: no bound, no bridge, no vlan, automatic IPv4 eth1: no bound, bridged, vlan 4, IP v4 and v6 allowed on the vlan, Assignment = None eth2: no bound, bridged, vlan 8, IP v4 allowed on the vlan, Assignment = None My VM uses br.1.4 for network, receives an IP and is reachable. I have a little struggle with docker. I tried multiple things: Scenario 1: using the br.2.8 on Docker settings using custom docker network with ipvlan and parent br.2.8 Containers doenst get a lease from my DHCP-Server and are not reachable Scenario 2: using the eth2.8 on Docker settings using custom docker network with ipvlan and parent eth2.8 Containers doenst get a lease from my DHCP-Server and are not reachable Scenario 3 RETURNING TO MY OLD CONFIG: originally my eth2.8 had an DHCP Lease via Network Settings (192.168.8.10) using the br2.8 on Docker Settings using custom docker network ("docker network create") Containers use the DHCP Leasee from above 192.168.8.10 and are reachable i can access the containers BUT my VM (HomeAssistant) can't integrate them despite being pingable the BIG problem with this configuration: unraid send their webgui response via eth2.8, some packets are blocked by OPNSense (state violation rule) and the WEbGUi is extremly slow and needs constant reloads. How do I do it right? Thank you :)
-
EmilS started following Multiple NIC Setup for Management, VM, Docker
-
Chache appdata folders for stopped docker containers gone
So, @Mainfrezzerwas right. In the past my Mover copied all files from my cache appdata to my array as a backup. After uninstalling Mover Tuning, the Mover actually moved the files. Appdata of Containers that where stopped/unused were completly moved and all running containers crashed, because the Mover moved files that the containers used not so often. Luckily I had backup from the Backup / Restore Appdata Plugin. After restoring all files into a new folders, changing all containers to use those now folders, everything works again. My data is not gone, nextcloud and dbs are running. Perfect. Man, that was scary.
-
Chache appdata folders for stopped docker containers gone
Very good hint. I had to uninstall Mover Tuning, since it has been deprecated.
-
Chache appdata folders for stopped docker containers gone
I also tried to rollback to 7.0.0. DId not help either
-
Chache appdata folders for stopped docker containers gone
I think I figured it out. It looks like these errors are caused by a docker problem on unraid. The docker network hostname resolution is not working. I configured my NPM to use the IP instead of the hostname for my other containers and everything works. Since the /mnt/cache/appdata/ directory is the main docker directory, the folders for the stopped containers could be deleted by docker. Now, I just have to figure out a solution. Disable and enable docker didn't help
-
Chache appdata folders for stopped docker containers gone
Hello everyone, today I got a notice from my own uptime-kuma, that my nextcloud is down. After checking my mariadb, I noticed, that I can't connect to the DB via: mariadb - uroot -p While looking into the problem, I noticed that some appdata folders on my chache-drive are gone. But only for stopped docker containers. My Cache disks are still "healthy" and the utilization is at 11%. It's really weird and I'm kind of scared. Luckily I have backups on my ZFS-Pool. But before I do anything, I wanted to ask for help. Here are my diagnostics: unraid-diagnostics-20250304-1126.zip
-
Nginx authlimit errors filling up the log
I had the same problem with Unraid 6.12.3 with macOS and the WebGUI via Firefox. I also tried to forget the "known servers" via Finder, but that was not the solution either. Finally, only the switch to Chrome brought success. Since then my logs are clean. I have no idea what Firefox is doing in the background.
-
NCT6775 & Dynamix System Temperature + Dynamix Auto Fan Control Support
Thanks for you greate step-by-step guide Works for ASUS W680-ACE
-
[Support] ich777 - AMD Vendor Reset, CoralTPU, hpsahba,...
I hope this will happen soon. As I said, I'm not good enough yet to build a custom kernel. I have now tried it and it works. I happened to find a post that you already commented on as well. NCT6775 & Dynamix System Temperature + Dynamix Auto Fan Control Support Can you explain why you do not like this way? You mentioned possible hardware damage. Thank you :)
-
[Support] ich777 - AMD Vendor Reset, CoralTPU, hpsahba,...
Hope it helps unraid-diagnostics-20230606-1612.zip
-
[Support] ich777 - AMD Vendor Reset, CoralTPU, hpsahba,...
Hey, first of all, thanks for your great work! I really appreciate it. My problem regards the plugin "Nuvoton NCT6687 Driver". The driver does not recognize the fan speeds. I use a ASUS W680 ACE (not IPMI). There is a known bug with ASUS Mainboards and nct6798d. https://bugzilla.kernel.org/show_bug.cgi?id=204807 And one approach to solve the problem: https://github.com/asus-wmi-boards-sensors/asus-board-dsdt Unfortunately, I am not advanced enough to fully understand the solution or write a modified kernel. However, this is a problem for which I would like to have a solution as soon as possible. Can you help me by maybe extending the plugin for ASUS motherboards? Thanks in advance
EmilS
Members
-
Joined