skois Posted December 18, 2019 Share Posted December 18, 2019 (edited) First of all. I want to say a big THANKS to anyone that even bothers reading this. This post is to get help, not solving any problems. I'll be happy to post all the solutions on my problems at the end so next people looking for same problems can get the help also. I'm including a lot of info. Maybe too much? I don't except from only one person to solve all my problems. I was running Unraid with an FX8350 and Gigabyte 990FXA-UD3. All of this was working fine, except pfsense which i couldn't due to low cpu count and resources (never tried to set it up) The reason posting all of my problems here (in motherboard/cpu section) is because it started after changing the MB/CPU :). If you think is should break the problems and post to different subcategories. I'll do it. It was just felt silly to post all info so many times. More problems might appear down the road. I just build the server 2 days ago and still discovering! The Build. MB: Gigabyte X399 Ex Designare CPU: Threadripper 2920x RAM: Corsair Vengeange 4x8G 3200 NVME: Samsung Evo Plus 970 500G(UD* for VM) GPU: Sapphire Rx 5700 8G Pulse SSDs: Samsung 850 Evo 250G(Cache), Samsung 860 Evo 250G(UD* for VM) HDDs: 2xWD Red 2TB(Array), 1xWD Blue 2TB (Parity) Extra: 1x4Port Gigabit Nic *Unassigned Devices What i want to achieve. -Unraid as NAS -Dockers (Plex, Sonarr, Radarr, Jacket, Bazarr, Deluge, Handbrake, Nextcloud, Unifi Controller) -VMs (1 x Windows*for Games*,1 x Linux*as daily driver*, 1 x pfSense*as Router/firewall*) Note: Windows VM - Linux VM and Handbrake will be pinned on the same CPU's because they will never run together! Only one at a time! Unraid Version: 6.8.0 rc7 Booting in UEFI Currently running bios: F12 Bios Setup: M.I.T/Advanced CPU Core Settings/Core Performance Boost: Auto M.I.T/Advanced CPU Core Settings/AMD Cool&Quiet function: Enabled M.I.T/Advanced CPU Core Settings/SVM Mode: Enabled M.I.T/Advanced CPU Core Settings/Global C-state Control: Enabled Disabled(After comming home from work VM was paused and server had locked up,disabled for testing) Enabled again, disabling it made it worse. M.I.T/Advanced CPU Core Settings/Power Supply Idle Control: Typical Current Idle M.I.T/Advanced CPU Core Settings/Opcache Control: Auto M.I.T/Advanced CPU Core Settings/Downcore Control: Auto M.I.T/Advanced CPU Core Settings/SMT Mode: Auto M.I.T/Extreme Memory Profile(X.M.P): Profile1 M.I.T/Precision Boost Overdrive: Auto Peripherals/AMD CPU fTPM: Disabled Peripherals/XHCI Hand-off: Enabled Peripherals/EHCI Hand-off: Enabled Peripherals/SR-IOV Support: Enabled Peripherals/Trusted Computing/Security Device Support: Disable Peripherals/AMD CBS/Enable IBS: Disabled Peripherals/AMD CBS/Custom Pstates - Throttling: UNTOUCHED* Peripherals/AMD CBS/Prefetcher Settings/L1 Stream HW Prefetcher: Auto Peripherals/AMD CBS/Prefetcher Settings/L2 Stream HW Prefetcher: Auto Peripherals/AMD CBS/Memory Interleaving: Auto Peripherals/AMD CBS/DRAM Controller Configuration/Gear Down Mode: Auto Peripherals/AMD CBS/DRAM Controller Configuration/DRAM Power Options/Power Down Enable: Auto Peripherals/AMD CBS/Precision Boost Overdrive Configuration: UNTOUCHED* Peripherals/AMD CBS/ACS Enable: Enable Peripherals/AMD CBS/PCIe ARI Support: Enable Peripherals/AMD CBS/cTDP Conrol: Auto Chipset/IOMMU: Enabled Chipset/SB Clock Spread Spectrum: Enabled Chipset/SATA Mode: AHCI Chipset/Chipset SATA Port Enable: Enabled Power/S3 Save Mode: Disabled Power/High Precision Event Timer: Enabled IOMMU with ACS Override Disabled: IOMMU group 0: [1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 1: [1022:1453] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 2: [1022:1453] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 3: [1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 4: [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 5: [1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 6: [1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 7: [1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 8: [1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 9: [1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 10: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 11: [1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 12: [1022:1460] 00:19.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:19.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:19.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:19.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:19.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:19.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:19.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1467] 00:19.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 13: [1022:43ba] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset USB 3.1 xHCI Controller (rev 02) [1022:43b6] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset SATA Controller (rev 02) [1022:43b1] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset PCIe Bridge (rev 02) [1022:43b4] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [8086:1539] 04:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) [8086:24fd] 05:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) [8086:1539] 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) [111d:8018] 07:00.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) [111d:8018] 08:02.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) [111d:8018] 08:04.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) [8086:10bc] 09:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) [8086:10bc] 09:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) [8086:10bc] 0a:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) [8086:10bc] 0a:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) IOMMU group 14: [144d:a808] 0b:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 IOMMU group 15: [1022:145a] 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 16: [1022:1456] 0c:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 17: [1022:145f] 0c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller IOMMU group 18: [1022:1455] 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function IOMMU group 19: [1022:7901] 0d:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 20: [1022:1457] 0d:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller IOMMU group 21: [1022:1452] 40:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 22: [1022:1452] 40:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 23: [1022:1452] 40:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 24: [1022:1453] 40:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 25: [1022:1452] 40:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 26: [1022:1452] 40:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 27: [1022:1454] 40:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 28: [1022:1452] 40:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 29: [1022:1454] 40:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 30: [1002:1478] 41:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 1478 (rev c4) IOMMU group 31: [1002:1479] 42:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 1479 IOMMU group 32: [1002:731f] 43:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5700 / 5700 XT] (rev c4) IOMMU group 33: [1002:ab38] 43:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio IOMMU group 34: [1022:145a] 44:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 35: [1022:1456] 44:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 36: [1022:145f] 44:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller IOMMU group 37: [1022:1455] 45:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function IOMMU group 38: [1022:7901] 45:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU with ACS Override: Both Quote IOMMU group 0:[1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 1:[1022:1453] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 2:[1022:1453] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 3:[1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 4:[1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 5:[1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 6:[1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 7:[1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 8:[1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 9:[1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 10:[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 11:[1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 12:[1022:1460] 00:19.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:19.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:19.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:19.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:19.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:19.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:19.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1467] 00:19.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 13:[1022:43ba] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset USB 3.1 xHCI Controller (rev 02) IOMMU group 14:[1022:43b6] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset SATA Controller (rev 02) IOMMU group 15:[1022:43b1] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset PCIe Bridge (rev 02) IOMMU group 16:[1022:43b4] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) IOMMU group 17:[1022:43b4] 02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) IOMMU group 18:[1022:43b4] 02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) IOMMU group 19:[1022:43b4] 02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) IOMMU group 20:[1022:43b4] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) IOMMU group 21:[8086:1539] 04:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 22:[8086:24fd] 05:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) IOMMU group 23:[8086:1539] 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 24:[111d:8018] 07:00.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) IOMMU group 25:[111d:8018] 08:02.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) IOMMU group 26:[111d:8018] 08:04.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) IOMMU group 27:[8086:10bc] 09:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) IOMMU group 28:[8086:10bc] 09:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) IOMMU group 29:[8086:10bc] 0a:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) IOMMU group 30:[8086:10bc] 0a:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) IOMMU group 31:[144d:a808] 0b:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 IOMMU group 32:[1022:145a] 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 33:[1022:1456] 0c:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 34:[1022:145f] 0c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller IOMMU group 35:[1022:1455] 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function IOMMU group 36:[1022:7901] 0d:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 37:[1022:1457] 0d:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller IOMMU group 38:[1022:1452] 40:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 39:[1022:1452] 40:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 40:[1022:1452] 40:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 41:[1022:1453] 40:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 42:[1022:1452] 40:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 43:[1022:1452] 40:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 44:[1022:1454] 40:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 45:[1022:1452] 40:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 46:[1022:1454] 40:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 47:[1002:1478] 41:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 1478 (rev c4) IOMMU group 48:[1002:1479] 42:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 1479 IOMMU group 49:[1002:731f] 43:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5700 / 5700 XT] (rev c4) IOMMU group 50:[1002:ab38] 43:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio IOMMU group 51:[1022:145a] 44:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 52:[1022:1456] 44:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 53:[1022:145f] 44:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller IOMMU group 54:[1022:1455] 45:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function IOMMU group 55:[1022:7901] 45:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) New IOMMU after moving NIC to 4th slot with ACS Override: Both Quote IOMMU group 0:[1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 1:[1022:1453] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 2:[1022:1453] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 3:[1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 4:[1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 5:[1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 6:[1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 7:[1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 8:[1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 9:[1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 10:[1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 11:[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 12:[1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 13:[1022:1460] 00:19.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:19.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:19.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:19.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:19.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:19.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:19.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1467] 00:19.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 14:[1022:43ba] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset USB 3.1 xHCI Controller (rev 02) IOMMU group 15:[1022:43b6] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset SATA Controller (rev 02) IOMMU group 16:[1022:43b1] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset PCIe Bridge (rev 02) IOMMU group 17:[1022:43b4] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) IOMMU group 18:[1022:43b4] 02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) IOMMU group 19:[1022:43b4] 02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) IOMMU group 20:[1022:43b4] 02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) IOMMU group 21:[1022:43b4] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) IOMMU group 22:[8086:1539] 04:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 23:[8086:24fd] 05:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) IOMMU group 24:[8086:1539] 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 25:[144d:a808] 08:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 IOMMU group 26:[111d:8018] 09:00.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) IOMMU group 27:[111d:8018] 0a:02.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) IOMMU group 28:[111d:8018] 0a:04.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) IOMMU group 29:[8086:10bc] 0b:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) IOMMU group 30:[8086:10bc] 0b:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) IOMMU group 31:[8086:10bc] 0c:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) IOMMU group 32:[8086:10bc] 0c:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) IOMMU group 33:[1022:145a] 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 34:[1022:1456] 0d:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 35:[1022:145f] 0d:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller IOMMU group 36:[1022:1455] 0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function IOMMU group 37:[1022:7901] 0e:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 38:[1022:1457] 0e:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller IOMMU group 39:[1022:1452] 40:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 40:[1022:1452] 40:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 41:[1022:1452] 40:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 42:[1022:1453] 40:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 43:[1022:1452] 40:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 44:[1022:1452] 40:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 45:[1022:1454] 40:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 46:[1022:1452] 40:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 47:[1022:1454] 40:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 48:[1002:1478] 41:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 1478 (rev c4) IOMMU group 49:[1002:1479] 42:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 1479 IOMMU group 50:[1002:731f] 43:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5700 / 5700 XT] (rev c4) IOMMU group 51:[1002:ab38] 43:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio IOMMU group 52:[1022:145a] 44:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 53:[1022:1456] 44:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 54:[1022:145f] 44:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller IOMMU group 55:[1022:1455] 45:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function IOMMU group 56:[1022:7901] 45:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) VM Settings/PCIe ACS override: Disabled VMSettings/VFIO allow unsafe interrupts: No Kernel Parameters: rcu_nocbs=0-23 vfio-pci.ids=8086:10bc (testing without rcu_nocbs after updating to F12 Bios) lstopo (stays tha same with acs disabled and both) image attached. After moving NIC to 4th slot the new topo is Problems i have so far 1) Parity Disk Log shows The Bold and Underlined lines are in Orange (Warnings) Also note that the other 2 Disks does not show: Prometheus root: /usr/sbin/wsdd Quote Dec 18 22:18:02 Prometheus kernel: ata3: SATA max UDMA/133 abar m131072@0xba780000 port 0xba780200 irq 84 Dec 18 22:18:02 Prometheus kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 18 22:18:02 Prometheus kernel: ata3.00: ATA-9: WDC WD20EZRZ-22Z5HB0, WD-WCC4M4CDUT5X, 80.00A80, max UDMA/133 Dec 18 22:18:02 Prometheus kernel: ata3.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA Dec 18 22:18:02 Prometheus kernel: ata3.00: configured for UDMA/133 Dec 18 22:18:02 Prometheus kernel: sd 3:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Dec 18 22:18:02 Prometheus kernel: sd 3:0:0:0: [sdd] 4096-byte physical blocks Dec 18 22:18:02 Prometheus kernel: sd 3:0:0:0: [sdd] Write Protect is off Dec 18 22:18:02 Prometheus kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Dec 18 22:18:02 Prometheus kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 18 22:18:02 Prometheus kernel: sdd: sdd1 Dec 18 22:18:02 Prometheus kernel: sd 3:0:0:0: [sdd] Attached SCSI disk Dec 18 22:18:03 Prometheus wsdd[2639]: udp_send: Failed to send udp packet with Invalid argument Dec 18 22:18:03 Prometheus wsdd[2639]: Failed to send hello with Invalid argument Dec 18 22:19:01 Prometheus emhttpd: WDC_WD20EZRZ-22Z5HB0_WD-WCC4M4CDUT5X (sdd) 512 3907029168 Dec 18 22:19:01 Prometheus kernel: mdcmd (1): import 0 sdd 64 1953514552 0 WDC_WD20EZRZ-22Z5HB0_WD-WCC4M4CDUT5X Dec 18 22:19:01 Prometheus kernel: md: import disk0: (sdd) WDC_WD20EZRZ-22Z5HB0_WD-WCC4M4CDUT5X size: 1953514552 Dec 18 22:19:04 Prometheus root: /usr/sbin/wsdd Dec 18 22:19:06 Prometheus emhttpd: shcmd (23): echo 128 > /sys/block/sdd/queue/nr_requests Dec 18 22:22:19 Prometheus emhttpd: shcmd (216): echo 128 > /sys/block/sdd/queue/nr_requests Dec 18 22:22:35 Prometheus root: /usr/sbin/wsdd DONE 2) Navi Reset Bug (Would like a help rebuilding latest kernel with Gnif's V2 Patch https://forum.level1techs.com/t/navi-reset-kernel-patch/147547/47 But this can be done after fixing all the other problems 3) dmesg shows in red Quote [ 19.724050] udevd[2003]: invalid key/value pair in file /etc/udev/rules.d/70-persistent-net.rules on line 3, starting at character 1 ('-') 70-persistent-net.rules contains Quote # PCI device 0x8086:0x1539 (igb) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="b4:2e:99:39:72:e0", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" -- # PCI device 0x8086:0x1539 (igb) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="b4:2e:99:39:72:e2", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" Tried removing the "--" but after reboot the -- comes back. Run dmesg -c and rebooted. Attached dmesg with the error. 4) pfSense VM only see one of the 4 ports of the passed PCI NIC pfSense: pciconf -l gives: (only pasted the line that refers to the NIC) After changing the NIC slot it still does the same. Tried it on a bare metal machine and the NIC works fine. It recognized all ports. So its something with the Virtualisation causing problems. Quote em0@pci0:1:0:0: class=0x704b103c chip=0x10bc8086 rev=0x06 hdr=0x00 XML Quote <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>pfSense</name> <uuid>5ff288d8-878b-0683-bb41-15b42c4fe42e</uuid> <metadata> <vmtemplate xmlns="unraid" name="FreeBSD" icon="pfsense.png" os="freebsd"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='15'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='17'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/5ff288d8-878b-0683-bb41-15b42c4fe42e_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Linux/pfSense-CE-2.4.4-RELEASE-p3-amd64.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/pfSense/vdisk1.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='2'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain> I made changes on XML from this Quote <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> to this i saw 2 ports: the 01:00:0 and 01:00:1 Quote <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev> Then changed each port's address on XML to 01:00:0, 01:00:1, 01:00:2, 01:00:3 and i could see all ports in the pfSense VM. But i'm not sure if this correct and if i'm supposed to do it like that. 5) Windows and Linux VM having problems resetting onboard Audio, Weird thing is that when booted the sounds works. Quote ErrorWarningSystemArrayLogin -device pcie-root-port,port=0x11,chassis=11,id=pci.11,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=0x12,chassis=12,id=pci.12,bus=pcie.0,addr=0x2.0x2 \ -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 \ -device usb-hub,id=hub0,bus=usb.0,port=1 \ -drive 'file=/mnt/disks/Samsung_SSD_970_EVO_Plus_500GB_S4EVNF0M862976E/Windows 10/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' \ -device virtio-blk-pci,scsi=off,bus=pci.4,addr=0x0,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \ -drive file=/mnt/user/isos/Windows/Win10_1909_EnglishInternational_x64.iso,format=raw,if=none,id=drive-sata0-0-0,readonly=on \ -device ide-cd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=2 \ -drive file=/mnt/user/isos/virtio-win-0.1.160-1.iso,format=raw,if=none,id=drive-sata0-0-1,readonly=on \ -device ide-cd,bus=ide.1,drive=drive-sata0-0-1,id=sata0-0-1 \ -netdev tap,fd=35,id=hostnet0,vhost=on,vhostfd=36 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:4d:ed:a1,bus=pci.2,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=38,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=5 \ -device 'vfio-pci,host=0000:43:00.0,id=hostdev0,bus=pci.5,addr=0x0,romfile=/mnt/user/isos/RX 5700 8G Pulse VBios.rom' \ -device vfio-pci,host=0000:43:00.1,id=hostdev1,bus=pci.6,addr=0x0 \ -device vfio-pci,host=0000:0d:00.3,id=hostdev2,bus=pci.8,addr=0x0 \ -device usb-host,hostbus=3,hostaddr=2,id=hostdev3,bus=usb.0,port=2 \ -device usb-host,hostbus=3,hostaddr=4,id=hostdev4,bus=usb.0,port=3 \ -device usb-host,hostbus=1,hostaddr=4,id=hostdev5,bus=usb.0,port=4 \ -device usb-host,hostbus=1,hostaddr=3,id=hostdev6,bus=usb.0,port=6 \ -device usb-host,hostbus=3,hostaddr=5,id=hostdev7,bus=usb.0,port=1.1 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2019-12-18 21:08:55.204+0000: Domain id=6 is tainted: high-privileges 2019-12-18 21:08:55.204+0000: Domain id=6 is tainted: host-cpu char device redirected to /dev/pts/1 (label charserial0) 2019-12-18T21:08:56.788565Z qemu-system-x86_64: vfio: Cannot reset device 0000:0d:00.3, depends on group 35 which is not owned. 2019-12-18T21:08:57.827710Z qemu-system-x86_64: vfio: Cannot reset device 0000:0d:00.3, depends on group 35 which is not owned. 2019-12-18T21:09:10.334916Z qemu-system-x86_64: warning: guest updated active QH 2019-12-18T21:09:16.679208Z qemu-system-x86_64: warning: guest updated active QH 2019-12-18T21:09:51.152200Z qemu-system-x86_64: terminating on signal 15 from pid 18451 (/usr/sbin/libvirtd) 2019-12-18 21:09:55.001+0000: shutting down, reason=shutdown XML Quote <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='6'> <name>Windows 10</name> <uuid>716c8c11-ea23-cc14-0025-c735a924e388</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows_teamred.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='14'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='15'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='16'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='17'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/716c8c11-ea23-cc14-0025-c735a924e388_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='8' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/Samsung_SSD_970_EVO_Plus_500GB_S4EVNF0M862976E/Windows 10/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows/Win10_1909_EnglishInternational_x64.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.160-1.iso'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xe'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0xf'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x10'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' port='0x11'/> <alias name='pci.11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='12' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='12' port='0x12'/> <alias name='pci.12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:4d:ed:a1'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-6-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='5'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x43' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/RX 5700 8G Pulse VBios.rom'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x43' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x3'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0x0843'/> <address bus='3' device='2'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc08b'/> <address bus='3' device='4'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x054c'/> <product id='0x0268'/> <address bus='1' device='4'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0a12'/> <product id='0x0001'/> <address bus='1' device='3'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='6'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0c45'/> <product id='0x8502'/> <address bus='3' device='5'/> </source> <alias name='hostdev7'/> <address type='usb' bus='0' port='1.1'/> </hostdev> <hub type='usb'> <alias name='hub0'/> <address type='usb' bus='0' port='1'/> </hub> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> <source> <vendor id='0x054c'/> <product id='0x0268'/> <address bus='1' device='4'/> </source> <alias name='hostdev9'/> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0a12'/> <product id='0x0001'/> <address bus='1' device='3'/> </source> <alias name='hostdev10'/> <address type='usb' bus='0' port='6'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0c45'/> <product id='0x8502'/> <address bus='3' device='5'/> </source> <alias name='hostdev11'/> <address type='usb' bus='0' port='1.1'/> </hostdev> <hub type='usb'> <alias name='hub0'/> <address type='usb' bus='0' port='1'/> </hub> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> 6) Having this crash at random times Quote Dec 19 01:39:33 Prometheus kernel: BUG: kernel NULL pointer dereference, address: 00000000000000f0 Dec 19 01:39:33 Prometheus kernel: #PF: supervisor read access in kernel mode Dec 19 01:39:33 Prometheus kernel: #PF: error_code(0x0000) - not-present page Dec 19 01:39:33 Prometheus kernel: PGD 71a0f7067 P4D 71a0f7067 PUD 71d3a2067 PMD 0 Dec 19 01:39:33 Prometheus kernel: Oops: 0000 [#1] SMP NOPTI Dec 19 01:39:33 Prometheus kernel: CPU: 23 PID: 24635 Comm: java Tainted: P O 5.3.12-Unraid #1 Dec 19 01:39:33 Prometheus kernel: Hardware name: Gigabyte Technology Co., Ltd. X399 DESIGNARE EX/X399 DESIGNARE EX-CF, BIOS F12i 09/24/2019 Dec 19 01:39:33 Prometheus kernel: RIP: 0010:task_h_load+0x23/0xd1 Dec 19 01:39:33 Prometheus kernel: Code: 84 02 f0 09 00 00 c3 48 8b b7 00 01 00 00 4c 8b 05 71 e1 f8 00 48 8b 86 50 01 00 00 48 8b 96 30 01 00 00 4c 3b 86 20 01 00 00 <48> 8b 80 f0 00 00 00 48 63 92 48 0a 00 00 48 8d 04 d0 75 1f 48 8b Dec 19 01:39:33 Prometheus kernel: RSP: 0018:ffffc900035c3cd0 EFLAGS: 00010002 Dec 19 01:39:33 Prometheus kernel: RAX: 0000000000000000 RBX: 0000000000000017 RCX: 0000000000000017 Dec 19 01:39:33 Prometheus kernel: RDX: 0000000000000000 RSI: ffff8887487d7400 RDI: ffff88871dbdec00 Dec 19 01:39:33 Prometheus kernel: RBP: 0000000000000005 R08: 00000000fffd9637 R09: 0000000000000001 Dec 19 01:39:33 Prometheus kernel: R10: 0000000000000035 R11: 0000000000000035 R12: 0000000000000000 Dec 19 01:39:33 Prometheus kernel: R13: ffff888858d8c540 R14: 0000000000000017 R15: ffff88871dbdec00 Dec 19 01:39:33 Prometheus kernel: FS: 0000150fe03f3700(0000) GS:ffff88885d3c0000(0000) knlGS:0000000000000000 Dec 19 01:39:33 Prometheus kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 19 01:39:33 Prometheus kernel: CR2: 00000000000000f0 CR3: 0000000717d46000 CR4: 00000000003406e0 Dec 19 01:39:33 Prometheus kernel: Call Trace: Dec 19 01:39:33 Prometheus kernel: select_task_rq_fair+0x28b/0x83f Dec 19 01:39:33 Prometheus kernel: ? hrtimer_init+0x2/0x2 Dec 19 01:39:33 Prometheus kernel: ? get_futex_key+0x8f/0x2b5 Dec 19 01:39:33 Prometheus kernel: try_to_wake_up+0x188/0x30e Dec 19 01:39:33 Prometheus kernel: ? futex_wake+0x120/0x147 Dec 19 01:39:33 Prometheus kernel: wake_up_q+0x2d/0x4e Dec 19 01:39:33 Prometheus kernel: do_futex+0x5ab/0x9dc Dec 19 01:39:33 Prometheus kernel: __se_sys_futex+0x12c/0x151 Dec 19 01:39:33 Prometheus kernel: do_syscall_64+0x57/0xfd Dec 19 01:39:33 Prometheus kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Dec 19 01:39:33 Prometheus kernel: RIP: 0033:0x150ff7495a26 Dec 19 01:39:33 Prometheus kernel: Code: 00 00 00 74 17 49 8b 48 20 44 8b 59 10 41 83 e3 30 41 83 fb 20 74 1e be 85 00 00 00 41 ba 01 00 00 00 41 b9 01 00 00 04 0f 05 <48> 3d 01 f0 ff ff 73 1f 31 c0 c3 be 8c 00 00 00 49 89 c8 4d 31 d2 Dec 19 01:39:33 Prometheus kernel: RSP: 002b:0000150fe03f2d08 EFLAGS: 00000283 ORIG_RAX: 00000000000000ca Dec 19 01:39:33 Prometheus kernel: RAX: ffffffffffffffda RBX: 0000150ff0029b00 RCX: 0000150ff7495a26 Dec 19 01:39:33 Prometheus kernel: RDX: 0000000000000001 RSI: 0000000000000085 RDI: 0000150ff0029b54 Dec 19 01:39:33 Prometheus kernel: RBP: 0000150fe03f2d20 R08: 0000150ff0029b50 R09: 0000000004000001 Dec 19 01:39:33 Prometheus kernel: R10: 0000000000000001 R11: 0000000000000283 R12: 0000150ff0029b28 Dec 19 01:39:33 Prometheus kernel: R13: 0000150ff746780c R14: 0000150ff003c000 R15: 0000150ff001f560 Dec 19 01:39:33 Prometheus kernel: Modules linked in: xt_nat xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost veth tap iptable_filter xfs md_mod it87 hwmon_vid fam15h_power iptable_nat xt_MASQUERADE nf_nat ip_tables wireguard ip6_udp_tunnel udp_tunnel bonding igb i2c_algo_bit edac_mce_amd kvm_amd btusb btrtl btbcm kvm btintel bluetooth rsnvme(PO) crct10dif_pclmul crc32_pclmul crc32c_intel wmi_bmof ghash_clmulni_intel mxm_wmi aesni_intel aes_x86_64 crypto_simd cryptd glue_helper i2c_piix4 i2c_core ecdh_generic nvme k10temp e1000e ccp ecc nvme_core ahci wmi libahci button acpi_cpufreq [last unloaded: i2c_algo_bit] Dec 19 01:39:33 Prometheus kernel: CR2: 00000000000000f0 Dec 19 01:39:33 Prometheus kernel: ---[ end trace f6a83aa0f0e86276 ]--- Dec 19 01:39:33 Prometheus kernel: RIP: 0010:task_h_load+0x23/0xd1 Dec 19 01:39:33 Prometheus kernel: Code: 84 02 f0 09 00 00 c3 48 8b b7 00 01 00 00 4c 8b 05 71 e1 f8 00 48 8b 86 50 01 00 00 48 8b 96 30 01 00 00 4c 3b 86 20 01 00 00 <48> 8b 80 f0 00 00 00 48 63 92 48 0a 00 00 48 8d 04 d0 75 1f 48 8b Dec 19 01:39:33 Prometheus kernel: RSP: 0018:ffffc900035c3cd0 EFLAGS: 00010002 Dec 19 01:39:33 Prometheus kernel: RAX: 0000000000000000 RBX: 0000000000000017 RCX: 0000000000000017 Dec 19 01:39:33 Prometheus kernel: RDX: 0000000000000000 RSI: ffff8887487d7400 RDI: ffff88871dbdec00 Dec 19 01:39:33 Prometheus kernel: RBP: 0000000000000005 R08: 00000000fffd9637 R09: 0000000000000001 Dec 19 01:39:33 Prometheus kernel: R10: 0000000000000035 R11: 0000000000000035 R12: 0000000000000000 Dec 19 01:39:33 Prometheus kernel: R13: ffff888858d8c540 R14: 0000000000000017 R15: ffff88871dbdec00 Dec 19 01:39:33 Prometheus kernel: FS: 0000150fe03f3700(0000) GS:ffff88885d3c0000(0000) knlGS:0000000000000000 Dec 19 01:39:33 Prometheus kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 19 01:39:33 Prometheus kernel: CR2: 00000000000000f0 CR3: 0000000717d46000 CR4: 00000000003406e0 EDIT 22/12/19 After disabled Handbrake container, unraid seems stable, no lockouts, no weird things, (except know bugs like navi reset) For some reason even if handbrake wasn't doing anything it was doing something bad. If it was encoding. the server would become unusable soon after the 1st failed encode. Nothing was showing on dmesg or system logs. Had a couple of lockups but at the same time i was doing stuff. like adding second cache drive where balance got stuck and tried to stop balance and reboot. At first day when windows vm goes to sleep cant wake (because of the navi bug), but it was also locking up host. Now it wont lock host. I don't know if it was just coincidence the 1st day. because i didnt do any changes on settings etc. The only thing i've done is to update to 6.8.0 stable and revert back to 6.8.0. rc7. Will report back in a couple of days to see how its going. dmesg Edited December 21, 2019 by skois Quote Link to comment
IronBeardKnight Posted December 19, 2019 Share Posted December 19, 2019 (edited) Hi there. I have the same board and cpu combo as you running 65 tb total all sata occupied with 2 x nvme and 3 GPUs. You may be overloading people with this much info straight away lol Ever since upgrading to 6.8 I have been having none stop freeze drives dropping mainly my parity drives I recently added what I believe to be hgst or WD Red 10 tb drives to the array a little time before upgrading and it appears they are having the issues only after updating to the new version 6.8 from 6.7.2. My board and cpu combo was rock solid on 6.7.2 even with the new drives. I seem to be giving quite a bit of instability with vms shutting off and drives in parity disabling as well with the new build of Unraid. ps I forgot to mention I’m on the same bios version as you but gigabyte seem to have con issues as the latest revision now has gone back to f11 using 8.8.8.8 from Australia Edited December 19, 2019 by IronBeardKnight More info Quote Link to comment
skois Posted December 19, 2019 Author Share Posted December 19, 2019 (edited) 9 minutes ago, IronBeardKnight said: Hi there. I have the same board and cpu combo as you running 65 tb total all sata occupied with 2 x nvme and 3 GPUs. You may be overloading people with this much info straight away lol Ever since upgrading to 6.8 I have been having none stop freeze drives dropping mainly my parity drives I recently added what I believe to be hgst or WD Red 10 tb drives to the array a little time before upgrading and it appears they are having the issues only after updating to the new version 6.8 from 6.7.2. My board and cpu combo was rock solid on 6.7.2 even with the new drives. I seem to be giving quite a bit of instability with vms shutting off and drives in parity disabling as well with the new build of Unraid. Thanks for replying! I was thinking to go 6.8.0 stable. Maybe 4.19.88 kernel is more stable? But not sure if my hardware is even supported on this kernel Do you mind sharing some info about bios? Like what version you running and what is your bios settings, and what kernel parameters you have? Maybe that will give me a good headstart to start digging more. I though i could give as much info as i can to avoid things like, "hey send this, run this command, try this" if i have already done it But i agree this info was maybe too much lol! Edited December 19, 2019 by skois Quote Link to comment
IronBeardKnight Posted December 19, 2019 Share Posted December 19, 2019 1 hour ago, skois said: Thanks for replying! I was thinking to go 6.8.0 stable. Maybe 4.19.88 kernel is more stable? But not sure if my hardware is even supported on this kernel Do you mind sharing some info about bios? Like what version you running and what is your bios settings, and what kernel parameters you have? Maybe that will give me a good headstart to start digging more. I though i could give as much info as i can to avoid things like, "hey send this, run this command, try this" if i have already done it But i agree this info was maybe too much lol! Sure I’ll have some time tomorrow night and pull some stats for you. I’m running designer rev 1 board with f12i bios but I’m thinking it’s more a controller issue perhaps for me or sata cables but I plan on doing some testing tomorrow after work will let you know. Quote Link to comment
skois Posted December 19, 2019 Author Share Posted December 19, 2019 Just now, IronBeardKnight said: Sure I’ll have some time tomorrow night and pull some stats for you. I’m running designer rev 1 board with f12i bios but I’m thinking it’s more a controller issue perhaps for me or sata cables but I plan on doing some testing tomorrow after work will let you know. Mine is also v1, if you dont mind please tell me if you using any kernel parameters between append and initrd! I'll be waiting Thanks! Quote Link to comment
skois Posted December 19, 2019 Author Share Posted December 19, 2019 6 hours ago, IronBeardKnight said: ps I forgot to mention I’m on the same bios version as you but gigabyte seem to have con issues as the latest revision now has gone back to f11 using 8.8.8.8 from Australia Wait, i just checked again from my laptop and my mobile data, and Gigabyte might have pulled F12 down? I was able to see F12 but now i can see F11 as latest. What is going here? Quote Link to comment
IronBeardKnight Posted December 20, 2019 Share Posted December 20, 2019 8 hours ago, IronBeardKnight said: Sure I’ll have some time tomorrow night and pull some stats for you. I’m running designer rev 1 board with f12i bios but I’m thinking it’s more a controller issue perhaps for me or sata cables but I plan on doing some testing tomorrow after work will let you know. Ill check this out tonight. This bios download changes happened a few times now on the gigabyte site. I know that bifurcation is supported in f12i at 4x4 and a newer agesa but not sure what else may be in the firmware. It is very annoying as they put no information as to why its taken down or what changes where done.. On the BIOS note I'm hesitant do downgrade as it appears that the agesa version in f11 is a beta from the looks of it So after booting in this morning before work I found that another drive went offline along with my two parity drives. I'm thinking that this may be drive type specific more than controller and cable as all others are working without issue. Either that or the latest kernal may be having support issues in my board perhaps will need to do further digging. Quote Link to comment
skois Posted December 20, 2019 Author Share Posted December 20, 2019 5 hours ago, IronBeardKnight said: Ill check this out tonight. This bios download changes happened a few times now on the gigabyte site. I know that bifurcation is supported in f12i at 4x4 and a newer agesa but not sure what else may be in the firmware. It is very annoying as they put no information as to why its taken down or what changes where done.. On the BIOS note I'm hesitant do downgrade as it appears that the agesa version in f11 is a beta from the looks of it So after booting in this morning before work I found that another drive went offline along with my two parity drives. I'm thinking that this may be drive type specific more than controller and cable as all others are working without issue. Either that or the latest kernal may be having support issues in my board perhaps will need to do further digging. There it is! F12 is up (no letters after it, guessing its a stable.., will try tonight!) https://www.gigabyte.com/Motherboard/X399-DESIGNARE-EX-rev-10/support#support-dl-bios Quote Link to comment
skois Posted December 22, 2019 Author Share Posted December 22, 2019 I just wanted to make an update. Turns out that RAM XMP profile was VERY unstable, this was causing a lot of issues. Now its running far more stable. Still testing and will report back! Quote Link to comment
IronBeardKnight Posted December 30, 2019 Share Posted December 30, 2019 Excellent news. I however still seem to be having issues with shucked easystore WD100EMAZ drives waiting for yet another rebuild then once its done ill probably roll back to 6.7 to see if that helps Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.