November 3, 20241 yr Hello dear people , One of my VM servers started to act up , it doesnt get much use (only like 2 out of 10 VMs are used) attached syslog and diags , could that be cache drive? how do i check it? parity seems ok and smart looks fine too. Point me in the right direction maybe? syslog newtechsrv-diagnostics-20241103-1213.zip
November 6, 20241 yr Community Expert Looks like your aladin VM is breaking. 2024-11-03 10:17:25.899+0000: 5052: error : virQEMUFileOpenAs:11390 : Failed to open file '/mnt/firstvmbtrfs/VMs1/aladinVM/aladin - Copy.img': No such file or directory Nov 3 12:17:20 NewTechSRV emhttpd: shcmd (78): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 Nov 3 12:17:20 NewTechSRV kernel: loop3: detected capacity change from 0 to 2097152 Nov 3 12:17:20 NewTechSRV kernel: BTRFS: device fsid daa59398-7d6e-414b-b36a-22bb25496535 devid 1 transid 724 /dev/loop3 did you change vm settings and file paths or move the vm from /mnt/user/domaind to /mnt/diskname/domains? double check share and that mover isn't breaking the vdisk image path.... You may need to double-check xml and set to path that the unraid share domains is using... not enough info, some data needed ins't captured via the diag. But this seems more like a path/setting was changed and not set correctly. *diagnostic also has the syslog. Edited November 6, 20241 yr by bmartino1 typo
November 6, 20241 yr Author The path to the disk is not what is in the log at all: 2024-11-03 10:17:25.899+0000: 5052: error : virQEMUFileOpenAs:11390 : Failed to open file '/mnt/firstvmbtrfs/VMs1/aladinVM/aladin - Copy.img': No such file or directory And it is working , untill it freezes , what causes it to try to access some old path , i think there was a time when i did some stuff with the VM and the image was image - COPY.img but after i finished i i deleted the copy , so its not there , but what calls for it?
November 6, 20241 yr Community Expert The syslog is after a reboot, enable the syslog server and post that after a crash.
November 6, 20241 yr Author 8 hours ago, JorgeB said: The syslog is after a reboot, enable the syslog server and post that after a crash. This is after crash, there is nothing, and than it froze and nothing was written , I will reapply VM options , and if it crashes again I will post updated syslog
November 26, 20241 yr Author On 11/6/2024 at 2:54 PM, JorgeB said: The syslog is after a reboot, enable the syslog server and post that after a crash. ok so i understood where i got it wrong , i posted the diags file after the boot , so now ill post both , the after and before , which does contain stuff before there was no access to webgui and VMs. What i ended up doing is SSH into unraid and reboot it. newtechsrv-diagnostics-20241126-0818-Before.zip newtechsrv-diagnostics-20241126-0916-After Reboot.zip
November 26, 20241 yr Community Expert There's a crash logged but unclear to me what caused it, if you leave the VM off, does the server run stable?
November 27, 20241 yr Author 20 hours ago, JorgeB said: if you leave the VM off, does the server run stable? The server has nothing besides 2 VMs running on it at all times. Technically 3 , but only 2 of them used sometimes.
November 30, 20241 yr Author today i rebooted the server via webgui > shell > reboot and it did not boot , so i had to ask someone to unplug the power , and plug it back in , and than it booted , and here is the syslog: maybe @JorgeB you could shed some light why it didnt boot , also i think i figured that syslog is the actual log file you wanted all along syslog.txt
November 30, 20241 yr Community Expert 6.12.14 release I recommend a upgrade to the latest stable. Unclean Shutdown Detected FCP is showing update savable for CA and others... Looks like your mover script failed to move/do something.. crond[1553]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null *Double check disk shares and run mover manual Can ignore but in the log: Hardware and ACPI Warnings: PCI and ACPI-related messages indicate potential resource allocation issues or BIOS misconfigurations. Known ACPI issues... The docker0 bridge reports disabled states for connected interfaces kernel: docker0: port 1(vethf076c21) entered disabled state kernel: device vethf076c21 left promiscuous mode kernel: docker0: port 1(vethf076c21) entered disabled state But this is normal first docker run virtual bridge creation for networking... nothing major outside of the cron / scheduled move operation... General troubleshooting: Monitor and Test Stability: Use tools like htop or iostat to monitor CPU, memory, and disk I/O performance. Run a parity check to ensure array health.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.