I've been using unraid for probably 1.5 - 2 years with the same hardware and almost no issues. I rarely rebooted or did any work besides an O/S upgrade.

 

I'm currently on 6.0beta14b and this issue was occuring on beta6 as well. I tried the upgrade to fix it.

 

My server will run for a couple of days and then just stop responding. If I try to telnet, it says "connected" and then nothing.

 

telnet session:

Air:~ aus$ telnet 192.168.1.2
Trying 192.168.1.2...
Connected to fileserver.
Escape character is '^]'.

 

then I reboot and all seems to be well for a while again (see attached syslog).

 

I can't seem to "catch" the issue and figure out what is causing it. It sure does seem like a hardware failure, but I don't know how to troubleshoot and try to find out what is causing it. Any ideas?

syslog.zip

Do you have a monitor attached directly to the server?  You may need that to see if there are any messages indicating the reason for a crash.

 

You could also try running the memtest option from the unRAID boot menu to see if perhaps you have a RAM stick going bad.    That can cause all sorts of unpredictable faults.

Sorry, I left out some detail there. After it occurred twice, I connected a monitor. There is nothing there indicating a crash. When I looked at it this morning (it was frozen and non-responsive) it was showing that it had just loaded sickbeard, but no errors or anything.

 

I also tried extending the syslog to 3 days to try to capture it, but as you can see by my log, it didnt seem to keep it on reboot. Does syslog ever persist through a reboot? Maybe I lost my syslog setting when I upgraded to latest beta.

 

Thanks for the idea though. I'm real tempted to just order all new hardware, this thing has been around forever already.

Thanks for the idea though. I'm real tempted to just order all new hardware, this thing has been around forever already.

With no obvious errors, the first piece of hardware I'd replace would be the power supply