No Eth0 under raid 5 setup on new server.

vdemuth · 02-28-2013, 12:46 AM

So, just built a new server and set it up as raid5 for / /boot and swap.
During the setup (which was an adventure in itself due to the Slackware documentation having errors) I noticed that I had both eth0 and eth1 available. However, when complete, upon booting the new server, using an initrd, I only get Eth1. Eth0 is now showing as 'rename2' when probing using ifconfig. 'rename2' is unable to be setup.

Also, even though I have set up Eth1 for a static ip, it fails to connect to the network with an error of 'network unreachable' I got round it by first doing a dhcpcd on it, then downing it and bringing it back up with the static ip I need in rc.local. But that is a bit of a cludge really.

So, all in all, a successful server build, but just a couple of small issues to address.

FYI, lspci is thus:

Quote:

root@Blackpig1:/home/vic# lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 06)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7 (rev 06)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 8 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
01:00.0 PCI bridge: nVidia Corporation NF200 PCIe 2.0 switch (rev a3)
02:00.0 PCI bridge: nVidia Corporation NF200 PCIe 2.0 switch (rev a3)
02:02.0 PCI bridge: nVidia Corporation NF200 PCIe 2.0 switch (rev a3)
03:00.0 VGA compatible controller: nVidia Corporation GT218 [GeForce 8400 GS] (rev a2)
03:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
0a:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)
root@Blackpig1:/home/vic#

And ifconfig:

Quote:

root@Blackpig1:/home/vic# ifconfig
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.201 netmask 255.255.255.255 broadcast 192.168.1.201
inet6 fe80::20b:e0ff:fef0:ed prefixlen 64 scopeid 0x20<link>
ether 00:0b:e0:f0:00:ed txqueuelen 1000 (Ethernet)
RX packets 50838003 bytes 71945699040 (67.0 GiB)
RX errors 0 dropped 6 overruns 0 frame 0
TX packets 25637932 bytes 2102164305 (1.9 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 90 bytes 10612 (10.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 90 bytes 10612 (10.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

rename2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:0b:e0:f0:00:ed txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

root@Blackpig1:/home/vic#

Any one able to assist?

TIA

zasavage · 02-28-2013, 01:31 AM

@vdemuth

I would delete the file /etc/udev/rules.d/70-persistent-net.rules restart and see what you have then ..

Could be that udev did some thing funky with the naming of the Ethernet

Lawrence

mRgOBLIN · 02-28-2013, 02:36 AM

Quote:

Originally Posted by vdemuth

So, just built a new server and set it up as raid5 for / /boot and swap.
During the setup (which was an adventure in itself due to the Slackware documentation having errors)

TIA

Care to elaborate on those errors?

vdemuth · 02-28-2013, 10:10 AM

Yeah, sorry, should have been more succinct.

Followed the rather excellent Slackware guide for setting up a raid array, but ended up with a kernel panic as it turns out that booting from a raid array doesn't allow udev to create the device nodes until it has mounted the raid array which it can't do until udev has created the device nodes which it........ Well you get the picture.

Any way, turned out to be an error in the guide which fails to mention that you need to create an /etc/mkinitrd.conf file which contains the line "UDEV"="1" as per this guide https://sites.google.com/site/pincza...at-4kb-sectors. (based off of the Slackware one)
The other error was to do with sfdisk, which doesn't seem able to copy a partition table from one drive to another if the recipient drive has no existing part table, so really just lacking info on that score.

Anyhow sorted all that and up and running, but now still stuck with the weird network interfaces issue.

vdemuth · 03-03-2013, 05:59 AM

Tried deleting the persistent net rules. On reboot just the same.

Anyone got any ideas?

vdemuth · 03-06-2013, 02:38 PM

Still looking for an answer on this problem. Anyone?

TIA

vdemuth · 03-07-2013, 09:22 AM

More info,

Doing a

Code:

dmesg | grep eth

gives this response

Quote:

[ 10.994666] r8169 0000:06:00.0 eth0: RTL8168d/8111d at 0xffffc900103f8000, 00:0b:e0:f0:00:ed, XID 083000c0 IRQ 46
[ 11.004843] r8169 0000:06:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 11.015349] r8169 0000:05:00.0 eth1: RTL8168d/8111d at 0xffffc900103fe000, 00:0b:e0:f0:00:ed, XID 083000c0 IRQ 48
[ 11.015350] r8169 0000:05:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 50.077423] r8169 0000:05:00.0 eth1: link down
[ 50.077432] r8169 0000:05:00.0 eth1: link down
[ 51.802367] r8169 0000:05:00.0 eth1: link up

It seems that both eth0 and eth1 are recognised at boot time but they both seem to have the same MAC address, which is wierd. I have checked all the logs I can find and see no reason why this should be.
It would explain why I am having some networking issues and probably why eth0 is getting wrongly identified as rename2, but not why the boot/install cd sees both IF's with different MACs.

I'm also no further forward in finding an answer.

Anyone able to assist at all?