Govnah

Looking for a sanity check and a best-practice consensus on my Unraid network config. Everything works today, but I want to confirm I'm doing it the "right" way before I build more on top of it. Environment Unraid: 7.3.1 Router / firewall: OPNsense — handles all inter-VLAN routing, firewalling, and DHCP (Kea). Unraid host uses static IPs. Switch: Unifi — Unraid's uplink port is untagged/native on VLAN 30 (PVID 30) and tagged for VLANs 10 / 20 / 40 / 60. Uplink: [single NIC / bond — mode] Docker custom network type: ipvlan (Settings → Docker). Deliberately not macvlan, to avoid the macvlan call traces / host lockups. Bridging: enabled. VLANs: enabled. Current config (Settings → Network Settings, eth0/bond0 → br0) br0 VLAN 30 (untagged / native) 192.168.30.20 /24 GW 192.168.30.1 metric 20 -> management / host GUI br0.10 VLAN 10 (tagged) 192.168.10.20 /24 GW 192.168.10.1 metric 4 -> current default egress br0.20 VLAN 20 (tagged) 192.168.20.0 /24 GW 192.168.20.1 metric 5 -> Docker and VMs br0.40 VLAN 40 (tagged) 192.168.40.0 /25 GW 192.168.40.1 metric 6 -> Docker and VMs br0.60 VLAN 60 (tagged) 192.168.60.0 /24 GW 192.168.60.1 metric 7 -> Docker and VMsImportant detail: VLAN 30 is not defined as a tagged VLAN in Unraid. The management IP (192.168.30.20) lives directly on br0 as the untagged/native network. The lowest routing metric (i.e. the host's default route) currently sits on VLAN 10, not on the management VLAN. Questions: Single gateway / default route placement. Since OPNsense routes between all VLANs, should the host have exactly one gateway — and if so, where? Right now my default route egresses VLAN 10 (lowest metric) while management is on VLAN 30. Is it better practice to put the single gateway on the management VLAN (30) for predictable return traffic, or is "default route on a dedicated VLAN, management elsewhere" a perfectly normal pattern? Any real downside to having a gateway defined on more than one VLAN interface (asymmetric routing, etc.)? Docker-only VLANs. VLANs 20 / 40 / 60 exist purely to place Docker containers. Do those interfaces need a host IP and/or gateway at all, or is it cleaner to set IPv4 assignment = None and just let the br0.X parent exist for container placement? Does leaving them gateway-less (or IP-less) cause any issues for container connectivity, given OPNsense is the gateway for each subnet? Native / untagged management. Any reason to avoid running management on the untagged/native VLAN (30) and instead tag every VLAN (no native VLAN on the port)? Mostly thinking about VLAN-hopping / segmentation hygiene versus keeping it simple. IPVLAN specifics. Confirming ipvlan is the right call here. With ipvlan (containers sharing the host MAC), what's the current recommended approach for host↔container reachability on the same parent interface — the "Host access to custom networks" shim — and are there routing quirks I should expect compared to macvlan? Metric / routing behavior. Confirming my mental model: only interfaces that have a gateway defined participate in the host's default routing, and the lowest metric wins the default route. Is that correct, and is there any reason to set explicit metrics on interfaces that have no gateway?

***Update*** The version provided by the dev seemed to address my issue, here: dlandon/unassigned.devices-next: Continued private development of the Unraid Unassigned Devices plugins by dlandon. Also, same issue on both unRAID instances, Prod and Spare. Nothing I have tried addresses the issue. Lastly, I have no unRAID array, just ZFS pools. Thanks

Here yo go, doh! Thanks unraid-spare-diagnostics-20260510-0020.zip

@tjm Did you ever get this resolved? Having the same issue, if I stop the array from the GUI and restart from GUI, the array will not start. If I remove the UD Plugin, have no issue. Diagnostics attached.

Seems to be working great, again thanks for this plugin!

Thanks for your effort on this plugin, one more issue/question. When I set Advanced Context" to click, seems to always default back to hover i.e., If I select click and hover it opens, but once I click it seems to stick until I exit the tab and go back. Seems to always to default to hover on the initial engagement.

Seems the "Advanced Preview Context" does not work for me. When I select that, nothing works when clicking or hovering over the container. Only "Default Preview Works. Not from the Dashboard, but from the Docker Tab.

Another issue, under preview, click nor hover is working, when I hover or click on a container from the docker tab I get nothing, from the dashboard it worrks. Thanks

Same issue as the other w/ the additional pop-up and when I make any changes and click submit I get the following:

*****Resolved**** Having an issue where Plugins will not update, "not available" or install from CA. I can ping github.com just fine and all other services are working fine, docker and can check for an OS Update. From the console, I can ping externally just fine. I have changed DNS to Google, Cloudflare, bounced my network stack (router and switches), and renewed cert. I have been corresponding w/ some helpful folks on DISCORD as well. See attached diagnostic file. Thanks

15-Feb-2025 09:05:43 America/Chicago] PHP Warning: Trying to access array offset on null in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 244 [15-Feb-2025 09:05:43 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106 [15-Feb-2025 09:05:55 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769) : eval()'d code(5): require_once('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769): eval() #3 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #4 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106 [15-Feb-2025 09:12:42 America/Chicago] PHP Warning: Undefined array key 0 in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 244 [15-Feb-2025 09:12:42 America/Chicago] PHP Warning: Trying to access array offset on null in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 244 [15-Feb-2025 09:12:42 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106 [15-Feb-2025 09:12:52 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769) : eval()'d code(5): require_once('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769): eval() #3 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #4 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106 [15-Feb-2025 09:16:37 America/Chicago] PHP Warning: Undefined array key 0 in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 244 [15-Feb-2025 09:16:37 America/Chicago] PHP Warning: Trying to access array offset on null in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 244 [15-Feb-2025 09:16:37 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106 [15-Feb-2025 09:17:01 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769) : eval()'d code(5): require_once('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769): eval() #3 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #4 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106 [15-Feb-2025 09:29:59 America/Chicago] PHP Warning: Undefined array key 0 in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 244 [15-Feb-2025 09:29:59 America/Chicago] PHP Warning: Trying to access array offset on null in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 244 [15-Feb-2025 09:29:59 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106 [15-Feb-2025 09:30:08 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769) : eval()'d code(5): require_once('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769): eval() #3 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #4 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106 [15-Feb-2025 09:33:34 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769) : eval()'d code(5): require_once('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769): eval() #3 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #4 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106 [15-Feb-2025 09:37:49 America/Chicago] PHP Warning: Undefined array key 0 in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 244 [15-Feb-2025 09:37:49 America/Chicago] PHP Warning: Trying to access array offset on null in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 244 [15-Feb-2025 09:37:49 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106 [15-Feb-2025 09:38:01 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769) : eval()'d code(5): require_once('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769): eval() #3 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #4 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106 [15-Feb-2025 09:38:52 America/Chicago] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #2 must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:106 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(106): array_merge(Array, false) #1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769) : eval()'d code(5): require_once('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(769): eval() #3 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #4 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 106

