For the past couple of weeks my unraid server keeps becoming unresponsive, I haven't managed to find out what triggers this.

 

I cannot access the web ui and I cannot telnet into it, the only way I can get it to respond is to do a hard power cycle, which means I have no syslog, as it gets overwritten on reboot.

 

Can anyone suggest how I can get a syslog so I can try and provide some more information about the underlying problem.

 

I run my server headless and it auto sleeps after an hour of no disk activity.

 

I am running version: 5.0-rc10 however it is not a problem that is specific to this version as I updated to this version hoping that it would fix it.

 

It also seems to occur when running a parity check as well, so I am unsure of the integrity of my current data and having to do a hard power cycle is making me real uneasy.

 

If you need any more information please let me know.

 

Cheers.

 

Tom.

 

Yup... surprisingly easy and this has helped me in several instances allready:

 

Create a small script:

 

#!/bin/bash
cp /var/log/syslog /mnt/cache/syslog

 

Save this on your flashdrive (in the CONFIG directory) as a file called SendLog

 

Then add the following to your GO file:

 

cp /boot/config/SendLog /etc/cron.hourly/SendLog
chmod +x /etc/cron.hourly/SendLog

 

This will make your syslog get written to the root of your flashdrive every hour. It has been a surprise to me how often this will continue to work when everything else is unresponsive.

 

Added benefit is that you can now make a shortcut on your pc to view your syslog without the need to log on.

 

 

Hi,

 

Many thanks for the reply.

 

My server has just crashed again so I will install the script after I have rebooted it and post some logs when it happens again.

 

Cheers.

I finally manage to capture a syslog of the error occurring.

 

I apologise but I had no way of copying the contents of the console from my pi to my pc to post so I had to take a photo of the log.

 

After the last line my server became unresponsive.

 

Cheers.

 

 

It locked up again, however this time I get a different error, see attached log.

 

Can anyone help me out, its getting to the point where I am going to have to stop using my server as I am worried about the state of the drives if I keep having to hard power cycle it.

 

Cheers.

syslog.txt

Run memtest overnight.

Many thanks for the suggestion I ran memtest over night last night and it reported no errors.

 

Cheers.

Use the cp command in the above script to copy the syslog to the flash drive. The put the flash in your PC and attach the entire syslog. zip if needed.