Hi All,

 

Over the last week or so I've been getting some real strange issues with my server. It will just freeze. I have a monitor connected and it doesn't wake up when I tap a keyboard key.

 

Once I did see some output on the console which was a Kernel panic, but instead of taking down details I stupidly just rebooted the box thinking it was a one off.

 

Can't really figure this one out...thought it could be docker macvlan - but mine is set to ipvlan. Thought it could be realtek network drivers, but tried those and it didn't help. Wasn't using that network card anyway so went into the bios and disabled it along with anything else I didn't need hardware wise (wifi card, bluetooth, sound etc.). Tried updating to the latest version of unraid (I was only a few minor revisions behind anyway) but hasn't made any difference. Thought it could be something to do with parity checking as the server would start a check after a bad start but I cancelled the check and it still freezes after some random amount of time.

 

Tried a memtest but it didn't come up with any issues either, so now I'm out of ideas. 

 

I've attached my diagnostics file and hopefully you guys can figure this out.

 

Thank you!

trinity-diagnostics-20240408-1022.zip

Just happened again and I saw out of the corner of my eye the system having a kernel panic before the screen going blank ...again didn't really catch anything. If the diagnostics file above doesn't hold that info, is there is somewhere I can pull the kernel panic info to post here?

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field. 

Thanks - will do this now.

 

Its just crashed again - now the system doesn't stay up for more than 5 minutes before a panic.

 

It held on the error screen though...pasting here and then gonna reboot and do a syslog setup

Well that didn't take long.

 

Not sure if it was a kernel panic but the system rebooted which I haven't seen before.

 

Diags attached (this time with syslog hopefully enabled)

trinity-diagnostics-20240408-1107.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.

Arrggh...super annoying. Took your advice - disabled all but my plex docker container and things seemed totally stable. It was all fine and dandy. Ended up disabling the syslog stuff as I didn't want any wear and I thought the problem had been cracked. Didn't need the additional dockers anyway so was content to leave it like this.

 

Then just a minute ago I come back to a kernel panic. Took a photo of the screen in case there is anything it can allude to, but otherwise think this is either the plex docker container or just a hardware issue and I'm gonna have to rebuild the whole thing to figure it out.

 

Photo attached - All help appreciated

Plex container has been known to crash servers, seen it multiple times in the forums recently.

Just done a search and yea seems to be a thing at the moment. Will keep an eye on those threads, and update this one if there is an answer there.