The last few days my server has been shutting down on its own. I usually notice it when my Sagetv is trying to record shows to the server. Sometimes I am ripping movies and it will say that the server is not found. Any ideas what could be causing this?

Capture a syslog using the tail method described here: http://lime-technology.com/forum/index.php?topic=9880.0

Here is my system log because the server shut down again tonight.

 

tower.txt

It looks like it shutdown within 5 minutes of starting. Run a memtest overnight. Post full system specs and SMART reports for all drives.

Sounds a bit like some higher end gaming systems i have worked on - you stress them and there is a problem, system shutdown to protect itself. Usually this is the CPU overheating or the PSU cutting out. Have you checked those?

 

Shawn

Wife said her tv show recordings were pixelated. I saw the recordings tonight and they were horrible and unwatchable. I am using sagetv with hd homeruns recording to my unraid server. Wondering if the server is not fast enough to record multiple live tv shows which could be causing the server crashes. I was also ripping a blu ray to the server last night also.

The syslog appears to be from right after a reboot so does not tell us much.

 

Did the system start doing a parity check after it had shut down unexpectedly?

 

The one thing that will tell you the most is the command

tail -f /var/log/syslog

 

If you open a telnet window and then type the above command it will print out what is being logged as it happens.  Leave that open, make sure your desktop computer does not go to sleep or hibernation, and then leave that running.  When the server goes down it should hopefully print something of use so that we can figure out what is going on.

The syslog appears to be from right after a reboot so does not tell us much.

 

Did the system start doing a parity check after it had shut down unexpectedly?

 

The one thing that will tell you the most is the command

tail -f /var/log/syslog

 

 

I turned on Telnet Client and in the box I typed this ( tail -f /var/log/syslog ) and it is saying invalid command.

If you open a telnet window and then type the above command it will print out what is being logged as it happens.  Leave that open, make sure your desktop computer does not go to sleep or hibernation, and then leave that running.  When the server goes down it should hopefully print something of use so that we can figure out what is going on.

I turned on Telnet Client and in the box I typed this ( tail -f /var/log/syslog ) and it is saying invalid command.

 

you need to telnet into the server first by typing

telnet IP_ADDRESS_OF_SERVER

 

then type the command I gave earlier.

I am typing telnet and ip address. Here are the IP addresses in my router and I used them all.

Try using putty. Google putty. Or does anyone know Microsoft telnet?

Here is the link to download Putty..

 

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

 

Also supports serial now as well.

 

Shawn

 

Wonder if I need to look into a cache drive. Thinking with all the writing to the server with my multiple live HD recordings and ripping movies to to the sever could be causing this crashing.

I am typing telnet and ip address.

 

Errr .... if you're at the telnet prompt, you don't need to type 'telnet', rather you should use 'open <address>'.

 

You use 'telnet <address>' if you're at the O/S prompt, eg C:\> telnet tower.

Geeze, if you type the ?/help as suggested you might get some info on how to use it...

 

Peter

 

I have not used telnet built into Microsoft Windows... I have always used putty.  From my quick searching it appears telnet is disabled by default on Windows 7 so has to be enabled.

 

You can use the Windows telnet or you can download and try using putty.

 

If you can load the unRAID webGUI you can grab the IP address of the server from the "Settings" page.

 

from there use putty to telnet to the IP address and then with the tail command I gave earlier.

OK I got the tail syslog running now. I want to apologize to anyone I offended because of my frustration. I really hope to get this resolved and greatly appreciate any help that I receive.

Good luck with your problem. Google and the built in program help are both your friends and if you don't know much about computers then you should try using these resources instead of expecting to be spoon fed every single detail.

 

http://lmgtfy.com/?q=using+windows+telnet

 

Second link is the Microsoft page on using telnet.

 

Peter

Doubt if this will help but this sort of thing kept happening to me, finally after quite a while troubleshooting I looked in the case and the CPU fan power cable was keeping the CPU fan from spinning.  CPU was getting too hot and shutting down to save itself.  Boy did I feel dumb after that but it's worth checking out all your hardware.

Doubt if this will help but this sort of thing kept happening to me, finally after quite a while troubleshooting I looked in the case and the CPU fan power cable was keeping the CPU fan from spinning.  CPU was getting too hot and shutting down to save itself.  Boy did I feel dumb after that but it's worth checking out all your hardware.

 

Ya, I mentioned that many posts ago but didn't see any response to it. Typically a pc under some sort of load that powers itself off is doing so to "save" itself in the case of the CPU overheating, or the PSU is just cutting out, to much draw.

 

Shawn

Ya, I mentioned that many posts ago but didn't see any response to it. Typically a pc under some sort of load that powers itself off is doing so to "save" itself in the case of the CPU overheating, or the PSU is just cutting out, to much draw.

 

Shawn

 

The CPU fan wire getting dislodged and therefor in the way of the fan is possible.  The PSU in the server is not overloaded, I know that for a fact.  Unless it has decided to go bad it should be more than enough for the number of drives he currently has in the system.

Every time we've encountered a problem with one of our servers in the data center randomly rebooting, it was usually due to a faulty power supply.  The voltage drops and the system thinks someone hit the reset button.  We start there and usually end there.

 

If that doesn't fix it, memory was the second culprit.  Heating has, for us, never been a problem.

OK I got the tail syslog running now. I want to apologize to anyone I offended because of my frustration. I really hope to get this resolved and greatly appreciate any help that I receive.

 

Apology accepted.  I removed the posts containing the "negativity". 

 

Please remember that everyone here is a volunteer (except LimeTech).  It makes sense that frustration levels can be high when you are worried about your data, but most people here are friendly and trying to be helpful.  Please remember that, and don't allow your frustration to spill over into offensive language towards others.

 

If you ever feel anyone is posting anything inappropriate, please let one of the moderators know and we can handle.

Ok so my server is at it again. I had 2 random shut downs today and one yesterday. Of course I was not running a syslog at the time. I now have the syslog running hoping to capture the problem.

syslog.txt

This syslog appears to be taken after a restart. Try to get one before a restart.