makin

Hi everyone, back in 2022 I reported an issue with my Debian VM with GPU Passthrough leading to network hanging which I could more or less resolve by putting the VM into its own VLAN. Stupid, but case closed. Two weeks ago a seemingly new issue evolved: My Unifi WiFi cameras kept randomly disconnecting and reconnecting and devices in my home have severe troubles with connectivity and the worst thing being trouble with my wife that is working from home and suffers dropping connections. 😅 How could this be connected to each other, right? I opened a support ticket with Unifi, asked around in their subreddit... Now... Desperate times called for desperate measures. As soon as I stopped the VM (a Windows VM replaced the old Debian VM), all the issues magically disappeared. So no more doubts. Something's seriously wrong here. Do you guys have any ideas how to troubleshoot or solve the issue?

Hi again, I finally took the time to restart the server and the flash seems to be fine so everything got back to normal. However, when tried to update again, it happened the way before... plugin: run failed: /bin/bash retval: 1 After restarting the flash could be backed up flawlessly and now... well... here I am again.

Can you tell me which settings I will lose? How about VMs, Dockers etc.?

Hi itimpi, thanks for answering. Unfortunately my last backup is from before changing slots of the disks so I do not have a backup. Did not make it to activate MyServers which I always wanted for exactly that reason... I thought that the CA Backup app would backup the flash but it did not...

