I hope this is the right forum I'm running Unraid 4.5 Release and just installed it today.  I'm not sure how long this issue has been going on, but I think I might have finally found what's causing my videos in Sage to stutter during play back.  With the new version of Unraid the speaker on my box started working and I caught it beeping at me seemingly randomly.  I checked the syslog (via the built in //tower/log/syslog) and I found this.

Dec 29 18:48:16 NAS kernel: sky2 eth0: hung mac 0:4 fifo 69 (55:124)
Dec 29 18:48:16 NAS kernel: sky2 eth0: receiver hang detected
Dec 29 18:48:16 NAS kernel: sky2 eth0: disabling interface
Dec 29 18:48:16 NAS kernel: sky2 eth0: enabling interface
Dec 29 18:48:16 NAS ifplugd(eth0)[1107]: Link beat lost.
Dec 29 18:48:19 NAS kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Dec 29 18:48:19 NAS ifplugd(eth0)[1107]: Link beat detected.
Dec 29 19:53:09 NAS kernel: mdcmd (1455): spindown 1
Dec 29 19:53:09 NAS kernel: mdcmd (1456): spindown 2
Dec 29 21:20:41 NAS kernel: sky2 eth0: hung mac 0:105 fifo 82 (175:57)
Dec 29 21:20:41 NAS kernel: sky2 eth0: receiver hang detected
Dec 29 21:20:41 NAS kernel: sky2 eth0: disabling interface
Dec 29 21:20:41 NAS kernel: sky2 eth0: enabling interface
Dec 29 21:20:42 NAS ifplugd(eth0)[1107]: Link beat lost.
Dec 29 21:20:44 NAS kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Dec 29 21:20:45 NAS ifplugd(eth0)[1107]: Link beat detected.
Dec 29 21:41:41 NAS kernel: sky2 eth0: hung mac 0:13 fifo 110 (175:85)
Dec 29 21:41:41 NAS kernel: sky2 eth0: receiver hang detected
Dec 29 21:41:41 NAS kernel: sky2 eth0: disabling interface
Dec 29 21:41:41 NAS kernel: sky2 eth0: enabling interface
Dec 29 21:41:41 NAS ifplugd(eth0)[1107]: Link beat lost.
Dec 29 21:41:44 NAS kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Dec 29 21:41:44 NAS ifplugd(eth0)[1107]: Link beat detected.
Dec 29 22:41:51 NAS kernel: sky2 eth0: hung mac 0:48 fifo 92 (100:192)
Dec 29 22:41:51 NAS kernel: sky2 eth0: receiver hang detected
Dec 29 22:41:51 NAS kernel: sky2 eth0: disabling interface
Dec 29 22:41:51 NAS kernel: sky2 eth0: enabling interface
Dec 29 22:41:52 NAS ifplugd(eth0)[1107]: Link beat lost.
Dec 29 22:41:54 NAS kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Dec 29 22:41:55 NAS ifplugd(eth0)[1107]: Link beat detected.
Dec 29 23:06:57 NAS kernel: sky2 eth0: hung mac 0:19 fifo 125 (14:139)
Dec 29 23:06:57 NAS kernel: sky2 eth0: receiver hang detected
Dec 29 23:06:57 NAS kernel: sky2 eth0: disabling interface
Dec 29 23:06:57 NAS kernel: sky2 eth0: enabling interface
Dec 29 23:06:57 NAS ifplugd(eth0)[1107]: Link beat lost.
Dec 29 23:07:00 NAS kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Dec 29 23:07:00 NAS ifplugd(eth0)[1107]: Link beat detected.
Dec 29 23:27:41 NAS kernel: sky2 eth0: hung mac 0:63 fifo 73 (54:127)
Dec 29 23:27:41 NAS kernel: sky2 eth0: receiver hang detected
Dec 29 23:27:41 NAS kernel: sky2 eth0: disabling interface
Dec 29 23:27:41 NAS kernel: sky2 eth0: enabling interface
Dec 29 23:27:41 NAS ifplugd(eth0)[1107]: Link beat lost.
Dec 29 23:27:44 NAS kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Dec 29 23:27:44 NAS ifplugd(eth0)[1107]: Link beat detected.
Dec 30 00:42:13 NAS kernel: sky2 eth0: hung mac 0:33 fifo 64 (105:169)
Dec 30 00:42:13 NAS kernel: sky2 eth0: receiver hang detected
Dec 30 00:42:13 NAS kernel: sky2 eth0: disabling interface
Dec 30 00:42:13 NAS kernel: sky2 eth0: enabling interface
Dec 30 00:42:13 NAS ifplugd(eth0)[1107]: Link beat lost.
Dec 30 00:42:16 NAS kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Dec 30 00:42:17 NAS ifplugd(eth0)[1107]: Link beat detected.

 

 

