My server is dropping the connection.  In the middle of watching a movie, I simply loose the connection.  I can intermittently connect via my browser.  Any suggestions?

Here is my syslog

syslog-2012-08-18.txt

Look like it just rebooted, is that expected?

Look like it just rebooted, is that expected?

no, not unless you lost power.  unRAID servers never reboot themselves.

 

I'd start with a memory check, preferably several cycles or overnight.  Verify the memory voltage, clock speed, and timing are set correctly for your specific memory strips.  Most BIOS set them automatically, some get it wrong.

 

Also, check your fans and CPU heatsink.  If the CPU overheats, it can cause the server to shut down.

 

Joe L.

Here is the whole story:

 

1.  My modem was defective and it was replaced.  I have had unRaid running for 7 months without issue.

2.  I am a noob with linux.  I have a monitor attached to my server and can ifcofig.  I can also modify my unRaid files via my Mac using text edit.  That's the extent of my skill level although I'm fearless.

3.  I set up my new modem bridged and used my Airport Express to serve up DHCP addresses.  I set the range from 192.168.0.10 to 192.168.0.200.  My subnet was 255.255.254.0

4.  My unRaid network config file was historically set as follows:

    /boot/config/network.cfg

    USE_DHCP=yes

    IPADDR=

    NETMASK=

    GATEWAY=

5.  This set up consistently gave the server an address of: inet addr: 192.168.45.7 Bcast:192.168.45.255 Mask: 255.255.255.0

6.  Obviously, I could not connect.

7.  I then reconfigured the Airport Express to use the subnet 255.255.255.0 and edited the network config file as follows:

    /boot/config/network.cfg

    USE_DHCP=

    IPADDR=192.168.0.100

    NETMASK=255.255.255.0

    GATEWAY=192.168.0.1 (which I am certain is my Airport address)

8.  if config showed the right ip and I could connect via my browser every 1 in 30-50 tries.  I could mount my files occasionally on my desktop by qeurying smb://192.168.0.100

9.  The files simply disappear and the server goes offline at random times, never longer than 30 minutes.  I follow #8 again with the identical results.

10. Interestingly with configuration #7, "tower" does not show up as a share at all in my finder.  It used to always be there.

 

I have also tried setting up my modem to give out ip's and my Airport Extreme as bridged with the same result.

 

All other computers and accessories receive proper addresses within my requested range and work fine.  It is only the unRaid box that won't grab the right address.

 

I am guessing that this is a network "handshake" issue.  Why else would my ip address on the server show as in #5 above when not manually configured in my network.cfg file?  It should accept and address in the 192.168.0.10 - 192.168.0.200 range as all my other computers are.

 

I am at a loss.  I have never had this problem before.  Per Joe's reply, I have no clue how to verify any of my memory.  If I restart and provide another syslog, will this help?

 

Tonight is supposed to be movie night!

Change the mask from  255.255.254.0 to  255.255.255.0 in the router and set the server to use DHCP.

I did that already.  See #7.

#7 indicates a static configuration on the server.

Change the mask from  255.255.254.0 to  255.255.255.0 in the router and set the server to use DHCP.

Sorry dgaschk.  I don't understand.  Are you suggesting a rename of files on the flash drive?

No. Setting->Network Settings->Obtain IP Address Automatically: yes

As soon as I do that and check on my server via ifconfig, I get

 

inet addr: 192.168.45.11 Bcast: 192.168.45.255 Mask: 255.255.255.0

That looks ok.

That looks ok.

 

Not if this statement is correct:

3.  I set up my new modem bridged and used my Airport Express to serve up DHCP addresses.  I set the range from 192.168.0.10 to 192.168.0.200.  My subnet was 255.255.254.0

Your right. It looks like there is no communication with the DHCP server. The interface is getting a default address.

Server still dropping out.  Here is syslog

syslog-2012-08-22.txt.zip

The syslog shows the address 192.168.1.100 is being configured static. Could another computer on the LAN be coming on and being issued that address by DHCP, thus cutting off the server? Try setting it to 192.168.1.201

I will try that and update this post with my findings.  Thank you.