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.

Network connection die completely - acer h340

Featured Replies

Searched the forums and didn't see the hardware in incompatible. So not sure what's going on. Unraid will boot fine on it. If I don't enable the array, seems like the network will stay up (haven't fullly verify). But once the array is enabled the network drops completely.

 

Attached is the syslog

syslog.txt

  • Author

Forget to mention that this is a new array, there is no data on any of the drives

 

But the drives are old

Could not see anything obvious looking in the log.

 

I did notice that the LAN interface only seems to be running at 100Mbps - is this expected?  Just checking as if you are on a Gigabit LAN then lower speeds often indicate issues with the LAN cable or the port it is plugged into on the router.

  • Author

Yes, the network is running at 100Mbps plugged directly into the router.

 

Is there a way to force the nic to run at 100 in the config files ?

 

Could not see anything obvious looking in the log.

 

I did notice that the LAN interface only seems to be running at 100Mbps - is this expected?  Just checking as if you are on a Gigabit LAN then lower speeds often indicate issues with the LAN cable or the port it is plugged into on the router.

Dec 18 09:01:02 FS2 kernel: sky2 0000:09:00.0: error interrupt status=0x8

 

This occurred 20 minutes after array start.  I assume network lost at that point.  It was assigned interrupt 40, not shared, so does not appear a problem with that.  But its setup does trouble me, it appears to require io space of 00 to ff, which the syslog reports as an overlap of the motherboards interest in a number of ports or io areas within that.  (0000:09:00.0 is the network chipset)

 

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x0010-0x001f] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x0024-0x0025] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x0028-0x0029] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x002c-0x002d] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x0030-0x0031] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x0034-0x0035] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x0038-0x0039] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x003c-0x003d] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x0050-0x0053] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x0072-0x0077] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x0080] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x0090-0x009f] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x00a4-0x00a5] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x00a8-0x00a9] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x00ac-0x00ad] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x00b0-0x00b5] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x00b8-0x00b9] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x00bc-0x00bd] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

Dec 18 08:41:20 FS2 kernel: pnp 00:00: disabling [io  0x002e-0x002f] because it overlaps 0000:09:00.0 BAR 2 [io  0x0000-0x00ff]

 

Check for a way to reconfigure the NIC in the BIOS.  If not, then you may have to disable it, and add a different NIC to the system.  It's also possible that the newer kernel in v6 (currently 6.0-beta12) may have better support for this board.

  • Author

Yea, no way to configure anything in the bios.

 

Anyway, running this on 6 now. Seems to be stable. Thanks for the help.

 

 

  • Author

So with unraid 6 it is still doing the same thing but only when I'm doing transfers

 

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 896

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 912

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

sky2 0000:09:00.0: error interrupt status=0x40000008

sky2 0000:09:00.0 eth0: rx error, status 0x7ffc0001 length 992

I suspect you will need a new network adapter.  If/when you get one, make sure you disable the onboard one.

  • Author

Seems like you are right. I ended up plugging a usb ethernet onto the server and it's been stable for now.

 

asix 1-4:1.0 eth1: register 'asix' at usb-0000:00:1d.7-4, ASIX AX88772 USB 2.0 Ethernet, 9c:eb:e8:08:b8:e4

 

I suspect you will need a new network adapter.  If/when you get one, make sure you disable the onboard one.

  • 1 year later...

Sadly, I have the same box and the same issue. Plugging in a Cisco USB adapter.

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.