Tom082

Thank you both very much for your help!

Yes, I'm aware that I will have to flash IT mode on the 9400-16i Controller. Thank you!

Thanks. But I guess in case this does not work and I have to rollback to running Unraid on bare-metal that I cannot use my motherboards TPM anymore right? Do you know where the disk IDs are coming from or how they are generated? Is this some sort of math e.g. on the serial number of the HDD?

OK, thanks! This means I have to transfer the License back to the USB drive and then passthrough the USB correct? One more question to avoid loosing data. Unraid is agnostic to where the drives are connected right? As long as It finds all the drives with the correct UUID I should be fine correct? I'm asking because currently my drives are connected to the motherboard's SATA port and I cannot passthrough all of them. Therefore I'm going to buy an HBA 9400-16i for passthrough and attach all the drives including Unraid Boot drives, cache and array disks there. Are there special steps I have to do? Unfortunately I cannot backup everything, I do not have enough storage.

Hi I recently moved to internal boot and transferred my License from USB to TPM. Can a virtualized Unraid read my TPM to confirm proppe Licensing or what do I have to do? Background: Unfortunately after upgrading to 7.3 I'm experiencing problems with Thunderbolt. Unraid is not only a server for me, I run my daily and gaming VM on it using iGPU and dGPU passthrough. My monitor is attached via USB4/Thunderbolt and keyboard and mouse are attached to the monitor's internal KVM. This setup worked fine for more than 1.5 years without issues. Since the Upgrade to 7.3.1 my Thunderbolt attached monitor remains black and mouse and keyboard are dead. I can see the login screen on my secondary monitor though so I know the daily VM is running just fine. This is a Thunderbolt issue and since Thunderbolt and Unraid is not exactly a match I would like to virtualize Unraid on Proxmox and move off all the Containers and VMs to Proxmox and just use the virtualized Unraid as NAS. This would at the same time give me a 3rd Proxmox node and would allow me to use CEPH.

@pacmac Thank you very much. Your config is basically identical with my configs from the opening post in this thread, yet for me this did not work when I tried. I tried again today and now this works. The only difference between then and now I see is the Unraid version and now I'm running the stock Unraid Kernel (I was using Thor-Kernel before). root@blackbox:~# echo "10 MGMT" >> /etc/iproute2/rt_tables root@blackbox:~# echo "30 APP" >> /etc/iproute2/rt_tables root@blackbox:~# ip route add default via 192.168.10.10 table MGMT root@blackbox:~# ip route add default via 192.168.30.10 table APP root@blackbox:~# ip rule add from 192.168.10.0/23 table MGMT root@blackbox:~# ip rule add from 192.168.30.0/23 table APP root@blackbox:~# cat /etc/iproute2/rt_tables 10 MGMT 30 APP root@blackbox:~# ip route show table MGMT default via 192.168.10.10 dev shim-br0.10 root@blackbox:~# ip route show table APP default via 192.168.30.10 dev shim-br0.30 root@blackbox:~# ip rule list 0: from all lookup local 32764: from 192.168.30.0/23 lookup APP 32765: from 192.168.10.0/23 lookup MGMT 32766: from all lookup main 32767: from all lookup default root@blackbox:~# ip -br a | grep br0. br0 UP 192.168.1.100/24 br0.10 UP 192.168.10.40/23 metric 1 br0.30 UP 192.168.30.40/23 metric 1 root@blackbox:~# ip route get 8.8.8.8 from 192.168.30.40 8.8.8.8 from 192.168.30.40 via 192.168.30.10 dev shim-br0.30 table APP uid 0 cache root@blackbox:~# ip route get 8.8.8.8 from 192.168.10.40 8.8.8.8 from 192.168.10.40 via 192.168.10.10 dev shim-br0.10 table MGMT uid 0 cache root@blackbox:~# ping -I 192.168.10.40 8.8.8.8 -c 3 PING 8.8.8.8 (8.8.8.8) from 192.168.10.40 : 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=7.12 ms root@blackbox:~# ping -I 192.168.30.40 8.8.8.8 -c 3 PING 8.8.8.8 (8.8.8.8) from 192.168.30.40 : 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=12.0 ms root@blackbox:~# traceroute -s 192.168.10.40 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 192.168.10.11 (192.168.10.11) 0.985 ms 0.969 ms 0.964 ms root@blackbox:~# traceroute -s 192.168.30.40 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 192.168.30.11 (192.168.30.11) 1.973 ms 1.928 ms 1.921 msThank you so much for your post. This motivated me to re-visit and try again!

