Aceriz

Hey I am wondering, So I have followed through and set up all the mappings as you said through the initial settings configuation stage. I can actually then get into the Bazarr main page. But at the top it says that Bazarr needs to be restarted to apply the changes made to general settings click here to restart. But when I do that I get it stalled on a page with it just saying Bazarr is restarting Please wait.. Even after waiting for 15-20 minutes nothings changes. If I close that window and try to reload the webui I get the error saying that the site can not be reached. Any ideas, I would really like to set this up, but at a loss at what to try next. This is my Log file after waiting like 15 min on that Bazarr is resetting page. ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Bazarr starting... 2019-01-17 15:58:15,867 - root (14dcd2c84b88) : INFO (main:1762) - BAZARR is started and waiting for request on http://0.0.0.0:6767/ 2019-01-17 16:00:22,587 - root (14dcd2c84b88) : INFO (main:382) - Config file created successfully 2019-01-17 16:02:37,437 - root (14dcd2c84b88) : INFO (main:222) - Bazarr is being restarted... Bazarr starting... 2019-01-17 16:02:38,454 - root (1459a60bcb88) : INFO (main:1762) - BAZARR is started and waiting for request on http://192.168.0.21:6767/ Traceback (most recent call last): File "/app/bazarr/bazarr/main.py", line 1764, in <module> server.serve_forever() File "/usr/lib/python2.7/site-packages/gevent/baseserver.py", line 360, in serve_forever self.start() File "/usr/lib/python2.7/site-packages/gevent/baseserver.py", line 304, in start self.init_socket() File "/usr/lib/python2.7/site-packages/gevent/pywsgi.py", line 1450, in init_socket StreamServer.init_socket(self)

Hey great post. I am relatively still new to Unraid and still trying to understand things. Below is my ACS override on grouping that contains the intel Audio. How should I append the following to include the ACS override as well as my other device passthough (USB controllers) kernel /bzimage append vfio-pci.ids=1b73:1100, 1b21:2142, 1b73:1100, 1b21:2142, 1b73:1100, 1b73:1100 initrd=/bzroot,/bzroot-gui pcie_acs_override=downstream,multifunction nomodeset IOMMU group 25: [8086:a2d3] 00:1f.0 ISA bridge: Intel Corporation C422 Chipset LPC/eSPI Controller [8086:a2a1] 00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller [8086:a2f0] 00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio [8086:a2a3] 00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller

anyone Have any other Ideas. I have back and started fresh with a new VM to ensure that nothing I did screwed up and still get stuck at the same point.

FYI I decided to try something else which was to start again fresh with uninstall of Nvidia drivers But then intead of adding the gtx 570 as a second card, and going through with the above steps, I placed it as the primary card with ROM file as I have found I need to make it run. Then boot the VM. I am able to them again remote in with spashtop but again it has under display adapter "Video Controller (VGA compatible)" and now a new one "mv video Hook Driver 2" ( i do wonder though if this is from spashtop...

I am indeed passing through the HDMI audio as well. I have installed spashtop remote viewer. I have gone through and was able to follow the instructions all the way through again but this time with Spashtop installed. On following step 7 I have to wait a while but windows in the device manager does eventually recognize the gtx 570 . Once it does recognize I am able to install the nvidia driver software on finishing the install if I let it reset immediately I get the error " nvlddmkm.sys" BSOD. after getting this I have had to go through and remove the drivers completely using the the uninstall video driver software to completely start again. If I go through the process but delay the reset after the install of nvidia, then Shut down the computer and change the VM template to remove VLC I am able to boot into the VM and then remote in with Spashtop. However in Device manager. I now only have under Display Adapter "Video Controller (VGA compatible)" No listed error code. with no video output on cable just on spashtop. And an attempt to install driver again here does not work. erroring with a forced reset and crash and no change in the Device Manager. FYI when the spashtop loads initially or after an error saying to install the "mirror driver" to help with performance due to CPU load. I really appreciate the help. Hopefully the info helps.

I have placed the VM log below 2018-10-27 17:39:28.883+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.15-unRAID, hostname: RizznetUnraid LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10 GTX 570 Seagate,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-22-Windows 10 GTX 570 S/master-key.aes' -machine pc-i440fx-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -m 6144 -realtime mlock=off -smp 8,sockets=1,cores=4,threads=2 -uuid 694a1eb9-f2c5-689e-e049-65b67b45afa4 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=27,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive 'file=/mnt/user/domains/Windows 10 GTX 570 Seagate/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' -device virt -device usb-host,hostbus=1,hostaddr=3,id=hostdev2,bus=usb.0,port=2 -device usb-host,hostbus=1,hostaddr=5,id=hostdev3,bus=usb.0,port=3 -device usb-host,hostbus=1,hostaddr=4,id=hostdev4,bus=usb.0,port=4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on 2018-10-27 17:39:28.883+0000: Domain id=22 is tainted: high-privileges 2018-10-27 17:39:28.883+0000: Domain id=22 is tainted: host-cpu 2018-10-27T17:39:28.926246Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)

So I went back to baseline and updated a very recent bios which is now giving me access to use the onboard graphics for unraid and move my gtx 570 to top PCI slot, thus taking out eh gtx 210. I have gotten through steps 1-6. The VM detects the GTX 570 in device manager eventually. ( I need to have ROM file dumped). But with this dumped I am able to run the Nvidia driver software from nvidia website. and it correctly updates and installs all the drivers. but when I move onto set 8 removing vnc and plugging in the gtx 570 . I am not getting any video output. And am not having any core pinned at 100% despite how long i wait even 5-10 min. Any ideas how to move forward.

Thanks I will give this a try this weekend, and update after

Hey wondering if anyone has any ideas on how to solve pass through problem. still very stuck

Thanks so much Squid for fixing things:) Appreciate all the work you do for this wicked setup.