Hi guys, I was just trying to update Unraid and during the update I received the message that my flash is either corrupted or offline. I attached the diagnostics file as I was told in the error message. The main dashboard is also cluttered with error messages like: Warning: file_put_contents(/boot/config/plugins/parity.check.tuning/parity.check.tuning.manual): failed to open stream: No such file or directory in or Warning: parse_ini_file(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 52 Warning: array_replace_recursive(): Expected parameter 2 to be an array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 52 Warning: parse_ini_file(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/include/libvirt_helpers.php on line 507 Not sure what to do know... All my dockers seem to be online but the Docker tab disappeared from the Unraid menu. When trying to backup my flash drive I am forwareded to a "NOT FOUND" site. SSH'ing on the server, I receive the following for the boot folder... boot# ls -al total 32 drwx------ 10 root root 32768 Jan 1 1970 ./ drwxr-xr-x 20 root root 440 Nov 20 14:40 ../ gravity-diagnostics-20221120-1440.zip

Hi everyone, I am currently facing a critical issue with my Unraid server's network hanging for reasons I don’t know. Physically reconnecting or disabling/enabling the port on my UniFi switch brings the server back online. I used to have this issue when my Debian VM with GPU passthrough was running. Plugging the ethernet cable in and out solves the issue for the next few minutes. With the VM being shut down, the server remained accessible. (I have created a thread on that in the past) I assumed that there was some network storming caused by the VM and to troubleshoot I created a new VLAN in which only the VM is running (managed by my UniFi UDM Pro). The server has not become inaccessible since then until yesterday. But this time not due to my GPU passthrough VM but rather due to the ZWaveJS2MQTT Docker. I checked my Home Assistant VM as I can see when devices (the network) became unavailable. The last two times were in the following timespans: Offline 8:46 - 8:58 Online in between Offline 9:59 - 10:13 I have not touched the port settings or the cable itself. It became available again on its own - just to say bye bye again shortly after. 😞 I can't find anything in dmesg nor in the syslog: dmesg -T: [Thu May 19 08:33:58 2022] usb 1-1.4: new full-speed USB device number 5 using xhci_hcd [Thu May 19 08:33:58 2022] usb 1-1.4: device descriptor read/64, error -32 [Thu May 19 08:33:58 2022] usb 1-1.4: device descriptor read/64, error -32 [Thu May 19 08:33:58 2022] usb 1-1.4: new full-speed USB device number 6 using xhci_hcd [Thu May 19 08:33:59 2022] usb 1-1.4: device descriptor read/64, error -32 [Thu May 19 08:33:59 2022] usb 1-1.4: device descriptor read/64, error -32 [Thu May 19 08:33:59 2022] usb 1-1-port4: attempt power cycle [Thu May 19 08:34:00 2022] usb 1-1.4: new full-speed USB device number 7 using xhci_hcd [Thu May 19 08:34:00 2022] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device [Thu May 19 08:34:59 2022] eth0: renamed from vethf1123ae [Thu May 19 09:51:56 2022] usb 3-4.4: new full-speed USB device number 4 using xhci_hcd [Thu May 19 09:51:57 2022] cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device [Thu May 19 09:52:00 2022] usb 3-4.4: USB disconnect, device number 4 [Thu May 19 09:52:00 2022] usb 3-4.4: new full-speed USB device number 5 using xhci_hcd [Thu May 19 09:52:00 2022] cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device [Thu May 19 09:53:52 2022] veth97f0b8f: renamed from eth0 [Thu May 19 09:53:52 2022] docker0: port 3(vethf6f1318) entered disabled state [Thu May 19 09:53:53 2022] docker0: port 3(vethf6f1318) entered disabled state [Thu May 19 09:53:53 2022] device vethf6f1318 left promiscuous mode [Thu May 19 09:53:53 2022] docker0: port 3(vethf6f1318) entered disabled state [Thu May 19 09:53:54 2022] docker0: port 3(veth1c69dab) entered blocking state [Thu May 19 09:53:54 2022] docker0: port 3(veth1c69dab) entered disabled state [Thu May 19 09:53:54 2022] device veth1c69dab entered promiscuous mode [Thu May 19 09:53:54 2022] docker0: port 3(veth1c69dab) entered blocking state [Thu May 19 09:53:54 2022] docker0: port 3(veth1c69dab) entered forwarding state [Thu May 19 09:53:54 2022] docker0: port 3(veth1c69dab) entered disabled state [Thu May 19 09:53:56 2022] eth0: renamed from vethaefd029 [Thu May 19 09:53:56 2022] IPv6: ADDRCONF(NETDEV_CHANGE): veth1c69dab: link becomes ready [Thu May 19 09:53:56 2022] docker0: port 3(veth1c69dab) entered blocking state [Thu May 19 09:53:56 2022] docker0: port 3(veth1c69dab) entered forwarding state [Thu May 19 10:51:49 2022] usb 3-4.4: USB disconnect, device number 5 [Thu May 19 10:51:50 2022] usb 3-4.4: new full-speed USB device number 6 using xhci_hcd [Thu May 19 10:51:50 2022] cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device [Thu May 19 10:51:53 2022] usb 3-4.4: USB disconnect, device number 6 [Thu May 19 10:51:53 2022] usb 3-4.4: new full-speed USB device number 7 using xhci_hcd [Thu May 19 10:51:54 2022] cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device cat /var/log/syslog: May 19 08:34:59 GRAViTY kernel: eth0: renamed from vethf1123ae May 19 08:59:05 GRAViTY vsftpd[19965]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:05 GRAViTY vsftpd[19965]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:05 GRAViTY vsftpd[19969]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:05 GRAViTY vsftpd[19969]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:22 GRAViTY vsftpd[20033]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:22 GRAViTY vsftpd[20033]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:22 GRAViTY vsftpd[20038]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:22 GRAViTY vsftpd[20038]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:22 GRAViTY vsftpd[20044]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:22 GRAViTY vsftpd[20044]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:22 GRAViTY vsftpd[20047]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:22 GRAViTY vsftpd[20047]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:22 GRAViTY vsftpd[20053]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:22 GRAViTY vsftpd[20053]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:23 GRAViTY vsftpd[20056]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:23 GRAViTY vsftpd[20056]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:23 GRAViTY vsftpd[20059]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:23 GRAViTY vsftpd[20059]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:23 GRAViTY vsftpd[20070]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:23 GRAViTY vsftpd[20070]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:23 GRAViTY vsftpd[20073]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:23 GRAViTY vsftpd[20073]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:23 GRAViTY vsftpd[20076]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:23 GRAViTY vsftpd[20076]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:23 GRAViTY vsftpd[20079]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:23 GRAViTY vsftpd[20079]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:23 GRAViTY vsftpd[20082]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:23 GRAViTY vsftpd[20082]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:23 GRAViTY vsftpd[20101]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:23 GRAViTY vsftpd[20101]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 08:59:23 GRAViTY vsftpd[20104]: connect from 10.10.10.62 (10.10.10.62) May 19 08:59:23 GRAViTY vsftpd[20104]: [mediaclient] OK LOGIN: Client "10.10.10.62" May 19 09:51:57 GRAViTY kernel: usb 3-4.4: new full-speed USB device number 4 using xhci_hcd May 19 09:51:57 GRAViTY kernel: cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device May 19 09:52:01 GRAViTY kernel: usb 3-4.4: USB disconnect, device number 4 May 19 09:52:01 GRAViTY kernel: usb 3-4.4: new full-speed USB device number 5 using xhci_hcd May 19 09:52:01 GRAViTY kernel: cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device May 19 09:53:53 GRAViTY kernel: veth97f0b8f: renamed from eth0 May 19 09:53:53 GRAViTY kernel: docker0: port 3(vethf6f1318) entered disabled state May 19 09:53:54 GRAViTY kernel: docker0: port 3(vethf6f1318) entered disabled state May 19 09:53:54 GRAViTY kernel: device vethf6f1318 left promiscuous mode May 19 09:53:54 GRAViTY kernel: docker0: port 3(vethf6f1318) entered disabled state May 19 09:53:55 GRAViTY kernel: docker0: port 3(veth1c69dab) entered blocking state May 19 09:53:55 GRAViTY kernel: docker0: port 3(veth1c69dab) entered disabled state May 19 09:53:55 GRAViTY kernel: device veth1c69dab entered promiscuous mode May 19 09:53:55 GRAViTY kernel: docker0: port 3(veth1c69dab) entered blocking state May 19 09:53:55 GRAViTY kernel: docker0: port 3(veth1c69dab) entered forwarding state May 19 09:53:55 GRAViTY kernel: docker0: port 3(veth1c69dab) entered disabled state May 19 09:53:56 GRAViTY kernel: eth0: renamed from vethaefd029 May 19 09:53:56 GRAViTY kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1c69dab: link becomes ready May 19 09:53:56 GRAViTY kernel: docker0: port 3(veth1c69dab) entered blocking state May 19 09:53:56 GRAViTY kernel: docker0: port 3(veth1c69dab) entered forwarding state May 19 10:51:50 GRAViTY kernel: usb 3-4.4: USB disconnect, device number 5 May 19 10:51:50 GRAViTY kernel: usb 3-4.4: new full-speed USB device number 6 using xhci_hcd May 19 10:51:51 GRAViTY kernel: cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device May 19 10:51:54 GRAViTY kernel: usb 3-4.4: USB disconnect, device number 6 May 19 10:51:54 GRAViTY kernel: usb 3-4.4: new full-speed USB device number 7 using xhci_hcd May 19 10:51:55 GRAViTY kernel: cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device Diagnostics file is attached. gravity-diagnostics-20220519-1157.zip

Hi again, not sure whether it is right to post here again instead of creating a new thread but I partly solved the issue with a workaround. i assume that there is some network storming caused by the VM and to troubleshoot I created a new VLAN in which only the VM is running (managed by my UniFi UDM Pro). The server has not become inaccessible since then until today. But this time not due to my HTPC VM but since I installed the ZWaveJS2MQTT Docker. i really have no idea how to troubleshoot but come on… I don’t want to create some artificial VLANs just to work around this problem. Do you guys have any idea?

Sorry if this the wrong place but I recently got my Conbee II stick and first thing I tried was to Passthrough to HA VM and set it up using the Zigbee integration. But after restarting I am getting this error [Errno 2] could not open port /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2497572-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2497572-if00 So some research revealed that there are issues with Passthrough of the USB device. Next thing I stumbled upon is to run Deconz and just skip the hassle. Now I am wondering whether there are any downsides of using this Docker and making it available to HA via the Deconz integration compared to what I tried. Especially regarding reaction speed (e.g. with motion sensors)? Also, any idea how to attack my initial problem with the USB Passthrough? Detaching and Re-attaching it does not help. And whenever I restart the unraid server I have to unplug and replug my Zwave stick or the Zwave devices do not work in HA. Not sure whether this is correlated though as I had the problem before adding Zigbee. 😅 I appreciate any info! Thanks a lot!

I found out the following: - When the VM is running, network access of the server is timing out and occasionally it is reachable again for a few minutes - Pulling the Ethernet cable and plugging it in again makes the server available again immediately (for a few minutes) - When the VM is shut down, the server is not reachable shortly after and remains that way until I re-plug Ethernet again I attached some screenshots from Ping attempts. And lastly, with the VM being shut down and the cable being pulled out and plugged in again.

Hi everyone, I am currently facing a critical issue with my Unraid server's network hanging when my Debian VM with GPU passthrough is running. I had a similar issue as described in this thread here but since I added another cache drive (M2 SSD) and reconfigured my VM's XML (changing the addresses within the XML form for GPU passthrough to work) after a few minutes the Unraid server is not accessible via the network anymore. Plugging the ethernet cable in and out solves the issue for the next few minutes. With the VM being shut down, the server remains accessible. Here is how I set up the VM and the xml (sorry for only providing screenshots). I am at my wits' end... I cannot see anything in the logs. Here is an extract with the network cable being pulled out and plugged in again. Apr 9 13:35:55 GRAViTY ntpd[2076]: no peer for too long, server running free now Apr 9 14:11:14 GRAViTY ntpd[2076]: no peer for too long, server running free now Apr 9 15:35:08 GRAViTY kernel: r8169 0000:04:00.0 eth0: Link is Down Apr 9 15:35:08 GRAViTY kernel: bond0: (slave eth0): link status definitely down, disabling slave Apr 9 15:35:08 GRAViTY kernel: device eth0 left promiscuous mode Apr 9 15:35:08 GRAViTY kernel: bond0: now running without any active interface! Apr 9 15:35:08 GRAViTY kernel: br0: port 1(bond0) entered disabled state Apr 9 15:35:14 GRAViTY kernel: r8169 0000:04:00.0 eth0: Link is Up - 1Gbps/Full - flow control off Apr 9 15:35:14 GRAViTY kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex Apr 9 15:35:14 GRAViTY kernel: bond0: (slave eth0): making interface the new active one Apr 9 15:35:14 GRAViTY kernel: device eth0 entered promiscuous mode Apr 9 15:35:14 GRAViTY kernel: bond0: active interface up! Apr 9 15:35:14 GRAViTY kernel: br0: port 1(bond0) entered blocking state Apr 9 15:35:14 GRAViTY kernel: br0: port 1(bond0) entered forwarding state Apr 9 15:35:58 GRAViTY kernel: br0: port 2(vnet0) entered disabled state Apr 9 15:35:58 GRAViTY kernel: device vnet0 left promiscuous mode Apr 9 15:35:58 GRAViTY kernel: br0: port 2(vnet0) entered disabled state Apr 9 15:35:58 GRAViTY kernel: usb 1-2: reset full-speed USB device number 3 using xhci_hcd Apr 9 15:35:58 GRAViTY kernel: input: Microsoft Microsoft® 2.4GHz Transceiver v7.0 as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-2/1-2:1.0/0003:045E:07B2.0004/input/input9 Apr 9 15:35:58 GRAViTY kernel: hid-generic 0003:045E:07B2.0004: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® 2.4GHz Transceiver v7.0] on usb-0000:02:00.0-2/input0 Apr 9 15:35:58 GRAViTY kernel: input: Microsoft Microsoft® 2.4GHz Transceiver v7.0 Mouse as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-2/1-2:1.1/0003:045E:07B2.0005/input/input10 Apr 9 15:35:58 GRAViTY kernel: input: Microsoft Microsoft® 2.4GHz Transceiver v7.0 Consumer Control as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-2/1-2:1.1/0003:045E:07B2.0005/input/input11 Apr 9 15:35:58 GRAViTY kernel: hid-generic 0003:045E:07B2.0005: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® 2.4GHz Transceiver v7.0] on usb-0000:02:00.0-2/input1 Apr 9 15:35:58 GRAViTY kernel: input: Microsoft Microsoft® 2.4GHz Transceiver v7.0 Consumer Control as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-2/1-2:1.2/0003:045E:07B2.0006/input/input12 Apr 9 15:35:58 GRAViTY kernel: input: Microsoft Microsoft® 2.4GHz Transceiver v7.0 System Control as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-2/1-2:1.2/0003:045E:07B2.0006/input/input14 Apr 9 15:35:58 GRAViTY kernel: hid-generic 0003:045E:07B2.0006: input,hiddev96,hidraw2: USB HID v1.11 Device [Microsoft Microsoft® 2.4GHz Transceiver v7.0] on usb-0000:02:00.0-2/input2 Apr 9 15:36:00 GRAViTY kernel: vfio-pci 0000:07:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem I have attached the diagnostics file. Appreciating any hint from you guys! The server being unaccessible sucks especially as my Home Assistant is running on the server and I heavily relay on that. Thanks in advance! gravity-diagnostics-20220409-1549.zip

The latest XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='5'> <name>Debian</name> <uuid>5a4535db-fe08-73fa-e4d1-e9c1e9f75a62</uuid> <metadata> <vmtemplate xmlns="unraid" name="Debian" icon="debian.png" os="debian"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>9</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='8'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='9'/> <vcpupin vcpu='5' cpuset='4'/> <vcpupin vcpu='6' cpuset='10'/> <vcpupin vcpu='7' cpuset='5'/> <vcpupin vcpu='8' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/5a4535db-fe08-73fa-e4d1-e9c1e9f75a62_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='9' threads='1'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Debian/vdisk1.img' index='2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/debian-testing-amd64-DVD-1.iso' index='1'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:27:74:46'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-5-Debian/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/vbios/GTX1050TI-Mini.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0461'/> <product id='0x0010'/> <address bus='1' device='4'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

Ok, apparently the vbios had issues and after dumping it following this legend's guide, it seems to work! 🙂

Hi guys, I am at my wits' end as although I followed all the GPU passthrough guides I could find, I cannot get it to work for my Debian VM (want to have Kodi running on it). After creating the VM, this is how the XML looks: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Debian</name> <uuid>5a4535db-fe08-73fa-e4d1-e9c1e9f75a62</uuid> <metadata> <vmtemplate xmlns="unraid" name="Debian" icon="debian.png" os="debian"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>9</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='8'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='9'/> <vcpupin vcpu='5' cpuset='4'/> <vcpupin vcpu='6' cpuset='10'/> <vcpupin vcpu='7' cpuset='5'/> <vcpupin vcpu='8' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/5a4535db-fe08-73fa-e4d1-e9c1e9f75a62_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='9' threads='1'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Debian/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/debian-testing-amd64-DVD-1.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:27:74:46'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' 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'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/Zotac.GTX1050Ti.4096.161221.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain> I edited it to look like this: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='2'> <name>Debian</name> <uuid>5a4535db-fe08-73fa-e4d1-e9c1e9f75a62</uuid> <metadata> <vmtemplate xmlns="unraid" name="Debian" icon="debian.png" os="debian"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>9</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='8'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='9'/> <vcpupin vcpu='5' cpuset='4'/> <vcpupin vcpu='6' cpuset='10'/> <vcpupin vcpu='7' cpuset='5'/> <vcpupin vcpu='8' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/5a4535db-fe08-73fa-e4d1-e9c1e9f75a62_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='9' threads='1'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Debian/vdisk1.img' index='2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/debian-testing-amd64-DVD-1.iso' index='1'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:27:74:46'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-2-Debian/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/vbios/Zotac.GTX1050Ti.4096.161221.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> And under Unraid OS I added the following boot attributes with my device IDs: append initrd=/bzroot vfio-pci.ids=10de:1c82,10de:0fb9 When adding video=efifb:off it still showed the unraid login on my screen. With the attributes above it shows the following with the cursor still flashing: ... AMD-Vi: AMD 10MMUvZ driver by Joerg Roedel <jroedelesuse.de› parport_pc 00:03: reported by Plug and Play ACPI parport0: PC-style at 0x378, irg 5 [PCSPP(....)] lp0: using parport0 (interrupt-driven). loop: module loaded Rounding down aligned max_sectors from 4294967295 to 4294967288 db_root: cannot open: /etc/target UFIO User Level meta-driver version: 0.3 ufio-pci 0000: 06:00.0: ugaarb: changed UGA decodes: olddecodes=io+mem, decodes=io +mem: owns=10+mem Any idea what else to try?

Hey guys, I’ve been using this for quite a while now and totally love it. But occasionally I get reading errors or “no Disc” errors. Rebooting the server helps whereas rebooting the docker does not. Is there any way to fix that without rebooting the server? Maybe some CLI command to power cycle the drive or something like that? Would be awesome!

You sir are a true hero! Thank you very much!

Thanks for answering! This is the xml form for my VM: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>HA OS</name> <uuid>0d290cc6-10fe-a591-adf8-4e49d5769d5d</uuid> <description>Home Assistant OS on Linux</description> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/0d290cc6-10fe-a591-adf8-4e49d5769d5d_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='3' threads='1'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/domains/HA OS/haos_ova-6.1.qcow2'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:c4:eb:8b'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' 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='tablet' bus='usb'> <address type='usb' bus='0' port='2'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='de'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0658'/> <product id='0x0200'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> </domain>

Hi everyone, I am facing an issue after moving my HA image from a parity disk to my cache disk on Unraid. This worked quite easy and was done in order to not having the parity check negatively affecting the performance of HA. fs0: brings 'fs0:' is not a valid mapping. I then performed the following (read in the Unraid forums): modprobe nbd max_part=8 qemu-nbd --connect=/dev/nbd0 /path/to/the/image/ha.qcow2 mkdir /path/to/the/mount/point/ fdisk /dev/nbd0 -l mount /dev/nbd0p1 /path/to/the/mount/point/ and the output is: Disk /dev/nbd0: 32 GiB, 34359738368 bytes, 67108864 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: A4E33CCF-98F3-43B5-B08D-6F37CFF42D17 Device Start End Sectors Size Type /dev/nbd0p1 2048 67583 65536 32M EFI System /dev/nbd0p2 67584 116735 49152 24M Linux filesystem /dev/nbd0p3 116736 641023 524288 256M Linux filesystem /dev/nbd0p4 641024 690175 49152 24M Linux filesystem /dev/nbd0p5 690176 1214463 524288 256M Linux filesystem /dev/nbd0p6 1214464 1230847 16384 8M Linux filesystem /dev/nbd0p7 1230848 1427455 196608 96M Linux filesystem /dev/nbd0p8 1427456 67108830 65681375 31.3G Linux filesystem So it appears to not be broken. After checking that, I unmounted and disconnected using: umount /path/to/the/mount/point/ qemu-nbd --disconnect /dev/nbd0 rmmod nbd What I did for the sake of a backup is to mount the biggest partition and download the supervisor folder which holds configs and backups... Do you guys have any idea what to try to get the VM back on running? Especially ZWave is what took soooo much time. 😦 Thanks a lot in advance guys!

Hey guys, after moving the HA VM from disk1 to cache, I encounter the same issue but the partitions seem to still be intact. Disk /dev/nbd0: 32 GiB, 34359738368 bytes, 67108864 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: A4E33CCF-98F3-43B5-B08D-6F37CFF42D17 Device Start End Sectors Size Type /dev/nbd0p1 2048 67583 65536 32M EFI System /dev/nbd0p2 67584 116735 49152 24M Linux filesystem /dev/nbd0p3 116736 641023 524288 256M Linux filesystem /dev/nbd0p4 641024 690175 49152 24M Linux filesystem /dev/nbd0p5 690176 1214463 524288 256M Linux filesystem /dev/nbd0p6 1214464 1230847 16384 8M Linux filesystem /dev/nbd0p7 1230848 1427455 196608 96M Linux filesystem /dev/nbd0p8 1427456 67108830 65681375 31.3G Linux filesystem Any idea how to save my VM? I do not have a backup...

It happened again a few hours ago. I will track temperature and see whether this might be a potential issue. syslog-3

Thanks for your reply. Any known bugs regarding AMD-V being enabled? I remember some issues with C-States but I guess a kernel panic would’ve been logged? And do you think the NIC can cause issues of that kind? Or could my latest Ubuntu VM cause something like that? One thing worth mentioning regarding the network stuff: The reason why I plugged the network cable out and in again was the fact that the unraid server as well as my home assistant VM (same VLAN) were not reachable while the other VM (different VLAN) was still reachable. After plugging the cable out and in again, everything was reachable again. The hardware itself hasn’t changed since the server was put together.

Hi everyone, a few days ago my unraid server started to shut itself down unexpectedly. I just noticed that my services were offline and then physically checked on the server and it was off. I enabled syslog on flash which I attached together with the diagnostics file (from after the shutdown unfortunately). Last week I enabled AMD-V on the bios in order to be able to work with VMs. I just had docker containers before. One thing also worth mentioning is that I use different VLANs for the unraid server, dockers and one of the VMs. Not sure whether this can cause such an issue though. From a time perspective, the behaviour occurred in the following timeframe. 18:16 Ethernet plugged out and back in 18:22 Reboot initiated Between 18:23 and 19:54 the system shut down itself. 19:54 it was manually booted up again. As you can see, there is no log entry between the reboot and the second time manually booting it. I am really at my wits end and have no idea what to try / troubleshoot. Thanks a lot in advance! gravity-diagnostics-20210723-2001.zip syslog-2

I am so blind... thank you!

Hi guys, I wanted to add some extra paramters for the docker version of andig/evcc in order to connect it to my energy home manager, chargers etc. The full command is for example: docker run --network host andig/evcc ... or docker run -v /etc/machine-id:/etc/machine-id -v /var/lib/dbus/machine-id:/var/lib/dbus/machine-id andig/evcc ... Now the "Extra Parameters" field as described in some posts seems to be removed. And just adding the commands after the repository entry does not work for me. As I am not at home right now, I can't provide the exact error message but maybe I am doing something wrong that is easy for you guys to spot? Looking forward to any help! Thanks guys.

Ok, cool. Thanks a lot. So: Bios Setting: Advanced --> AMD CBS --> Zen Common Options --> Global C-state Control Any idea how/when this hard lock happens? As I mentioned, the last day it was running fine. Maybe because the parity checks kept the system busy?

Diagnostics after installing mcelog. gravity-diagnostics-20210118-1147.zip