PDA

View Full Version : [SOLVED] Grub menu changed by itself



akssps011
May 4th, 2010, 01:39 PM
Hi

I am using kubuntu 9.04 dual booting with winXP. The package kit showed that I have 179 bug fixes. So I updated them.

Now the boot time grub menu shows 6(two different versions for kubuntu and kubuntu recovery mode) entries instead of usual 4(winXp + kubuntu + kubuntu recovery mode + memtest).
My grub.cfg file is as follows:



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

### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
insmod ext2
set root=(hd0,8)
search --no-floppy --fs-uuid --set 24a2b3cb-33b3-492e-be4d-c88e419bfd07
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

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

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-21-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,8)
search --no-floppy --fs-uuid --set 24a2b3cb-33b3-492e-be4d-c88e419bfd07
linux /boot/vmlinuz-2.6.31-21-generic root=UUID=24a2b3cb-33b3-492e-be4d-c88e419bfd07 ro quiet splash
initrd /boot/initrd.img-2.6.31-21-generic
}
menuentry "Ubuntu, Linux 2.6.31-21-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,8)
search --no-floppy --fs-uuid --set 24a2b3cb-33b3-492e-be4d-c88e419bfd07
linux /boot/vmlinuz-2.6.31-21-generic root=UUID=24a2b3cb-33b3-492e-be4d-c88e419bfd07 ro single
initrd /boot/initrd.img-2.6.31-21-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,8)
search --no-floppy --fs-uuid --set 24a2b3cb-33b3-492e-be4d-c88e419bfd07
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=24a2b3cb-33b3-492e-be4d-c88e419bfd07 ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,8)
search --no-floppy --fs-uuid --set 24a2b3cb-33b3-492e-be4d-c88e419bfd07
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=24a2b3cb-33b3-492e-be4d-c88e419bfd07 ro single
initrd /boot/initrd.img-2.6.31-14-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Professional (on /dev/sda1)" {
insmod ntfs
set root=(hd0,1)
search --no-floppy --fs-uuid --set 6e39591574b2ae8a
drivemap -s (hd0) ${root}
chainloader +1
}
### 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 ###




What is wrong. How can I change the entries. Which one to remove ?

psusi
May 4th, 2010, 02:12 PM
Nothing wrong here. You got a newer kernel installed so you have the choice between both. It is usually a good idea to keep at least one older kernel in case something goes wrong with the new one you have a backup. Otherwise, you can remove the older kernel in synaptic.

kansasnoob
May 4th, 2010, 02:25 PM
It looks like you actually have Ubuntu 9.10 from the kernel #? You can see by running:


lsb_release -a

Anyway I'd guess you just had a kernel update, so you now show a boot entry and a recovery mode entry for both kernels '2.6.31-21' and '2.6.31-14', so that alone accounts for 4 menu entries. Then you'd also have a 'memtest' entry and the entry for 'Microsoft Windows XP Professional'.

It's actually a good idea, and common practice, to leave at least two kernels installed so if something malfunctions with the newest kernel you can sometimes boot into the previous kernel.

It is however perfectly fine to remove the 'memtest' options, I mean how often is that used? It can be removed with the command:


sudo chmod -x /etc/grub.d/20_memtest86+

Should you decide to remove an older kernel at some point here's what I do, first run "sudo update-grub":


lance@lance-desktop:~$ sudo update-grub
[sudo] password for lance:
Generating grub.cfg ...
Found background image: moreblue-orbit-grub.png
Found linux image: /boot/vmlinuz-2.6.32-22-generic
Found initrd image: /boot/initrd.img-2.6.32-22-generic
Found linux image: /boot/vmlinuz-2.6.32-21-generic
Found initrd image: /boot/initrd.img-2.6.32-21-generic
Found Windows NT/2000/XP (loader) on /dev/sda1
Found Debian GNU/Linux (squeeze/sid) on /dev/sda12
Found Debian GNU/Linux (5.0.4) on /dev/sda14
Found Ubuntu 10.04 LTS (10.04) on /dev/sda16
Found Ubuntu 10.04 LTS (10.04) on /dev/sda18
Found Ubuntu 9.10 (9.10) on /dev/sda3
Found Ubuntu 10.04 LTS (10.04) on /dev/sdb1
Found Ubuntu 10.04 LTS (10.04) on /dev/sdb6
done


I multi-boot so I know that looks confusing but I want to remove Lucid's '2.6.32-21' kernel (as highlighted in that example), so I now open Synaptic Package Manager and click on Search, then I just copy-n-paste that kernel # to the search window, click on search, then I can see I need to remove three packages, so I mark them for removal, apply, run "sudo update-grub" again and voila, that kernel's now gone:

155442

Clear as mud :confused: