Mokkisjeva

Thank you for the docker! Had infinite issues with this pack on my Windows Game Host (several MC servers hosted prior no issues) and holy this is seamless and pain free. An absolute noob question, is it possible to to run commands somehow? Currently I need to do it myself while logged in to the server as OP which is a bit of a hassle when I need to fix something for others who's online. Edit; I came across gorcon/rcon-cli so I can now rcon in (also had to add new port for rcon).

Oh my... now my cache pool reports: 'Unmountable: wrong or no file system' Guess 40$ USB flash drive was not the cheap fix I was hoping for. Back to AMD, fingers crossed.

I've cycled all ram sticks, same errors. Could the actual OS (files) on the flash drive be bad? When I migrated USB drive I didn't do a clean install, just install from the backup I did. So the problematic files would still be present? I'm clueless so just thinking out loud here...

TLDR; I have loads of SQUASHFS error and I can't figure out what's wrong. Changed USB port, changed USB drive, updated unraid, updated bios, ran memtest for 13hours with no errors... Potentially unrelated context?: About a year ago I got myself an I9-14900k for my gaming PC, things didn't turn out quite as planned and I ended up with a 14900k collecting dust, so figured I could just get a motherboard for it and put in it my unraid server. Now I've had my unraid server for probably 10years or so running AMD with no issues apart from user errors. But as soon as I swapped to the I9 I started having issues with my VMs being very unstable, they'd freeze between an hour to a week so it was hard to figure out what was wrong, but isolating a p-core to each VM made it much better, like they'd freeze up maybe every two weeks or whatever, and I've had my unraid like this since then. But now (past month or two) things gotten worse. Unraid webui is unresponsive, but the dockers and VM running fine, dumb as I am I didn't figure out it was just the webui so I had to reboot the server which always made me have to restart the docker container else no dockers were available. So every other day I restarted unraid and disabled/enabled dockers, and instead of taking my time figuring out what's wrong I obviously neglected it so it got worse. Now when I restart the unraid I need to restart the webui and even run '/usr/local/sbin/emhttp start' to get the webui online. And now I've had it, time to figure out wtf is going on. After some searching it seems as the SQUASHFS errors are the most critical ones and could probably be the reason for emhttp failing to start? Either way, new flash drive was the answer I found. Got a new samsung flash drive, migrated and same errors. I swapped to a different USB port and same errors. Ran memtest for 13h which returned with 6passes and no errors. Updated unraid from 7.0.0 to 7.0.1, did not fix anything. I have now disabled VMs and dockers and it looks like I don't have issues with emhttp not starting any longer, coincidence or not I can't tell. Which other logs would you gurus need in order to help me figuring out what's wrong? Edit: When I get the server running, it'll run for a few days without issues. And when the webui dies I can restart it through terminal. But I'd prefer to have it like it used to be with my AMD system. Turn it on, and it can stay on for probably a year without any hickups. syslog.txt tower-diagnostics-20250412-1017.zip

At the time of changing hardware i upgraded Unraid too so when I read your post I was optimistic that it could just be an unraid issue, but I was still tempted to going back to the AMD system as I too run several VMs and are dependent on them. It's been an absolute shitshow the past few weeks trying to solve this problem and whatever information I could find on the internet has been tried. Then I came across a gaming VM optimization thread where it was recommended to isolate a core for the VM I got the idea to try it. I mean, it's either try that last thing or go back to the old AMD system. I hardly know what I'm doing most of the time when it comes to server stuff so finding a solution to me doesn't mean I know what the correct solution actually is. So if anyone see this and can give an educated guess to what the initial problem is and if there's a solution outside isolating cores then great, until then that's what I'm going with. I do run a i9-14900K (was supposed to be in my main rig but expensive mistakes were made) which has enough cores I can "waste".

I had the same issue, I too upgraded unraid but thought the issue was because I changed from AMD to Intel CPU. Figured it would be more likely that the hardware change was the cause as the VM has been operating flawlessly for years before that. I finally got it fixed by just isolating a core for the VM, if you haven't done so maybe give it a try?

The solution was to isolate a core for the VM. Never had to do this with the AMD CPU, but oh well. It works, that's what matters.

