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.