Login

dalby · 2011-11-08, 10:15 PM

i have updated from debian lenny to debian squeeze,

installed a new (custom) kernel to run vservers.

for some reason grub keeps booting the old kernel (i do not have console access, only ssh)

, it should boot Linux 2.6.32-5-vserver-amd64 but it boots Linux 2.6.18-6-vserver-amd64…

when rebooting after installing the first time, the system hung, and i rebooted and the old kernel was loaded i guess, how to reset?

anyone knows?

Thanks in advance!

-(~:#)-> cat /boot/grub/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 part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

if loadfont /usr/share/grub/unicode.pf2 ; then

set gfxmode=640x480

load_video

insmod gfxterm

fi

terminal_output gfxterm

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

set locale_dir=($root)/boot/grub/locale

set lang=en

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-5-vserver-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.32-5-vserver-amd64 ...'

linux /boot/vmlinuz-2.6.32-5-vserver-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.32-5-vserver-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-vserver-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.32-5-vserver-amd64 ...'

linux /boot/vmlinuz-2.6.32-5-vserver-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.32-5-vserver-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.32-5-amd64 ...'

linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

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 part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.32-5-amd64 ...'

linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.32-5-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.26-2-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.26-2-amd64 ...'

linux /boot/vmlinuz-2.6.26-2-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.26-2-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.26-2-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.26-2-amd64 ...'

linux /boot/vmlinuz-2.6.26-2-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.26-2-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-6-vserver-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-6-vserver-amd64 ...'

linux /boot/vmlinuz-2.6.18-6-vserver-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-6-vserver-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-6-vserver-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-6-vserver-amd64 ...'

linux /boot/vmlinuz-2.6.18-6-vserver-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-6-vserver-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-6-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-6-amd64 ...'

linux /boot/vmlinuz-2.6.18-6-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-6-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-6-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-6-amd64 ...'

linux /boot/vmlinuz-2.6.18-6-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-6-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-5-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-5-amd64 ...'

linux /boot/vmlinuz-2.6.18-5-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-5-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-5-amd64 ...'

linux /boot/vmlinuz-2.6.18-5-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-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 ###

**Dungeon-Dave** · 2011-11-08, 10:52 PM

you may need to run update-grub to update GRUB2 with the changes.

As you can't see the console, check your logfiles (in /var/log) for records of boot failures to explain the previous hang.

dalby · 2011-11-08, 11:53 PM

Quote:you may need to run update-grub to update GRUB2 with the changes.

As you can't see the console, check your logfiles (in /var/log) for records of boot failures to explain the previous hang.

thanks for the answer, yes i did the update-grub command

i am going through the logs, already found why the vserver crashes with the original kernel::

ov 6 03:17:02 Hetch kernel: ----------- [cut here ] --------- [please bite here ] ---------

Nov 6 03:17:02 Hetch kernel: Kernel BUG at kernel/vserver/context.c:140

Nov 6 03:17:02 Hetch kernel: invalid opcode: 0000 [4] SMP

Nov 6 03:17:02 Hetch kernel: CPU 1

Nov 6 03:17:03 Hetch kernel: Modules linked in: vmnet parport_pc parport vmmon ipv6 cpufreq_conservative cpufreq_stats cpufreq_ondemandfreq_userspace loop dm_mirror dm_snapshot dm_mod raid10 raid456 xor multipath linear ehci_hcd r8169 ohci_hcd sd_mod thermal fan powernowor raid1 raid0 md_mod atiixp ahci sata_nv sata_sil sata_via libata via82cxxx ide_core 3w_9xxx 3w_xxxx scsi_mod xfs ext3 jbd ext2 mbcache

Nov 6 03:17:03 Hetch kernel: Pid: 3429, comm: cron Tainted: P 2.6.18-6-vserver-amd64 #1

Nov 6 03:17:03 Hetch kernel: RIP: 0010:[<ffffffff80295c6b>] [<ffffffff80295c6b>] free_vx_info+0xb/0x6e

Nov 6 03:17:03 Hetch kernel: RSP: 0018:ffff8100025a3e00 EFLAGS: 00010246

Nov 6 03:17:03 Hetch kernel: RAX: ffff81004e99a001 RBX: ffff81004d1b0640 RCX: 0000000000000000

Nov 6 03:17:03 Hetch kernel: RDX: 0000000000000000 RSI: 0000000000000282 RDI: ffff81004e99a000

Nov 6 03:17:03 Hetch kernel: RBP: 0000000000000000 R08: ffff81004d1b08e8 R09: ffff81004d1b0380

Nov 6 03:17:03 Hetch kernel: R10: 00002b8f5dbf1fa8 R11: 0000000000000000 R12: 0000000000000000

Nov 6 03:17:03 Hetch kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff810002588c07

Nov 6 03:17:03 Hetch kernel: FS: 00002b8f5e2681a0(0000) GS:ffff810003ab4c

Nov 6 03:17:02 Hetch kernel: ----------- [cut here ] --------- [please bite here ] ---------

Nov 6 03:17:02 Hetch kernel: Kernel BUG at kernel/vserver/context.c:140

Nov 6 03:17:02 Hetch kernel: invalid opcode: 0000 [4] SMP

dalby · 2011-11-08, 11:57 PM

for the rest, i dont find anything...

then again, my main question is, how can i still boot with that new kernel? it seems to forget it it is there, once its booted its being saved as the default kernel

**Dungeon-Dave** · 2011-11-09, 07:12 PM

As far as I know, when the kernel is upgraded it adds the relevant lines into the grub config file so that it becomes the default.

This often means that people forget to uninstall older kernels, since they're overlooked. Uninstalling your older ones should remove their lines form the grub config file, thus preventing it from booting that one.

However, that was for GRUB legacy (older version). There should be a tool to amend your GRUB2 configs - try BUM (boot-up manager), see if that does the trick.

(not at my server at the mo, can't check, sorry)

Login
Username/Email:
Password:	Lost Password?
	Remember me