Hey fyi I would go through and try again. Might have been something down. It is now working on my comp. And I did nothing inbetween now and my post.

Anyone have ideas. still stalled here

@Squid I am hopeful you might be able to help figure out why things are not working. I had installed the Community Applications and it was all working great for the last few months. Today I was installing a few things. Did a reset of my computer and then when I came back online the Community Applications Tab no no longer shows any significant search results example a search for "Plex" only shows 2 things.. where I know it had shown a number of things earlier today. I have tried a number of things. I have tried uninstall of community application. including clearing of plugin data on flash both current/ old. running fix common problems and CA cleaner in between with a hard reboot. Unfortunately I continue to not get a full repository of results. with no clear errors showing up. I would appreciate any help. I have attached diagnostic info to hopefully help. thanks rizznetunraid-diagnostics-20180804-1731.zip

let me know how 1050 goes and general bump for anyone with other ideas

For the vBios I have tried a number of things. I have tried grabbing the GTX 570 vbios from techpower up, ensuring header removed. I have also grabbed the vbios directly from the card, and again also ensured the vBios was removed. For the driver issues. I have tried starting the VNC to set up without any Radeon installed on the VM. set up spashtop to be able to remote in. Then added GTX 570 and its associated sound card, but on restarting It never gets to point that spashtop will load..

Let me know if you find anything. As I said above I am drawing blank

Update to original post above. I have taken the GTX 570 and moved it around into different slots on the Motherboard no luck. I have taken a friends old AMD 4780HD and that card works in the second slot which is the preferred slot. I verified on my old tower that the card does still post and has no issues on a non VM machine. So yes any help will be much appreciated as I am drawing a blank..

