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.

losing network beat

Featured Replies

Nevermind. Bad network port on the switch...

I have a brand new unraid server, and I'm trying to get some data on it. It appears to work perfectly: boots, recognizes drives, etc. I can access it via the network, but it loses its connection quite a bit.

 

Here's the thing: I know nothing about the hardware. It's some experimental box from Intel (from 3-4 years ago). I've also never used linux before. Is there anything that you guys can tell me from the logs?

 

I've uploaded the log (cat /var/syslog/log) here:

http://gadberry.com/travis/temp/towerlog.txt

 

Excerpt:

Jan 17 05:20:32 Pararaid ifplugd(eth0)[1113]: Link beat detected.
Jan 17 05:20:32 Pararaid kernel: 0000:01:00.0: eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Jan 17 05:20:40 Pararaid kernel: 0000:01:00.0: eth0: Detected Tx Unit Hang:
Jan 17 05:20:40 Pararaid kernel:   TDH                  <4d>
Jan 17 05:20:40 Pararaid kernel:   TDT                  <57>
Jan 17 05:20:40 Pararaid kernel:   next_to_use          <57>
Jan 17 05:20:40 Pararaid kernel:   next_to_clean        <4d>
Jan 17 05:20:40 Pararaid kernel: buffer_info[next_to_clean]:
Jan 17 05:20:40 Pararaid kernel:   time_stamp           <10f2b3>
Jan 17 05:20:40 Pararaid kernel:   next_to_watch        <4d>
Jan 17 05:20:40 Pararaid kernel:   jiffies              <10f374>
Jan 17 05:20:40 Pararaid kernel:   next_to_watch.status <0>
Jan 17 05:20:46 Pararaid kernel: 0000:01:00.0: eth0: Detected Tx Unit Hang:
Jan 17 05:20:46 Pararaid kernel:   TDH                  <4d>
Jan 17 05:20:46 Pararaid kernel:   TDT                  <57>
Jan 17 05:20:46 Pararaid kernel:   next_to_use          <57>
Jan 17 05:20:46 Pararaid kernel:   next_to_clean        <4d>
Jan 17 05:20:46 Pararaid kernel: buffer_info[next_to_clean]:
Jan 17 05:20:46 Pararaid kernel:   time_stamp           <10f2b3>
Jan 17 05:20:46 Pararaid kernel:   next_to_watch        <4d>
Jan 17 05:20:46 Pararaid kernel:   jiffies              <10f5cc>
Jan 17 05:20:46 Pararaid kernel:   next_to_watch.status <0>
Jan 17 05:20:48 Pararaid ifplugd(eth0)[1113]: Link beat lost.
Jan 17 05:20:51 Pararaid kernel: 0000:01:00.0: eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Jan 17 05:20:51 Pararaid ifplugd(eth0)[1113]: Link beat detected.
Jan 17 05:20:59 Pararaid kernel: 0000:01:00.0: eth0: Detected Tx Unit Hang:
Jan 17 05:20:59 Pararaid kernel:   TDH                  <bb>
Jan 17 05:20:59 Pararaid kernel:   TDT                  <c6>
Jan 17 05:20:59 Pararaid kernel:   next_to_use          <c6>

  • Author

Nevermind.

 

I switched network ports on my hub... I think it was just a bad port.

 

It's been working for an hour or so (instead of erroring every couple of minutes...)

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.