[SOLVED] chainloading with grub and grub2

houndhen · 12-20-2010, 08:42 AM

I multi-boot Windows XP and 5 Linux distros on a single hard drive. Some of the distros come and go but I keep at least two that are my daily use distros. My boot loader is grub1 located on a ext3 formatted distro. I have installed a distro that requests the partition be formatted ext4, which I did. I have been trying to edit my grub1 menu.lst so that I can chainload the ext4 distro get errors or it goes to the command line with the last word being Grub. My question is, can grub1 ext3 chainload a grub2 ext4 distro?

Here is a sample of my menu.lst

Code:

title MEPIS at sda7, newest kernel
root (hd0,6)
kernel /boot/vmlinuz root=/dev/sda7 nomce quiet splash vga=789 
initrd /boot/initrd.img
boot

title Microsoft Windows XP Home Edition at sda1
rootnoverify (hd0,0)
chainloader +1

# for Mint Debian on sda5
title Mint Debian on sda5
root (hd0,4)
chainloader +1

# for Crunchbang on sda6
title Crunchbang
root (hd0,5)
chainloader +1

# for SuperOS on sda8
title SuperOS 10.10
root (hd0,7)
chainloader +1

#for Aptosid 2010
title Aptosid 2010
set root=(hd0,8)
chainloader +1
boot

Mepis is the location of my menu.lst and is ext3 on sda7 and aptosid is the ext4 distro that I am trying to boot on sda9 and it uses grub2.

Larry Webb · 12-20-2010, 09:26 AM

You should be able to use the menu for grub legacy as long as the partition is bootable.

If you have a rescue mode for Aptosid reinstall bootloader to sda9 /.

If you can use as a live cd grub-install --force /dev/sda9

Change
#for Aptosid 2010
title Aptosid 2010
root (hd0,8)
chainloader +1
boot

PTrenholme · 12-20-2010, 10:35 AM

Try the rootnoverify directive so GRUB 1 won't try to read the ext4 file and barf.

houndhen · 12-20-2010, 01:39 PM

Thanks, I solved it some time after my post. The install was not where I thought it was. Everything is fine.