@CkChong Thank you very much for this great plugin. Finally I have at least partial Fan Control. I'm looking forward to see where development of this plugin goes and what features get added. If you need some inspiration for additional features check this out: https://github.com/rem0o/fancontrol.releases This is basically exactly what I'm looking for, especially the feature with the mixed fan-curves. After that the only thing missing would be some sort of "VM-client" or "Container-Client" that can report back sensor values to the host plug-in to control fans based on passed through HW e.g GPU temperature from within a gaming or AI VM.

Das sehe ich anders wenn Unraid in Zuikuft mehr in die Business-Richtung gehen will und genau das wurde in den Jubiläums-Interviews öfters angedeutet wird. Den Thread zum englischen Forum ist oben verlinkt, habe den zuerst erstellt. Hab auch hier geposted weil ich dort keine Antwort erhalten habe.

Hat irgend jemand eine Idee? Muss ich ein zusätzliches Paket installieren oder einen Service aktivieren? Falls ja, welche und wie muss ich das machen? Jede Hilfe ist willkommen. Auch eine Bestätigung dass PBR von Unraid nicht unterstützt wird (dann kann ich wenigstens aufhören nach einer Lösung zu suchen). Herzlichen Dank!

Anyone? Do I have to install another packet do get this functionality? If so which one and how can I do this on Unraid? Any hints and help is highly appreciated, even if it's just a confirmation that this is not supported by Unraid (then at least like I can stop looking for a solution) for some reason. Thank you!

Hallo zusammen ich habe diesen Guide zu Slackware gefunden und möchte zusätzliche Routing Tabellen für Unraid erstellen damit ich mein Zonen-Konzept umsetzen kann. Es sieht für mich aber zurzeit nicht so aus dass Unraid das unterstützt. Mehr Infos zu meinem geplanten Setup hier im englischen Forum. Was mache ich falsch, was übersehe ich? Falls ich das nicht entsprechend dem Guide umsetzen kann gibt es eine andere Möglichkeit? Herzlichen Dank für die Hilfe und Feedbacks

Why can I not create additional routing tables in Unraid? I found this tutorial but sadly it seems even though the tutorial is for Slackware, Unraid does not support this? Why? Is there another way to do this and if so how?

Hi I want to redesign my homelab. Here is my zone-concept: My Unraid server has all the VLANs configured. E.g. I have a guest VM in VLAN-40, HomeAssistant in VLAN-20, multiple Dockers in VLAN-30, and VMs in VLAN-100. My goal is to limit Unraid's SMB and NFS service to VLAN-30 and Unraid's management (ssh, HTTP, HTTPS) to VLAN-10. I can easily implement these restrictions in the firewall. However I also need policy based routing in Unraid in order to route outgoing packets accordingly, in other words Unraid needs to use a different default GW depending on the service (source interface). Unraid IP config: VLAN-10: 192.168.10.40/23, default-GW: 192.168.10.10 (VIP of "opensense cluster") VLAN-30: 192.168.30.40/23, default-GW: 192.168.30.10 (VIP of "opensense cluster") From the "guests zone" (VLAN-40) Unraid can only be accessed via the "apps-zone" (VLAN-30). Unraid's default route therefore needs to point to 192.168.30.10. This is where Unraid's default GW points to. However from the "homeland zone" (VLAN-100) Unraid can be accessed via the "apps-zone" (SMB, NFS) and the "mgmt-zone" (SSH, HTTP, HTTPS). Since Unraid's default GW points to 192.168.30.10, the FW will drop SSH, HTTP and HTTPS packets (spoofing since the packets arrive on the wrong interface - VLAN-30 instead of VLAN-10 ). I need Policy Based Routing (PBR) on Unraid in order to fix this. Whenever Unraid uses 192.168.10.40 as it's source IP, it's default GW for routing needs to be 192.168.10.10 and not 192.168.40.10! Is the following config correct, am I missing something, is there another way to configure this and what do I have to do to make the config persistent over reboots? 1) modify (create) /etc/iproute2/rt_tables edit: why does this not exist in Unraid? # # reserved values # 255 local 254 main 253 default 0 unspec # # local # # my routing table for MGMT VLAN 10 MGMT # my routing table for APP VLAN 30 APP 2) populate the new routing tables: ip route add default via 192.168.10.10 table MGMT ip route add default via 192.168.30.10 table APP3) add rules for the kernel to decide when to use which routing table: ip rule add from 192.168.10.40/32 table MGMT ip rule add from 192.168.30.40/32 table APP Thank you very much!

