When the server boots up or like today that i have left it open after a day that all disks spun down unraid is unreachable . I can ping though. If i push in my win10 the network then it wakes up. Look video. https://cl.ly/3E1b1S2a0F2L The one is after i have manual shut down and now makes parity check. 

tower-syslog-20171009-1820.zip

no one? better to contact direct lime tech? Some guidance advice 

Full Diagnostics are always better than a simple syslog.  For instance, we have no idea if the webUI is running on a different port than the usual 80

From the command prompt

diagnostics

 

You can also try to boot the server into safe mode from the boot menu.

 

Thank you for the reply. Here are also the diagnostics.

tower-diagnostics-20171011-2038.zip

On 10/11/2017 at 4:43 PM, Squid said:

Full Diagnostics are always better than a simple syslog.  For instance, we have no idea if the webUI is running on a different port than the usual 80

From the command prompt

diagnostics

 

 

You can also try to boot the server into safe mode from the boot menu.

any ideas what the problem might be?

On 10/11/2017 at 4:43 PM, Squid said:

 

 

I see that you have used a fixed IP address of 192.168.1.2.  Have you made either (1) provision on your router to see that this address is not assigned to another device on your system or (2) that the address is outside of the range that your router is using when it assigns IP addresses?

 

Also try connecting using  http://192.168.1.2  and see what happens.

When i try now to connect to http://192.168.1.2  it works of course . I have also added to my router to give dynamic ips after 192.168.1.50 till 49 are reserved for me to give static. The problem occurs after some hours that all the disks are spun down. Also i have given the rule that i manually start the array. With this rule i couldn't connect to http://192.168.1.2  and had to try open the network connection from my windows machine. Of course connection was not possible but then i had access to  http://192.168.1.2  to start the array.

 

Now that i have changed the rule and the array starts automatically when the server boots up issue is solved but still after some hours i lose connection to the server. I can only ping http://192.168.1.2  but not web , telnet access. So i make not a clean shutdown and then parity check begins on next boot.This machine runs 5 years now with no problems. I dont know why all the sudden this happens.......

Have you connected up a monitor and keyboard directly to the server yet?  Then after it disappears from the network, see if you have access from the command line using that setup.  give a diagnostics file from the command line   diagnostics  at that point.

 

I have a note here that the there is a script for use on the command line to power down---  poweroff   ---  or you could try a quick push (~ 1 second) on the power button.  Either should accomplish a a clean shutdown.

Edited October 13, 20178 yr by Frank1940

I dont have monitor anymore for the server i could try it when this happens again. how do i take diagnostics from the command line? Does poweroff command start a clean shutdown? Clicking the power button server will close but when starts again its starts parity check. Clean shutdown i get only from the web interface

4 hours ago, naxiand said:

how do i take diagnostics from the command line?

 See my previous post for the command.  It will write the file in the logs folder/directory on the Flash Drive. 

 

4 hours ago, naxiand said:

Clicking the power button server will close but when starts again its starts parity check.

Yes. If you are not getting a clean shutdown,  most likely the array is not getting stopped before the shutdown happens. 

 

4 hours ago, naxiand said:

Clicking the power button server will close but when starts again its starts parity check.

A quick push (~ 1 second) should initiate a clean shutdown.  Three seconds or longer will force a shutdown will will always be unclean!

 

It sound like you are having some type of lockup of the server.  I would suggest that you install the Fix Common Problems plugin and turn on the 'troubleshooting' mode.  That will write a log file to the logs folder every half hours while taking a snapshot of your system every ten minutes.  There might be some clues in those files as to what is happening.  (Most of the time, these types of problems are usually found to be hardware related.)

 

I would also suggest that you open up the server and have a look to see how much dirt has collected inside of the case, vents, fans and heat sinks. 

 

 

Thank you for the tips the tower is super clean... Having all this time the pool to  start automatically and not manual seems it solved the problem...