Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Unraid Array broken - Can't open logs

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!!!

chrome 2020-10-04 at 22.41.10.png

chrome 2020-10-04 at 22.41.30.png

Link to post
Share on other sites

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?

Link to post
Share on other sites

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

“Remember to look up at the stars and not down at your feet. Try to make sense of what you see and wonder about what makes the universe exist. Be curious. And however difficult life may seem, there is always something you can do and succeed at. 
It matters that you don't just give up.”

-Stephen Hawking

Link to post
Share on other sites

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



Desktop: Ryzen 7 2700x | Aorus X470 Gaming Ultra | EVGA RTX2080 Super | 32GB (4x8GB) Corsair Vengeance RGB Pro 3200Mhz | Corsair H105 AIO, NZXT Sentry 3 | Corsair SP120's | 1TB Crucial P1 NVMe, 4TB WD Black | Phanteks Enthoo Pro | Corsair RM650v2 PSU | LG 32" 32GK850G Monitor | Ducky Shine 3 Keyboard, Logitech G502, MicroLab Solo 7C Speakers, Razer Goliathus Extended, X360 Controller | Windows 10 Pro | SteelSeries Siberia 350 Headphones



Server 1: Fractal Design Define R6 | Ryzen 3950x | ASRock X570 Taichi | EVGA GTX1070 FTW | 64GB (4x16GB) Corsair Vengeance LPX 3000Mhz | Corsair RM650v2 PSU | Fractal S36 Triple AIO | 10 x 8TB HGST Ultrastar He10 (WD Whitelabel) | 500GB Aorus Gen4 NVMe | 2 x 1TB Crucial P1 NVMe | LSI 9211-8i HBA


Server 2: Corsair 400R | IcyDock MB998SP & MB455SPF | Seasonic Focus Plus 650w PSU | 2 x Xeon X5650's | 48GB DDR3-ECC | Asus Z8NA-D6C Motherboard | AOC-SAS2LP-MV8 | LSI MegaRAID 9271-8i | RES2SV240 SAS Expander | Samsung 840Evo 120GB | 5 x 8TB Seagate Archives | 10 x 3TB WD Red


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now