iPenguin02

I swapped my GPU that I am passing through to a Windows 10 VM. I binded the GPU to VFIO before assigning it to the VM and it is booting just fine. However, my issue is with my other VMs. When they boot, it goes to Windows Boot Manager stating Windows failed to start. Status: Oxc000000f Info: A required device isn't connected or can't be accessed I've tried to repair the disk and tried deleting the template, but using the same vdisk img. No luck Not sure what to look for in the XML. Is this normal? I'm hoping I don't have to delete the entire vdisk and start over. Thanks in advance! <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>iP-Admin</name> <uuid>9402fe4d-f760-df48-1cc5-b52a1bca4bdb</uuid> <description>Windows 10</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>17301504</memory> <currentMemory unit='KiB'>17301504</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='20'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='21'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='24'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='25'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/9402fe4d-f760-df48-1cc5-b52a1bca4bdb_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <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' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> </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/Unraid/Domains/iP-Admin/iP-Admin.img'/> <target dev='hdc' bus='sata'/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Software/OS/Windows/Windows10_2022-09-27.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </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:d6:91:ba'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 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='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain>

I just followed the steps to install Backblaze_Personal_Backup and got this error after logging in and finishing the install Error: ERR_NotificationDialog_bad_bzdara_permission_Msg (Can't see the full message) I followed all the steps on the github and see the D drive. Anyone know what this means? The backup seems to be running just fine.

I'm having issues passing through a 4tb hdd using UD to a VM. I've tried formatting the drive as NTFS using UD and Windows without luck. I'm only passing through 1 partition, but when I do, the VM detects multiple partitions. I've tried GPT, MBR and dynamic to no luck. I've also tried formatting in Windows then changing the 2nd vDisk location to partition 1 after. The reason I need to pass through the partition only is because if I pass through the entire drive my dockers won't see new files. When I pass through the entire drive it works just fine. I can click on Storage and navigate the directories using the web /dev/disk/by-id/ata-ST4000DM004-2CV104_ZFN0FS4D-part1 This is what it looks like in the VM

Has anyone else experienced the backup process resetting? Yesterday, my backup progress was at 30%, this morning it is at 4%. This is the second time this occurred, this time I am concerned. I know it's not a result of the following: - Rebooting - Restarting the Docker - Power Loss, had a blackout yesterday and do not currently have an UPS (I know, something I need to buy) A parity check is currently running after I got Unraid back up after the power outage. Could the parity check cause this? Current errors found is 7.