Hi all, thanks in advance for the help in trying to solve my problem. I am not sure where to go next. I have recently put together Unraid build and am now trying to get Windows 10 VM up and running. I have been able to get it up and running with VNC, but when I try to change to dedicated graphics card for pass through My screen shows nothings, but black. And does not allow me to see anythings. Goal pass-through card at this time is the GTX 570. For context I have in the first slot of the MB the GTX 210, then in the Second slot the GTX 570, Then I have a USB 3 card in, and then in the last slow I have the AMD card. The MB is set to grab the GTX 210, and when I boot up Unraid and have monitor attached I can see unraid's initialization on that screen. I will give some information on the system, IOMMU groupings, PCI devices, and diagnostics below. Any help would be great I have tried a number of things that I could think of at this point but am drawing blanks. I have tried installing both on OVMF and SeaBios. I have tried in the Motherboard changing which card is grabed for unraid and it can grab the GTX 570 outputting unraid's initialization screen on the 570, then I tried to see if I could pass through the 210 with no luck not let me get any selected output on the 210. I have followed the steps on Spaceinvaider youtube's channel to grab the ROM from the 570 (same size as ones from techpower up), and linking this in the VM template, but still black screen. Again I appreciate the help. I have given hopefully enough info below to help solve problem. But if not let me know I am very open to trying things and changing things to solve this problem Model: Custom M/B: ASUSTeK COMPUTER INC. - WS C422 PRO_SE CPU: Intel® Xeon® W-2195 CPU @ 2.30GHz HVM: Enabled IOMMU: Enabled Cache: 1152 kB, 18432 kB, 25344 kB Memory: 32 GB Single-bit ECC (max. installable capacity 3072 GB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mb/s, full duplex, mtu 1500 eth1: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.14.49-unRAID x86_64 OpenSSL: 1.0.2o LOG from VM. ErrorWarningSystemArrayLogin 2018-06-20 00:52:10.194+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: RizznetUnraid LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10SeaBios,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Windows 10SeaBios/master-key.aes' -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -m 20480 -realtime mlock=off -smp 20,sockets=1,cores=10,threads=2 -uuid 079a41c0-9c8c-08a1-a4cd-f6611de6b12f -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-Windows 10SeaBios/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive 'file=/mnt/user/domains/Windows 10SeaBios/vdisk1.img,format=raw,if=none,id=dr570.rom -device vfio-pci,host=17:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device vfio-pci,host=b5:00.0,id=hostdev2,bus=pci.0,addr=0x8 -device vfio-pci,host=b6:00.0,id=hostdev3,bus=pci.0,addr=0x9 -device vfio-pci,host=b7:00.0,id=hostdev4,bus=pci.0,addr=0xa -device vfio-pci,host=b8:00.0,id=hostdev5,bus=pci.0,addr=0xb -device usb-host,hostbus=1,hostaddr=3,id=hostdev6,bus=usb.0,port=1 -device usb-host,hostbus=1,hostaddr=5,id=hostdev7,bus=usb.0,port=2 -device usb-host,hostbus=1,hostaddr=4,id=hostdev8,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xc -msg timestamp=on 2018-06-20 00:52:10.194+0000: Domain id=1 is tainted: high-privileges 2018-06-20 00:52:10.194+0000: Domain id=1 is tainted: host-cpu 2018-06-20T00:52:10.246378Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2018-06-20T00:52:56.766790Z qemu-system-x86_64: terminating on signal 15 from pid 19829 (/usr/sbin/libvirtd) 2018-06-20 00:52:58.568+0000: shutting down, reason=destroyed IOMMU group 0: [8086:2020] 00:00.0 Host bridge: Intel Corporation Sky Lake-E DMI3 Registers (rev 04) IOMMU group 1: [8086:2021] 00:04.0 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.1 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.2 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.3 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.4 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.5 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.6 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.7 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) IOMMU group 2: [8086:2024] 00:05.0 System peripheral: Intel Corporation Sky Lake-E MM/Vt-d Configuration Registers (rev 04) [8086:2025] 00:05.2 System peripheral: Intel Corporation Device 2025 (rev 04) [8086:2026] 00:05.4 PIC: Intel Corporation Device 2026 (rev 04) IOMMU group 3: [8086:2014] 00:08.0 System peripheral: Intel Corporation Sky Lake-E Ubox Registers (rev 04) [8086:2015] 00:08.1 Performance counters: Intel Corporation Sky Lake-E Ubox Registers (rev 04) [8086:2016] 00:08.2 System peripheral: Intel Corporation Sky Lake-E Ubox Registers (rev 04) IOMMU group 4: [8086:a2af] 00:14.0 USB controller: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller [8086:a2b1] 00:14.2 Signal processing controller: Intel Corporation 200 Series PCH Thermal Subsystem IOMMU group 5: [8086:a2ba] 00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1 IOMMU group 6: [8086:a282] 00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode] IOMMU group 7: [8086:a2e7] 00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0) IOMMU group 8: [8086:a2e9] 00:1b.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #19 (rev f0) IOMMU group 9: [8086:a2ea] 00:1b.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #20 (rev f0) IOMMU group 10: [8086:a290] 00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0) IOMMU group 11: [8086:a292] 00:1c.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #3 (rev f0) IOMMU group 12: [8086:a293] 00:1c.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #4 (rev f0) IOMMU group 13: [8086:a294] 00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0) IOMMU group 14: [8086:a2d3] 00:1f.0 ISA bridge: Intel Corporation Device a2d3 [8086:a2a1] 00:1f.2 Memory controller: Intel Corporation 200 Series PCH PMC [8086:a2f0] 00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio [8086:a2a3] 00:1f.4 SMBus: Intel Corporation 200 Series PCH SMBus Controller IOMMU group 15: [1b21:2142] 02:00.0 USB controller: ASMedia Technology Inc. Device 2142 IOMMU group 16: [1a03:1150] 03:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 04) [1a03:2000] 04:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41) IOMMU group 17: [1b21:2142] 05:00.0 USB controller: ASMedia Technology Inc. Device 2142 IOMMU group 18: [8086:1533] 06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 19: [8086:1533] 07:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 20: [8086:2030] 16:00.0 PCI bridge: Intel Corporation Sky Lake-E PCI Express Root Port A (rev 04) IOMMU group 21: [8086:2034] 16:05.0 System peripheral: Intel Corporation Device 2034 (rev 04) [8086:2035] 16:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04) [8086:2036] 16:05.4 PIC: Intel Corporation Device 2036 (rev 04) IOMMU group 22: [8086:208d] 16:08.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.4 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.5 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.6 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.7 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 23: [8086:208d] 16:09.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.4 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.5 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.6 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.7 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 24: [8086:208d] 16:0a.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:0a.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 25: [8086:208e] 16:0e.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.4 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.5 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.6 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.7 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 26: [8086:208e] 16:0f.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.4 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.5 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.6 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.7 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 27: [8086:208e] 16:10.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:10.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 28: [8086:2054] 16:1d.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:2055] 16:1d.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:2056] 16:1d.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:2057] 16:1d.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 29: [8086:2080] 16:1e.0 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2081] 16:1e.1 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2082] 16:1e.2 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2083] 16:1e.3 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2084] 16:1e.4 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2085] 16:1e.5 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2086] 16:1e.6 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) IOMMU group 30: [10de:1081] 17:00.0 VGA compatible controller: NVIDIA Corporation GF110 [GeForce GTX 570] (rev a1) [10de:0e09] 17:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1) IOMMU group 31: [8086:2030] 64:00.0 PCI bridge: Intel Corporation Sky Lake-E PCI Express Root Port A (rev 04) IOMMU group 32: [8086:2034] 64:05.0 System peripheral: Intel Corporation Device 2034 (rev 04) [8086:2035] 64:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04) [8086:2036] 64:05.4 PIC: Intel Corporation Device 2036 (rev 04) IOMMU group 33: [8086:2066] 64:08.0 System peripheral: Intel Corporation Device 2066 (rev 04) IOMMU group 34: [8086:2066] 64:09.0 System peripheral: Intel Corporation Device 2066 (rev 04) IOMMU group 35: [8086:2040] 64:0a.0 System peripheral: Intel Corporation Device 2040 (rev 04) [8086:2041] 64:0a.1 System peripheral: Intel Corporation Device 2041 (rev 04) [8086:2042] 64:0a.2 System peripheral: Intel Corporation Device 2042 (rev 04) [8086:2043] 64:0a.3 System peripheral: Intel Corporation Device 2043 (rev 04) [8086:2044] 64:0a.4 System peripheral: Intel Corporation Device 2044 (rev 04) [8086:2045] 64:0a.5 System peripheral: Intel Corporation Device 2045 (rev 04) [8086:2046] 64:0a.6 System peripheral: Intel Corporation Device 2046 (rev 04) [8086:2047] 64:0a.7 System peripheral: Intel Corporation Device 2047 (rev 04) IOMMU group 36: [8086:2048] 64:0b.0 System peripheral: Intel Corporation Device 2048 (rev 04) [8086:2049] 64:0b.1 System peripheral: Intel Corporation Device 2049 (rev 04) [8086:204a] 64:0b.2 System peripheral: Intel Corporation Device 204a (rev 04) [8086:204b] 64:0b.3 System peripheral: Intel Corporation Device 204b (rev 04) IOMMU group 37: [8086:2040] 64:0c.0 System peripheral: Intel Corporation Device 2040 (rev 04) [8086:2041] 64:0c.1 System peripheral: Intel Corporation Device 2041 (rev 04) [8086:2042] 64:0c.2 System peripheral: Intel Corporation Device 2042 (rev 04) [8086:2043] 64:0c.3 System peripheral: Intel Corporation Device 2043 (rev 04) [8086:2044] 64:0c.4 System peripheral: Intel Corporation Device 2044 (rev 04) [8086:2045] 64:0c.5 System peripheral: Intel Corporation Device 2045 (rev 04) [8086:2046] 64:0c.6 System peripheral: Intel Corporation Device 2046 (rev 04) [8086:2047] 64:0c.7 System peripheral: Intel Corporation Device 2047 (rev 04) IOMMU group 38: [8086:2048] 64:0d.0 System peripheral: Intel Corporation Device 2048 (rev 04) [8086:2049] 64:0d.1 System peripheral: Intel Corporation Device 2049 (rev 04) [8086:204a] 64:0d.2 System peripheral: Intel Corporation Device 204a (rev 04) [8086:204b] 64:0d.3 System peripheral: Intel Corporation Device 204b (rev 04) IOMMU group 39: [10de:0a65] 65:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) [10de:0be3] 65:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) IOMMU group 40: [8086:2030] b2:00.0 PCI bridge: Intel Corporation Sky Lake-E PCI Express Root Port A (rev 04) IOMMU group 41: [8086:2032] b2:02.0 PCI bridge: Intel Corporation Sky Lake-E PCI Express Root Port C (rev 04) IOMMU group 42: [8086:2034] b2:05.0 System peripheral: Intel Corporation Device 2034 (rev 04) [8086:2035] b2:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04) [8086:2036] b2:05.4 PIC: Intel Corporation Device 2036 (rev 04) IOMMU group 43: [8086:204c] b2:12.0 Performance counters: Intel Corporation Sky Lake-E M3KTI Registers (rev 04) [8086:204d] b2:12.1 Performance counters: Intel Corporation Sky Lake-E M3KTI Registers (rev 04) [8086:204e] b2:12.2 System peripheral: Intel Corporation Sky Lake-E M3KTI Registers (rev 04) IOMMU group 44: [8086:2018] b2:15.0 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04) IOMMU group 45: [8086:2018] b2:16.0 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04) [8086:2018] b2:16.4 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04) IOMMU group 46: [8086:2018] b2:17.0 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04) IOMMU group 47: [10b5:8608] b3:00.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) IOMMU group 48: [10b5:8608] b4:01.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) IOMMU group 49: [10b5:8608] b4:05.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) IOMMU group 50: [10b5:8608] b4:07.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) IOMMU group 51: [10b5:8608] b4:09.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) IOMMU group 52: [1b73:1100] b5:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) IOMMU group 53: [1b73:1100] b6:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) IOMMU group 54: [1b73:1100] b7:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) IOMMU group 55: [1b73:1100] b8:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) IOMMU group 56: [1002:9440] b9:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:aa30] b9:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV770 HDMI Audio [Radeon HD 4850/4870] CPU Thread Pairings Pair 1: cpu 0 / cpu 18 Pair 2: cpu 1 / cpu 19 Pair 3: cpu 2 / cpu 20 Pair 4: cpu 3 / cpu 21 Pair 5: cpu 4 / cpu 22 Pair 6: cpu 5 / cpu 23 Pair 7: cpu 6 / cpu 24 Pair 8: cpu 7 / cpu 25 Pair 9: cpu 8 / cpu 26 Pair 10: cpu 9 / cpu 27 Pair 11: cpu 10 / cpu 28 Pair 12: cpu 11 / cpu 29 Pair 13: cpu 12 / cpu 30 Pair 14: cpu 13 / cpu 31 Pair 15: cpu 14 / cpu 32 Pair 16: cpu 15 / cpu 33 Pair 17: cpu 16 / cpu 34 Pair 18: cpu 17 / cpu 35   USB Devices Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 003: ID 046d:c07d Logitech, Inc. G502 Mouse Bus 001 Device 004: ID 1b1c:1b02 Corsair Bus 001 Device 005: ID 1b1c:0c12 Corsair Bus 001 Device 006: ID 0781:5575 SanDisk Corp. Cruzer Glide Bus 001 Device 007: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 008: ID 046d:c054 Logitech, Inc. Bluetooth mini-receiver Bus 001 Device 009: ID 04f2:0760 Chicony Electronics Co., Ltd Acer KU-0760 Keyboard Bus 001 Device 010: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 011: ID 0b05:1867 ASUSTek Computer, Inc. Bus 001 Device 012: ID 046b:ff20 American Megatrends, Inc. Bus 001 Device 013: ID 046b:ff40 American Megatrends, Inc. Bus 001 Device 014: ID 046b:ff31 American Megatrends, Inc. Bus 001 Device 015: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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 Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub SCSI Devices [0:0:0:0] disk SanDisk Cruzer Glide 1.27 /dev/sda 8.00GB [1:0:0:0] cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 - [2:0:0:0] disk AMI Virtual Floppy0 1.00 /dev/sdb - [3:0:0:0] disk AMI Virtual HDisk0 1.00 /dev/sdc - [3:0:0:1] disk AMI Virtual HDisk1 1.00 /dev/sdd - [4:0:0:0] disk ATA ST12000VN0007-2G SC60 /dev/sde 12.0TB [5:0:0:0] disk ATA ST12000VN0007-2G SC60 /dev/sdf 12.0TB [6:0:0:0] disk ATA Samsung SSD 840 DB6Q /dev/sdg 1.00TB [7:0:0:0] disk ATA Samsung SSD 860 1B6Q /dev/sdh 1.00TB [8:0:0:0] disk ATA ST12000VN0007-2G SC60 /dev/sdi 12.0TB [9:0:0:0] disk ATA ST12000VN0007-2G SC60 /dev/sdj 12.0TB  XML <domain type='kvm'> <name>Windows 10SeaBios</name> <uuid>079a41c0-9c8c-08a1-a4cd-f6611de6b12f</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>20971520</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>20</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='19'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='20'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='21'/> <vcpupin vcpu='6' cpuset='4'/> <vcpupin vcpu='7' cpuset='22'/> <vcpupin vcpu='8' cpuset='5'/> <vcpupin vcpu='9' cpuset='23'/> <vcpupin vcpu='10' cpuset='6'/> <vcpupin vcpu='11' cpuset='24'/> <vcpupin vcpu='12' cpuset='7'/> <vcpupin vcpu='13' cpuset='25'/> <vcpupin vcpu='14' cpuset='8'/> <vcpupin vcpu='15' cpuset='26'/> <vcpupin vcpu='16' cpuset='9'/> <vcpupin vcpu='17' cpuset='27'/> <vcpupin vcpu='18' cpuset='10'/> <vcpupin vcpu='19' cpuset='28'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type> </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='10' threads='2'/> </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/user/domains/Windows 10SeaBios/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows 10 Iso/Windows.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <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.141-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:b8:e6:73'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <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='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x17' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/gtx570.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x17' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0xb5' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0xb6' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0xb7' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0xb8' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc07d'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x0c12'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x1b02'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </memballoon> </devices></domain> rizznetunraid-diagnostics-20180621-1936.zip

