Fix common problems always reports the following only when I boot unRAID.

 

Currently running unRAID i.e. 6.4.0_rc18f, but probably not related to it as it was also happening in 6.4.0_rc17b.

 

This only happened after I after I assigned my 10 gbe port to eth0 in the interface rules.  But come to think of it, I think I also installed the Fix Common Problems Plugin as well around this point.

 

Network.cfg:

 

# Generated settings:
IFNAME[0]="br0"
BONDNAME[0]="bond0"
BONDING_MIIMON[0]="100"
BRNAME[0]="br0"
BRSTP[0]="no"
BRFD[0]="0"
BONDING_MODE[0]="1"
BONDNICS[0]="eth0"
BRNICS[0]="bond0"
DESCRIPTION[0]="Physical Lan 3 - 10 gbe"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="yes"
METRIC[0]="217"
DHCP_KEEPRESOLV="yes"
DNS_SERVER1="192.168.19.1"
DNS_SERVER2="8.8.8.8"
DNS_SERVER3="8.8.4.4"
USE_DHCP6[0]="yes"
DHCP6_KEEPRESOLV="no"
MTU[0]=""
SYSNICS="1"

 

Syslog snippet:

Dec 29 10:30:32 Brutus root: Fix Common Problems Version 2017.12.11a
Dec 29 10:30:33 Brutus dhcpcd[1828]: br0: carrier lost
Dec 29 10:30:33 Brutus dhcpcd[1828]: br0: deleting default route via 192.168.19.1
Dec 29 10:30:33 Brutus dhcpcd[1828]: br0: deleting route to 192.168.19.0/24
Dec 29 10:30:33 Brutus avahi-daemon[9240]: Withdrawing address record for 192.168.19.75 on br0.
Dec 29 10:30:33 Brutus avahi-daemon[9240]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.19.75.
Dec 29 10:30:33 Brutus avahi-daemon[9240]: Interface br0.IPv4 no longer relevant for mDNS.
Dec 29 10:30:35 Brutus ntpd[1882]: Deleting interface #1 br0, 192.168.19.75#123, interface stats: received=6, sent=6, dropped=0, active_time=18 secs
Dec 29 10:30:35 Brutus ntpd[1882]: 199.223.248.101 local addr 192.168.19.75 -> <null>
Dec 29 10:30:36 Brutus kernel: ixgbe 0000:03:00.0 eth0: NIC Link is Up 10 Gbps, Flow Control: None
Dec 29 10:30:36 Brutus kernel: bond0: link status definitely up for interface eth0, 10000 Mbps full duplex
Dec 29 10:30:36 Brutus kernel: bond0: making interface eth0 the new active one
Dec 29 10:30:36 Brutus kernel: device eth0 entered promiscuous mode
Dec 29 10:30:36 Brutus dhcpcd[1828]: br0: carrier acquired
Dec 29 10:30:36 Brutus kernel: bond0: first active interface up!
Dec 29 10:30:36 Brutus kernel: br0: port 1(bond0) entered blocking state
Dec 29 10:30:36 Brutus kernel: br0: port 1(bond0) entered forwarding state
Dec 29 10:30:36 Brutus dhcpcd[1828]: br0: rebinding lease of 192.168.19.75
Dec 29 10:30:36 Brutus dhcpcd[1828]: br0: probing address 192.168.19.75/24
Dec 29 10:30:38 Brutus root: Fix Common Problems: Error: Unable to communicate with GitHub.com
Dec 29 10:30:38 Brutus root: Fix Common Problems: Other Warning: Could not check for blacklisted plugins
Dec 29 10:30:38 Brutus root: Fix Common Problems: Other Warning: Could not perform unknown plugins installed checks

Network setting GUI settings:

 

.

 

 

Edited December 29, 20178 yr by Limy
Add version

If after the server is all up and running, if you re-scan within FCP does it return the same error?  If not, don't worry about it (ie: ignore the error), as it just means that at the time of array start, the network isn't fully up and running.

1 minute ago, Squid said:

If after the server is all up and running, if you re-scan within FCP does it return the same error?  If not, don't worry about it (ie: ignore the error), as it just means that at the time of array start, the network isn't fully up and running.

 

Yes, the error disappears when there is a rescan.  I just wanted to make sure that I wasn't necessarily missing something.

 

Thanks.