Hi, I recently built a new server on new hardware and migrated the disks and flash drive - as well as upgrading to 7.0.1. Since then, I've experienced total system hangs semi-frequently, where the system becomes unavailable, and display output stops. I've tried singularly pressing the power button and waiting for a shutdown, but it won't happen, so I have to force-shutdown every time, giving an unclean shutdown and parity rebuild.

 

Sometimes it lasts 4/5 days before suddenly hanging, sometimes it hangs during the parity check after the last unclean shutdown and must be restarted again. There is nothing obvious I have found that is pointing to causing this issue (e.g. it only happens when a certain container is running).

 

I've run memtest on the memory for 2hrs and seen no errors

 

Diagnostics post-crash and syslog with logs before/after the most recent crash is attached - the crash occurred approx. 5pm 15/04, there appears to be no output in the syslog at this time

 

Thanks

tower-diagnostics-20250415-1934.zip syslog-192.168.0.117.log

Nothing relevant logged, but since memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

Unfortunately I'm still encountering this issue. I've since tried either RAM stick individually with the same result - so I don't think it's the RAM. Although, I did also install the Intel GPU TOP plugin (I use plex and passthrough the iGPU for transcoding - just an idea I had) and now get a different error when it crashes (see attached syslog - starts on a line with "May  5 02:53:01 Tower kernel: BUG: kernel NULL pointer dereference, address: 00000000000004e8"syslog-192.168.0.117 (1).log

tower-diagnostics-20250505-1119.zip

It's the same scenario in that it crashes after a couple of days running

 

Also attached the most recent diagnostics file

There are multiple call traces logged, but can't see if they are software or hardware related, 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, including the docker containers.