TurboMyPC

UnRaid started auto-detecting the GPU now. That's convenient. However, when passing through to windows, or ubuntu as primary GPU, i just get a jumbled color splash screen looping and the VM won't boot. However, it does work as a secondary GPU in ubuntu (working), and detected in windows (but display driver issues)

To passthrough the PCI x1 device; 00:1c.5 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #6 (rev d5) Would I use the following code? <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1c' function='0x5'/> </source> <address type='pci' domain='0x0000' bus='0x01(NEXTBus#available)' slot='0x00' function='0x0'/> </hostdev> omitting the () note.

I am successfully passing through 4 x16 GPUs (filling all x16 ports). I'd like to use the additional 3 x1 ports to pass-through GPUs on risers as well. Is it possible to use a mining type x1 > USB > x16 riser adapter to pass-through a GPU to a VM? UnRaid is not detecting the device as a GPU, but depending on the x1 port used, one of the following; 00:1c.5 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #6 (rev d5) 00:1c.6 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #7 (rev d5) 00:1c.7 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #8 (rev d5) Should i start with manually using the XML file to pass-through this device?

I had it plugged into the BIOS port, which looks like it may have been part of my 3.1 USB hub. I thought i was in trouble, because the only pure 2.0 ports are on the motherboard header. However, it's now working fine in the 3.0/2.0 hub instead of the 3.1. The strange thing is that it never gave me issues in this port until now. Marking as Solved, Thank you all! Chipset+Intel® USB 3.1 controller: 1 x USB Type-C™ port on the back panel, with USB 3.1 support 1 x USB 3.1 Type-A port (red) on the back panel Chipset+2 Renesas® USB 3.0 Hubs: 8 x USB 3.0/2.0 ports (4 ports on the back panel, 4 ports available through the internal USB headers) Chipset: 2 x USB 3.0/2.0 ports on the back panel 4 x USB 2.0/1.1 ports available through the internal USB headers

I will try the df next. I attached the diagnostics in OP ^. I did a lsblk and it appeared to be attached, but not mounted. Windows just scanned without finding any problems (no further action required).

Good catch. It was saving to /boot/logs and didn't persist on the USB key. I've been attempting to copy it for about an hour so far with no luck. Last attempt i uploaded it to a seperate mounted USB key, but now i cannot open the archive on windows (access denied), extract (no archives found). I didn't unmount, but i did poweroff - so i'll try that tomorrow.

I attempted the 6.6 upgrade from 6.5.3, it failed with a (corrupt? check USB) error. After this error I could no longer see my VMs or docker info in the web GUI. Next, I assumed I could gracefully shut everything down, and try again. Except when i booted back up, i can no longer get an IP address. I get a 169.x. The MAC address is different than it used to be. I think I had an eth0 before, but now i only see br0 and lo. I did not try turning off autostart VMs yet, how can i set this in the cfg? If we can get back up on either version i'll be happy, but i'm not sure how to do a 'restore' while keeping my VM and docker configs. Other weird things; root login on the local console doesn't ask for my root password. attempted to turn off docker on startup DOCKER_ENABLED="no", same results. Not my switch / router: I used a completely different switch using the same cables, with the same results. Used an ubuntu boot CD on same hardware and got a good ip address, and saw all hardware attached. Not disk failure; USB key is viewable and editable on windows. Primary Unraid SSD is readable in ubuntu boot CD environment. Not the USB key config; I restored the USB key configs back to a previous backup, and i get the same 169.x address. I ran a check disk in windows to verify it's not corrupt. I'm at a loss here, and even though I've been using unraid for about a year - i feel like i'm new to managing unraid. What can i do next?

I'll +1 this. I could use this feature in the GUI. This is the 2nd most viewed request on feature request.