Intel NIC driver issue

Status
Not open for further replies.

xmicks

Dabbler
Joined
Apr 28, 2016
Messages
33
Hello i'm new to Freenas and last week installed version 9.3 and this week version 9.10

But the error messages window is just constantly reporting errors. For what i've read on the forums its related to a nic driver issue with freebsd. I'm on a supermicro X10SLM-F motherboard with 2 intel nics eatch an other controller. The first one is a intel i210-AT and the other one is a intel i217-LM.

this is from the error messages log
i'm now connected through the i217LM network controller (mac: 00:25:90:59:ef:ef)

Code:
Apr 28 13:56:27 FreeNAS devd: Executing '/etc/pccard_ether bridge0 start'
Apr 28 13:56:27 FreeNAS devd: Executing '/etc/pccard_ether epair0a start'
Apr 28 13:56:27 FreeNAS devd: Executing '/etc/pccard_ether epair0b start'
Apr 28 15:56:27 FreeNAS bridge0: Ethernet address: 02:03:78:21:15:00
Apr 28 15:56:27 FreeNAS kernel: em0: promiscuous mode enabled
Apr 28 15:56:27 FreeNAS kernel: bridge0: link state changed to UP
Apr 28 15:56:27 FreeNAS kernel: bridge0: link state changed to UP
Apr 28 15:56:27 FreeNAS epair0a: Ethernet address: 02:ff:20:00:05:0a
Apr 28 15:56:27 FreeNAS epair0b: Ethernet address: 02:ff:70:00:06:0b
Apr 28 15:56:27 FreeNAS kernel: epair0a: link state changed to UP
Apr 28 15:56:27 FreeNAS kernel: epair0a: link state changed to UP
Apr 28 15:56:27 FreeNAS kernel: epair0b: link state changed to UP
Apr 28 15:56:27 FreeNAS kernel: epair0b: link state changed to UP
Apr 28 15:56:27 FreeNAS kernel: em0: link state changed to DOWN
Apr 28 15:56:27 FreeNAS kernel: em0: link state changed to DOWN
Apr 28 15:56:27 FreeNAS kernel: epair0a: promiscuous mode enabled
Apr 28 13:56:27 FreeNAS devd: Executing '/etc/rc.d/dhclient quietstart epair0a'
Apr 28 15:56:27 FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Apr 28 15:56:27 FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Apr 28 13:56:30 FreeNAS devd: Executing '/etc/rc.d/dhclient quietstart em0'
Apr 28 15:56:30 FreeNAS dhclient: New IP Address (em0): 10.0.8.12
Apr 28 15:56:30 FreeNAS dhclient: New Subnet Mask (em0): 255.255.255.0
Apr 28 15:56:30 FreeNAS dhclient: New Broadcast Address (em0): 10.0.8.255
Apr 28 15:56:30 FreeNAS dhclient: New Routers (em0): 10.0.8.1
Apr 28 15:56:30 FreeNAS kernel: em0: link state changed to UP
Apr 28 15:56:30 FreeNAS kernel: em0: link state changed to UP
Apr 28 13:56:37 FreeNAS devd: Executing '/etc/pccard_ether epair1a start'
Apr 28 13:56:37 FreeNAS devd: Executing '/etc/pccard_ether epair1b start'
Apr 28 15:56:37 FreeNAS epair1a: Ethernet address: 02:ff:20:00:06:0a
Apr 28 15:56:37 FreeNAS epair1b: Ethernet address: 02:ff:70:00:07:0b
Apr 28 15:56:37 FreeNAS kernel: epair1a: link state changed to UP
Apr 28 15:56:37 FreeNAS kernel: epair1a: link state changed to UP
Apr 28 15:56:37 FreeNAS kernel: epair1b: link state changed to UP
Apr 28 15:56:37 FreeNAS kernel: epair1b: link state changed to UP
Apr 28 15:56:37 FreeNAS kernel: epair1a: promiscuous mode enabled
Apr 28 13:56:38 FreeNAS devd: Executing '/etc/rc.d/dhclient quietstart epair1a'
Apr 28 15:56:38 FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Apr 28 15:56:38 FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Apr 28 16:00:00 FreeNAS autosnap.py: [tools.autosnap:61] Popen()ing: /sbin/zfs snapshot "Volume1/SharedSet@auto-20160428.1600-2w"
Apr 28 16:17:20 FreeNAS kernel: arp: 10.0.8.12 moved from 02:ff:20:00:06:0a to 00:25:90:59:ef:ef on epair1b
Apr 28 18:14:22 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs list -H -o name '/mnt/Volume1/jails/.warden-template-pluginjail'
Apr 28 18:14:22 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/plexmediaserver_1'
Apr 28 18:14:22 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/sabnzbd_1'
Apr 28 18:14:22 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs list -H -o name '/mnt/Volume1/jails/.warden-template-pluginjail'
Apr 28 18:14:22 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/plexmediaserver_1'
Apr 28 18:14:22 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/sabnzbd_1'
Apr 28 18:14:54 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs list -H -o name '/mnt/Volume1/jails/.warden-template-pluginjail'
Apr 28 18:14:54 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/plexmediaserver_1'
Apr 28 18:14:54 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/sabnzbd_1'
Apr 28 18:14:54 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs list -H -o name '/mnt/Volume1/jails/.warden-template-pluginjail'
Apr 28 18:14:54 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/plexmediaserver_1'
Apr 28 18:14:54 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/sabnzbd_1'
Apr 28 18:15:48 FreeNAS kernel: arp: 10.0.8.12 moved from 02:ff:20:00:06:0a to 00:25:90:59:ef:ef on epair1b
Apr 28 18:16:45 FreeNAS kernel: epair1a: link state changed to DOWN
Apr 28 18:16:45 FreeNAS kernel: epair1a: link state changed to DOWN
Apr 28 18:16:45 FreeNAS kernel: epair1b: link state changed to DOWN
Apr 28 18:16:45 FreeNAS kernel: epair1b: link state changed to DOWN
Apr 28 18:16:46 FreeNAS kernel: ifa_del_loopback_route: deletion failed: 48
Apr 28 18:16:46 FreeNAS Freed UMA keg (udp_inpcb) was not empty (120 items). Lost 12 pages of memory.
Apr 28 18:16:46 FreeNAS Freed UMA keg (udpcb) was not empty (1169 items). Lost 7 pages of memory.
Apr 28 18:16:46 FreeNAS Freed UMA keg (tcptw) was not empty (405 items). Lost 9 pages of memory.
Apr 28 18:16:46 FreeNAS Freed UMA keg (tcp_inpcb) was not empty (120 items). Lost 12 pages of memory.
Apr 28 18:16:46 FreeNAS Freed UMA keg (tcpcb) was not empty (36 items). Lost 12 pages of memory.
Apr 28 18:16:46 FreeNAS Freed UMA keg (ripcb) was not empty (30 items). Lost 3 pages of memory.
Apr 28 18:16:46 FreeNAS hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Apr 28 18:16:46 FreeNAS hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Apr 28 18:16:50 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs list -H -o name '/mnt/Volume1/jails/.warden-template-pluginjail'
Apr 28 18:16:50 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/plexmediaserver_1'
Apr 28 18:16:50 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/sabnzbd_1'
Apr 28 18:16:50 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs list -H -o name '/mnt/Volume1/jails/.warden-template-pluginjail'
Apr 28 18:16:50 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/plexmediaserver_1'
Apr 28 18:16:50 FreeNAS manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/Volume1/jails/sabnzbd_1'
Apr 28 18:17:03 FreeNAS manage.py: [plugins.utils:91] Couldn't retrieve http://10.0.8.12/plugins/sabnzbd/4/_s/status: No JSON object could be decoded
Apr 28 18:17:13 FreeNAS notifier: Performing sanity check on nginx configuration:
Apr 28 18:17:13 FreeNAS notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Apr 28 18:17:13 FreeNAS notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Apr 28 16:17:13 FreeNAS devd: Executing '/etc/pccard_ether epair1a start'
Apr 28 16:17:13 FreeNAS devd: Executing '/etc/pccard_ether epair1b start'
Apr 28 16:17:13 FreeNAS devd: Executing '/etc/rc.d/dhclient quietstart epair1a'
Apr 28 18:17:13 FreeNAS epair1a: Ethernet address: 02:ff:20:00:06:0a
Apr 28 18:17:13 FreeNAS epair1b: Ethernet address: 02:ff:70:00:07:0b
Apr 28 18:17:13 FreeNAS kernel: epair1a: link state changed to UP
Apr 28 18:17:13 FreeNAS kernel: epair1a: link state changed to UP
Apr 28 18:17:13 FreeNAS kernel: epair1b: link state changed to UP
Apr 28 18:17:13 FreeNAS kernel: epair1b: link state changed to UP
Apr 28 18:17:13 FreeNAS kernel: epair1a: promiscuous mode enabled
Apr 28 18:17:13 FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Apr 28 18:17:13 FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b