@bmartino1 Thank you very much for your long answer and explanations. I'm not sure though if we have a misunderstanding. Just to clarify I do not need to power off the monitor. I do get the errors independent of the monitor's power state as long as I have the Dashboard tab of Unraid's Web UI open in a browser.

Bolt and USB passthrough was my first attempt. I did not work reliably and I always had blackscreen issues. See here for more details. The power stat error messages I only get when I refresh the VMS tab in the Unraid GUI or ervery few seconds as long as I remain on the DASHBOARD tab. As soon as I navigate away e.g. to SETTINGS the errors immediately stop. This is why I think that in those two tabs, Unraid tries to read some stats and then sees some conflicts. It does not matter if the monitor is powered ON or OFF. As long as I have the DASHBOARD of the Unraid GUI open in a browser I get these messages: [1580441.237843] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580441.251374] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580443.238651] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580443.251005] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580444.522330] thunderbolt 0-1: device disconnected [1580445.237055] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580445.250417] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580447.239106] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580447.253058] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580449.239796] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580449.252973] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580451.241709] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580451.255736] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580453.243492] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580453.256542] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580455.242512] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580455.256439] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580457.259949] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580457.273274] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580459.259047] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580459.273195] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580460.905226] thunderbolt 0-1: new device found, vendor=0xd4 device=0xc045 [1580460.905232] thunderbolt 0-1: DELL U2724DE [1580461.266454] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible Navigate away or close the Unraid WebUI and they stop.

No I did not change syslinux yet

I currently don't have issues with my setup, everything is working and is stable. But I do get error messages in the logs and I try to understand and fix them. The first error is the one in this thread. The updated udev rule fixed those. I can now power cycle my monitor and do not get error messages anymore. Yes with power cycling I mean turning the screen on and off via power button. I do not have a dock. The monitor is directly connected to my motherboard. My motherboard has only 1 HDMI and 2x USB4/TB for iGPU display output. My secondary monitor is connected via HDMI and therefore the primary monitor (incl KWM) is attached via USB4/TB. Yes, that is my primary monitor. The secondary is the same model but without KVM and TB (U2724D) When I did my setup all of this (Unraid and Linux) where new to me. I first tried TB Controller plus USB controller passthrough to the VM. This did not work properly and my screen remained black after power cycling the monitor. My journey is described here. At this stage I needed to authenticate the monitor manually. After a lot of trial and error by chance I figured out that there was no need to passthrough the Thunderbolt controller, only the USB controller. Since the Thunderbolt Controller is back under Unraid's control I created the original udev rule. Once all worked I did not go back to see that is really needed and what not, I was just happy that I somehow managed to get it working. One week ago I started to improve and optimize my setup and update my documentation as preparation for my upcoming homelab expansion. I got hooked This kind of an addiction... Thank you very much for all the other hints and recommendations. So far I have not touched my syslinux configuration. But I will certainly look in to the power saving options. For me this issue is solved, with the updated udev rule I do not see the error message anymore and the monitor gets authenticated every time on boot as well after power cycles. The other thread describes another error I see in my logs. Even though they are both related to Thunderbolt I don't think that they are related. I will post updates and clarification for that over there.