Unfortunately, my System Tab is still blank, guess I'll wait for the devs reply. Thanks

There is no patch showing, I removed the plugin, deleted the plugin directory, and reinstalled. The System Tab is blank, did you install the patch manually or is there an update? When I check for an update all I receive is the following: Thanks

No, I did not find a solution.

Am I missing some additional workflow after the latest update? I have some containers that show an update is ready, but the button at the bottom, Update All is greyed out and when I click on Apply Update nothing occurs and remains the same, Update Ready.

This may be trivial to some, running 7RC1 and Tailscale enabled. I have 2 networks on this server, 192.168.1.0/24 and 192.168.20.0/24. eth0 is on the 192.168.1.0/24 network and Tailscale works fine. The issue I am running into, I have several containers on the 192.168.20.0/24 network and I can't access by IP or FQDN using Tailscale, they show up in my TailNet and I approve and that as far as it goes. I have tried adding routes, restarting services, and several other efforts. I assume this is possible, what am I missing? Thanks

This maybe a trivial question but, is there a way to add additional footer options? I would like to add all fan speeds in addition to what I already have, I am running 7RC1.

Update: I rolled back, installed, and then upgraded. I installed 6.12.10 on another USB and works. On my current version, do you suggest I downgrade to load the driver and then upgrade again to beta/unRAID 7? I rather not unless that's what is recommended. Thanks

