Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Server Dropping - Again!

Featured Replies

Hi all.  This is my second post regarding this troubling issue.  My server sporadically drops its connection.  It can be up 5 minutes or 5 days and then....nada.  Constant refresh of my browser pulls up unraid maybe once every 100 refreshes.

 

I have reserved 192.168.1.100 on my unraid and also reserved it on my router (airport express).

 

My range is 192.168.1.100 - 192.168.1.200

 

ifconfig shows that the ip is being generated properly.  Should I be reserving an address outside of my DHCP range?

 

Please see attached syslog

 

QUESTION:  I am currently running 4.7.  Should I upgrade to 5 and try out AFP as all of my clients are Mac?

syslog-2012-09-15.txt.zip

As long as the address is reserved in the router you don't need to worry about the range. Are you able to ping or telnet to the server when the page won't load?

This shows to problem:

 kernel: r8169: eth0: link down
Sep 15 01:21:21 Tower ifplugd(eth0)[1473]: Link beat lost.
Sep 15 01:21:32 Tower ifplugd(eth0)[1473]: Executing '/etc/ifplugd/ifplugd.action eth0 down'.
Sep 15 01:21:32 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 down
Sep 15 01:21:32 Tower nss_wins[1511]: ntpd exiting on signal 15
Sep 15 01:21:32 Tower ifplugd(eth0)[1473]: client: Stopping NTP daemon...
Sep 15 01:21:33 Tower ifplugd(eth0)[1473]: Program executed successfully.
Sep 15 01:21:33 Tower kernel: r8169: eth0: link down
Sep 15 01:21:55 Tower kernel: r8169: eth0: link up
Sep 15 01:21:55 Tower ifplugd(eth0)[1473]: Link beat detected.
Sep 15 01:21:57 Tower ifplugd(eth0)[1473]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.

 

Show the output of "ifconfig" and "ethtool eth0"

 

 

QUESTION:  I am currently running 4.7.  Should I upgrade to 5 and try out AFP as all of my clients are Mac?

It may improve performance a bit but it's not related to the current problem.

This shows to problem:

 kernel: r8169: eth0: link down
Sep 15 01:21:21 Tower ifplugd(eth0)[1473]: Link beat lost.
Sep 15 01:21:32 Tower ifplugd(eth0)[1473]: Executing '/etc/ifplugd/ifplugd.action eth0 down'.
Sep 15 01:21:32 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 down
Sep 15 01:21:32 Tower nss_wins[1511]: ntpd exiting on signal 15
Sep 15 01:21:32 Tower ifplugd(eth0)[1473]: client: Stopping NTP daemon...
Sep 15 01:21:33 Tower ifplugd(eth0)[1473]: Program executed successfully.
Sep 15 01:21:33 Tower kernel: r8169: eth0: link down
Sep 15 01:21:55 Tower kernel: r8169: eth0: link up
Sep 15 01:21:55 Tower ifplugd(eth0)[1473]: Link beat detected.
Sep 15 01:21:57 Tower ifplugd(eth0)[1473]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.

 

Show the output of "ifconfig" and "ethtool eth0"

 

 

QUESTION:  I am currently running 4.7.  Should I upgrade to 5 and try out AFP as all of my clients are Mac?

It may improve performance a bit but it's not related to the current problem.

 

I have seen and experienced this before.

Is this a mobo with a realtek 8111e NIC? then that is the problem and upgrading to 5.0 RCx could well fix it.

This shows to problem:

 kernel: r8169: eth0: link down
Sep 15 01:21:21 Tower ifplugd(eth0)[1473]: Link beat lost.
Sep 15 01:21:32 Tower ifplugd(eth0)[1473]: Executing '/etc/ifplugd/ifplugd.action eth0 down'.
Sep 15 01:21:32 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 down
Sep 15 01:21:32 Tower nss_wins[1511]: ntpd exiting on signal 15
Sep 15 01:21:32 Tower ifplugd(eth0)[1473]: client: Stopping NTP daemon...
Sep 15 01:21:33 Tower ifplugd(eth0)[1473]: Program executed successfully.
Sep 15 01:21:33 Tower kernel: r8169: eth0: link down
Sep 15 01:21:55 Tower kernel: r8169: eth0: link up
Sep 15 01:21:55 Tower ifplugd(eth0)[1473]: Link beat detected.
Sep 15 01:21:57 Tower ifplugd(eth0)[1473]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.

 

Show the output of "ifconfig" and "ethtool eth0"

 

 

QUESTION:  I am currently running 4.7.  Should I upgrade to 5 and try out AFP as all of my clients are Mac?

It may improve performance a bit but it's not related to the current problem.

 

I have seen and experienced this before.

Is this a mobo with a realtek 8111e NIC? then that is the problem and upgrading to 5.0 RCx could well fix it.

 

