mik

My pc has 2 gpu one RX580(first pci slot) and Nvidia 760(second slot). I tried adding the rx580 to a windows 10 vm and I encountered similar problems like: https://forums.unraid.net/topic/77964-solved-is-it-possible-to-pass-through-an-amd-gpu/. Prior to this incident my windows install was running on i440fx-2.7 with SeaBIOS. I tested with q35 as suggested in the other thread. However this made my vm blue screen with and without the gpu passed thorough. My problem is that now I can’t revert back to i440fx, I am getting an error “XML error: The PCI controller with index='0' must be model='pci-root' for this machine type, but model='pcie-root' was found instead”. Anny suggestions on how I can fix that? Also it seems easier to passthrough gpus on a q35 with OVFM however however i would prefer not to reinstall my wm. Is there any way of passing an rx580 on SeaBIOS? I have read about dumping gpuBIOS and modifying it, however as far as I understand this was only something that could help on nvidia cards? on nvidia cards? Note my nvidia 760 worked without problems(no bios mod) on this vm. Ganeralt pc specs: cpu: i7-5820K M/B: MSI X99A RAIDER (MS-7885) gpu: msi RX580 armor 8gb gpu msi Nvidia 760 unraid:6.7.0 any help would be appreciated here is the win10 xml: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>ede7d07c-1102-60e2-0a8f-2af47277b0ff</uuid> <description> </description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>14680064</memory> <currentMemory unit='KiB'>14680064</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>7</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='6'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='7'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='8'/> <vcpupin vcpu='6' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-3.1'>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='7' threads='1'/> </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/os disk/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/orgin/Windows 10/vdisk2.img'/> <target dev='hdd' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </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='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='pci' index='7' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xe'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x03' 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:2f:8d:00'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' 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='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> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain>

sorry i am a newbie, do you mean a "Write corrections to parity check"?

About 2-3 min. before the power disappeared I was moving/deleting files from shares. I actually started a shutdown about 5-10 seconds before the power disappeared. So maybe the server was doing something?

