I have been running Unraid for a few years with no problems.  Lately I have been having stuttering when watching a movie or even transferring files to it.  I have included my syslog if anyone that knows how to read it could take a look  and see if anything sticks out I would really appreciate it.

 

I am running an external lan card and it is fairly new.

I am running 4.5 beta 6

What you are experiencing is this:

Nov  2 22:25:41 Tower kernel: e1000e: eth0 NIC Link is Down

Nov  2 22:25:41 Tower ifplugd(eth0)[1281]: Link beat lost.

Nov  2 22:25:44 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Nov  2 22:25:44 Tower ifplugd(eth0)[1281]: Link beat detected.

Nov  2 22:32:01 Tower kernel: e1000e: eth0 NIC Link is Down

Nov  2 22:32:02 Tower ifplugd(eth0)[1281]: Link beat lost.

Nov  2 22:32:04 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Nov  2 22:32:05 Tower ifplugd(eth0)[1281]: Link beat detected.

Nov  2 22:34:35 Tower kernel: e1000e: eth0 NIC Link is Down

Nov  2 22:34:35 Tower ifplugd(eth0)[1281]: Link beat lost.

Nov  2 22:34:38 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Nov  2 22:34:38 Tower ifplugd(eth0)[1281]: Link beat detected.

Nov  2 22:35:13 Tower kernel: e1000e: eth0 NIC Link is Down

Nov  2 22:35:13 Tower ifplugd(eth0)[1281]: Link beat lost.

Nov  2 22:35:16 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Nov  2 22:35:16 Tower ifplugd(eth0)[1281]: Link beat detected.

Nov  2 22:40:12 Tower kernel: e1000e: eth0 NIC Link is Down

Nov  2 22:40:13 Tower ifplugd(eth0)[1281]: Link beat lost.

Nov  2 22:40:16 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Nov  2 22:40:16 Tower ifplugd(eth0)[1281]: Link beat detected.

 

There must be over 10,000 lines like that.  I of course did not check all of them, but I never saw the network down for more than 3 seconds at a time, but still, that is up and down and up and down and ...  No wonder you saw stuttering!

 

I can't say what the problem is.  You have what appears to be a good Intel PRO/1000 PCI Express card, and did not appear to ever have any trouble negotiating a full gigabit connection (over and over and ....).  Since I have never seen a constant 3 second network drop like this before, I don't have any good ideas, but perhaps someone else has heard of a similar case, and will have an idea.

 

Your troubleshooting should include the card itself (try swapping it with another), the network cable (try replacing it), and the switch or router it is connected to.  Check the router logs for errors or reboots or something odd.  Make sure the network cable connectors are tight, not vibrating loose occasionally.  Check for an unusual source of strong interference very close to the network cable somewhere.  Can't think of anything else, but others will ...

Forgot one minor note, check for a tiny jumper on your Seagate 1TB drive.  See the Improving unRAID Performance, Remove SATA150 Jumper section.

thanks Rob

 

I will try another network card tomorrow and see if that does it. 

Thanks for the tip on the jumper I will check that also when I open it up.

This is starting to drive nuts.

well it is still doing it

 

I changed the network card

changed lan wire

changed port on switch

 

here is the last part of the log when playing hd movie with serious stuttering

 

Nov  4 14:09:09 Tower kernel: sd 3:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Nov  4 15:43:11 Tower emhttp: shcmd (48): /usr/sbin/hdparm -y /dev/hdb >/dev/null

Nov  4 16:54:58 Tower emhttp: shcmd (49): /usr/sbin/hdparm -y /dev/hda >/dev/null

Nov  4 16:54:58 Tower emhttp: shcmd (50): /usr/sbin/hdparm -y /dev/hdg >/dev/null

Nov  4 17:35:24 Tower emhttp: shcmd (51): /usr/sbin/hdparm -y /dev/sda >/dev/null

Nov  4 17:35:24 Tower emhttp: shcmd (52): /usr/sbin/hdparm -y /dev/sdg >/dev/null

