Hi All,

 

I have been searching the forum for a number of days now though have not really been able to find a post with a solution that solves my issue. The issue seems to be common which is that at some stage throughout a day my unraid server will become unresponsive and the only way to bring it back up is to hard reboot it (GUI unresponsive, Telnet & at the console)

 

I have provided below a number of steps I have undertaken to try and resolve the issue though they do not seem to be working.

 

1. Drives were set to spin down after 1 hour of inactivity. When drives were requested to spin up (through accessing an SMB share) the unraid server would become unresponsive. I had set the drives to stay spun up and this worked for 2 days and then when trying to access a drive after the 2 days it became unresponsive. Did not solve issue.

 

2. Upgrade from 6.1.8  to 6.1.9. Did not solve issue.

 

I have also noticed that if the server becomes unresponsive through SMB shares but I can still access the webGUI, when I go to stop the array and then reboot it gets stuck on Syncing Filesystem.

 

If anybody could point me in the direction to a solution for this issue that would be greatly appreciated. I have attached my system log for your reference.

 

Thanks.

 

Regards,

 

Sam.

 

 

syslog.txt

Hi,

 

Just following up to see if anybody can assist with my issue?

 

Thanks in advance.

Is it a recent thing or has it always been like that.

You said you upgraded from 6.1.8 to 6.1.9 - that suggests you have had unRAID for a while so this problem has got to be quite recent?

Is it a recent thing or has it always been like that.

You said you upgraded from 6.1.8 to 6.1.9 - that suggests you have had unRAID for a while so this problem has got to be quite recent?

 

Yes the issue started a few weeks after a upgraded to 6.1.8. To try and resolve the issue I then upgraded to 6.1.9 though the issue is still present. There are no scheduled tasks etc. so that is not the issue.

Hi,

 

Just following up to see if anybody can assist with my issue?

 

Thanks in advance.

 

If you post your full diagnostic zip someone might spot something, otherwise it's just guesswork.

Hi,

 

Just following up to see if anybody can assist with my issue?

 

Thanks in advance.

 

If you post your full diagnostic zip someone might spot something, otherwise it's just guesswork.

 

Hi there,

 

diagnostic information has now been attached. Thanks for your help.

wilnas-diagnostics-20160804-1633.zip

I'm assuming the date is out to lunch on your server, as the last entry in the syslog is dated Aug 4.

 

But, since there's nothing really of any use in there, what you might consider doing is installing Fix Common Problems plugin, and then toss it into Troubleshooting Mode, which will continually tail the syslog, do some tests every 10 minutes.  And everything gets saved to the flash drive, so that after you are forced to reboot, maybe there will be some usable information contained in those files.

I'm assuming the date is out to lunch on your server, as the last entry in the syslog is dated Aug 4.

 

But, since there's nothing really of any use in there, what you might consider doing is installing Fix Common Problems plugin, and then toss it into Troubleshooting Mode, which will continually tail the syslog, do some tests every 10 minutes.  And everything gets saved to the flash drive, so that after you are forced to reboot, maybe there will be some usable information contained in those files.

 

Hi Squid,

 

Apologies as I uploaded the incorrect file. The server had been running fine for a few days and has basically just started having issues (cannot connect to shares etc.) and I have been able to grab a fresh new diagnostics folder. If you could let me know if you see any issues that would be great.

 

I will also install the plugin suggested.

 

Cheers,

 

Sam.

wilnas-diagnostics-20160810-1322.zip

I'm assuming the date is out to lunch on your server, as the last entry in the syslog is dated Aug 4.

 

But, since there's nothing really of any use in there, what you might consider doing is installing Fix Common Problems plugin, and then toss it into Troubleshooting Mode, which will continually tail the syslog, do some tests every 10 minutes.  And everything gets saved to the flash drive, so that after you are forced to reboot, maybe there will be some usable information contained in those files.

 

Hi Squid,

 

Apologies as I uploaded the incorrect file. The server had been running fine for a few days and has basically just started having issues (cannot connect to shares etc.) and I have been able to grab a fresh new diagnostics folder. If you could let me know if you see any issues that would be great.

 

I will also install the plugin suggested.

 

Cheers,

 

Sam.

 

 

 

 

Hi Squid,

 

Well I have been completing some tests over the past few weeks and believe I have narrowed the issue down though it is inconsistent.

 

The issue is appearing when I try to access shares either through Windows or the WebGUI (Shares tab). I have managed to keep the server running for 2 full days without issues (connecting to shares, browsing the webGUI etc.) without issues. Tonight when I tried to access a share it stopped responding.

 

I have also tried leaving the disks spun up though the issue eventually occurs and a few times now the disks have been spun down for quite some time and spin up fine when accessing a share.

 

I have attached the syslog with the Fix Common Problems troubleshooting mode output for your review.

 

Quite frustrating given I have had no issues with unRAID for 5+ years now. Looking for suggestions to try and resolve this. Is it worth perhaps recreating my array? (providing I lose no data).

 

Thanks again. Look forward to hearing from you.

 

 

syslog.zip

That is only a snippet of the syslog, and typically one wants to see the full log.    It would be much more useful to provide the full diagnostics (Tools->Diagnostics) when asking for help as that includes much more than the syslog.

Hi itimpi,

 

No problems. As above though I provided the full diagnostics and then was asked to provide only the syslog where I had run the Fix Common Problems plugin.

Any ideas?

Any ideas?

You definitely need the diagnostics that FCP was continually getting (the last dated one that's on the flash drive).

 

Something happened ~4:47 on Aug 25.  That's where the scheduled run of FCP looks like it never finished its tests, and its CPU usage (and cpuload) began to skyrocket.  (Not FCP, as it previously ran fine the day before, but something else in the system was causing it to do this)  Best guess would be something up with the disks, but not quite sure, and nothings in the logs.  It might be prudent to turn on the logging for mover so that those entries get logged into the syslog.