Yes I have clicked on detect and here is the output: root@unRAID-Spare:~# sensors-detect bash: sensors-detect: command not found sensors: root@unRAID-Spare:~# sensors coretemp-isa-0000 Adapter: ISA adapter Package id 0: +70.0°C (high = +100.0°C, crit = +100.0°C) Core 0: +60.0°C (high = +100.0°C, crit = +100.0°C) Core 4: +64.0°C (high = +100.0°C, crit = +100.0°C) Core 8: +70.0°C (high = +100.0°C, crit = +100.0°C) Core 9: +70.0°C (high = +100.0°C, crit = +100.0°C) Core 10: +70.0°C (high = +100.0°C, crit = +100.0°C) Core 11: +70.0°C (high = +100.0°C, crit = +100.0°C) Core 12: +69.0°C (high = +100.0°C, crit = +100.0°C) Core 13: +69.0°C (high = +100.0°C, crit = +100.0°C) Core 14: +69.0°C (high = +100.0°C, crit = +100.0°C) Core 15: +69.0°C (high = +100.0°C, crit = +100.0°C) eth1-pci-5800 Adapter: PCI adapter PHY Temperature: +44.0°C MAC Temperature: +44.0°C nvme-pci-0100 Adapter: PCI adapter Composite: +45.9°C (low = -5.2°C, high = +79.8°C) (crit = +84.8°C) acpitz-acpi-0 Adapter: ACPI interface temp1: +27.8°C it8613-isa-0a30 Adapter: ISA adapter in0: 1.18 V (min = +0.92 V, max = +1.49 V) in1: 1.12 V (min = +2.73 V, max = +0.34 V) ALARM in2: 2.04 V (min = +2.77 V, max = +2.09 V) ALARM in4: 2.01 V (min = +2.64 V, max = +2.08 V) ALARM in5: 2.06 V (min = +2.04 V, max = +2.50 V) 3VSB: 3.30 V (min = +5.57 V, max = +3.59 V) ALARM Vbat: 2.75 V +3.3V: 3.34 V Array Fan: 1814 RPM (min = 0 RPM) Array Fan: 720 RPM (min = 0 RPM) Array Fan: 694 RPM (min = 0 RPM) temp1: +74.0°C (low = +62.0°C, high = -77.0°C) ALARM sensor = Intel PECI temp2: +32.0°C (low = -8.0°C, high = -70.0°C) ALARM sensor = thermal diode temp3: -128.0°C (low = -102.0°C, high = +33.0°C) intrusion0: ALARM eth0-pci-5900 Adapter: PCI adapter PHY Temperature: +57.0°C MAC Temperature: +57.0°C nvme-pci-5700 Adapter: PCI adapter Composite: +40.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +40.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +44.9°C (low = -273.1°C, high = +65261.8°C) nvme-pci-5600 Adapter: PCI adapter Composite: +45.9°C (low = -5.2°C, high = +83.8°C) (crit = +87.8°C) Thanks

No, downloaded driver just fine, just no drivers detected, see attached.

Having same issue, had ITE working w/ unRAID7, which was an upgrade and in the process of troubleshooting I uninstalled, rebooted, and installed, now the driver does not detect any drivers. Attached diag. Thanks unraid-spare-diagnostics-20240701-1533.zip

All good, thanks again!!

NP, again thanks for the effort.

Showing only populated slots now, but Link LED still showing orange/red and I am connected at 10Gb, not a big issue just more of an FYI.

Link light is still orange/red and all Disk lights are lit even though I only have slots 1-3 populated. Diagnostics attached. Thanks unraid-spare-diagnostics-20240627-1029.zip