Can't boot the new kernel after Update to 2.1

chewbaccus

New Member
Jan 24, 2012
16
0
1
I have a problem after update to 2.1

The new kernel is set in the grub.cfg but the boot menu shows me only the older kernels.
Even older kernels which i have uninstall.
update-grub didn't helped.
I can't boot the new kernel !!
Here is my grub.cfg

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
set locale_dir=($root)/boot/grub/locale
set lang=de
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-14-pve' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-14-pve ...'
linux /boot/vmlinuz-2.6.32-14-pve root=/dev/mapper/pve-root ro quiet irqpoll
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-14-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-14-pve (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-14-pve ...'
linux /boot/vmlinuz-2.6.32-14-pve root=/dev/mapper/pve-root ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-14-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-12-pve' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-12-pve ...'
linux /boot/vmlinuz-2.6.32-12-pve root=/dev/mapper/pve-root ro quiet irqpoll
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-12-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-12-pve (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-12-pve ...'
linux /boot/vmlinuz-2.6.32-12-pve root=/dev/mapper/pve-root ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-12-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-10-pve' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-10-pve ...'
linux /boot/vmlinuz-2.6.32-10-pve root=/dev/mapper/pve-root ro quiet irqpoll
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-10-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-10-pve (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-10-pve ...'
linux /boot/vmlinuz-2.6.32-10-pve root=/dev/mapper/pve-root ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-10-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/pve-root ro quiet irqpoll
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/pve-root ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-12-pve
proxmox-ve-2.6.32: 2.1-74
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-12-pve: 2.6.32-68
pve-kernel-2.6.32-14-pve: 2.6.32-74
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-49
pve-firmware: 1.0-18
libpve-common-perl: 1.0-30
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-31
vncterm: 1.0-3
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-8
ksm-control-daemon: 1.1-1
 
No. I have Grub2 installed !! /boot/grub/grub.cfg
The update shows no errors.
I can't find the problem.
 
Look in my grub.cfg
there are this kernel entries listed.
- 2.6.32-14-pve
- 2.6.32-12-pve
- 2.6.32-10-pve
- 2.6.32-5-amd64

when i boot the host, the grub boot menu shows me:
- 2.6.32-12-pve
- 2.6.32-10-pve
- 2.6.32-7-pve
- 2.6.32-6-pve
- 2.6.32-5-amd64
 
Look in my grub.cfg
there are this kernel entries listed.
- 2.6.32-14-pve
- 2.6.32-12-pve
- 2.6.32-10-pve
- 2.6.32-5-amd64

when i boot the host, the grub boot menu shows me:
- 2.6.32-12-pve
- 2.6.32-10-pve
- 2.6.32-7-pve
- 2.6.32-6-pve
- 2.6.32-5-amd64
Do you by any chance use RAID? If so have you installed the new grub on all raid devices? The BIOS should tell which device is used for booting.
 
that's why we recommend everybody using hardware raid instead of mdraid :)
 
Can't fix my problem !!
I have done:
grub-install -- modules=raid dev/sda
grub-install -- modules=raid dev/sdb
update-grub

The Boot-Menu shows me furthermore the old kernels !!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!