did you ever figure this out. I am having same problem

did you ever figure this out. I am having same problem

<domain type='kvm'> <name>Windows 10SeaBios</name> <uuid>079a41c0-9c8c-08a1-a4cd-f6611de6b12f</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>20971520</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>20</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='19'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='20'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='21'/> <vcpupin vcpu='6' cpuset='4'/> <vcpupin vcpu='7' cpuset='22'/> <vcpupin vcpu='8' cpuset='5'/> <vcpupin vcpu='9' cpuset='23'/> <vcpupin vcpu='10' cpuset='6'/> <vcpupin vcpu='11' cpuset='24'/> <vcpupin vcpu='12' cpuset='7'/> <vcpupin vcpu='13' cpuset='25'/> <vcpupin vcpu='14' cpuset='8'/> <vcpupin vcpu='15' cpuset='26'/> <vcpupin vcpu='16' cpuset='9'/> <vcpupin vcpu='17' cpuset='27'/> <vcpupin vcpu='18' cpuset='10'/> <vcpupin vcpu='19' cpuset='28'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type> </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='10' threads='2'/> </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/user/domains/Windows 10SeaBios/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows 10 Iso/Windows.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <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.141-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:b8:e6:73'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <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='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x17' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/gtx570.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x17' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0xb5' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0xb6' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0xb7' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0xb8' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc07d'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x0c12'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x1b02'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </memballoon> </devices> </domain>

