Unraid Array broken - Can't open logs

[Stoigeboiii]

My temperatures have been really high since my house does have AC and I can't open the windows due to air quality. So I have been trying to watch my Unraid stuff. Then it just stopped working. My errors spiked on my parity and then stuff hit the fan. 

 

So if you look at the Screenshots the logs are taking up all the ram (at least I think). I also just can't open logs to see what happened. I closed the Array but it's still stopping. I'm afraid to reboot the system because I have no idea what's going on. I think I missed information but can't tell as I'm freaking out a little haha. Any advise would be amazing. I can answer any questions to help. 

I have ordered new drives incase I need to make any swaps. Also got a new case on the way to try to help with airflow. Again any advise would be amazing!!!

[Electronics Wizardy]

WHat is using the ram? Can you run top?

 

 

Did you diskable the parity drive? What does the smart data say?

 

What logs are here? Can you delete them?

[Mihle]

If you have any dockers and VMs, try stopping them and see if ram usage charges.

[Jarsky]

I'd check to see what's using the memory as already stated. This should tell you what the highest offenders are

ps aux --sort -rss

 

Try reading the syslog through the shell as well see if theres anything obvious showing in there, e.g

cat /var/log/syslog | tail -n 100

 

You could try and check what Processes are still holding files open which are preventing the array from stopping. 

Try running this

lsof /mnt/user && lsof /mnt/user0 | grep smbd

If it lists files as open, you can terminate them by using the kill command, and the PID i.e "kill <PID>"

Once theres no more files being used by smbd, then try stop samba and restart

/usr/local/sbin/samba stop
powerdown -r