February 11, 201610 yr I recently rebooted my server. It never connected to the network. From the console, I looked in the syslog and found the following: Feb 10 06:36:27 Tower kernel: r8169 0000:02:00.0 rename6: renamed from eth0 Feb 10 06:36:27 Tower kernel: r8169 0000:03:00.0 rename7: renamed from eth1 Feb 10 06:37:57 Tower udevd[1376]: error changing net interface name rename6 to eth2: Feb 10 06:37:58 Tower udevd[1375]: error changing net interface name rename7 to eth2: Feb 10 06:37:58 Tower logger: /etc/rc.d/rc.inet1: List of interfaces: 'bond0' Feb 10 06:37:58 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Feb 10 06:37:58 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Feb 10 06:37:58 Tower logger: /etc/rc.d/rc.inet1: modprobe bonding mode=0 miimon=100 Feb 10 06:37:58 Tower kernel: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Feb 10 06:37:58 Tower kernel: MII link monitoring set to 100 ms Feb 10 06:37:58 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig bond0 up Feb 10 06:37:58 Tower logger: /etc/rc.d/rc.inet1: echo +eth2 > /sys/class/net/bond0/bonding/slaves Feb 10 06:37:58 Tower kernel: bond0: Adding slave eth2 Feb 10 06:37:58 Tower kernel: bond0: Enslaving eth2 as an active interface with a down link Feb 10 06:37:58 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig bond0 192.168.2.158 broadcast 192.168.2.255 netmask 255.255.255.0 Feb 10 06:37:58 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.2.1 metric 1 (note the lines "error changing net interface name rename* to eth2: File exists") So my ethernet devices are getting renamed (as noted in the first two lines above), and that is causing the network bonding to fail (since it doesn't try to enslave either eth0 or eth1). It does try to use eth2 (which corresponds to an onboard LAN port which is not in use). It seems strange to me that those two ethernet ports have somehow been renamed from the usual (eth0 and eth1) to 'rename6' and 'rename7'! Here is where they were loaded (earlier in the syslog): Feb 10 06:36:27 Tower kernel: r8169 0000:02:00.0 eth0: RTL8168e/8111e at 0xffffc9000314e000, 10:fe:ed:02:06:6d, XID 0c200000 IRQ 27 Feb 10 06:36:27 Tower kernel: r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] Feb 10 06:36:27 Tower kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Feb 10 06:36:27 Tower kernel: r8169 0000:03:00.0 eth1: RTL8168e/8111e at 0xffffc9000369c000, 10:fe:ed:02:06:6d, XID 0c200000 IRQ 28 Feb 10 06:36:27 Tower kernel: r8169 0000:03:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko] Feb 10 06:36:27 Tower kernel: alx 0000:04:00.0 eth2: Qualcomm Atheros AR816x/AR817x Ethernet [10:fe:ed:02:06:6d] So rather than really fix this, I focused on just getting the box connected to the network. I finally figured out that I could change the /etc/rc.d/rc.inet1.config file: From BONDNAME=${BONDNAME:="bond0"} BONDNICS=${BONDNICS:="eth0 eth1 eth2 eth3"} to BONDNAME=${BONDNAME:="bond0"} BONDNICS=${BONDNICS:="eth0 eth1 eth2 eth3 rename6 rename7"} Then, I ran /etc/rc.d/rc.inet1 restart and everything works. But this isn't permanent -- it will fail again when the box is rebooted. What's going on and how do I fix it?
February 12, 201610 yr Author More data on this... I can see now (after a couple of reboots) that the assignment of eth0/eth1/eth2 to my devices is random. As long as eth2 doesn't get assigned to the unused onboard port, things work ok. eg: Feb 12 06:43:49 Tower kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Feb 12 06:43:49 Tower kernel: r8169 0000:02:00.0 eth0: RTL8168e/8111e at 0xffffc9000314e000, 10:fe:ed:02:06:6d, XID 0c200000 IRQ 27 Feb 12 06:43:49 Tower kernel: r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] Feb 12 06:43:49 Tower kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Feb 12 06:43:49 Tower kernel: alx 0000:04:00.0 eth1: Qualcomm Atheros AR816x/AR817x Ethernet [10:fe:ed:02:06:6d] Feb 12 06:43:49 Tower kernel: r8169 0000:03:00.0 eth2: RTL8168e/8111e at 0xffffc90003646000, 10:fe:ed:02:06:6d, XID 0c200000 IRQ 28 Feb 12 06:43:49 Tower kernel: r8169 0000:03:00.0 eth2: jumbo features [frames: 9200 bytes, tx checksumming: ko] Then, the renaming occurs (renaming eth0 to rename6 and eth1 to rename7), which means that the bonding (which tries eth0-eth3) only finds eth2: Feb 12 06:43:49 Tower kernel: r8169 0000:02:00.0 rename6: renamed from eth0 Feb 12 06:43:49 Tower kernel: alx 0000:04:00.0 rename7: renamed from eth1 Feb 12 06:44:17 Tower kernel: usb 1-3: USB disconnect, device number 2 Feb 12 06:44:17 Tower kernel: usb 1-4: USB disconnect, device number 3 Feb 12 06:45:19 Tower udevd[1372]: error changing net interface name rename6 to eth2: File exists Feb 12 06:45:20 Tower udevd[1376]: error changing net interface name rename7 to eth2: File exists Feb 12 06:45:20 Tower logger: /etc/rc.d/rc.inet1: List of interfaces: 'bond0' Feb 12 06:45:20 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Feb 12 06:45:20 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Feb 12 06:45:20 Tower logger: /etc/rc.d/rc.inet1: modprobe bonding mode=0 miimon=100 Feb 12 06:45:20 Tower kernel: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Feb 12 06:45:20 Tower kernel: MII link monitoring set to 100 ms Feb 12 06:45:20 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig bond0 up Feb 12 06:45:20 Tower logger: /etc/rc.d/rc.inet1: echo +eth2 > /sys/class/net/bond0/bonding/slaves Feb 12 06:45:20 Tower kernel: bond0: Adding slave eth2 Feb 12 06:45:20 Tower kernel: r8169 0000:03:00.0 eth2: link down Feb 12 06:45:20 Tower kernel: r8169 0000:03:00.0 eth2: link down Feb 12 06:45:20 Tower kernel: bond0: Enslaving eth2 as an active interface with a down link Feb 12 06:45:20 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig bond0 192.168.2.158 broadcast 192.168.2.255 netmask 255.255.255.0 Feb 12 06:45:20 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.2.1 metric 1 So in this (random) assignment, I don't have bonded cards but at least I do have network connectivity. I found some seemingly related information here http://www.linuxquestions.org/questions/linux-networking-3/network-interface-being-renamed-how-to-prevent-that-946662/. Unfortunately, I think that changes described here are pretty hard to implement when the related files are in the compressed image on the USB key. I found a workaround. I added this to the top of my /boot/config/go line: sed -i 's/eth0 eth1 eth2 eth3/eth0 eth1 eth2 eth3 rename6 rename7/' /etc/rc.d/rc.inet1.conf /etc/rc.d/rc.inet1 stop /etc/rc.d/rc.inet1 start This adds 'rename6' and 'rename7' as usable ethernet devices and restarts the network. Not ideal (and may break sometime down the road), but it works for now.
February 12, 201610 yr are your network devices usb based? Can you post the output of System Devices inside the Tools page? probably the diagnostics zip as well...
February 12, 201610 yr Author My network cards are not USB based. Here is the devices output: PCI Devices 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) 00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c4) 00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev 04) 00:1f.2 IDE interface: Intel Corporation 7 Series/C210 Series Chipset Family 4-port SATA Controller [iDE mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 00:1f.5 IDE interface: Intel Corporation 7 Series/C210 Series Chipset Family 2-port SATA Controller [iDE mode] (rev 04) 01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 04:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10) 05:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41) 07:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) 07:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1) IOMMU Groups /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/2/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:16.0 /sys/kernel/iommu_groups/4/devices/0000:00:1a.0 /sys/kernel/iommu_groups/5/devices/0000:00:1b.0 /sys/kernel/iommu_groups/6/devices/0000:00:1c.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.1 /sys/kernel/iommu_groups/8/devices/0000:00:1c.2 /sys/kernel/iommu_groups/9/devices/0000:00:1c.3 /sys/kernel/iommu_groups/9/devices/0000:05:00.0 /sys/kernel/iommu_groups/10/devices/0000:00:1c.4 /sys/kernel/iommu_groups/11/devices/0000:00:1d.0 /sys/kernel/iommu_groups/12/devices/0000:00:1f.0 /sys/kernel/iommu_groups/12/devices/0000:00:1f.2 /sys/kernel/iommu_groups/12/devices/0000:00:1f.3 /sys/kernel/iommu_groups/12/devices/0000:00:1f.5 /sys/kernel/iommu_groups/13/devices/0000:02:00.0 /sys/kernel/iommu_groups/14/devices/0000:03:00.0 /sys/kernel/iommu_groups/15/devices/0000:04:00.0 /sys/kernel/iommu_groups/16/devices/0000:07:00.0 /sys/kernel/iommu_groups/16/devices/0000:07:00.1 USB Devices Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 13fe:3e00 Kingston Technology Company Inc. Flash Drive Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04d9:1503 Holtek Semiconductor, Inc. Shortboard Lefty Bus 001 Device 004: ID 04f3:0234 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub SCSI Devices [0:0:0:0] disk USB DISK 2.0 PMAP /dev/sda [1:0:0:0] disk ATA WDC WD4001FFSX-6 0A81 /dev/sde [1:0:1:0] disk ATA WDC WD30EFRX-68E 0A80 /dev/sdf [1:0:2:0] disk ATA WDC WD40EZRX-00S 0A80 /dev/sdg [1:0:3:0] disk ATA ST4000VN000-1H41 SC43 /dev/sdh [1:0:4:0] disk ATA WDC WD40EZRX-22S 0A80 /dev/sdi [1:0:5:0] disk ATA ST4000DM000-1F21 CC52 /dev/sdj [1:0:6:0] disk ATA WDC WD30EZRX-00D 0A80 /dev/sdk [2:0:0:0] disk ATA KINGSTON SH103S3 C4 /dev/sdb [2:0:1:0] disk ATA ST380013AS 8.12 /dev/sdc [3:0:0:0] disk ATA KINGSTON SH103S3 BBF0 /dev/sdd diagnostic file attached tower-diagnostics-20160212-1422.zip
February 12, 201610 yr Can you return the output of: # cat /etc/udev/rules.d/70-persistent-net.rules though I don't understand why this could be a problem since it is generated every startup (stored in ram)
February 16, 201610 yr Author As requested.. # This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key. # PCI device 0x1969:/sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0 (alx) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="10:fe:ed:02:06:6d", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x10ec:/sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0 (r8169) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="10:fe:ed:02:06:6d", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x10ec:/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0 (r8169) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="10:fe:ed:02:06:6d", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
February 16, 201610 yr now I'm confused. see that all the addresses have the same value. that means from the "device manager" point of view, all your devices have the same mac address. In fact the rules here are stating that all your devices should have the same eth2 (that's why eth0 and eth1 got renamed), since its the last rule. and upon a little reviewing, I think the file is generated every bootup so, I'm not sure why you are getting this. can you also port the output of ip link and ethtool rename6 ethtool rename7
February 16, 201610 yr Author ip link # ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN mode DEFAULT link/gre 0.0.0.0 brd 0.0.0.04: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN mode DEFAU LT qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff5: ip_vti0@NONE: <NOARP> mtu 1364 qdisc noop state DOWN mode DEFAULT link/ipip 0.0.0.0 brd 0.0.0.0 6: rename6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000 link/ether 10:fe:ed:02:06:6d brd ff:ff:ff:ff:ff:ff 7: rename7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000 link/ether 10:fe:ed:02:06:6d brd ff:ff:ff:ff:ff:ff 8: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000 link/ether 10:fe:ed:02:06:6d brd ff:ff:ff:ff:ff:ff 10: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT link/ether 10:fe:ed:02:06:6d brd ff:ff:ff:ff:ff:ff 11: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT link/ether a2:46:fb:b0:86:c7 brd ff:ff:ff:ff:ff:ff 12: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT link/ether 52:54:00:0b:15:fd brd ff:ff:ff:ff:ff:ff 13: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN mode DEFAULT qlen 500 link/ether 52:54:00:0b:15:fd brd ff:ff:ff:ff:ff:ff 15: veth559b2d4@if14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT link/ether a2:46:fb:b0:86:c7 brd ff:ff:ff:ff:ff:ff 16: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN mode DEFAULT qlen 500 link/ether fe:54:00:e5:36:e4 brd ff:ff:ff:ff:ff:ff and ethtool... root@Tower:~# ethtool rename6 Settings for rename6: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: no root@Tower:~# ethtool rename7 Settings for rename7: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Current message level: 0x000060e4 (24804) link ifup rx_err tx_err hw wol Link detected: no I'm flummoxed..
February 17, 201610 yr I'm stumped. but I'd try this: boot the machine with a LIVE Linux CD or USB drive. then take a look if the eth interfaces still have the same address. Maybe removing any addon network card will help.
Archived
This topic is now archived and is closed to further replies.