Spritzup

Evening all, I'm having an intermittent problem with my containers becoming inaccessible, in that I attempt to access the webpage, but it simply endlessly spins. The after a random amount of time, everything is accessible until it happens again. When this happens, the unRaid GUI is fully accessible, as well as any containers that are not bridged (eg - have a dedicated IP). The only thing I see the in log (though I've attached my full log) is that what I assume are the container ports become disabled. Curiously, I also see it trying to get an IPv6 address, despite the fact that it should be disabled... May 23 14:46:16 Dyson emhttpd: Starting services... May 23 14:46:17 Dyson emhttpd: shcmd (22523): /etc/rc.d/rc.samba restart May 23 14:46:19 Dyson root: Starting Samba: /usr/sbin/smbd -D May 23 14:46:19 Dyson root: /usr/sbin/nmbd -D May 23 14:46:19 Dyson root: /usr/sbin/wsdd May 23 14:46:19 Dyson root: /usr/sbin/winbindd -D May 23 14:46:19 Dyson wsdd[109770]: set_multicast: Failed to set IPv4 multicast May 23 14:46:19 Dyson wsdd[109770]: Failed to add multicast for WSDD: Address already in use May 23 14:46:19 Dyson wsdd[109770]: set_multicast: Failed to set IPv4 multicast May 23 14:46:49 Dyson kernel: veth1bd4b6a: renamed from eth0 May 23 14:46:49 Dyson kernel: docker0: port 9(vethdc56c05) entered disabled state May 23 14:46:49 Dyson kernel: docker0: port 9(vethdc56c05) entered disabled state May 23 14:46:49 Dyson kernel: device vethdc56c05 left promiscuous mode May 23 14:46:49 Dyson kernel: docker0: port 9(vethdc56c05) entered disabled state May 23 14:46:53 Dyson kernel: veth188f45b: renamed from eth0 May 23 14:46:53 Dyson kernel: docker0: port 10(vethc70e6f9) entered disabled state May 23 14:46:53 Dyson kernel: docker0: port 10(vethc70e6f9) entered disabled state May 23 14:46:53 Dyson kernel: device vethc70e6f9 left promiscuous mode May 23 14:46:53 Dyson kernel: docker0: port 10(vethc70e6f9) entered disabled state May 23 14:46:57 Dyson kernel: veth0f85da6: renamed from eth0 May 23 14:46:57 Dyson kernel: docker0: port 11(veth9b57cdc) entered disabled state May 23 14:46:57 Dyson kernel: docker0: port 11(veth9b57cdc) entered disabled state May 23 14:46:57 Dyson kernel: device veth9b57cdc left promiscuous mode May 23 14:46:57 Dyson kernel: docker0: port 11(veth9b57cdc) entered disabled state May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered blocking state May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered disabled state May 23 14:59:19 Dyson kernel: device veth79fed20 entered promiscuous mode May 23 14:59:19 Dyson kernel: IPv6: ADDRCONF(NETDEV_UP): veth79fed20: link is not ready May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered blocking state May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered forwarding state May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered disabled state May 23 14:59:20 Dyson kernel: eth0: renamed from veth9fce0fd May 23 14:59:20 Dyson kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth79fed20: link becomes ready May 23 14:59:20 Dyson kernel: docker0: port 4(veth79fed20) entered blocking state May 23 14:59:20 Dyson kernel: docker0: port 4(veth79fed20) entered forwarding state May 23 14:59:46 Dyson kernel: docker0: port 9(veth4bfae45) entered blocking state May 23 14:59:46 Dyson kernel: docker0: port 9(veth4bfae45) entered disabled state May 23 14:59:46 Dyson kernel: device veth4bfae45 entered promiscuous mode May 23 14:59:46 Dyson kernel: IPv6: ADDRCONF(NETDEV_UP): veth4bfae45: link is not ready May 23 14:59:47 Dyson kernel: eth0: renamed from vethc1dbbde May 23 14:59:47 Dyson kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4bfae45: link becomes ready May 23 14:59:47 Dyson kernel: docker0: port 9(veth4bfae45) entered blocking state May 23 14:59:47 Dyson kernel: docker0: port 9(veth4bfae45) entered forwarding state May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered blocking state May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered disabled state May 23 15:00:11 Dyson kernel: device veth9a9edae entered promiscuous mode May 23 15:00:11 Dyson kernel: IPv6: ADDRCONF(NETDEV_UP): veth9a9edae: link is not ready May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered blocking state May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered forwarding state May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered disabled state May 23 15:00:12 Dyson kernel: eth0: renamed from vethff20ae0 May 23 15:00:12 Dyson kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9a9edae: link becomes ready May 23 15:00:12 Dyson kernel: docker0: port 10(veth9a9edae) entered blocking state Any assistance would be appreciated! ~Spritz dyson-syslog-20200523-2207.zip