Hi Unraid keeps spamming the following errors: Aug 24 11:31:26 blackbox kernel: pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible Aug 24 11:31:26 blackbox kernel: pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessibleThis happens exactly once every time I reload the "VMS" tab (with my VMs running) or continuously every couple of seconds when displaying the "DASHBOARD" tab. It's related to Thunderbolt (I have a Thunderbolt monitor with build-in KVM)root@blackbox:~# lspci | grep 1b 1b:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:01.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:02.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:03.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:04.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) root@blackbox:~#The device is authorized: root@blackbox:~# cat /sys/bus/thunderbolt/devices/0-1/device_name U2724DE root@blackbox:~# cat /sys/bus/thunderbolt/devices/0-1/authorized 1 root@blackbox:~# My iGPU is passed through to a Kubuntu-VM as well as one of the USB-Controllers that is part of Thunderbolt. The Thunderbolt Controller is managed by Unraid though. I tried to pass it through to the VM as well but I could not get a stable setup with this. Here my full lspci: root@blackbox:~# lspci -k 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Root Complex Subsystem: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge IOMMU Subsystem: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453 Kernel driver in use: pcieport 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453 Kernel driver in use: pcieport 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453 Kernel driver in use: pcieport 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453 Kernel driver in use: pcieport 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] Subsystem: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] Kernel driver in use: pcieport 00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] Subsystem: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] Kernel driver in use: pcieport 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 71) Subsystem: ASRock Incorporation Device 790b Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) Subsystem: ASRock Incorporation Device 790e 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 3 Kernel driver in use: k10temp Kernel modules: k10temp 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 7 01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev 24) Subsystem: Tul Corporation / PowerColor Device 1478 Kernel driver in use: pcieport 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch (rev 24) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch Kernel driver in use: pcieport 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 48 [RX 9070/9070 XT] (rev c0) Subsystem: Tul Corporation / PowerColor Device 2435 Kernel driver in use: vfio-pci Kernel modules: amdgpu 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device ab40 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device ab40 Kernel driver in use: vfio-pci 04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] Subsystem: Samsung Electronics Co Ltd Device a801 Kernel driver in use: nvme Kernel modules: nvme 05:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Upstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:0c.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 07:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller Subsystem: JMicron Technology Corp. Device 0000 Kernel driver in use: ahci 0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8126 5GbE Controller (rev 01) Subsystem: ASRock Incorporation Device 8126 Kernel driver in use: r8169 Kernel modules: r8169 0b:00.0 Network controller: MEDIATEK Corp. Device 0717 Subsystem: MEDIATEK Corp. Device 0717 0c:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Upstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:0c.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 13:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] Subsystem: Samsung Electronics Co Ltd Device a801 Kernel driver in use: nvme Kernel modules: nvme 14:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 800 Series Chipset USB 3.x XHCI Controller (rev 01) Subsystem: ASMedia Technology Inc. Device 1142 Kernel driver in use: xhci_hcd 15:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset SATA Controller (rev 01) Subsystem: ASMedia Technology Inc. Device 1062 Kernel driver in use: ahci 16:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 800 Series Chipset USB 3.x XHCI Controller (rev 01) Subsystem: ASMedia Technology Inc. Device 1142 Kernel driver in use: vfio-pci 17:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset SATA Controller (rev 01) Subsystem: ASMedia Technology Inc. Device 1062 Kernel driver in use: ahci 18:00.0 PCI bridge: ASMedia Technology Inc. ASM4242 PCIe Switch Upstream Port (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 PCIe Switch Upstream Port Kernel driver in use: pcieport 19:00.0 PCI bridge: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port Kernel driver in use: pcieport 19:01.0 PCI bridge: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port Kernel driver in use: pcieport 19:02.0 PCI bridge: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port Kernel driver in use: pcieport 19:03.0 PCI bridge: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port Kernel driver in use: pcieport 1a:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 1b:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 1b:01.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 1b:02.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 1b:03.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 1b:04.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 7a:00.0 USB controller: ASMedia Technology Inc. ASM4242 USB 3.2 xHCI Controller (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 USB 3.2 xHCI Controller Kernel driver in use: vfio-pci 7b:00.0 USB controller: ASMedia Technology Inc. ASM4242 USB 4 / Thunderbolt 3 Host Router (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 USB 4 / Thunderbolt 3 Host Router Kernel driver in use: thunderbolt Kernel modules: thunderbolt 7c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Granite Ridge [Radeon Graphics] (rev c9) Subsystem: ASRock Incorporation Device 364e Kernel driver in use: vfio-pci Kernel modules: amdgpu 7c:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller Kernel driver in use: vfio-pci 7c:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 19h PSP/CCP Subsystem: Advanced Micro Devices, Inc. [AMD] Family 19h PSP/CCP Kernel driver in use: ccp Kernel modules: ccp 7c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 3.1 xHCI Subsystem: ASRock Incorporation Device 15b6 Kernel driver in use: xhci_hcd 7c:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 3.1 xHCI Subsystem: ASRock Incorporation Device 15b6 Kernel driver in use: xhci_hcd 7c:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller Subsystem: Advanced Micro Devices, Inc. [AMD] Device d601 7d:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 2.0 xHCI Subsystem: ASRock Incorporation Device 15b6 Kernel driver in use: xhci_hcd root@blackbox:~# My system is working fine and stable though. I'm just wondering why this happens and if there is a way to "fix" this. Currently my best guess is that those two tabs somehow try to read device states but cannot access them due to the USB passthrough. Thank you very much!

