I've been running this headless for a few years now, as a Media Server/NAS, and I'm not sure if it started after an Upgrade or not, I believe it did about a year ago, that's my memory. I didn't really know what was going on initially, as I haven't been using it much anymore.

However, after a while, I'd notice that all the services running on the machine and the data shares were not accessible, no way to get it to respond without a hard reboot, or waiting, sometimes just a few hours, sometimes longer.

I also noticed that memory usage was slowly climbing, then would drop after it came back online, so makes me wonder if it's something to do with the swap space? Tried doing weekly restarts, but that hasn't really seemed to help as much as I thought it would.

I was doing some reading and thinking about trying to manage the memory somehow, to see if that might resolve the freezing, and came across:

https://github.com/hakavlad/nohang

Or am I going straight to solution mode without figuring out what's actually wrong? I cannot see any errors when I tried checking system logs, and so not really sure, if someone might have some advice please?

The first thing I'd do is ssh in and run htop. It sounds like something is filling up.

In the days of 2.x.x kernels, 3.x.x kernels were experimental ones and my kids loaded one on their box once to sound 'with it' to their buddies on IRC. That 3.x.x kernel had a memory leak and gave exactly the symptoms you describe. The command 'free -h' gives memory stats including free memory, and 'df -h' does the same for disk usage.

Thanks, will try, I'm keeping an eye on the RAM usage via the OMV console, but so far nothing has happened. Sometimes it can take days or even a week or two before it happens.

Then it's more probably linked to a partition running out of space, a particular application, or something like that. Tell us anything else you know. All of us hate being given information in drip[ feed. It driver helpers away, because you're withholding what we need to help you.

It seems to me that the jump in kernel version might also contributed to the OPs issues. If I was to go forth in trying to further diagnose this issue is for the OP to try and gather as many logs as possible.