PeteyBoPetey

Hi Guys, Turned the server on and Unraid booted fine. Tried to start Windows 10 and it was stuck on 7% for ages. I let it be. Came back 30 minutes later to find the Windows Restarting screen with the cartwheel. Left it, and it hasn't restarted. I forced stopped the VM only to get the same problem. How do I fix?

Hi Guys, I have a problem with two VMs. First one seems to work ok, however the libvert log says: "2022-08-09 07:27:59.849+0000: 4597: warning : qemuDomainObjTaintMsg:6602 : Domain id=1 name='Dads Computer' uuid=be0a9c36-576b-730b-ae95-05796ce821d1 is tainted: custom-ga-command 2022-08-09 07:27:59.912+0000: 4595: error : qemuDomainAgentAvailable:8610 : Guest agent is not responding: QEMU guest agent is not connected" The second VM boots to windows login, after logging in I get a black screen. I don't think this is an NVIDIA problem because when I shut down the VM it display the "shuting down" and cart wheel of dots. I've tried: Fresh install of Windows 10, however, after installing the virt stor drivers windows reboots then starts services then gets stuck on "Getting Devices Ready" with the cart wheel of dots. Set VM to one CPU core Tried a fresh Windows 10.iso Made a copy of a working VMs vdisk and now able to boot into VNC However, both the old VM with a black screen and the new duplicate of a working VM give the same error message in the VM log: "xl_send_events: spice-server bug: guest stopped, ignoring" I think all my problems relate to the Guest Agent which I know nothing about.

I'm at wits end guys, I really am. I've googled everything and tried everything and nothing works :/. Everything is running fine on 6.9 Upgraded to 6.10.3 and nothing worked Discovered I need a motherboard bios update, so updated to ASUS latest bios Put append pcie_acs_override=multifunction video=efifb:off initrd=/bzroot in syslinux.cfg After I start VM primary GPU shuts down after about a minute with "Cannot power on device, stuck in D3" in the error log Tried vbios from Techpowerup with NVIDIA header removed I would assume this problem is related to Unraids update or bios update because everything was fine prior to updating Unraid and my bios. It could be coincidental that the GPU just happened to die, but I don't think so because it will display the bios screen for hours without shutting down?. Additionally, the GPU in the bottom most slot is code 43 and nothing I do fixes that either, I don't know if that's related somehow? I've tried rolling back bios and Unraid without any luck. Taking into consideration that it's shutting down, could this be due to the ASPM setting bios being incorrectly set? Should it be disabled, bios controlled or OS controlled?. I'd try Q35 instead of i440fx only I don't know how to configure the bus/slots Please help, I need this PC up and running for University. I don't want to RMA the GPU because that takes weeks and I suspect that Unraid or BIOS is the culprit. RMAing is a big job because it invloves dismantling a cooling loop, replacing the air cooler theeen send it back. Peter

I've had the exact same problem for 2 months now. Unraid 6.10 wouldn't boot, a BIOS update fixed that, but that's when all my GPU problems started. Second GPU became the primary GPU. I was able to get a VM to start and give video output on the primary GPU, but would stop after a minute and the VM log would say "could not power on, device stuck in D3". I think I have fixed it. In the BIOS menu and APM Advanced Power Management was set to disabled. I suspected that the GPU was turning off for some reason, but with APM disabled I assumed it wasn't due to APM powering it down. After trying everything else I randomly tried enabling APM and now my primary GPU outputs the BIOS and boot screen. So I think setting APM to enable was the fix. Just gotta redo my cooling loop to be 100% sure. It's counter intuitive, because you'd think that the default state of APM would be to leave everything powered on?

When creating a q35 VM how do I edit the bus and slot in the XML for Nvidia GPU

I've spent three weeks trying to solve this. Update to 6.10.3 and wouldn't boot. Forum posts from a multitude of people state that a bios update was a solution Updated to latest bios, Unraid now boots, but bios screen is outputing on GPU 2, GPU 3 says "Unable to power on,stuck in D3" Rolled back to Unraid 6.9.2 and rolled back to an older bios. GPU 2 & 3 now work, GPU 1 isn't the primary GPU anymore and it works for about 10 seconds then shuts down after windows loads. However, it doesn't have any problem displaying the windows repair menu for 10 minutes. I don't know if this is a bios problem, or driver problem. All the problems started with the bios update suggesting a bios problem. However, GPU 1 is working normally until windows loads suggests a driver issue? Why isn't GPU 1 the primary GPU and why is it powering down? UPDATE: The BIOS update included the addition of APM Advanced Power Management. The primary GPU would not be picked up as primary GPU and would shut down after two minutes and give a 'could not power on, stuck in D3' error which led me to believe it could be the power saving feature powering down the primary GPU. So I made sure APM was set to disabled, but it didn't fix the problem. I was about to pull the GPU out and send it back under warranty, as a last hail Mary I set APM to enable. F*ck me, everything is working!?. WTF??? It doesn't make sense?. You'd think that setting APM to disable would leave the GPU on all the time by default?.

