GRUB2 issue

Asked by Athani on 2009-08-01

I updated from Jaunty to Karmic Alpha 3. I installed GRUB2 from Synaptic. I have confirmed that GRUB2 works on my PC as I can see it as an option in my original GRUB and can boot to OSes using it. Now I want to get rid of the original GRUB. Following the steps on https://wiki.ubuntu.com/Grub2 did not work. What shall I do?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu grub2 Edit question
Assignee:
No assignee Edit question
Solved by:
Larry Jordan
Solved:
2009-11-05
Last query:
2009-11-05
Last reply:
2009-08-04

You edit the menu.lst in /boot/grub carefully and remove the entry for the old GRUB.

Hope that helps
Shane

Athani (chandan-athani) said : #2

I'm giving my menu.lst file contents below. Kindly tell me what to do. I also want to remove the old GRUB loader. And to change the order in which the OSes appear. Thanks.
******************************

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=e3abcfa1-2bd5-4391-aaeb-9e97dee747e1 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=e3abcfa1-2bd5-4391-aaeb-9e97dee747e1

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Chainload into GRUB 2
uuid e3abcfa1-2bd5-4391-aaeb-9e97dee747e1
kernel /boot/grub/core.img

title ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
root

title When you have verified GRUB 2 works, you can use this command to
root

title complete the upgrade: upgrade-from-grub-legacy
root

title ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
root

title Ubuntu karmic (development branch), kernel 2.6.31-4-generic
uuid e3abcfa1-2bd5-4391-aaeb-9e97dee747e1
kernel /boot/vmlinuz-2.6.31-4-generic root=UUID=e3abcfa1-2bd5-4391-aaeb-9e97dee747e1 ro quiet splash
initrd /boot/initrd.img-2.6.31-4-generic
quiet

title Ubuntu karmic (development branch), kernel 2.6.31-4-generic (recovery mode)
uuid e3abcfa1-2bd5-4391-aaeb-9e97dee747e1
kernel /boot/vmlinuz-2.6.31-4-generic root=UUID=e3abcfa1-2bd5-4391-aaeb-9e97dee747e1 ro single
initrd /boot/initrd.img-2.6.31-4-generic

title Ubuntu karmic (development branch), kernel 2.6.28-14-generic
uuid e3abcfa1-2bd5-4391-aaeb-9e97dee747e1
kernel /boot/vmlinuz-2.6.28-14-generic root=UUID=e3abcfa1-2bd5-4391-aaeb-9e97dee747e1 ro quiet splash
initrd /boot/initrd.img-2.6.28-14-generic
quiet

title Ubuntu karmic (development branch), kernel 2.6.28-14-generic (recovery mode)
uuid e3abcfa1-2bd5-4391-aaeb-9e97dee747e1
kernel /boot/vmlinuz-2.6.28-14-generic root=UUID=e3abcfa1-2bd5-4391-aaeb-9e97dee747e1 ro single
initrd /boot/initrd.img-2.6.28-14-generic

title Ubuntu karmic (development branch), memtest86+
uuid e3abcfa1-2bd5-4391-aaeb-9e97dee747e1
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Microsoft Windows XP Home Edition
rootnoverify (hd0,0)
savedefault
makeactive
chainloader +1

Athani (chandan-athani) said : #3

I mean that I also want to change the default OS to Windows XP as my girlfriend is not comfortable using either the GRUB or Ubuntu.

Athani (chandan-athani) said : #4

I'd tried a command. Please see the command and the result below.
***********************

chandan@chandan-desktop:~$ sudo update-from grub-legacy
sudo: update-from: command not found

Larry Jordan (larryjor) said : #5

     One of the reasons I love to check on this daily is that I learn so many new things....I wasn't aware there WAS a grub2. Having looked at this and checked for others with an internet search, I found a successful user of it at:
http://gastly.iblogger.org/how-to-install-grub2-on-ubuntu-jaunty/ who gives instruction. It looks like the only thing different is that you didn't hyphenate all the words and used 'update' instead of 'upgrade' - it maybe should have been "sudo upgrade-from-grub-legacy" instead of "sudo update-from grub-legacy". According to the 'gastly-iblogger', that worked fine.
     I saw others during the search who said the splash screen was ugly and they wanted to change it. You might want to try searching for grub2 on the internet if you agree.

Athani (chandan-athani) said : #6

Hi,

I did type 'sudo upgrade-from-grub-legacy' in the terminal. But I get the
following in the terminal window and I can't do anything after that except
to close the terminal window. The "OK" at the bottom of the window is not
click-able.

Package configuration

 ┌──────────────────────────┤ Configuring grub-pc
├──────────────────────────┐
 │

 │

 │ In order to replace the Legacy version of GRUB in your system, it is

 │ recommended that /boot/grub/menu.lst is adjusted to chainload GRUB 2

 │ from your existing GRUB Legacy setup. This step may be automaticaly

 │ performed now.

 │

 │ It's recommended that you accept chainloading GRUB 2 from menu.lst, and

 │ verify that your new GRUB 2 setup is functional for you, before you

 │ install it directly to your MBR (Master Boot Record).

 │

 │ In either case, whenever you want GRUB 2 to be loaded directly from MBR,

 │ you can do so by issuing (as root) the following command:

 │

 │ upgrade-from-grub-legacy

 │

 │
<Ok>
 │

 └──────────────────────────────────────────────────────────────────────────

2009/8/2 Larry Jordan <email address hidden>

> Your question #78852 on grub2 in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/grub2/+question/78852
>
> Status: Open => Answered
>
> Larry Jordan proposed the following answer:
> One of the reasons I love to check on this daily is that I learn so
> many new things....I wasn't aware there WAS a grub2. Having looked at this
> and checked for others with an internet search, I found a successful user of
> it at:
> http://gastly.iblogger.org/how-to-install-grub2-on-ubuntu-jaunty/ who
> gives instruction. It looks like the only thing different is that you
> didn't hyphenate all the words and used 'update' instead of 'upgrade' - it
> maybe should have been "sudo upgrade-from-grub-legacy" instead of "sudo
> update-from grub-legacy". According to the 'gastly-iblogger', that worked
> fine.
> I saw others during the search who said the splash screen was ugly and
> they wanted to change it. You might want to try searching for grub2 on the
> internet if you agree.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu/+source/grub2/+question/78852/+confirm?answer_id=4
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+source/grub2/+question/78852
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Best Larry Jordan (larryjor) said : #7

    Seems sad it isn't working as well as it should.
    I wonder if the <Ok> is 'selectable' by using the TAB key, in which case the Enter key would 'click' it. That's more of a Bash (shell) style, which doesn't use the mouse...

Athani (chandan-athani) said : #8

I performed a clean install of Karmic final release.

Thanks to everybody who helped.

Athani (chandan-athani) said : #9

Thanks Larry Jordan, that solved my question.