Server has been perfect for years. Only change I've made recently is adding an HBA for more drives:

https://amzn.to/4r38ruu

Drives show up fine with the HBA but for the second time now in a week server has fully locked up. Only way to recover is a hard shut down and boot back on.

I've enabled the syslog server so that hopefully whatever is causing this will persist in the log, but just want to make sure that's all I need to to do catch the problem. Is there any other way to see why this is happening?

Attached the diagnostics file as well if that can help.

limnas-diagnostics-20260120-0842.zip

The diagnostics do not seem to include a file from the syslog server. It might be worth posting a screenshot of your syslog server settings so we can check they are correct.

Sorry if I'm being an idiot, but is the screenshot in the post not my syslog server settings?

40 minutes ago, lotetreemedia said:

Sorry if I'm being an idiot, but is the screenshot in the post not my syslog server settings?

Yes - I’m the idiot 😊

The settings just put the server into listening mode for log messages from another machine. To actually get anything logged for this machine you either need to use the Mirror to flash option or put your server’s IP address into the remote server field. This is described in the link.

much appreciated. I can see a log file being populated in the directory I added "local syslog folder" setting which is on my array. and I have "localhost" as the remote server so seems like I should be good the next time it hangs.

32 minutes ago, lotetreemedia said:

should be good the next time it hangs

Yes, but you will need to separately post that file as it is not automatically included in diagnostics.

No worries! will make sure to do that when she locks up!

So been a week without any crashes and I the only thing I added was some fans blowing directly onto the HBA. Have a feeling it was overheating and causing a full lock. Will wait another week before calling this one solved!