tool666schism

Hey all, I could really use some help here. I'm banging my head against the wall trying to fix this issue. I attempted to update nextcloud using the web gui (i know, my first mistake) It failed on Step 7. I have tried multiple times to get past it, and nothing I do seems to work. I can no longer get into nextcloud as it's hung at the "update in process" page. Does anyone have any clue where to go from here? Error I'm getting: [✘] Delete old files failed core/shipped.json is not available Update failed. To resume or retry just execute the updater again I found other threads where people mentioned just creating the file.. but the file already exists within the /var/www/nextcloud/core directory EDIT: Had an appdata backup from yesterday, just went ahead and restored it to get nextcloud working again. Going to leave it for today and try the upgrade again tomorrow using the recommended steps outlined in the first post.

No response here and I have tried just about everything. Eventually I had to just roll back the update. Rolling back the update resolved the issue.

I attempted to delete libvirt.img and have it recreate to stop the issue but it is still persisting. Posting the updated xml for my VM. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Ash-Test</name> <uuid>66a2a82d-d8a3-6b64-5d13-92c1c9b915fc</uuid> <description>ssd passthrough</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/66a2a82d-d8a3-6b64-5d13-92c1c9b915fc_VARS-pure-efi.fd</nvram> </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' migratable='on'> <topology sockets='1' dies='1' cores='3' threads='1'/> <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='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_860_EVO_500GB_S59UNJ0MC07008P'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/nvme-Samsung_SSD_970_EVO_1TB_S5H9NS0N937318Z'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.190-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='nec-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <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='3'/> </input> <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='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc339'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04d9'/> <product id='0xa09f'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> </domain>

Hey all, I am fairly new to unraid so please forgive any ignorance on my part. I'm having some trouble getting my VM to run after upgrading unraid. I am tempted to roll back the upgrade, but would rather just fix this outright if possible. The weirdest part of this issue, is that if I reboot the unraid server itself, the VM will start just fine for the first launch. After shutting down the VM and then trying to start it again is when I notice my issues. No amount of subsequent force stops or starts will get the VM running and as soon as I reboot the entire server, I can start the VM once more. The first signs of trouble when starting the VM are that I do not see activity on 2 of the 3 cores I have set for the VM to use. 1 of the 3 will go to 100% utilization but the remaining 2 will sit at 0. I get no video output at all. The VM won't shut down on it's own and a force stop is needed. Was wondering if anyone could point me in the right direction as to where to begin troubleshooting this issue. I've checked any logs I thought might be relevant but I'm struggling to understand what exactly is happening here. I've posted the XML for the VM below as well as attached my diagnostics log. Not sure if either of those are helpful or not. tower-diagnostics-20210406-1017.zip vmconfig.txt

Ah, yea I was avoiding the debug variable for the exact reason you mentioned. Thanks very much I will see if I can get a feature request going with the Valheim guys. Much appreciated. Also, great work on this. Super easy to use/set up. Highly recommend.

Could anyone point me in the right direction here. Trying to determine how I can access connection logs for the Valheim server I set up. I attempted to just open the direct console for the Valheim container but I do not know steamcmd at all. Server starts fine, I can have quite a few people join, but I have one individual who keeps getting errors. Trying to determine if he's actually hitting the server or not.