Upgrade 1.5 to 1.6 on OVH

M

meto

Member
Apr 6, 2010
96
0
6
Hi,

I've recently upgraded, but i did't do a reboot, since I got error:

Code: 
Setting up pve-kernel-2.6.32-3-pve (2.6.32-12) ...
update-initramfs: Generating /boot/initrd.img-2.6.32-3-pve
W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl8168d-1.fw for module r8169
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Searching for GRUB installation directory ... found: /boot/grub

I'm using OVH's Kimsufi i7-4 server.
 
Pls also contact OVH support.
 
There is none ;) I think they would say to BUY KVM which is not an option...

The ethernet adaptor which is mounted:
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)

Also with 2.6.32-2 there is no such error:
update-initramfs: Generating /boot/initrd.img-2.6.32-2-pve
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Searching for GRUB installation directory ... found: /boot/grub
Click to expand...

Might that be solution to this problem?
http://us.generation-nt.com/bug-561...ule-r8169-rtl8168d-1-2-fw-help-168938801.html
 
Last edited:
I've done some research, and it seams that it might be working despite the warning (module r8169 is in the kernel). Although I don't want to learn myself by hard at my production servers. Unfortunately i don't have any spare one that could be broken.
 
meto said:
I've done some research, and it seams that it might be working despite the warning (module r8169 is in the kernel). Although I don't want to learn myself by hard at my production servers. Unfortunately i don't have any spare one that could be broken.
Click to expand...

Seems those firmware files are not available at all. I guess the driver still works if it worked before.
 
Last edited by a moderator:
this ovh thread is about 2.6.32-12 - actual is 2.6.32-13 - is this better?
 
dietmar said:
Seems those firmware files are not available at all. I guess the driver still works if it worked before.
Click to expand...

Hello,
sadly it's not the case, atleast for the Hetzner Servers.
The pve_2.6.32-8 works, the latest pve_2.6.32-13 doesn't

It looks as the problem is due to the kernel package.
how to test it:

# dpkg -P --force-all pve-firmware pve-kernel-2.6.32-2-pve pve-kernel-2.6.32-3-pve
# rm -rf /lib/modules/2.6.32-*


# dpkg -i /var/cache/apt/archives/pve-firmware_1.0-7_all.deb

# dpkg -i pve-kernel-2.6.32-2-pve_2.6.32-8_amd64.deb
...
Setting up pve-kernel-2.6.32-2-pve (2.6.32-8) ...
update-initramfs: Generating /boot/initrd.img-2.6.32-2-pve
Searching for GRUB installation directory ... found: /boot/grub
...
Updating /boot/grub/menu.lst ... done


# dpkg -i pve-kernel-2.6.32-3-pve_2.6.32-13_amd64.deb
...
Setting up pve-kernel-2.6.32-3-pve (2.6.32-13) ...
update-initramfs: Generating /boot/initrd.img-2.6.32-3-pve
W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl8168d-1.fw for module r8169
Searching for GRUB installation directory ... found: /boot/grub
...
Updating /boot/grub/menu.lst ... done
 
fortuik said:
Hello,
sadly it's not the case, atleast for the Hetzner Servers.
The pve_2.6.32-8 works, the latest pve_2.6.32-13 doesn't

It looks as the problem is due to the kernel package.
how to test it:

# dpkg -P --force-all pve-firmware pve-kernel-2.6.32-2-pve pve-kernel-2.6.32-3-pve
# rm -rf /lib/modules/2.6.32-*


# dpkg -i /var/cache/apt/archives/pve-firmware_1.0-7_all.deb

# dpkg -i pve-kernel-2.6.32-2-pve_2.6.32-8_amd64.deb
...
Setting up pve-kernel-2.6.32-2-pve (2.6.32-8) ...
update-initramfs: Generating /boot/initrd.img-2.6.32-2-pve
Searching for GRUB installation directory ... found: /boot/grub
...
Updating /boot/grub/menu.lst ... done


# dpkg -i pve-kernel-2.6.32-3-pve_2.6.32-13_amd64.deb
...
Setting up pve-kernel-2.6.32-3-pve (2.6.32-13) ...
update-initramfs: Generating /boot/initrd.img-2.6.32-3-pve
W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl8168d-1.fw for module r8169
Searching for GRUB installation directory ... found: /boot/grub
...
Updating /boot/grub/menu.lst ... done
Click to expand...
I've finally tested and .32-3 doesn't work with kernel .32-13 on OVH also. PVE 1.6 + kernel from .32-2 works good, but i switched to .18 to spare me some nerves.

Seams that 2.6.32 with OpenVZ is buggy as hell. Why whould you push it so hard to release? I am personally waiting for cutting edge KVM-only stable kernel.
 
You must log in or register to reply here.
Top Bottom