SlimeKnight

I've ran a few passes and everything checks, I also had this problem on 16GB of RAM when I first setup the server. When looking at my logs from when I was actively on the server after coming home and starting Mover I see this section here. Jun 24 13:39:32 Cloud emhttpd: shcmd (601506): /usr/local/sbin/mover start &> /dev/null & Jun 24 13:39:33 Cloud emhttpd: read SMART /dev/sdj Jun 24 13:39:50 Cloud emhttpd: read SMART /dev/sdk Jun 24 13:40:02 Cloud emhttpd: read SMART /dev/sdm Jun 24 13:42:35 Cloud kernel: mpt3sas_cm0: SAS host is non-operational !!!! Jun 24 13:42:36 Cloud kernel: pcieport 0000:02:08.0: Unable to change power state from D3hot to D0, device inaccessible Jun 24 13:42:36 Cloud kernel: mpt3sas_cm1: SAS host is non-operational !!!! Jun 24 13:42:37 Cloud kernel: mpt3sas_cm0: SAS host is non-operational !!!! Jun 24 13:42:37 Cloud kernel: mpt3sas_cm1: SAS host is non-operational !!!! That happens and the server stays on but is unresponsive to either webgui or anything physically at the server until a hard shutdown. I'm unclear if it's something with my LSI adapter or the drives themselves starting the issue though.

Heres that file. cloud-diagnostics-20250624-1500.zip

I've been having issues with my server that pop up randomly, I can be actively using the server or just coming home to pull it up and it's still showing on my router and powered on, can hear everything humming away but will no longer be accessable. I finally got logging setup and have a file to start from but I'm unclear on where to start with the problem, any help in the right direction would be much appreciated. syslog-previous