broken network on the node

[hamed]

Hi,
I was running proxmox 2.3, and suddenly my server stopped working.
I rebooted the system, but after that, the eth0 is not present!

ifup eth0

SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
eth0: ERROR while getting interface flags: No such device


root@node1 ~ # pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-96
pve-kernel-2.6.32-19-pve: 2.6.32-96
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1




Does anyone has any idea how to solve this?

Thanks

 

[screenie]

do you see the nic in the output of 'lspci'

 

[hamed]

yes, it displays Realtek ethernet controller in lspci.
When I boot the system using a rescue cd, the network works just fine. the main os has some problems that I can't figure out.

 

[wahmed]

Did you try to run ifconfig or ifconfig -a to see if it shows any ethX ?

 

[hamed]

root@node1 ~ # ifconfig eth0
eth0: error fetching interface information: Device not found

 

[wahmed]

only type ifconfig -a without any ethX. See if device name changed to eth2 or eth3 or something else.

 

[hamed]

available networks from ifconfig -a
lo
venet0-00
vmbr1

 

[wahmed]

Your venet0-00 might be the old eth0. Try to change it in /etc/network/interfaces and see if it works.

 

[hamed]

no, It's not.
Here is the output of iconfig -a:

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)


venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: fe80::1/128 Scope:Link
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


vmbr1     Link encap:Ethernet  HWaddr 16:65:8c:19:ef:b1
          inet addr:10.20.30.40  Bcast:10.20.30.255  Mask:255.255.255.0
          inet6 addr: fe80::1465:8cff:fe19:efb1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)

When I boot using rescue disk (in which eth0 works properly), venet0-00 still exist.

 

[hamed]

Ok, I finally found the problem.

in the file /etc/modprobe.d/blacklist.conf , my network device was inserted!
blacklist r8169

I removed this line and restarted the system and it's working fine now.
I just don't know how it got there!

And thank you for trying to help me

 

[mir]

The reason you have a blacklist r8169 must be because you at one time have installed the driver downloaded from Realtek (r8168). When you install this driver it will blacklist the use of r8169 from the kernel since they are substituting each other and to ensure using the right driver when the server boots.

 

[wahmed]

Another reason to stay away from Realtek.
I am glad you found out the cause of the issue though! Will come in handy for somebody in future no doubt.

 

[mir]

As of kernel 3.0 with the addition of firmware-realtek the r8169 driver in the kernel will be identical to realtek's own r8168.
8169 10/100/1000 GIGABIT ETHERNET DRIVER
M: Realtek linux nic maintainers <nic_swsd@realtek.com>
M: Francois Romieu <romieu@fr.zoreil.com>
L: netdev@vger.kernel.org
S: Maintained
F: drivers/net/ethernet/realtek/r8169.c

 

[Donatchiligui]

Hello dear community,
Here is my current problem. The 2 physical network cards are inactive. To be able to access my proxmox interface, I had to install a usb-network adapter. This annoys me enormously. I've done the PVE updates, and everything else I know, but nothing. Can someone please help me activate the cards?

Bests regards!!!