Yes, this is true. Has the server ever worked correctly?

  • Author

Here are the answers to the above posts:

 

1.  The server went months (about 6) without any issues whatsoever;

 

2.  Ethernet info attached;

 

3.  Motherboard is ECS A885GM-A2 (V1.1) 880G AM3 R.  Additional configuration details below;

 

4.  I have upgraded to 5 and currently have the shares mounted so I can not test it via a ping but I am still dropping out.

 

Unraid Configuration

 

Motherboard:         ECS| A885GM-A2 (V1.1) 880G AM3 R

RAID Card: SUPERMICRO AOC-SASLP-MV8

CPU: AMD|SEM 145 2.8G AM3 RT

Memory:         4G RENDITION RM25664BA1339 R

PSU:         Corsair TX750

 

 

Ethernet info

 

 

NIC info (from ethtool)

Settings for eth0:

Supported ports: [ TP MII ]

Supported link modes:  10baseT/Half 10baseT/Full

                        100baseT/Half 100baseT/Full

                        1000baseT/Half 1000baseT/Full

Supports auto-negotiation: Yes

Advertised link modes:  10baseT/Half 10baseT/Full

                        100baseT/Half 100baseT/Full

                        1000baseT/Half 1000baseT/Full

Advertised pause frame use: Symmetric Receive-only

Advertised auto-negotiation: Yes

Link partner advertised link modes:  10baseT/Half 10baseT/Full

                                    100baseT/Half 100baseT/Full

Link partner advertised pause frame use: Symmetric

Link partner advertised auto-negotiation: Yes

Speed: 100Mb/s

Duplex: Full

Port: MII

PHYAD: 0

Transceiver: internal

Auto-negotiation: on

Supports Wake-on: pumbg

Wake-on: g

Current message level: 0x00000033 (51)

Link detected: yes

 

NIC driver info (from ethtool -i)

driver: r8169

version: 2.3LK-NAPI

firmware-version: rtl_nic/rtl8168d-1.fw

bus-info: 0000:04:00.0

 

Ethernet config info (from ifconfig)

eth0      Link encap:Ethernet  HWaddr 10:78:d2:1e:82:53 

          inet addr:192.168.1.150  Bcast:192.168.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:2476993 errors:0 dropped:161 overruns:0 frame:0

          TX packets:10554738 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:370279040 (353.1 MiB)  TX bytes:2006938925 (1.8 GiB)

          Interrupt:43 Base address:0x4000

 

  • Author

Is there some function I have not completed that forces me to the 100 mbps speed?

Is there some function I have not completed that forces me to the 100 mbps speed?

Nothing in unraid. What is the part / model number of the switch that the unraid network cable is plugged into? How long is the cable? Are your other devices reporting 1000mbps speeds?

there are various reasons for being "stuck" on 100base-T. 

 

to be on 1000base-T (gigabit), verify:

- your switch (or device you are plugging into, e.g. home router/cable modem/etc.) is gigabit

- your cable is at least cat5e (cat5 is not sufficient) or cat6 (this is usually printed on the cable itself)

- you have not set your speed in both sides' (unraid and e.g. switch) settings to be 100MB (edit: I see another post just got posted before mine that says there's nothing in unraid.  having read that, now I'm not sure about this :), but I would at least verify since I know in many products, this is "settable" - e.g. auto/10/100/1000 & full/half duplex.  unfortunately, I'm at work so I can't verify myself if there's a setting in unraid, so sorry for the confusion otherwise)

 

there are probably others, but these are probably the easiest to verify (and eliminate).

- you have not set your speed in both sides' (unraid and e.g. switch) settings to be 100MB (edit: I see another post just got posted before mine that says there's nothing in unraid.  having read that, now I'm not sure about this :)

You can switch the settings around with the command line, but there is no gui element that I am aware of. Thus my statement that it's not something he could accidentally change without knowing it. There would have to be a command in the go script or some other manual setting made to change it.

 

So, you're correct, it could be set incorrectly, but the chances of it being set without his direct knowledge and action is slim to none. 

  • Author

I run an Apple Airport Extreme.  My cable is only 5'.  I have switched cables to test with no changes.

I run an Apple Airport Extreme.  My cable is only 5'.  I have switched cables to test with no changes.

Have you tried a different port on the switch? If that doesn't change the situation, I'd say either the network card has gone bad, or there is some driver factor that hasn't been uncovered in the troubleshooting so far. My money given what's transpired is a bad network card in the server. If you have a spare slot I'd pick up an intel gigabit NIC and disable the current port.

I run an Apple Airport Extreme.  My cable is only 5'.  I have switched cables to test with no changes.

 

The length of the cable is not the issue. The type of cable may be the problem. Is it CAT 5, CAT 5e, or CAT 6?

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.