I'm pretty much a linux noob so this doesn't tell me much.  Can someone point me in the right direction?  Why does my connection to my router seem to be resetting at odd intervals, even as you can see here once the hard drives are spun down.  If it's doing this while in use that would explain the random pauses I get streaming my video.  IF this fixes that I'll have removed my only major complaint about Unraid. 

A google search of

sky2 eth0: "hung mac"

 

led me to this.

 

http://kerneltrap.org/mailarchive/linux-netdev/2008/8/25/3069244

 

it seems to say the underlying issue is buggy firmware driver in the MB bios for your networking chipset and that an update from the manufacturer might be available to fix it.

How is it I would have instantly been hitting google for a windows problem and completely dropped the ball on even looking for that issue just b/c it was Linux.

Thanks, I'm off to check with Gigabyte to see if there's a Bios upgrade, especially one with a nod to fixing networking issues.

Hope they've got a way to easily do it w/o windows installed!

Well that didn't seem to help.  After reading the linked page above the update was to address an overflow issue, the hung mac is a separate issue.  Searching around on it some more I've only seen mention of it being a bug in the sky2 driver and suggestions to try a different network driver.  Here's some excerpts from the syslog again.

 

Dec 31 01:27:14 NAS kernel: mdcmd (1163): spindown 2
Dec 31 02:02:17 NAS kernel: mdcmd (1374): spindown 1
Dec 31 03:19:46 NAS kernel: md: sync done. time=17911sec rate=54534K/sec
Dec 31 03:19:46 NAS kernel: md: recovery thread sync completion status: 0
Dec 31 04:19:48 NAS kernel: mdcmd (2211): spindown 0
Dec 31 04:57:16 NAS kernel: sky2 eth0: hung mac 0:118 fifo 83 (131:14)
Dec 31 04:57:16 NAS kernel: sky2 eth0: receiver hang detected
Dec 31 04:57:16 NAS kernel: sky2 eth0: disabling interface
Dec 31 04:57:16 NAS kernel: sky2 eth0: enabling interface
Dec 31 04:57:16 NAS ifplugd(eth0)[1107]: Link beat lost.
Dec 31 04:57:19 NAS kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Dec 31 04:57:19 NAS ifplugd(eth0)[1107]: Link beat detected.
Dec 31 05:01:21 NAS kernel: mdcmd (2461): spindown 1
Dec 31 05:01:21 NAS kernel: mdcmd (2462): spindown 2
Dec 31 05:41:57 NAS kernel: sky2 eth0: hung mac 0:15 fifo 85 (162:47)

Dec 31 08:06:48 NAS kernel: sky2 eth0: hung mac 0:8 fifo 106 (22:128)

Dec 31 08:57:22 NAS kernel: sky2 eth0: hung mac 0:123 fifo 121 (10:131)

 

One thing I noticed was during the parity rebuild (accidentally pulled the power moving the tower).  There were no errors for several hours.  After that I'm getting a seemingly random timing on the errors and the tower was just sitting still unused over night.  I'll keep checking and see how often it happens but so far it's looking to be 2hrs at maximum between errors.  That's definitely not enough to watch a movie from it w/o interruption. 

 

Anyone have any other suggestions?  What else can I try/check?

Well that didn't seem to help.  After reading the linked page above the update was to address an overflow issue, the hung mac is a separate issue.  Searching around on it some more I've only seen mention of it being a bug in the sky2 driver and suggestions to try a different network driver.  Here's some excerpts from the syslog again.

 

One thing I noticed was during the parity rebuild (accidentally pulled the power moving the tower).  There were no errors for several hours.  After that I'm getting a seemingly random timing on the errors and the tower was just sitting still unused over night.  I'll keep checking and see how often it happens but so far it's looking to be 2hrs at maximum between errors.  That's definitely not enough to watch a movie from it w/o interruption. 

 

Anyone have any other suggestions?  What else can I try/check?

 

install an intel pro1000 NIC in the machine and disable the onboard one.

http://www.newegg.com/product/product.aspx?item=N82E16833106121

 

I'll keep that in mind.  Something like this will do the trick?  Just any Intel Pro Gig card would work? 

If it's as simple as install card, turn of on-board, and unraid just works that's quickly going to be my go to plan.

 

For now though the machine after rebooting last night has been up for 15hrs with out a 'hung mac'.  I know at least one transfer happened last night (scheduled backup) but we'll see how things go.