this is the output of ifconfig
Code:

[root@FreeNAS ~]# ifconfig
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=40098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO>
ether 00:25:90:59:ef:ef
inet 10.0.8.12 netmask 0xffffff00 broadcast 10.0.8.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO>
ether 00:25:90:59:ef:ee
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:03:78:21:15:00
nd6 options=1<PERFORMNUD>
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 6 priority 128 path cost 2000
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 5 priority 128 path cost 2000
member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:20:00:05:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:20:00:06:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
[root@FreeNAS ~]# 


hope somebody can see whats wrong here. if i need to input more info, let me know.
 

xmicks

Dabbler
Joined
Apr 28, 2016
Messages
33
no i am not. really frustrating. i think its a driver relative problem, i have a supermiro x10slm-f with a i210 and a i217 nic. i think the driver isnt working correctly but i cant figure out how to update the driver.can somebody explain how i update the nics-driver?

or maybe the problem can be solved another way? maybe the firmware of my nics are outdated, could that be the problem?
 
D

dlavigne

Guest
i cant figure out how to update the driver.can somebody explain how i update the nics-driver?

You don't, it comes with the OS.

What exactly is the problem? Are the cards flapping? Or are you starting/stopping jails? Are they both plugged in or is your posted ifconfig from when only one was connected?
 