Hey @hotio, I just wanted to say that I'm really happy with your Containers. At least for me, the configuration just seems to make sense. That said, I'm running into an issue with your Plex container (likely something I'm doing), where it shows that remote access is not enabled. Likely because it thinks its local IP is on the docker private network (172.x.x.x), while the port forward is obviously to the unRaid IP. Yup, as expected, I'm just an idiot. I had been doing some testing with other Plex containers and had changed my standard port forwarding rule to a random IP... and I forgot to change it back. My apologies. Any thoughts? EDIT2 - Just a thought, because it's not clear. It may be an idea to put in an example of what the format of the "Advertise_IP" variable should be. I had originally put in there the IP, but according to Plex it should be "http://<hostIPAddress>:32400/", which isn't really clear. Thanks! ~Spritz

So in theory, I could delete the variable from the container and simply use path mapping... assuming I configured it correctly from the Web UI? As you said though, this is currently untested. ~Spritz

@binhex just a quick question regarding how you've set your container up for transcoding. What is the purpose of having the "TRANS_DIR" variable, vs just having a path mapping and putting the transcode directory properly in the Plex settings? Thanks you! ~Spritz

Yeah, that looks awesome! Thanks a bunch! ~Spritz

Try changing your NIC to e1000-82545em. ~Spritz

Apologies about a second post prior to getting an answer to my first post, but I've just been thinking. Is it possible to do further tweaking to maximize performance once the VM is built? @SpaceInvaderOne perhaps similar to the windows VM tweaking video you did, but using the assumption that people are building the Mac VM based upon this docker? ~Spritz

Hey all, So I just got finished setting up this docker/VM for the wife and everything is going swimmingly (so far!). I've passed through a Radeon 570, as well as a USB controller without issue. However I have the disk hosted on a NVMe drive and am not seeing the performance I'm expecting. For comparison I'm seeing nearly 4 times the performance on an equivalent Windows 10 VM. I suspect the limiting factor is having to use the SATA interface for the drive... is their anyway to change it so that it's still picked up by Catalina? Thanks in advance! ~Spritz

Hey All, Just a few quick questions to clear up the use of the Emulator Pin. From what I've read / seen the current rule of thumb is to pin the emulator pin the lowest physical CPU, as Unraid prefers to use the lower cores. It's also considered best practice to isolate the cores of the VM's that you're using (if you're using them for gaming PC's / latency sensitive PC's). So my questions then --> 1. If the VM cores are isolated, can't we just let Unraid control where the emulator functions occur, or does KVM use the emulator on the isolated CPU's? 2. If we do need to specify the emulator pinning, wouldn't it make sense to either pin it to more cores (so that unraid tasks don't conflict) or alternatively pin it to your highest pair of cores (again so no conflict)? 3. Again, assuming we've isolated cores for our VM's, what's the best practice with our dockers? Isolate them from the emulator pin, or simply let Unraid control everything? Thanks in advance for any insight! ~Spritz

Great idea, why I didn't think of that! @matto2494, any chance you can modify the banner?

I don't have the skills for this, but would anybody be willing to upgrade these for the new style banner of Unraid? My thoughts were remove the unraid logo, and center up the icons. If one wanted to get real fancy, we could have one banner for Intel, and one for Ryzen. Thanks in advance! ~Spritz

Thanks again for the reply @testdasi, I'll verify my bios settings. What did you passthrough to your VM's? ~Spritz

Thanks for the reply @testdasi, it's very much appreciated. I wholly agree, changes within unRaid should not affect the motherboard bios, but it's what occured. Perhaps the drives overheated, but they're back now so just something to monitor. Also, good catch on the bios, however it still shows the same date... perhaps build vs release date. Model: Custom M/B: Gigabyte Technology Co., Ltd. X399 DESIGNARE EX-CF Version x.x - s/n: Default string BIOS: American Megatrends Inc. Version F12. Dated: 12/11/2019 CPU: AMD Ryzen Threadripper 2970WX 24-Core @ 3000 MHz HVM: Enabled IOMMU: Enabled Cache: 2304 KiB, 12288 KiB, 65536 KiB Memory: 64 GiB DDR4 (max. installable capacity 512 GiB) Network: bond0: IEEE 802.3ad Dynamic link aggregation, mtu 1500 eth0: interface down eth1: interface down eth2: 1000 Mbps, full duplex, mtu 1500 eth3: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 4.19.107-Unraid x86_64 Would you be willing to share your bios settings? Did you have luck passing through a USB controller? Thanks! ~Spritz

@testdasi Thank you for your help. I didn't attach the zip file because I had rebuilt the box since posting, so no error logs. That said, here is the topic --> ThreadRipper Build Issue's ~Spritz

Hey all, So what better way to spend some social isolation by building myself (and the wife) a new unRaid box. The dual 2670's were starting to get long in the tooth, especially with friends and family slamming plex to keep their sanity during this trying time. So what should have been a leisurely build has devolved into a gong show... I had got cocky with to much success with various builds between home and work, and the compute gods have decided to punish me Anyways, onto the specs first and then the issue's --> Threadripper WX2970 Gigagebyte X399 Designware 64GB PC3200 Crucial Ballistix 2x WD Black 750 m2.nvme (500GB) evga 1300 Watt PSU nvidia GTX 1060 (6gb) nvidia 1660 (6gb) Radeon 570 (4GB) The intent for the build was to break unRaid into two boxes. The new one would host parity, cache, and the 2x virtualized desktops. The 1660 would be used for Plex to do transcoding (and therefore is the unRaid video card). Then using an HBA I'd connect to my old Norco-4224 and that's where the 24-date drives would live... I have not got to the second part of this plan, which is why no HBA or data drives are listed. It should also be noted that with the previous build I had successfully built and was using a gaming PC. Anyways, onto the issue's --> 1. Creating the VM's while passing through the motherboards USB ports 2. Passing through the WD Black drives (though, what kind of performance hit would it be to just use it as a raw virtual disk) 3. Passing through the GTX1060 The symptoms are basically the same, build the VM, try and boot and the entire system hangs. I tried building a more basic system, only trying to pass through the WD, but I couldn't install Windows to it. Deleted the VM, and then the drive was gone from unRaid and the bios. Multiple reboots and resetting the bios finally got things back. Essentially at this point, if it can go wrong with building the VM's, it has gone wrong. Model: Custom M/B: Gigabyte Technology Co., Ltd. X399 DESIGNARE EX-CF Version x.x - s/n: Default string BIOS: American Megatrends Inc. Version F12. Dated: 12/11/2019 CPU: AMD Ryzen Threadripper 2970WX 24-Core @ 3000 MHz HVM: Enabled IOMMU: Enabled Cache: 2304 KiB, 12288 KiB, 65536 KiB Memory: 64 GiB DDR4 (max. installable capacity 512 GiB) Network: bond0: IEEE 802.3ad Dynamic link aggregation, mtu 1500 eth0: interface down eth1: interface down eth2: 1000 Mbps, full duplex, mtu 1500 eth3: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 4.19.107-Unraid x86_64 OpenSSL: 1.1.1d 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.3 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:1460] 00:1a.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:1a.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:1a.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:1a.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:1a.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:1a.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:1a.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1467] 00:1a.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 15: [1022:1460] 00:1b.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:1b.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:1b.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:1b.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:1b.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:1b.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:1b.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1467] 00:1b.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 16: [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) [8086:105e] 07:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) (rev 06) [8086:105e] 07:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) (rev 06) IOMMU group 17: [10de:2184] 08:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660] (rev a1) [10de:1aeb] 08:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1) [10de:1aec] 08:00.2 USB controller: NVIDIA Corporation Device 1aec (rev a1) [10de:1aed] 08:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] (rev a1) IOMMU group 18: [1002:67df] 09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef) [1002:aaf0] 09:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] IOMMU group 19: [1022:145a] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 20: [1022:1456] 0a:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 21: [1022:145f] 0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller IOMMU group 22: [1022:1455] 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function IOMMU group 23: [1022:7901] 0b:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 24: [1022:1452] 20:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 25: [1022:1452] 20:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 26: [1022:1452] 20:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 27: [1022:1452] 20:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 28: [1022:1452] 20:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 29: [1022:1454] 20:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 30: [1022:1452] 20:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 31: [1022:1454] 20:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 32: [1022:145a] 21:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 33: [1022:1456] 21:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 34: [1022:1455] 22:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function IOMMU group 35: [1022:1452] 40:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 36: [1022:1453] 40:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 37: [1022:1453] 40:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 38: [1022:1452] 40:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 39: [1022:1452] 40:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 40: [1022:1453] 40:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 41: [1022:1452] 40:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 42: [1022:1452] 40:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 43: [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 44: [1022:1452] 40:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 45: [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 46: [15b7:5002] 41:00.0 Non-Volatile memory controller: Sandisk Corp WD Black 2018/PC SN720 NVMe SSD IOMMU group 47: [15b7:5002] 42:00.0 Non-Volatile memory controller: Sandisk Corp WD Black 2018/PC SN720 NVMe SSD IOMMU group 48: [10de:1c03] 43:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1) [10de:10f1] 43:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) IOMMU group 49: [1022:145a] 44:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 50: [1022:1456] 44:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 51: [1022:145f] 44:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller IOMMU group 52: [1022:1455] 45:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function IOMMU group 53: [1022:7901] 45:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 54: [1022:1452] 60:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 55: [1022:1452] 60:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 56: [1022:1452] 60:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 57: [1022:1452] 60:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 58: [1022:1452] 60:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 59: [1022:1454] 60:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 60: [1022:1452] 60:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 61: [1022:1454] 60:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 62: [1022:145a] 61:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 63: [1022:1456] 61:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 64: [1022:1455] 62:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function CPU Thread Pairings Pair 1: cpu 0 / cpu 24 Pair 2: cpu 1 / cpu 25 Pair 3: cpu 2 / cpu 26 Pair 4: cpu 3 / cpu 27 Pair 5: cpu 4 / cpu 28 Pair 6: cpu 5 / cpu 29 Pair 7: cpu 6 / cpu 30 Pair 8: cpu 7 / cpu 31 Pair 9: cpu 8 / cpu 32 Pair 10: cpu 9 / cpu 33 Pair 11: cpu 10 / cpu 34 Pair 12: cpu 11 / cpu 35 Pair 13: cpu 12 / cpu 36 Pair 14: cpu 13 / cpu 37 Pair 15: cpu 14 / cpu 38 Pair 16: cpu 15 / cpu 39 Pair 17: cpu 16 / cpu 40 Pair 18: cpu 17 / cpu 41 Pair 19: cpu 18 / cpu 42 Pair 20: cpu 19 / cpu 43 Pair 21: cpu 20 / cpu 44 Pair 22: cpu 21 / cpu 45 Pair 23: cpu 22 / cpu 46 Pair 24: cpu 23 / cpu 47 USB Devices Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 2109:2813 VIA Labs, Inc. USB2.0 Hub Bus 001 Device 004: ID 2109:2813 VIA Labs, Inc. Bus 001 Device 005: ID 2109:2811 VIA Labs, Inc. Hub Bus 001 Device 006: ID 0955:7214 NVIDIA Corp. Bus 001 Device 007: ID 2109:2811 VIA Labs, Inc. Hub Bus 001 Device 008: ID 1038:12ad SteelSeries ApS Bus 001 Device 009: ID 046d:c338 Logitech, Inc. Bus 001 Device 010: ID 046d:c332 Logitech, Inc. G502 Proteus Spectrum Optical Mouse Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Ultra Fit Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub SCSI Devices [0:0:0:0] disk SanDisk Ultra Fit 1.00 /dev/sda 15.3GB [1:0:0:0] disk ATA ST8000NC0002-1XX CN02 /dev/sdb 8.00TB [2:0:0:0] disk ATA Crucial_CT512MX1 MU01 /dev/sdc 512GB [3:0:0:0] disk ATA ST8000NC0002-1XX CN02 /dev/sdd 8.00TB Any help will be appreciated, and let me know what else I can do to help myself. The system is pretty barebones right now. Thanks! ~Spritz