Update: Hah!, According to AI the rule can be simplified: # Automatically authorize a Dell U2724DE Thunderbolt monitor (matched by device_name > cat /sys/bus/thunderbolt/devices/.../device_name) ACTION=="add", SUBSYSTEM=="thunderbolt", ATTR{device_name}=="U2724DE", # only act if device is my DELL monitor ATTR{authorized}=="0", # only act if monitor is unauthorized ATTR{authorized}="1" # if all the above is true, authorize itThis way I should still have some security and not blindly accept all devices. Also the run command seems to be redundant and for Display Port and USB functionality a rescan is not required as pointed out by @bmartino1 My original rule was busted because dma-protection and security requirements required for the rule to trigger are not met by the monitor. That is why the RUN part of the rule was required. Update 2: this brought back the errors. I'm experimenting with DEVPATH to constrain the level but so far without success. Update 3: rewriting the rule like this and removing comments somehow fixed it: ACTION=="add", SUBSYSTEM=="thunderbolt", \ ATTR{device_name}=="U2724DE", \ ATTR{authorized}=="0", \ ATTR{authorized}="1"I do not understand why. Here are the logs: [1496611.598446] thunderbolt 0-1: device disconnected [1496624.280732] thunderbolt 0-1: new device found, vendor=0xd4 device=0xc045 [1496624.280739] thunderbolt 0-1: DELL U2724DE [1496625.575269] thunderbolt 0-1: device disconnected [1496629.083819] thunderbolt 0-1: new device found, vendor=0xd4 device=0xc045 [1496629.083827] thunderbolt 0-1: DELL U2724DE ^C root@blackbox:~# cat /sys/bus/thunderbolt/devices/0-1/device_name U2724DE root@blackbox:~# cat /sys/bus/thunderbolt/devices/0-1/authorized 1 root@blackbox:~# I still get this connect, disconnect, connect behavior even without the scan. My best guess is that this happens due to authorization.

Thank you for sharing this post. I'm on 7.1.2 right now but using the 6.14.6-thor kernel (for RX9070 support). Not sure if this applies to my system. Except for the dmseg error messages it alwaysworked. Unraid always finds my Thunderbolt monitor and even my original udev rule always authorized the monitor. So in a way this is a cosmetic issue. I could have ignored the logs but I try to improve my Unraid and Linux skills and want to understand my logs and learn how to fix issues.