xmicks

Dabbler
Joined
Apr 28, 2016
Messages
33
im now connected on the (em0) i217 nic, the ifconfig i posted was when i was connected to only that interface. when i connect on the other nic, the (igb0) i210, i get errors that my jails(currently sabnzbd and emby) cant load the tree menu.

Code:
An error occurred while unserializing from http://10.0.8.12/plugins/sabnzbd/6/_s/treemenu: No JSON object could be decoded
 
D

dlavigne

Guest
That JSON thing is a known bug that is being investigated.

What are you actually trying to achieve? eg run both NICs at once, run the one that works better? We need more information about your network setup and goals to help you.
 

xmicks

Dabbler
Joined
Apr 28, 2016
Messages
33
also when i first installed the os and booted for the first time, there weren't any network interfaces configured in the web gui. when i try to do that in the webgui it messes up the connectivity. or when i then reboot the system looses connectivity. for instance when i configure it with dhcp it doesnt load the config correctly(for instance without a gateway).

it seems to work the best when i remove all the network config, boot and let the network be configured when the system boots.
 

xmicks

Dabbler
Joined
Apr 28, 2016
Messages
33

xmicks

Dabbler
Joined
Apr 28, 2016
Messages
33
next thing im going to do is to run both nics at once and see what that gives me. is it possible that the firmware of my nics are outdated? the motherboard is 2-3 years old.

is there something i can do to debug this? are there perticular logs i can see to help me figure this out? are there commands i can run that will yield something?
 

pirateghost

Unintelligible Geek
Joined
Feb 29, 2012
Messages
4,219
Have you tried reinstalling from scratch to see if it's a corrupt install?

And try not to post multiple threads for the same issue, it's pretty rude.
 

xmicks

Dabbler
Joined
Apr 28, 2016
Messages
33
i'm doing a fresh install right now, ill report here if that solved the issue.
 

xmicks

Dabbler
Joined
Apr 28, 2016
Messages
33
just did a fresh install and it seems that that didnt solved the issue.

after the fresh install i went to network interfaces and there was no interface configuered. when i wnt to network summary there was a ip of the freenas box, gateway enz. so looks like the dhcp thing worked on boot but it didt made a interface in the os. when i then made a network interface of the em0 interface im connected through right now, network connectivity was corrupted. i can connect to my freenas box but i cant ping 8.8.8.8 on the freenas box.

now im going to see what happens when i boot with both the em0 and the igb0 interface connected.
 

xmicks

Dabbler
Joined
Apr 28, 2016
Messages
33
oh, but why do i lose internet connectivity when i configure a interface?

