GRUB2 migration from GRUB Legacy

1 2012-07-13 Background

What's Grub?

Grub is one of the most commonly found boot loaders in use on non-embedde= d Linux machines. The role of Grub is to facilitate the Linux kernel being = loaded from your disk into memory and start executing the Linux kernel.

So Why Migrate?

Firstly, GRUB Legacy is no longer maintained and as such no longer receiv= es updates. GRUB Legacy was created at a time when the developers felt safe = in making several assumptions which no longer hold true today. For example, GRUB Legacy is unable to boot from disks larger than 2TB and assumes that newer filesystems wouldn't come to replace /boot.

GRUB2 aims to be more robust, more portable, more powerful and is maintai= ned with a cleaner code base. GRUB2 supports more hardware configurations, mo= re filesystems and more drive layouts than its predecessor.

Migration to GRUB2

Migration to GRUB2 is fairly straightforward: it will be pulled in as par= t of your regular upgrade process by your package manager. If it is not pul= led in automatically, you can always install sys-boot/grub:2.

Boot Drive

The first important part is to understand what your bootable drive is. Fo= r many people it will be /dev/sda. The easiest way to find thi= s is to look at how your existing GRUB Legacy is setup by viewing /boot/grub/grub.conf. An example one is provided below.

You must have your /boot mounted to be able to view these fi= les. It should be as simple as mount /boot to mount /boot.

default 0
timeout 30
splashimage=3D(hd0,0)/boot/grub/splash.xpm.gz

title Gentoo Linux 3.2.12
root (hd0,0)
kernel /boot/kernel-3.2.12-gentoo root=3D/dev/sda3 quiet dolvm
initrd /boot/initramfs-genkernel-x86_64-3.2.12-gentoo

Based on the above file we know that (hd0) is the boot drive but w= e must map this to a real device. To know this you must view /boot/grub/device.map. An example one is provided below.

(fd0) /dev/fd0
(hd0) /dev/sda
(hd1) /dev/sdb

Based on the above file we know that /dev/sda is the boot dr= ive.

=09

Installing and Configuring GRUB2

The next step is to install and configure GRUB2 on your /boot partition without removing GRUB Legacy from your MBR. The example below uses /dev/sda but you must replace it with your boot drive p= ath. The first step installs the necessary GRUB2 files to /boot/grub2, while the second step scans your available kernels and generates a suitab= le config file to /boot/grub2/grub.cfg.

# grub2-install --grub-setup=3D/bin/true /dev/sda
Installation finished. No error reported.
# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/kernel-3.2.12-gentoo
Found initrd image: /boot/initramfs-genkernel-x86_64-3.2.12-gentoo
done

GRUB2 has strict naming requirements for kernels and initramfs images. A kernel must be named kernel-${version} while an initramfs must be named initramfs-${version}, initramfs-genkernel-${version}, initramfs-genkernel-${arch}-${version}, initrd-${version}.img, initrd.img-${version}, initrd-${version}.gz, or initrd-${version}. Together with ${version}, the filename must match a corresponding kernel that is available in /boot.

Chainloading GRUB2 from GRUB Legacy to test the setup

Because a broken GRUB configuration could mean an unbootable system, we want to test our GRUB2 configuration before making it permenan= t. To do this we will chainload GRUB2 from GRUB Legacy. This is done by addi= ng a new section into /boot/grub/grub.conf. An example is shown below.

Beaware that your root maybe different from (hd0,0) used in the example and make sure you reuse the same root value from your /boot/grub/grub.conf.

default 0
timeout 30
splashimage=3D(hd0,0)/boot/grub/splash.xpm.gz

title GRUB2 Chainload
root (hd0,0)
kernel /boot/grub2/i386-pc/core.img
boot

title Gentoo Linux 3.2.12
root (hd0,0)
kernel /boot/kernel-3.2.12-gentoo root=3D/dev/sda3 quiet dolvm
initrd /boot/initramfs-genkernel-x86_64-3.2.12-gentoo

At this point you should reboot your machine and select the GRUB2 Chainload from the GRUB menu when your machine begins to boo= t. You will be presented with another GRUB menu which should advertise itsel= f as GRUB 2.0.0 or higher at the top and show your available kernel(s) to b= oot. Should this not work, simply reboot your system and pick your normal boot option instead of GRUB2 Chainload.

Replacing and removing GRUB Legacy

At this point if everything worked successfully you can replace GRUB Lega= cy and remove it from your system.

Since you've rebooted your system, you may need to mount /boot again. You should also take note to use your boot drive path instead of /dev/sda.

# grub2-install /dev/sda
Installation finished. No error reported.
# rm -rf /boot/grub/

At this point you can use your package manager to remove sys-boot/grub= :0. The migration is complete.

Maintaining GRUB2

Whenever you install a new kernel, you must perform the next step so that your GRUB2 configuration recognizes the new kernel.

You must have your /boot partition mounted for this step.

# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/kernel-3.3.8-gentoo
Found initrd image: /boot/initramfs-genkernel-x86_64-3.3.8-gentoo
Found linux image: /boot/kernel-3.2.12-gentoo
Found initrd image: /boot/initramfs-genkernel-x86_64-3.2.12-gentoo
done

FAQ / Known Problems / Gotchas

Content to come.