I tried modifying in the runtime environment. This seems to work. In order not to loose the keyboard and mouse I left the rescan in for now. I will experiment with that later. Here are the dmesg log I get now: POWER-OFF [1486828.614255] thunderbolt 0-1: device disconnected [1486829.474582] pcieport 0000:1b:00.0: Unable to change power state from D3hot to D0, device inaccessible [1486829.476126] pcieport 0000:1b:04.0: Unable to change power state from D3hot to D0, device inaccessiblePOWER-ON [1486847.852133] thunderbolt 0-1: new device found, vendor=0xd4 device=0xc045 [1486847.852139] thunderbolt 0-1: DELL U2724DE [1486848.018060] pcieport 0000:1a:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486848.018159] pcieport 0000:1b:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486848.018172] pcieport 0000:1b:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486848.018184] pcieport 0000:1b:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486848.018195] pcieport 0000:1b:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486848.018216] pcieport 0000:1b:04.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486848.018250] pci_bus 0000:1c: busn_res: [bus 1c] end is updated to 1c [1486848.018282] pci_bus 0000:1d: busn_res: [bus 1d-2b] end is updated to 2b [1486848.018312] pci_bus 0000:2c: busn_res: [bus 2c-3a] end is updated to 3a [1486848.018341] pci_bus 0000:3b: busn_res: [bus 3b-48] end is updated to 48 [1486848.018371] pci_bus 0000:49: busn_res: [bus 49] end is updated to 49 [1486848.018377] pci_bus 0000:1b: busn_res: [bus 1b-49] end is updated to 49 [1486849.138586] thunderbolt 0-1: device disconnected [1486849.740645] pcieport 0000:1b:04.0: Unable to change power state from D3hot to D0, device inaccessible [1486849.742187] pcieport 0000:1b:00.0: Unable to change power state from D3hot to D0, device inaccessible [1486852.641049] thunderbolt 0-1: new device found, vendor=0xd4 device=0xc045 [1486852.641054] thunderbolt 0-1: DELL U2724DE [1486852.804162] pcieport 0000:1a:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486852.804260] pcieport 0000:1b:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486852.804272] pcieport 0000:1b:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486852.804284] pcieport 0000:1b:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486852.804295] pcieport 0000:1b:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486852.804315] pcieport 0000:1b:04.0: bridge configuration invalid ([bus 00-00]), reconfiguring [1486852.804350] pci_bus 0000:1c: busn_res: [bus 1c] end is updated to 1c [1486852.804383] pci_bus 0000:1d: busn_res: [bus 1d-2b] end is updated to 2b [1486852.804414] pci_bus 0000:2c: busn_res: [bus 2c-3a] end is updated to 3a [1486852.804443] pci_bus 0000:3b: busn_res: [bus 3b-48] end is updated to 48 [1486852.804473] pci_bus 0000:49: busn_res: [bus 49] end is updated to 49 [1486852.804479] pci_bus 0000:1b: busn_res: [bus 1b-49] end is updated to 49My guess is that the disconnect reconnect cycle happens due to the rescan. Correct? What are those power state errors I'm getting now and why did I not see them before? How can I fix those? They are related to Thunderbolt: root@blackbox:~# lspci | grep 1a: 1a:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) root@blackbox:~# lspci | grep 1b: 1b:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:01.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:02.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:03.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:04.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) root@blackbox:~# Also I'm not sure if powering off the monitor will immediately invalidate the authorization or if there is some kind a timeout, meaning that if I power on before the timeout expired the monitor is still authorized and I do not test the udev rule. In case of a timeout I will have more updates tomorrow after the monitor was off over night. So far it looks much improved :-) Thank you so much @bmartino1

Changing to macvlan solved the issue. Thank you very much. I have to read up on the different types of docker networks. I remember networkchuck also has a pretty good video about this topic. Well with the managed switch I will anyway have to read up on how to create additional networks on Unraid and how to assign VLANs to them. I want to have at least 5 different zones (guests, iot, trusted-clients, a danger-zone (port-forwarding form Inet e.g. for torrent) and one more for all the services I want to expose via tailscale).