hey, i just had a power outage (a scheduled correcting parity check was running). I booted the server and started a noncorecting parity check. 10% done and I have over 600 Sync errors detected. Should I be conserd that my data is corrupted. I check the files I was working on just before the power went and they all look fine. What should I do when the noncorrecting parity check is completed? I am running version 6.3.5 with a 6TB parity drive and 1TB 2TB 3TB storage drives. syslog: Aug 4 19:05:46 minpc kernel: mdcmd (42): check nocorrect Aug 4 19:05:46 minpc kernel: md: recovery thread: check P ... Aug 4 19:05:46 minpc kernel: md: using 1536k window, over a total of 5860522532 blocks. Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=0 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=96 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=112 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=320 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=1848 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=1856 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=2440 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=60296 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=60304 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=77648 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=77656 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=77664 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=129920 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=130456 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=130496 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=131088 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=132608 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=153824 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=153832 Aug 4 19:05:47 minpc kernel: md: recovery thread: P incorrect, sector=392800 Aug 4 19:05:47 minpc kernel: md: recovery thread: P incorrect, sector=394208 Aug 4 19:05:47 minpc kernel: md: recovery thread: P incorrect, sector=394240 Aug 4 19:05:47 minpc kernel: md: recovery thread: P incorrect, sector=394248 Aug 4 19:05:47 minpc kernel: md: recovery thread: P incorrect, sector=448536 Aug 4 19:05:52 minpc kernel: md: recovery thread: P incorrect, sector=1987240 Aug 4 19:05:53 minpc kernel: md: recovery thread: P incorrect, sector=2371488 Aug 4 19:05:53 minpc kernel: md: recovery thread: P incorrect, sector=2371504 Aug 4 19:06:00 minpc kernel: md: recovery thread: P incorrect, sector=4756008 Aug 4 19:06:13 minpc kernel: md: recovery thread: P incorrect, sector=9330152 Aug 4 19:06:15 minpc kernel: md: recovery thread: P incorrect, sector=10079688 Aug 4 19:06:15 minpc kernel: md: recovery thread: P incorrect, sector=10079696 Aug 4 19:06:16 minpc kernel: md: recovery thread: P incorrect, sector=10231672 Aug 4 19:08:33 minpc kernel: md: recovery thread: P incorrect, sector=58813000 Aug 4 19:08:33 minpc kernel: md: recovery thread: P incorrect, sector=58813048 Aug 4 19:09:09 minpc kernel: md: recovery thread: P incorrect, sector=71848016 Aug 4 19:09:10 minpc kernel: md: recovery thread: P incorrect, sector=71934032 Aug 4 19:09:10 minpc kernel: md: recovery thread: P incorrect, sector=71936672 Aug 4 19:09:10 minpc kernel: md: recovery thread: P incorrect, sector=71946752 Aug 4 19:10:10 minpc kernel: md: recovery thread: P incorrect, sector=93504336 Aug 4 19:10:22 minpc kernel: md: recovery thread: P incorrect, sector=97560096 Aug 4 19:10:22 minpc kernel: md: recovery thread: P incorrect, sector=97560104 Aug 4 19:10:22 minpc kernel: md: recovery thread: P incorrect, sector=97560112 Aug 4 19:10:23 minpc kernel: md: recovery thread: P incorrect, sector=97884536 Aug 4 19:10:23 minpc kernel: md: recovery thread: P incorrect, sector=97900512 Aug 4 19:10:23 minpc kernel: md: recovery thread: P incorrect, sector=97900520 Aug 4 19:10:23 minpc kernel: md: recovery thread: P incorrect, sector=97900528 Aug 4 19:10:24 minpc kernel: md: recovery thread: P incorrect, sector=98503536 Aug 4 19:10:38 minpc kernel: md: recovery thread: P incorrect, sector=103401392 Aug 4 19:10:38 minpc kernel: md: recovery thread: P incorrect, sector=103401400 Aug 4 19:10:38 minpc kernel: md: recovery thread: P incorrect, sector=103457040 Aug 4 19:10:45 minpc kernel: md: recovery thread: P incorrect, sector=106048656 Aug 4 19:11:18 minpc kernel: md: recovery thread: P incorrect, sector=117445056 Aug 4 19:11:18 minpc kernel: md: recovery thread: P incorrect, sector=117445096 Aug 4 19:11:18 minpc kernel: md: recovery thread: P incorrect, sector=117445104 Aug 4 19:11:19 minpc kernel: md: recovery thread: P incorrect, sector=117831432 Aug 4 19:11:19 minpc kernel: md: recovery thread: P incorrect, sector=117831440 Aug 4 19:11:20 minpc kernel: md: recovery thread: P incorrect, sector=118275696 Aug 4 19:11:20 minpc kernel: md: recovery thread: P incorrect, sector=118275704 Aug 4 19:11:23 minpc kernel: md: recovery thread: P incorrect, sector=119416120 Aug 4 19:11:29 minpc kernel: md: recovery thread: P incorrect, sector=121564472 Aug 4 19:11:36 minpc kernel: md: recovery thread: P incorrect, sector=124089920 Aug 4 19:11:36 minpc kernel: md: recovery thread: P incorrect, sector=124106304 Aug 4 19:11:36 minpc kernel: md: recovery thread: P incorrect, sector=124106336 Aug 4 19:11:36 minpc kernel: md: recovery thread: P incorrect, sector=124106344 Aug 4 19:11:37 minpc kernel: md: recovery thread: P incorrect, sector=124262224 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=128909064 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=128909072 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=128909080 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=128915032 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=129106816 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=129106856 Aug 4 19:11:54 minpc kernel: md: recovery thread: P incorrect, sector=130426272 Aug 4 19:11:54 minpc kernel: md: recovery thread: P incorrect, sector=130426360 Aug 4 19:11:54 minpc kernel: md: recovery thread: P incorrect, sector=130500952 Aug 4 19:11:54 minpc kernel: md: recovery thread: P incorrect, sector=130501128 Aug 4 19:11:55 minpc kernel: md: recovery thread: P incorrect, sector=130597080 Aug 4 19:12:13 minpc kernel: md: recovery thread: P incorrect, sector=136882824 Aug 4 19:12:13 minpc kernel: md: recovery thread: P incorrect, sector=136882832 Aug 4 19:12:13 minpc kernel: md: recovery thread: P incorrect, sector=137001880 Aug 4 19:24:10 minpc kernel: md: recovery thread: P incorrect, sector=381521488 Aug 4 19:24:10 minpc kernel: md: recovery thread: P incorrect, sector=381521496 Aug 4 19:24:10 minpc kernel: md: recovery thread: P incorrect, sector=381645464 Aug 4 19:24:13 minpc kernel: md: recovery thread: P incorrect, sector=382585696 Aug 4 19:24:16 minpc kernel: md: recovery thread: P incorrect, sector=383529584 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384413368 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384413376 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384413544 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384413552 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384413560 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384727968 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384727976 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384727984 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384727992 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384728000 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384728008 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384728016 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384728024 Aug 4 19:24:21 minpc kernel: md: recovery thread: P incorrect, sector=385316928 Aug 4 19:24:21 minpc kernel: md: recovery thread: P incorrect, sector=385316936 Aug 4 19:24:43 minpc kernel: md: recovery thread: P incorrect, sector=392694880 Aug 4 19:24:55 minpc kernel: md: recovery thread: stopped logging

I am no expert on Unriad, but linux has a config file that lets you choose a command to send if the power-button is pressed. So if you can find a way to start a VM from command line you can I theory start a VM with the power-button.

I am running a windows VM on my Unraid machine. I wood like to passport(pci) usb controller and audio card to my wm. However I have used up all the integrated IO and have only ONE PCI-Ex1 left I my pc. Does any one know of a singel PCI-Ex1 card (single slot height) that has both USB and audio controller on the same card?

I did read the upgrade guide after I my pc crached. I had almost every setting correct. After my original post I have fix my issues. Apparently avast antivirus works on 6.1.9 but not on 6.2 . I discovered this after trying to install of win. 10 in a new VM. Everything works great until I installed avast. I also discovered people on the forum have been complained about avast before. But there systems only crashed the VM. I can’t find anyone else that have experienced FULL system hang from avast. Solution: I downgraded to 6.9.1(VM worked great) uninstalled avast and upgraded again. Now everything works fine. I think it is strange that software in a VM can crach the Unraid OS.

I just updated unraid from 6.1.9 to 6.2 and I am having problems with my windows 10 vm. Windows hangs on boot. Some times the windows recovery stars but the only option available is to refresh the install. All my other vm’s are fine. I cant turn windows 10 off, so I tried forced shutdown. I tried to start windwos 10 again and it var still hanging. But when I tried forced stop the 2. time all the my vm’s crash, I lose connection to web, ssh, and unraid gui and command line. I could not shutdown unraid and was forced to cut power to my pc. I have tried several times after that. some forced stop crashes unraid server other do not. Anny ideas to what is wrong? pc specs: cpu: Intel® Core™ i7-5820K CPU @ 3.30GHz ram: 16 GB mb: MSI - X99A RAIDER (MS-7885)