Nov  4 17:40:16 Tower kernel: md: sync done. time=21097sec rate=34724K/sec

Nov  4 17:40:16 Tower kernel: md: recovery thread sync completion status: 0

Nov  4 18:10:27 Tower emhttp: shcmd (53): /usr/sbin/hdparm -y /dev/sdd >/dev/null

Nov  4 18:10:27 Tower emhttp: shcmd (54): /usr/sbin/hdparm -y /dev/sdf >/dev/null

Nov  4 18:10:28 Tower emhttp: shcmd (55): /usr/sbin/hdparm -y /dev/sde >/dev/null

Nov  4 18:10:29 Tower emhttp: shcmd (56): /usr/sbin/hdparm -y /dev/sdb >/dev/null

Nov  4 23:42:15 Tower dhcpcd[1434]: sending DHCP_REQUEST for 192.168.1.107 to 192.168.1.1

Nov  4 23:42:15 Tower dhcpcd[1434]: dhcpIPaddrLeaseTime=86400 in DHCP server response.

Nov  4 23:42:15 Tower dhcpcd[1434]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec

Nov  4 23:42:15 Tower dhcpcd[1434]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec

Nov  4 23:42:15 Tower dhcpcd[1434]: DHCP_ACK received from  (192.168.1.1)

Nov  5 07:35:57 Tower emhttp: shcmd (57): /usr/sbin/hdparm -y /dev/sda >/dev/null

Nov  5 07:35:57 Tower emhttp: shcmd (58): /usr/sbin/hdparm -y /dev/sde >/dev/null

Nov  5 07:35:58 Tower emhttp: shcmd (59): /usr/sbin/hdparm -y /dev/hdb >/dev/null

Nov  5 07:35:58 Tower emhttp: shcmd (60): /usr/sbin/hdparm -y /dev/sdg >/dev/null

Nov  5 07:35:58 Tower emhttp: shcmd (61): /usr/sbin/hdparm -y /dev/hdg >/dev/null

Nov  5 07:35:58 Tower emhttp: shcmd (62): /usr/sbin/hdparm -y /dev/sdb >/dev/null

Nov  5 07:36:08 Tower emhttp: shcmd (63): /usr/sbin/hdparm -y /dev/sdd >/dev/null

Nov  5 07:36:08 Tower emhttp: shcmd (64): /usr/sbin/hdparm -y /dev/sdf >/dev/null

Nov  5 07:36:19 Tower emhttp: shcmd (65): /usr/sbin/hdparm -y /dev/hda >/dev/null

Nov  5 07:51:14 Tower kernel: e1000e: eth0 NIC Link is Down

Nov  5 07:51:15 Tower ifplugd(eth0)[1282]: Link beat lost.

Nov  5 07:51:16 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Nov  5 07:51:17 Tower ifplugd(eth0)[1282]: Link beat detected.

Nov  5 08:11:44 Tower kernel: e1000e: eth0 NIC Link is Down

Nov  5 08:11:44 Tower ifplugd(eth0)[1282]: Link beat lost.

Nov  5 08:11:47 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Nov  5 08:11:47 Tower ifplugd(eth0)[1282]: Link beat detected.

