Ok so I apologize for the long winded story - I'm gonna dive into a little background.

 

Been using unraid for a few years now, I'd say I'm an intermediate user. I have always had a mobo/cpu/ram from either my old gaming rig, or a friend's hand me down server hardware. Currently I'm running an X8DTH supermicro motherboard with dual x5650 cpus and 16gb of ram (more backstory to the ram incoming). I use my server to host tv shows and movies via plex over chromecast, 24/7 video recording from two security cameras via zoneminder, run a couple VMs for windows and linux, run an rsnapshot to an offsite unraid server that I installed at my brother's, and I'm starting to experiment with homeassistant and smart home devices. 

 

Here's where my problem comes in. The server runs great when it's running, but it won't run consistently for more than one to three days now. I thought the initial culprit was the ram, but I ran a Memtest from the unraid boot options and it passed. My friend gave me 28gb of ram (he's very generous), and I could only get 16gb of it to work together at one time. The motherboard may have some dead ram slots, or I'm not installing the ram into the proper slots...I don't know. But I expected the ram to be the issue. 

 

I've read the syslog i've attached, and can't find anything that resembles an error around the last time that it was running. The last crash that happened seems to have occurred after 4:00am on April 4th, and I restarted the machine this afternoon around 5:30p - I was gone all day on the 4th. I did make sure to set it up to persist the syslogs onto the flash. 

 

I've also attached the diagnostics file - that should have a wealth of information - again I can't find anything that I think helps me there. 

 

Finally, I've attached the extended scan from fix common problems, again not much help. It mentions a bunch of filename issues that windows might have a problem with, probably not causing my issue.

 

My plan is to replace everything but the hard drives and upgrade, but before I spend $800 I want to see if this fantastic community can help me solve the mystery!

nas-diagnostics-20200405-2002.zip syslog Extended scan fix common problems.txt

Just a bump here. Crash happened again and no help from syslog. Also crashed at a different time (about 6p yesterday) so it's not because of some nightly process that is having issues. I'm really thinking best bet would be to just replace it all unless someone has any ideas... 

When your server crashed, did it freeze or crash?

1. Freeze = internal light still on and/or display still showing stuff and/or you need to press and hold power button to hard shutdown before being able to switch on.
2. Crash = light off, no display, a normal press of power button to switch it on.

If it's (1) then potentially issue with CPU / mobo / RAM.

If it's (2) then potentially power related issue e.g. PSU problem or even a shorted connector.

 

Your syslog does not show any clue at all so it will be hard to diagnose so I can narrow it down to the above.

 

Btw, the mover constantly tries to move your libvirt and docker images. Check your share settings.

Thanks for the response testdasi! It is a freeze. Fans are running, system looks to be functional but there is no access to the webgui or any of the applications running, or the samba shares. I have not tested whether there is graphics output of the unraid command line, but I don't anticipate it showing. I either have to do a hard shutdown or hit the physical restart button, which also works. 

 

Follow on question to the libvirt and docker images. What settings should I be looking at specifically? Is it because it's trying to move those files onto the array but they already exist on the disk in the array? Should I copy them off the unraid machine, delete them, then put them back on the array in the right position? 

Hey guy - I REALLY hope this helps, because I've been fighting the same thing silently -- only my story is slightly longer because it spans six CPUs, two motherboards, and 3 sets of 6x4GB of RAM, trying to track down the fscking problem, lol

 

First, log into your terminal and run this. It disables all C-States on all processors. It won't persist across reboots, so if it breaks anything or doesn't help, you can just move on. If it DOES help, you can disable them in the BIOS and/or via bootscript in unRAID itself.

 

for cpus in /sys/devices/system/cpu/cpu*/cpuidle/state*/disable; do echo 1 > $cpus; done

 

If it works, you can try disabling "deeper" c-states and keeping the "shallower" ones. Good luck!

 

EDIT: Woof, didn't notice this was from a full year ago. Is it seriously 2021 now? Sorry, lol. Hope it helps anyway!

Edited April 28, 20215 yr by codefaux
Necro-apology