Hi all, thanks in advance for the help in trying to solve my problem. I am not sure where to go next. I have recently put together Unraid build and am now trying to get Windows 10 VM up and running. I have been able to get it up and running with VNC, but when I try to change to dedicated graphics card for pass through My screen shows nothings, but black. And does not allow me to see anythings. Goal pass-through card at this time is the GTX 570. For context I have in the first slot of the MB the GTX 210, then in the Second slot the GTX 570, Then I have a USB 3 card in, and then in the last slow I have the AMD card. The MB is set to grab the GTX 210, and when I boot up Unraid and have monitor attached I can see unraid's initialization on that screen. I will give some information on the system, IOMMU groupings, PCI devices, and diagnostics below. Any help would be great I have tried a number of things that I could think of at this point but am drawing blanks. I have tried installing both on OVMF and SeaBios. I have tried in the Motherboard changing which card is grabed for unraid and it can grab the GTX 570 outputting unraid's initialization screen on the 570, then I tried to see if I could pass through the 210 with no luck not let me get any selected output on the 210. I have followed the steps on Spaceinvaider youtube's channel to grab the ROM from the 570 (same size as ones from techpower up), and linking this in the VM template, but still black screen. Again I appreciate the help. Model: Custom M/B: ASUSTeK COMPUTER INC. - WS C422 PRO_SE CPU: Intel® Xeon® W-2195 CPU @ 2.30GHz HVM: Enabled IOMMU: Enabled Cache: 1152 kB, 18432 kB, 25344 kB Memory: 32 GB Single-bit ECC (max. installable capacity 3072 GB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mb/s, full duplex, mtu 1500 eth1: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.14.49-unRAID x86_64 OpenSSL: 1.0.2o LOG from VM. ErrorWarningSystemArrayLogin 2018-06-20 00:52:10.194+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: RizznetUnraid LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10SeaBios,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Windows 10SeaBios/master-key.aes' -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -m 20480 -realtime mlock=off -smp 20,sockets=1,cores=10,threads=2 -uuid 079a41c0-9c8c-08a1-a4cd-f6611de6b12f -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-Windows 10SeaBios/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive 'file=/mnt/user/domains/Windows 10SeaBios/vdisk1.img,format=raw,if=none,id=dr570.rom -device vfio-pci,host=17:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device vfio-pci,host=b5:00.0,id=hostdev2,bus=pci.0,addr=0x8 -device vfio-pci,host=b6:00.0,id=hostdev3,bus=pci.0,addr=0x9 -device vfio-pci,host=b7:00.0,id=hostdev4,bus=pci.0,addr=0xa -device vfio-pci,host=b8:00.0,id=hostdev5,bus=pci.0,addr=0xb -device usb-host,hostbus=1,hostaddr=3,id=hostdev6,bus=usb.0,port=1 -device usb-host,hostbus=1,hostaddr=5,id=hostdev7,bus=usb.0,port=2 -device usb-host,hostbus=1,hostaddr=4,id=hostdev8,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xc -msg timestamp=on 2018-06-20 00:52:10.194+0000: Domain id=1 is tainted: high-privileges 2018-06-20 00:52:10.194+0000: Domain id=1 is tainted: host-cpu 2018-06-20T00:52:10.246378Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2018-06-20T00:52:56.766790Z qemu-system-x86_64: terminating on signal 15 from pid 19829 (/usr/sbin/libvirtd) 2018-06-20 00:52:58.568+0000: shutting down, reason=destroyed IOMMU group 0: [8086:2020] 00:00.0 Host bridge: Intel Corporation Sky Lake-E DMI3 Registers (rev 04) IOMMU group 1: [8086:2021] 00:04.0 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.1 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.2 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.3 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.4 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.5 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.6 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) [8086:2021] 00:04.7 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) IOMMU group 2: [8086:2024] 00:05.0 System peripheral: Intel Corporation Sky Lake-E MM/Vt-d Configuration Registers (rev 04) [8086:2025] 00:05.2 System peripheral: Intel Corporation Device 2025 (rev 04) [8086:2026] 00:05.4 PIC: Intel Corporation Device 2026 (rev 04) IOMMU group 3: [8086:2014] 00:08.0 System peripheral: Intel Corporation Sky Lake-E Ubox Registers (rev 04) [8086:2015] 00:08.1 Performance counters: Intel Corporation Sky Lake-E Ubox Registers (rev 04) [8086:2016] 00:08.2 System peripheral: Intel Corporation Sky Lake-E Ubox Registers (rev 04) IOMMU group 4: [8086:a2af] 00:14.0 USB controller: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller [8086:a2b1] 00:14.2 Signal processing controller: Intel Corporation 200 Series PCH Thermal Subsystem IOMMU group 5: [8086:a2ba] 00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1 IOMMU group 6: [8086:a282] 00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode] IOMMU group 7: [8086:a2e7] 00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0) IOMMU group 8: [8086:a2e9] 00:1b.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #19 (rev f0) IOMMU group 9: [8086:a2ea] 00:1b.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #20 (rev f0) IOMMU group 10: [8086:a290] 00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0) IOMMU group 11: [8086:a292] 00:1c.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #3 (rev f0) IOMMU group 12: [8086:a293] 00:1c.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #4 (rev f0) IOMMU group 13: [8086:a294] 00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0) IOMMU group 14: [8086:a2d3] 00:1f.0 ISA bridge: Intel Corporation Device a2d3 [8086:a2a1] 00:1f.2 Memory controller: Intel Corporation 200 Series PCH PMC [8086:a2f0] 00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio [8086:a2a3] 00:1f.4 SMBus: Intel Corporation 200 Series PCH SMBus Controller IOMMU group 15: [1b21:2142] 02:00.0 USB controller: ASMedia Technology Inc. Device 2142 IOMMU group 16: [1a03:1150] 03:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 04) [1a03:2000] 04:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41) IOMMU group 17: [1b21:2142] 05:00.0 USB controller: ASMedia Technology Inc. Device 2142 IOMMU group 18: [8086:1533] 06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 19: [8086:1533] 07:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 20: [8086:2030] 16:00.0 PCI bridge: Intel Corporation Sky Lake-E PCI Express Root Port A (rev 04) IOMMU group 21: [8086:2034] 16:05.0 System peripheral: Intel Corporation Device 2034 (rev 04) [8086:2035] 16:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04) [8086:2036] 16:05.4 PIC: Intel Corporation Device 2036 (rev 04) IOMMU group 22: [8086:208d] 16:08.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.4 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.5 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.6 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:08.7 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 23: [8086:208d] 16:09.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.4 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.5 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.6 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:09.7 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 24: [8086:208d] 16:0a.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208d] 16:0a.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 25: [8086:208e] 16:0e.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.4 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.5 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.6 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0e.7 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 26: [8086:208e] 16:0f.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.4 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.5 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.6 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:0f.7 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 27: [8086:208e] 16:10.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:208e] 16:10.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 28: [8086:2054] 16:1d.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:2055] 16:1d.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:2056] 16:1d.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) [8086:2057] 16:1d.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) IOMMU group 29: [8086:2080] 16:1e.0 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2081] 16:1e.1 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2082] 16:1e.2 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2083] 16:1e.3 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2084] 16:1e.4 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2085] 16:1e.5 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) [8086:2086] 16:1e.6 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) IOMMU group 30: [10de:1081] 17:00.0 VGA compatible controller: NVIDIA Corporation GF110 [GeForce GTX 570] (rev a1) [10de:0e09] 17:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1) IOMMU group 31: [8086:2030] 64:00.0 PCI bridge: Intel Corporation Sky Lake-E PCI Express Root Port A (rev 04) IOMMU group 32: [8086:2034] 64:05.0 System peripheral: Intel Corporation Device 2034 (rev 04) [8086:2035] 64:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04) [8086:2036] 64:05.4 PIC: Intel Corporation Device 2036 (rev 04) IOMMU group 33: [8086:2066] 64:08.0 System peripheral: Intel Corporation Device 2066 (rev 04) IOMMU group 34: [8086:2066] 64:09.0 System peripheral: Intel Corporation Device 2066 (rev 04) IOMMU group 35: [8086:2040] 64:0a.0 System peripheral: Intel Corporation Device 2040 (rev 04) [8086:2041] 64:0a.1 System peripheral: Intel Corporation Device 2041 (rev 04) [8086:2042] 64:0a.2 System peripheral: Intel Corporation Device 2042 (rev 04) [8086:2043] 64:0a.3 System peripheral: Intel Corporation Device 2043 (rev 04) [8086:2044] 64:0a.4 System peripheral: Intel Corporation Device 2044 (rev 04) [8086:2045] 64:0a.5 System peripheral: Intel Corporation Device 2045 (rev 04) [8086:2046] 64:0a.6 System peripheral: Intel Corporation Device 2046 (rev 04) [8086:2047] 64:0a.7 System peripheral: Intel Corporation Device 2047 (rev 04) IOMMU group 36: [8086:2048] 64:0b.0 System peripheral: Intel Corporation Device 2048 (rev 04) [8086:2049] 64:0b.1 System peripheral: Intel Corporation Device 2049 (rev 04) [8086:204a] 64:0b.2 System peripheral: Intel Corporation Device 204a (rev 04) [8086:204b] 64:0b.3 System peripheral: Intel Corporation Device 204b (rev 04) IOMMU group 37: [8086:2040] 64:0c.0 System peripheral: Intel Corporation Device 2040 (rev 04) [8086:2041] 64:0c.1 System peripheral: Intel Corporation Device 2041 (rev 04) [8086:2042] 64:0c.2 System peripheral: Intel Corporation Device 2042 (rev 04) [8086:2043] 64:0c.3 System peripheral: Intel Corporation Device 2043 (rev 04) [8086:2044] 64:0c.4 System peripheral: Intel Corporation Device 2044 (rev 04) [8086:2045] 64:0c.5 System peripheral: Intel Corporation Device 2045 (rev 04) [8086:2046] 64:0c.6 System peripheral: Intel Corporation Device 2046 (rev 04) [8086:2047] 64:0c.7 System peripheral: Intel Corporation Device 2047 (rev 04) IOMMU group 38: [8086:2048] 64:0d.0 System peripheral: Intel Corporation Device 2048 (rev 04) [8086:2049] 64:0d.1 System peripheral: Intel Corporation Device 2049 (rev 04) [8086:204a] 64:0d.2 System peripheral: Intel Corporation Device 204a (rev 04) [8086:204b] 64:0d.3 System peripheral: Intel Corporation Device 204b (rev 04) IOMMU group 39: [10de:0a65] 65:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) [10de:0be3] 65:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) IOMMU group 40: [8086:2030] b2:00.0 PCI bridge: Intel Corporation Sky Lake-E PCI Express Root Port A (rev 04) IOMMU group 41: [8086:2032] b2:02.0 PCI bridge: Intel Corporation Sky Lake-E PCI Express Root Port C (rev 04) IOMMU group 42: [8086:2034] b2:05.0 System peripheral: Intel Corporation Device 2034 (rev 04) [8086:2035] b2:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04) [8086:2036] b2:05.4 PIC: Intel Corporation Device 2036 (rev 04) IOMMU group 43: [8086:204c] b2:12.0 Performance counters: Intel Corporation Sky Lake-E M3KTI Registers (rev 04) [8086:204d] b2:12.1 Performance counters: Intel Corporation Sky Lake-E M3KTI Registers (rev 04) [8086:204e] b2:12.2 System peripheral: Intel Corporation Sky Lake-E M3KTI Registers (rev 04) IOMMU group 44: [8086:2018] b2:15.0 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04) IOMMU group 45: [8086:2018] b2:16.0 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04) [8086:2018] b2:16.4 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04) IOMMU group 46: [8086:2018] b2:17.0 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04) IOMMU group 47: [10b5:8608] b3:00.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) IOMMU group 48: [10b5:8608] b4:01.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) IOMMU group 49: [10b5:8608] b4:05.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) IOMMU group 50: [10b5:8608] b4:07.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) IOMMU group 51: [10b5:8608] b4:09.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) IOMMU group 52: [1b73:1100] b5:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) IOMMU group 53: [1b73:1100] b6:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) IOMMU group 54: [1b73:1100] b7:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) IOMMU group 55: [1b73:1100] b8:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) IOMMU group 56: [1002:9440] b9:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:aa30] b9:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV770 HDMI Audio [Radeon HD 4850/4870] CPU Thread Pairings Pair 1: cpu 0 / cpu 18 Pair 2: cpu 1 / cpu 19 Pair 3: cpu 2 / cpu 20 Pair 4: cpu 3 / cpu 21 Pair 5: cpu 4 / cpu 22 Pair 6: cpu 5 / cpu 23 Pair 7: cpu 6 / cpu 24 Pair 8: cpu 7 / cpu 25 Pair 9: cpu 8 / cpu 26 Pair 10: cpu 9 / cpu 27 Pair 11: cpu 10 / cpu 28 Pair 12: cpu 11 / cpu 29 Pair 13: cpu 12 / cpu 30 Pair 14: cpu 13 / cpu 31 Pair 15: cpu 14 / cpu 32 Pair 16: cpu 15 / cpu 33 Pair 17: cpu 16 / cpu 34 Pair 18: cpu 17 / cpu 35 USB Devices Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 003: ID 046d:c07d Logitech, Inc. G502 Mouse Bus 001 Device 004: ID 1b1c:1b02 Corsair Bus 001 Device 005: ID 1b1c:0c12 Corsair Bus 001 Device 006: ID 0781:5575 SanDisk Corp. Cruzer Glide Bus 001 Device 007: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 008: ID 046d:c054 Logitech, Inc. Bluetooth mini-receiver Bus 001 Device 009: ID 04f2:0760 Chicony Electronics Co., Ltd Acer KU-0760 Keyboard Bus 001 Device 010: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 011: ID 0b05:1867 ASUSTek Computer, Inc. Bus 001 Device 012: ID 046b:ff20 American Megatrends, Inc. Bus 001 Device 013: ID 046b:ff40 American Megatrends, Inc. Bus 001 Device 014: ID 046b:ff31 American Megatrends, Inc. Bus 001 Device 015: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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 Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub SCSI Devices [0:0:0:0] disk SanDisk Cruzer Glide 1.27 /dev/sda 8.00GB [1:0:0:0] cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 - [2:0:0:0] disk AMI Virtual Floppy0 1.00 /dev/sdb - [3:0:0:0] disk AMI Virtual HDisk0 1.00 /dev/sdc - [3:0:0:1] disk AMI Virtual HDisk1 1.00 /dev/sdd - [4:0:0:0] disk ATA ST12000VN0007-2G SC60 /dev/sde 12.0TB [5:0:0:0] disk ATA ST12000VN0007-2G SC60 /dev/sdf 12.0TB [6:0:0:0] disk ATA Samsung SSD 840 DB6Q /dev/sdg 1.00TB [7:0:0:0] disk ATA Samsung SSD 860 1B6Q /dev/sdh 1.00TB [8:0:0:0] disk ATA ST12000VN0007-2G SC60 /dev/sdi 12.0TB [9:0:0:0] disk ATA ST12000VN0007-2G SC60 /dev/sdj 12.0TB rizznetunraid-diagnostics-20180619-1757.zip

Wondering in the old SB version to correctly copy data onto the array you would want to go under UNRAID then user then shares. In this new one just wondering as I don't see the same path but there is a path for media that then had all my created shares in it is this going to correctly use the array? And sorry if stupid question just new to unraid

Hi thanks that is great to know.

Thanks for letting me know. Let me know how the swab up goes