this is the log
Code:
May 11 15:44:52 freenas notifier: Cannot 'stop' rtsold. Set rtsold_enable to YES in /etc/rc.conf or use 'onestop' instead of 'stop'.
May 11 15:44:52 freenas notifier: Setting hostuuid: 1855ef7b-17c8-11e6-8e9c-00259059efef.
May 11 15:44:52 freenas notifier: Setting hostid: 0xd7622393.
May 11 15:44:52 freenas notifier: dhclient already running? (pid=907).
May 11 15:44:54 freenas notifier: Starting Network: lo0 em0 igb0.
May 11 15:44:54 freenas notifier: lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
May 11 15:44:54 freenas notifier: options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
May 11 15:44:54 freenas notifier: inet6 ::1 prefixlen 128
May 11 15:44:54 freenas notifier: inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
May 11 15:44:54 freenas notifier: inet 127.0.0.1 netmask 0xff000000
May 11 15:44:54 freenas notifier: nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
May 11 15:44:54 freenas notifier: em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
May 11 15:44:54 freenas notifier: options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
May 11 15:44:54 freenas notifier: ether 00:25:90:59:ef:ef
May 11 15:44:54 freenas notifier: inet 10.0.8.12 netmask 0xffffff00 broadcast 10.0.8.255
May 11 15:44:54 freenas notifier: nd6 options=9<PERFORMNUD,IFDISABLED>
May 11 15:44:54 freenas notifier: media: Ethernet autoselect (1000baseT <full-duplex>)
May 11 15:44:54 freenas notifier: status: active
May 11 15:44:54 freenas notifier: igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
May 11 15:44:54 freenas notifier: options=403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO>
May 11 15:44:54 freenas notifier: ether 00:25:90:59:ef:ee
May 11 15:44:54 freenas notifier: nd6 options=9<PERFORMNUD,IFDISABLED>
May 11 15:44:54 freenas notifier: media: Ethernet autoselect
May 11 15:44:54 freenas notifier: status: no carrier
May 11 15:44:55 freenas notifier: route: writing to routing socket: File exists
May 11 15:44:55 freenas notifier: add net fe80::: gateway ::1 fib 0: route already in table
May 11 15:44:55 freenas notifier: route: writing to routing socket: File exists
May 11 15:44:55 freenas notifier: add net ff02::: gateway ::1 fib 0: route already in table
May 11 15:44:55 freenas notifier: route: writing to routing socket: File exists
May 11 15:44:55 freenas notifier: add net ::ffff:0.0.0.0: gateway ::1 fib 0: route already in table
May 11 15:44:55 freenas notifier: route: writing to routing socket: File exists
May 11 15:44:55 freenas notifier: add net ::0.0.0.0: gateway ::1 fib 0: route already in table
May 11 15:44:55 freenas notifier: Cannot 'start' rtsold. Set rtsold_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'.
May 11 15:44:55 freenas notifier: Setting hostname: freenas.local.
May 11 15:44:55 freenas notifier: Stopping collectd.
May 11 15:44:55 freenas notifier: Waiting for PIDS: 2644.
May 11 15:44:55 freenas notifier: Starting collectd.
May 11 15:44:55 freenas notifier: default 10.0.8.1 -fib 0 done
May 11 15:44:55 freenas notifier: delete net fe80::: gateway ::1
May 11 15:44:55 freenas notifier: delete net ff02::: gateway ::1
May 11 15:44:55 freenas notifier: delete net ::ffff:0.0.0.0: gateway ::1
May 11 15:44:55 freenas notifier: delete net ::0.0.0.0: gateway ::1
May 11 15:44:55 freenas notifier: add net fe80::: gateway ::1
May 11 15:44:55 freenas notifier: add net ff02::: gateway ::1
May 11 15:44:55 freenas notifier: add net ::ffff:0.0.0.0: gateway ::1
May 11 15:44:55 freenas notifier: add net ::0.0.0.0: gateway ::1
May 12 00:46:34 freenas notifier: Stopping ntpd.
May 11 15:46:34 freenas ntpd[6923]: ntpd exiting on signal 15 (Terminated)
May 12 00:46:35 freenas notifier: Waiting for PIDS: 6923, 6923.
May 12 00:46:35 freenas notifier: Starting ntpd.
May 12 00:46:35 freenas ntpd[10358]: ntpd 4.2.8p6-a (1): Starting
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
oh, but why do i lose internet connectivity when i configure a interface?

The better question would be if you have internet connectivity then why do you keep breaking it by trying to configure an interface?
 

xmicks

Dabbler
Joined
Apr 28, 2016
Messages
33
i just checked the 'cofigure ipv4 dhcp' box
 

xmicks

Dabbler
Joined
Apr 28, 2016
Messages
33
i now get this in the footer log, when im connected to both the nics
Code:
May 12 01:04:55 FreeNAs mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801409D60 FreeNAs.local. (Addr) that's already in the list
May 12 01:04:55 FreeNAs mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 000000080140A180 13.8.0.10.in-addr.arpa. (PTR) that's already in the list
 
Status
Not open for further replies.
Top