Thank you very much. I will try your updated udev rule and report back. Do I have to reboot Unraid for the updated rule to take effect or can I for testing just update the runtime udev rule and power cycle my monitor? To be honest, I have no clue about udev. This was the very first rule I created when I started with Linux and Unraid approximately 7 months ago. Once I got the monitor authenticated automatically and had access to mouse and keyboard in the VM even after power cycling I was happy.

No, I'm not yet using tailscale. I plan to use it though once I have the FW and managed switches up and running. But at this point Pi-Hole will be on the Mini-PC too.

Hi When I POWER-OFF my Thunderbolt monitor Unraid logs the following dmesg errors: [1453854.908746] thunderbolt 0-1: device disconnected [1453854.909252] udevd[406675]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/nvm_non_active1/authorized} for writing: No such file or directory [1453854.909325] udevd[406676]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/nvm_active1/authorized} for writing: No such file or directory [1453854.909525] udevd[406677]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/wakeup/wakeup108/authorized} for writing: No such file or directory [1453854.910399] udevd[406675]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/authorized} for writing: No such file or directoryWhen I POWER-ON the monitor Unraid lots the following (dmesg): [1453903.569804] thunderbolt 0-1: new device found, vendor=0xd4 device=0xc045 [1453903.569811] thunderbolt 0-1: DELL U2724DE [1453903.660254] udevd[413098]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/nvm_active1/authorized} for writing: Permission denied [1453903.660598] udevd[413100]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/nvm_non_active1/authorized} for writing: Permission denied [1453903.686230] udevd[413098]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/wakeup/wakeup108/authorized} for writing: Permission denied [1453904.884342] thunderbolt 0-1: device disconnected [1453904.884468] udevd[413098]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/nvm_non_active1/authorized} for writing: No such file or directory [1453904.884468] udevd[413100]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/nvm_active1/authorized} for writing: No such file or directory [1453904.884763] udevd[413275]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/wakeup/wakeup108/authorized} for writing: No such file or directory [1453904.885475] udevd[413275]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/authorized} for writing: No such file or directory [1453908.393509] thunderbolt 0-1: new device found, vendor=0xd4 device=0xc045 [1453908.393514] thunderbolt 0-1: DELL U2724DE [1453908.487415] udevd[413632]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/nvm_active1/authorized} for writing: Permission denied [1453908.487655] udevd[413640]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/nvm_non_active1/authorized} for writing: Permission denied [1453908.513435] udevd[413632]: error opening ATTR{/sys/devices/pci0000:00/0000:00:02.2/0000:18:00.0/0000:19:03.0/0000:7b:00.0/domain0/0-0/0-1/wakeup/wakeup108/authorized} for writing: Permission denied How can I fix this? I do not understand why after the power on the monitor flaps e.g. detected, diconnected, and detected again and then stays stable even though the error logs are the same in both cases. My keyboard and mouse are connected to the monitors KVM and the monitor also has an Ethernet port (which I don't use). My Unraid server runs headless, the monitor is connected to a USB-4 port coupled with the iGPU which is passed through to a VM. In order tho get this to work I first tried to passthrough the whole Thunderbolt controller. However this didn't work. What is working, is leaving Thunderbolt under the management of Unraid and then only passthrough the USB-port so that the VM can handle mouse and keyboard. For Thunderbolt authentication I created the following udev rules in Unraid: root@blackbox:~# cat /boot/config/udev/50_enable_thunderbolt.rules ACTION=="add", SUBSYSTEM=="thunderbolt", \ ATTR{iommu_dma_protection}=="1", \ ATTR{security}=="dponly", \ ATTR{authorized}=="0", \ ATTR{authorized}="1", \ RUN+="/bin/sh -c 'echo 1 > /sys/bus/thunderbolt/devices/domain0/0-0/0-1/authorized && echo 1 > /sys/bus/pci/rescan'" root@blackbox:~# Here is the VM config that shows iGPU and USB passthrough: Any help is appreciated. Thank you.