feliksk

I think unraid_notify.cfg is an artifact of some very old plugin. I renamed the file, and Unraid notifications still work, and Fix common problem no longer reports the issue. I'll just delete the file if the next server reboot doesn't complain about it

Have you ever figured it out? I'm in the same boat

Yes, with 6.9.2 I'm passing both GPU and USB controller through. Nvidia GeForce GT 730 GPU and ASRock X570 Taichi motherboard. Never had any issues until 6.10.x. I haven't tried 6.11 yet

I just created a new Windows VM and pointed it to the previous primary vDisk Location.

I did not solve, rather gave up. I downgraded to 6.9.2 and had to recreate Windows VM to get everything working again. With 6.10.3, I couldn't get the GPU passthrough working even with a new VM There's no harm trying to upgrade as you can always go back. I'm sure it's something specific to my setup as I don't see any reports with a similar issue. I use the old way of isolating vfio, so when I get a chance I'll change it and will try again

I've been running Windows VM on 6.9 with NVidia GPU passthrough for a long time with 0 issues. After the upgrade, VM tab says that Windows is started, but the monitor is blank. There are no errors in the VM log, so I'm attaching the full diagnostics. Any help is greatly appreciated as this is my primary work machine

I connect to my Windows 7 VM through Remote Desktop. The screen redraws and youtube videos are very choppy, scrolling in a browser is also not smooth at all. My specs: Unraid 6.2 Pro i5-4590 3.3 GHz CPU 16Gigs Ram GeForce GT 730 passthrough Is this an expected performance? Any help is much appreciated. Here's the VM spec: <domain type='kvm' id='38'> <name>Win7Vm</name> <uuid>55263123-e4df-89be-493f-50f37dccb4f6</uuid> <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/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='1'/> </cpu> <clock offset='localtime'> <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/Win7Vm/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <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/VM ISO/Win_7.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <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/VM ISO/virtio-win-0.1.102.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </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='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:a7:bb:47'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-Win7Vm/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> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <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='0x02' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain>

Got it, thank you

After adding a new video card to my system and assigning it to a Ubuntu VM, I'm able to start the VM, but 'VNC Remote' option has disappeared. Is there a recommended way to access the VM that has GPU passthrough? Changing graphics card back to VNC restore the 'VNC Remote' option. Thanks, Feliks

Thank you. Started the array and everything is looking normal. Running the permissions update script.

Thanks, but is 'MBR:unaligned' normal too?

Just upgraded from 4.7. All my disks say Partition format: MBR: unaligned File sytem type: unknown Is it safe to start the array?

Thanks, I'll run another preclear and will post the results

I ran preclear twice on the same WD20EARS disk. The first time I got this in the summary: Changed attributes in files: /tmp/smart_start_hda /tmp/smart_finish_hda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 115 114 0 ok 37 Reallocated_Event_Count = 198 199 0 ok 2 No SMART attributes are FAILING_NOW 1 sector was pending re-allocation before the start of the preclear. 1 sector was pending re-allocation after pre-read in cycle 1 of 1. 1 sector was pending re-allocation after zero of disk in cycle 1 of 1. 1 sector is pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 2 sectors had been re-allocated before the start of the preclear. 4 sectors are re-allocated at the end of the preclear, a change of 2 in the number of sectors re-allocated. The second time, for the same disk: <code> rt_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 0 ok 0 Temperature_Celsius = 109 110 0 ok 43 No SMART attributes are FAILING_NOW 1 sector was pending re-allocation before the start of the preclear. 1 sector was pending re-allocation after pre-read in cycle 1 of 1. 1 sector was pending re-allocation after zero of disk in cycle 1 of 1. 1 sector is pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 4 sectors had been re-allocated before the start of the preclear. 4 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. Can I trust this disk in the array? Thank you