I've had the occasional crash / *something that makes the server stop working and responding to anything* a few times now, with some months in between and once I could identify some plugin (I think it was some GPU statistics?) when it happened more often.

 

But now I've had to leave and the server went unresponsive twice in 2 weeks (Crashed Mar 28th, restarted on Apr 3rd, crashed on 5 and only managed after reseating the usb drive...) and it became unresponsive again after less than 3days. -> API lost connection, no pings got answered, Dockers and VM were unaccessible. I don't know whether it still did something, it was still powered on (fans running), but no new syslog entries.

I - again - can't find anything telling me what caused it. In the syslog I could find the Parity Tuner Plugin spamming errors - because I had to reset the server to start it again and it then had the flags for automatic and manual parity check (although I didn't start it manually? Must be from the "crash")
I'm adding the syslog from after the restart on Apr 3rd -> End Apr 5th, I only changed the hostname (now I know that is useless because it appears in the anonymized diagnostics) and where the warning "Parity Check Tuning: ERROR: marker file found for both automatic and manual check P" happened multiple times so it only appears once.

Since I haven't really done any changes apart from updating docker and unraid, this is really bothering me.
 

Steps I have planned:

- run a full memtest  (although the server has quite high utilization on ram/cpu, so I can't see why defective memory wouldn't have shown earlier...)

 

If I can't figure out why this is happening (and I don't have IPMI to reset it remotely) I'm thinking of either running Unraid as VM on proxmox (migration might be easy or impossible... ) + unloading the most important services to a micro server (Nextcloud, Homeassistant)
In terms of resetting, only easy solution I can up atm is power cycling with a remote contrallable power plug... (could hurt the hardware eventually, but then I can't see a cheap alternative... if I don't want to go for a pikvm or similar)

 

syslog-192.168.2.101-shortened.log unraid-diagnostics-20240417-1828.zip

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/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.

I guess hardware issue is one of the downside of reusing outdated hardware 😕
I'm gonna try relocating some important services, then run the memtest (maybe other hardware tests on live os I have lying around) and then the "slow and one service after another".