December 15, 20223 yr I have build small Unraid server using HP Elitedesk 800 G4 i5-8500t with double nvme 500GB drives ond 8GB of memory (will be upgraded to 32GB soon). Only have one VM - Windows Server. But I noticed unraid is crashing very often, I checked cooling - CPU have around 44C, nothing else noticed. Attached syslog syslog hydra-diagnostics-20221215-1010.zip Edited December 15, 20223 yr by mucflyer added diagnostics
December 15, 20223 yr Author Fresh crash 10:56 - 57 just about now. Logs attached. I was installing WS2022 and in the middle of the virtio drivers installation it crashed, not sure if it's related or not. Added 32GB of RAM - another crash happened after few minutes after starting Windows VM, and another after starting array, before I started VM or docker hydra-diagnostics-20221215-1100.zip syslog Edited December 15, 20223 yr by mucflyer
December 15, 20223 yr Author 2 hours ago, ChatNoir said: I think that JorgeB means to run a test from https://www.memtest86.com/ Will do, but I already replaced whole RAM with other one (was single 8GB, now I have two 16GB) still the same, so I think memory can be excluded ? Edited December 15, 20223 yr by mucflyer
December 15, 20223 yr Community Expert One more thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
December 15, 20223 yr 2 hours ago, JorgeB said: One more thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. This is exactly what I did. Ran it as a NAS for a few days over the weekend while we was gone then went back to normal and turn on 1 thing at a time. We use Plex a lot so I turned on only Plex docker than each day I turned on another and another. Come to find out one of my dockers wasn't configured right and it was eating up resources and crashing. Sometimes the simplest things are the key to fixing things.
December 16, 20223 yr Author I let it run with stopped array overnight. 9 Hours withoit crashes. I started array in the morning and windows vm, immediately crashed and rebooted. It seems it can be virtualisation related, but how to get any logs or clues what is happening and why?
December 16, 20223 yr Community Expert Are you passing-though any hardware to the VM? If not try disabling vt-d.
December 16, 20223 yr Author 3 hours ago, JorgeB said: Are you passing-though any hardware to the VM? If not try disabling vt-d. I did disabled vt-d , was about to say, looks better but crashed after 1 hour and 42 minutes
December 16, 20223 yr Community Expert Could be some kvm related compatibility issue with that hardware and the kernel, you can try an older Unraid release to see if it makes any difference, like 6.10.3
December 19, 20223 yr Author On 12/16/2022 at 1:13 PM, JorgeB said: Could be some kvm related compatibility issue with that hardware and the kernel, you can try an older Unraid release to see if it makes any difference, like 6.10.3 Seems stable on 6.10.3
December 19, 20223 yr Community Expert Solution Suggest staying with that release for now, then try v6.12 when available, it will use a different kernel.
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.