December 5, 20232 yr Hey, running unraid for months without issues. Updated to 6.12.6 right after it was released (coming form 6.12.5). I don't know if it is related to the update, but I didn't change any other thing except unraid. It's an really weird issue, because unraid just turns off without any logging. For example I did an docker update and within downloading unraid just stops and the VM is off and proxmox doesn't show anything... But it's not related to a docker update, because if I run the server and just do nothing (except the docker-apps are running) it turns off, too. This happens within 5 to 15 minutes. Is it possible that there is an issue regarding zfs, because my appdata/docker filesystem is zfs? I'm turned back to 6.12.5 and will check if the same behaviour is still present. Edit: 6.12.5 is now running for 30 minutes without issues. Keep tracking... unraid-diagnostics-20231205-0909.zip Edited December 5, 20232 yr by enJOyIT
December 5, 20232 yr Virtualizating Unraid is not supported, moved here so that hopefully other users doing it can help, if not see if you can replicate the issue bare metal.
December 5, 20232 yr Author Yeah I know it's not officially supported. I think the issue has something to do with zfs! Because my 6.12.5 is still running (since 1 1/2 hour). So maybe bare metal is affected, too! Testing bare metal is currently not possible... Maybe unraid will support VM snapshots... then I'm going to move bare metal.
December 5, 20232 yr 1 hour ago, enJOyIT said: So maybe bare metal is affected, too! There are no other reports so far, and a lot of users already updated, including me.
December 5, 20232 yr 1 hour ago, enJOyIT said: Maybe unraid will support VM snapshots... This is expected for 6.13
December 6, 20232 yr Author Reply to myself 🙂 I think I finally found the root cause... I had too much memory allocated to my proxmox VMs in total.... A bit confusing, since this setup ran for months without any issues... But I dug a bit deeper in proxmox and came to that error: root@pve:~# cat /var/log/syslog | grep oom 2023-12-04T21:45:11.083522+01:00 pve kernel: [3490554.611772] CPU 2/KVM invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0 2023-12-04T21:45:11.193598+01:00 pve kernel: [3490554.611817] oom_kill_process+0x10d/0x1c0 2023-12-04T21:45:11.195148+01:00 pve kernel: [3490554.612109] [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name 2023-12-04T21:45:11.195619+01:00 pve kernel: [3490554.612361] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=qemu.slice,mems_allowed=0,global_oom,task_memcg=/qemu.slice/215.scope So no unraid issue! 🙂
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.