How should I troubleshoot this problem? I've had 3 VMs running for years without any problems, then I upgraded the hardware and nothing seemed to work. I made a new VM just to see if it was settings in the VM that didn't do well with the new HW but this too have same problem. The VM might run anywhere between seconds to days before it inevitably crashes. error: kvm run failed Invalid argument RAX=fffff8062437040c RBX=000000000000000c RCX=000000000000000c RDX=0000000000000071 RSI=000000000000000c RDI=ffffae00115f9e68 RBP=000000000000000c RSP=ffffae00115f9d78 R8 =ffffae00115f9e01 R9 =0000000000000001 R10=fffff806243704e0 R11=0000000000000000 R12=00000000ffffffff R13=000000f28f706ad5 R14=0000000000000000 R15=fffff80624c04468 RIP=fffff806243704f2 RFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 00000000 00409300 DPL=0 DS [-WA] DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] FS =0053 0000000000000000 0003fc00 0040f300 DPL=3 DS [-WA] GS =002b ffffae00115df000 ffffffff 00c0f300 DPL=3 DS [-WA] LDT=0000 0000000000000000 ffffffff 00c00000 TR =0040 ffffae00115ee000 00000067 00008b00 DPL=0 TSS64-busy GDT= ffffae00115effb0 00000057 IDT= ffffae00115ed000 00000fff CR0=80050033 CR2=000001c579302000 CR3=00000000001ae000 CR4=00350ef8 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff4ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=cc cc 66 90 90 ba 70 00 00 00 8a c1 ee 90 ba 71 00 00 00 90 <ec> 90 c3 cc cc cc cc cc cc cc cc cc cc cc 66 90 90 44 8a c2 ba 70 00 00 00 8a c1 ee 90 ba This is what I find in the log. Trying to resume the VM I get this error: internal error: unable to execute QEMU command 'cont': Resetting the Virtual Machine is required I've tried different pinning, i1440 / q35, ram size and non of it seem to matter. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='15'> <name>Power Automate Bot</name> <uuid>99500cc9-3605-0037-fc4c-2809e1ec0052</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>24</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='7'/> <vcpupin vcpu='8' cpuset='8'/> <vcpupin vcpu='9' cpuset='9'/> <vcpupin vcpu='10' cpuset='10'/> <vcpupin vcpu='11' cpuset='11'/> <vcpupin vcpu='12' cpuset='12'/> <vcpupin vcpu='13' cpuset='13'/> <vcpupin vcpu='14' cpuset='14'/> <vcpupin vcpu='15' cpuset='15'/> <vcpupin vcpu='16' cpuset='16'/> <vcpupin vcpu='17' cpuset='17'/> <vcpupin vcpu='18' cpuset='18'/> <vcpupin vcpu='19' cpuset='19'/> <vcpupin vcpu='20' cpuset='20'/> <vcpupin vcpu='21' cpuset='21'/> <vcpupin vcpu='22' cpuset='22'/> <vcpupin vcpu='23' cpuset='23'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/99500cc9-3605-0037-fc4c-2809e1ec0052_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='12' 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/domains/Power Automate Bot/vdisk1.img' index='2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.248.iso' index='1'/> <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='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='0x04' function='0x0'/> </controller> <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> <interface type='bridge'> <mac address='52:54:00:40:48:38'/> <source bridge='br0'/> <target dev='vnet13'/> <model type='e1000'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-15-Power Automate Bot/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> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <graphics type='vnc' port='5901' autoport='yes' websocket='5700' 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'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> I don't seem to find much useful in the windows logs itself either, but that doesn't necessarily mean there's nothing there, rather my limited knowledge. The Unraid Server itself works flawlessly, it's just the VMs that keeps dying and needs to be forced stop and started. And to me it's weird it can run for days before it crashes. Any help is appreciated.

Since I can't find any topic regarding this I'm quite sure there's something I don't understand, not necessarily something that's wrong. But, looking at attached picture, how come I get 1tb and not 1.5tb assuming it's 1tb for redundancy? 1tb+1tb+0.5tb = 1tb? Edit: From what I can understand after some googleing is that zfs does not work quite like how I thought it would in this regard as to how I used to have it with btrfs. So I need to replace the 500gb with a 1tb disk to get 2tb I guess then?

------------------------------------- ---OpenTTD not found! Downloading,--- ---compiling and installing v1.11.0--- ---Please be patient, this can take-- ---some time, waiting 15 seconds..--- ------------------------------------- ---Successfully downloaded OpenTTD v1.11.0--- /opt/scripts/start-server.sh: line 60: /serverdata/serverfiles/compileopenttd/openttd-1.11.0/configure: No such file or directory make: *** No targets specified and no makefile found. Stop. make: *** No rule to make target 'install'. Stop. ---Something went wrong, couldn't install OpenTTD v1.11.0--- Any help regarding this? Am I supposed to install anything manually first or?

Can you elaborate? I'm quite .... bad at this. Where should I run these commands?