Hi Guys, Planning a future build. My last build was on an Asus X299 Gaming E II which works ok but has some flaws, like the location of the GPU pcie slots. I made the mistake of going with this board because it looked pretty cool, but there's no point having something good that doesn't work. Another reason I chose this board was because it had 3 M.2 slots for a nvme for each VM. I've since learnt that V disks are simply a folder and if that folder size exceeds the nvme drive capacity it simply spills over onto the array, so one nvme would have been sufficient. I was thinking of going with a Asus X299 WS Sage as it only has one M.2 slot and 7 pcie slots which give me more flexibility with my system design. If I want more M.2 slots I can install a hyper card 4 x nvme to pcie and I would then have 5 x nvme drive pool. It comes with 8 x sata ports, or I can install a HBA. I can also add USB to pcie cards. But I don't know how the pcie lanes are allocated. In Asus literature it says a 4 GPU config of x16 x16 x16 x16 which would be good for 3 x GPUs and a 4 x nvme add in card, but does that disable the other pcie slots? Should I consider a Supermicro board perhaps?. Or do I need more pcie lanes which requires a dual xeon route?. Or Epyc or Threadripper?. What would be the best board/cpu for a 3 gamer Unreal Unraid machine? TIA Peter

Hi Guys, Has anyone passed through the USB controller with all the RGB control on it and booted from a USB PCIE card?

Did you remove th header from the vbios?

Hi Guys, Tried to boot any of my 3 VMs I would get "VFIO: UNABLE TO POWER ON DEVICE, STUCK IN D3" in the VM log. Read on google that a bios update is the solution. Updated the bios and VMs 1 & 2 boot but I still get "unable to power on stuck in D3" error. So I'm close. However, I just realised that when I boot my server the bios splash logo is appearing on monitor 2 which means my server is treating gpu i2 as the main gpu. Furthermore, the gpu pcie speeds are x8 x16 and x8. I think Unraid my have gpu 3 and not releasing it? UPDATE: The BIOS update included the addition of APM Advanced Power Management. The primary GPU would not be picked up as primary GPU and would shut down after two minutes and give a 'could not power on, stuck in D3' error which led me to believe it could be the power saving feature powering down the primary GPU. So I made sure APM was set to disabled, but it didn't fix the problem. I was about to pull the GPU out and send it back under warranty, as a last hail Mary I set APM to enable. F*ck me, everything is working!?. WTF??? It doesn't make sense?. You'd think that setting APM to disable would leave the GPU on all the time by default?. tower-diagnostics-20220619-2010.zip