Nov  5 09:47:34 Tower login[1342]: ROOT LOGIN  on `tty1'

 

any other suggestions I can try

Have you checked the router logs yet?

well it is still doing it

 

I changed the network card

changed lan wire

changed port on switch

 

here is the last part of the log when playing hd movie with serious stuttering

 

Nov  4 14:09:09 Tower kernel: sd 3:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Nov  4 15:43:11 Tower emhttp: shcmd (48): /usr/sbin/hdparm -y /dev/hdb >/dev/null

Nov  4 16:54:58 Tower emhttp: shcmd (49): /usr/sbin/hdparm -y /dev/hda >/dev/null

Nov  4 16:54:58 Tower emhttp: shcmd (50): /usr/sbin/hdparm -y /dev/hdg >/dev/null

Nov  4 17:35:24 Tower emhttp: shcmd (51): /usr/sbin/hdparm -y /dev/sda >/dev/null

Nov  4 17:35:24 Tower emhttp: shcmd (52): /usr/sbin/hdparm -y /dev/sdg >/dev/null

Nov  4 17:40:16 Tower kernel: md: sync done. time=21097sec rate=34724K/sec

Nov  4 17:40:16 Tower kernel: md: recovery thread sync completion status: 0

Nov  4 18:10:27 Tower emhttp: shcmd (53): /usr/sbin/hdparm -y /dev/sdd >/dev/null

Nov  4 18:10:27 Tower emhttp: shcmd (54): /usr/sbin/hdparm -y /dev/sdf >/dev/null

Nov  4 18:10:28 Tower emhttp: shcmd (55): /usr/sbin/hdparm -y /dev/sde >/dev/null

Nov  4 18:10:29 Tower emhttp: shcmd (56): /usr/sbin/hdparm -y /dev/sdb >/dev/null

Nov  4 23:42:15 Tower dhcpcd[1434]: sending DHCP_REQUEST for 192.168.1.107 to 192.168.1.1

Nov  4 23:42:15 Tower dhcpcd[1434]: dhcpIPaddrLeaseTime=86400 in DHCP server response.

Nov  4 23:42:15 Tower dhcpcd[1434]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec

Nov  4 23:42:15 Tower dhcpcd[1434]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec

Nov  4 23:42:15 Tower dhcpcd[1434]: DHCP_ACK received from  (192.168.1.1)

Nov  5 07:35:57 Tower emhttp: shcmd (57): /usr/sbin/hdparm -y /dev/sda >/dev/null

Nov  5 07:35:57 Tower emhttp: shcmd (58): /usr/sbin/hdparm -y /dev/sde >/dev/null

Nov  5 07:35:58 Tower emhttp: shcmd (59): /usr/sbin/hdparm -y /dev/hdb >/dev/null

Nov  5 07:35:58 Tower emhttp: shcmd (60): /usr/sbin/hdparm -y /dev/sdg >/dev/null

Nov  5 07:35:58 Tower emhttp: shcmd (61): /usr/sbin/hdparm -y /dev/hdg >/dev/null

Nov  5 07:35:58 Tower emhttp: shcmd (62): /usr/sbin/hdparm -y /dev/sdb >/dev/null

Nov  5 07:36:08 Tower emhttp: shcmd (63): /usr/sbin/hdparm -y /dev/sdd >/dev/null

Nov  5 07:36:08 Tower emhttp: shcmd (64): /usr/sbin/hdparm -y /dev/sdf >/dev/null

Nov  5 07:36:19 Tower emhttp: shcmd (65): /usr/sbin/hdparm -y /dev/hda >/dev/null

Nov  5 07:51:14 Tower kernel: e1000e: eth0 NIC Link is Down

Nov  5 07:51:15 Tower ifplugd(eth0)[1282]: Link beat lost.

Nov  5 07:51:16 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Nov  5 07:51:17 Tower ifplugd(eth0)[1282]: Link beat detected.

Nov  5 08:11:44 Tower kernel: e1000e: eth0 NIC Link is Down

Nov  5 08:11:44 Tower ifplugd(eth0)[1282]: Link beat lost.

Nov  5 08:11:47 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Nov  5 08:11:47 Tower ifplugd(eth0)[1282]: Link beat detected.

Nov  5 09:47:34 Tower login[1342]: ROOT LOGIN  on `tty1'

 

any other suggestions I can try

 

To eliminate the router/switch itself, plug straight into the unraid server directly. If you are still getting network connection issues, check the nic on the desktop end, or try a new cat5e or Cat6 cable. Although Cat5 should work, I experienced strange things in the past on longer runs.

 

Cheers!

thanks for all the suggestions.

 

I believe I have narrowed it down to the switch.  I bypassed it and everything is works fine.