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 issue with Aquantia AQC107 10gb nic

Featured Replies

Hi, I moved my unraid to a new hardwares and I'm having a little issue with Aquantia 10gb nic on Asrock X399 Fatality motherboard. 

 

When the array autostart is set to yes, I can't find my server in Finder > Network, and sometimes br0 fails to establish. I have to stop and restart the array in order to get everything working or disable the autostart.   

 

I've looked at my syslog and found that some avahi-daemon services are not establishing properly when the array autostart is enabled. 

Oct  4 20:02:27 funazserver avahi-daemon[8707]: Server startup complete. Host name is funazserver.local. Local service cookie is 1295385096.
Oct  4 20:02:28 funazserver avahi-daemon[8707]: Interface eth0.IPv6 no longer relevant for mDNS.
Oct  4 20:02:28 funazserver avahi-daemon[8707]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::7285:c2ff:feb4:e4e9.
Oct  4 20:02:28 funazserver kernel: br0: port 1(eth0) entered disabled state
Oct  4 20:02:28 funazserver kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  4 20:02:28 funazserver kernel: br0: port 1(eth0) entered blocking state
Oct  4 20:02:28 funazserver kernel: br0: port 1(eth0) entered forwarding state
Oct  4 20:02:28 funazserver kernel: br0: port 1(eth0) entered disabled state
Oct  4 20:02:28 funazserver dhcpcd[2365]: br0: carrier lost
Oct  4 20:02:28 funazserver avahi-daemon[8707]: Withdrawing address record for fe80::7285:c2ff:feb4:e4e9 on eth0.
Oct  4 20:02:28 funazserver kernel: br0: port 1(eth0) entered disabled state
Oct  4 20:02:28 funazserver avahi-daemon[8707]: Withdrawing address record for 10.1.1.114 on br0.
Oct  4 20:02:28 funazserver dhcpcd[2365]: br0: deleting route to 10.1.1.0/24
Oct  4 20:02:28 funazserver dhcpcd[2365]: br0: deleting default route via 10.1.1.1
Oct  4 20:02:28 funazserver avahi-daemon[8707]: Leaving mDNS multicast group on interface br0.IPv4 with address 10.1.1.114.
Oct  4 20:02:28 funazserver avahi-daemon[8707]: Interface br0.IPv4 no longer relevant for mDNS.

compare to this (when autostart is disabled).

Oct  4 19:50:38 funazserver avahi-daemon[8705]: Server startup complete. Host name is funazserver.local. Local service cookie is 939670838.
Oct  4 19:50:38 funazserver root: error: /webGui/include/ProcessStatus.php: wrong csrf_token
Oct  4 19:50:39 funazserver avahi-daemon[8705]: Service "funazserver" (/services/ssh.service) successfully established.
Oct  4 19:50:39 funazserver avahi-daemon[8705]: Service "funazserver" (/services/smb.service) successfully established.
Oct  4 19:50:39 funazserver avahi-daemon[8705]: Service "funazserver" (/services/sftp-ssh.service) successfully established.

 

I think it is due to that ipv6 error happening at the wrong time. I've tried disable/enable ipv6 on eth0, but nothing works.

Also, when I use other nic (intel 1gb) on the motherboard, I have no issue with this. 

 

Any ideas? 

 

Diagnostic #1 - array autostart = yes, after boot, manually stopped and restarted the array.

Diagnostic #2 - array autostart = no, after boot, manually started the array.

yesAutoStart-funazserver-diagnostics-20191005-0306.zip noAutoStart-funazserver-diagnostics-20191005-0258.zip

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.