UPDATE: I searched google using "vfio unable to power on, stuck in D3" and there are numerous posts on numerous virt forums with the same problem that are all solved with a bios update. Now, I can't see how an upgrade from Unraid 6.9.2 to 6.10.3 can change something that would require a motherboard bios update. In the outback in Australia we have a saying "If it ain't broke, don't try and fix it". So I was very reluctant to touch my bios because, even though a lot of people have solved the problem with a bios update, I really couldn't see the connection or as a solution. Plus, a bios update has the potential to create more problems, on top of the problems I already have. Updated the motherboard bios and now Unraid boots properly (sometimes it would not detect and boot from USB) and faster. In the past it would search all 3 nvme and 6 sata drives for a boot record before going to the Unraid USB, now it just goes straight the Unraid USB. Boots nearly as fast as a windows 10 on a nvme drive (I haven't enabled fast boot yet) . VM1 works. VM2 boot into wrong resolution with a code 43 which was resolved with a driver update. VM3 is still failing to power on D3. Still investigating, but definitely making progress

Jumped the gun. VM 1 is working. VM 2 displays a screen but freezes and VM 3 unable to power on stuck in D3. I'm ready to give up. I'm at a loss?

Resolved by editing syslinux as shown HERE

Found THIS thread relating to the "failing to mmap" but I don't understand it or the msi stuff?

Hi Guys, Extremely frustrated and at wits end. VM wont output video. All 3 VMs were working on Unraid 6.9 but can't get them to work on 6.10. Edited xml with multifunction='0n' and put all 3 functions into the same slot Download vbios from techpowerup and removed the Nvidia header It is the primary gpu and it appears as though unraid is releasing it when I start the VM, but I'm not sure?. Do I need to edit the syslinix with apend....... to free up the gpu?. Is it a vbios problem? I'm at a loss. I need to get this up and running for my university studies. It's been down 3 weeks now :/. UPDATE: The BIOS update included the addition of APM Advanced Power Management. The primary GPU would not be picked up as primary GPU and would shut down after two minutes and give a 'could not power on, stuck in D3' error which led me to believe it could be the power saving feature powering down the primary GPU. So I made sure APM was set to disabled, but it didn't fix the problem. I was about to pull the GPU out and send it back under warranty, as a last hail Mary I set APM to enable. F*ck me, everything is working!?. WTF??? It doesn't make sense?. You'd think that setting APM to disable would leave the GPU on all the time by default?. tower-diagnostics-20220616-1349.zip

Hi Guys, When shopping for array hard disks is disk cache relevant if I have a cache drive? Peter

UPDATE: In the last couple of days I've had trouble expanding the iso directory tree to select the vbios, sometimes it wont boot, I wonder if my Sandisk is on the way out?. Replacement is on my To Do list, so I guess I better Do sooner rather than later?. I live in Australia, everything takes forever to get delivered, so it might be a while before I get my new USB and continue with my trouble shooting.

OK. Deleted pcie acs override=multifunction and when I boot I get the attached screen

Have you done this successfully? I've tried passing through the ASUStek usb devices but the Aura software doesn't work? u u

Hi Guys, Upgraded to 6.10 from 6.9 with a clean install, transferred super.dat and plus.key to new config folder. VMs worked flawlessly in 6.9. Recreated VMs in 6.10. Dads VM starts sometimes, Erics VM always starts but freezes at Windows sign in and Isabelles VM nothing at all. I get "Unable to power on device, stuck in D3" in the VM logs. A quick google search shows numerous people with the exact same problem resolved with a motherboard bios update. Why would an Unraid upgrade require a bios update? I'm reluctant to 'try' a bios update to see if this solves the problem because it has the potential to brick the motherboard. So far I have: Edited the xml of each VM so each GPU is in a slot with functions 0,1,2 and 3 Dads Super Computer slot 5 Erics Computer slot 6 Isabelle Computer slot 9 Removed the Nvidia header from the vbios with a hex editor and placed in the isos root folder (A few times Unraid said it couldn't find the rom file?) Edited syslynix so Unraid wouldn't use the GPU's Set PCIe ACS override to Both Set VFIO allow unsafe interrupts to Yes What am I doing wrong? TIA Peter Dads Super ComputerXML.txt Dads VM Log.txt Erics VM Log.txt Erics VM XML.txt Isabelle VM Log.txt Isabelle VM XML.txt tower-diagnostics-20220607-1153.zip tower-syslog-20220606-1901.zip syslinux.cfg

Hi Guys, I want to passthrough my USB 2.0/3.0 controller to see if I can trick ASUS Aura into thinking it's working natively by passing the USB controller it's on through to my main VM. All the other USB controllers are passed through to VMs. I tried booting from a PCIE USB3.0 card but got a sda1 can't mount error. I assume this is because Unraid doesn't like USB3?. Will Unraid boot from THIS PCIE USB 2.0 card? TIA Peter

Resolved. Unraid has export set to no by default.

Hi Guys, Clean install of 6.10.2 from 6.9. Copied super.dat to new config folder, all drives show up in order and array is online. However, the isos folder wont expand when I'm creating a VM, went to windows file explorer to recreate the isos folder and discovered that none of my shares are showing up?. Followed the pinned post but that didn't resolve it. What have I done wrong? TIA Peter

Diag tower-diagnostics-20220605-2139.zip

I bind to the vfio if that's what you mean? I found this error in the VM log -device usb-tablet,id=input0,bus=usb.0,port=6 \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \ -k en-us \ -device qxl-vga,id=video0,max_outputs=1,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pci.0,addr=0x2 \ -device vfio-pci,host=0000:65:00.0,id=hostdev0,bus=pci.0,multifunction=on,addr=0x6 \ -device vfio-pci,host=0000:65:00.1,id=hostdev1,bus=pci.0,addr=0x6.0x1 \ -device vfio-pci,host=0000:07:00.0,id=hostdev2,bus=pci.0,addr=0x9 \ -device vfio-pci,host=0000:65:00.2,id=hostdev3,bus=pci.0,addr=0x6.0x2 \ -device vfio-pci,host=0000:65:00.3,id=hostdev4,bus=pci.0,addr=0x6.0x3 \ -device usb-host,hostdevice=/dev/bus/usb/001/011,id=hostdev5,bus=usb.0,port=1 \ -device usb-host,hostdevice=/dev/bus/usb/001/004,id=hostdev6,bus=usb.0,port=2 \ -device usb-host,hostdevice=/dev/bus/usb/001/007,id=hostdev7,bus=usb.0,port=3 \ -device usb-host,hostdevice=/dev/bus/usb/001/006,id=hostdev8,bus=usb.0,port=4 \ -device usb-host,hostdevice=/dev/bus/usb/001/008,id=hostdev9,bus=usb.0,port=5 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring 2022-06-05T11:22:17.183342Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2022-06-05T11:22:17.183393Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2022-06-05T11:22:18.221871Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2022-06-05T11:22:18.222028Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3