So I'm at a loss here and hoping that someone who has been through this can assist. Long story short, built a Threadripper 2970wx system using this motherboard. However, where I'm struggling is setting up two VM's with USB passthrough, as well as passing through two Western Digital Black NVMe to the above VM's. Any help or guidance that you guys can offer will be greatly appreciated! Thanks. ~Spritz

@Squid, awesome! That's what I was hoping for Thanks for your help. ~Spritz

Thanks for the reply @Squid, but that only partially helps me. Like I said (or likely didn't say clearly enough), I'd like to run the new system and old system in parallel for a brief period... at least until I can get my desktop VM rebuilt on the new system. Once that's done, the remaining rebuild is a pretty simple endeavor (famous last words). Is this something that's possible? ~Spritz

Good Morning All, So I've taken the plunge and decided to upgrade my aging system to something quite a bit more modern. I believe this will be my 4th (5th) upgrade since I started running Unraid ~10 years ago, but this is the first time that I really need to minimize downtime. Mostly because my desktop is a VM that runs on it, and more importantly, the kids will murder me if Plex is offline for to long Anyways, the complication arise from the fact that I intend to re-use portions of my existing server while building the new one. Please see below --> NEW CPU Motherboard RAM HBA Case Parity Drives RE-USE Hard Drives Cache SSD's SAS Expander Case (I'll be re-purposing the Norco-4224 as a DAS) PSU My hope is that I could build the new system to a state where I can verify stability of the new components, and then get my Desktop VM build on it. At that point, do the final portion of the upgrade. I vaguely recall that it's possible to import the disk configuration when changing hardware, just need to dig it out again. But basically, I suppose what I'm asking, is it possible to get a temp license to have to unRaid boxes running for a brief period? Thanks in advance, and apologies if this is the wrong forum. ~Spritz

Hey All, So it's time to upgrade my aging setup to something a bit more modern. I'm currently running dual 2670v1's with 128GB Ram in a Norco-4224. It has served me well, but my needs are changing so here I am. The new primary use of my server will be storage, Plex, and running two desktops... one a Windows gaming PC and one a Mac. I'd also like to I'd also like to use a video card to assist with Plex transcoding. At a high level, my thought is to repurpose the Norco as a DAS, and then build out the rest of the system in a new case with better cooling. Has anyone done this, and if so, what hardware did you use to connect the systems and power the system's on? Any gotcha's I should be aware of? The second consideration is what hardware to look at. I'm good with hitting up Ebay for slightly older server grade hardware, or is Threadripper the way to go? Lastly, I assume that passing through a USB port is dependent on your hardware config, but the safest bet would be to purchase a card. Are there any cards that support being passed through to two different VM's? Thanks in advance for the help! ~Spritz

I suspect I know what the issue is, but my CrashPlanPro is stuck at "Waiting for Connection". I'm also running the "LetsEncrypt" container on my box which has port 443 forward to it. I'm guessing it' some sort of conflict? Thanks for any help. ~Spritz

I'm having the same issue as above. How did you get it to start manually? ~Spritz

I believe I figured it out. I had to delete it and then remove the template. Even though I wasn't using the template, apparently it was pulling info from there. ~Spritz

I am using the example that was created, and followed the instructions that were located within. ~Spritz