PDA

View Full Version : [ubuntu] Dual boot Ubuntu 9.10 and 9.04



crazyness003
November 28th, 2009, 10:34 PM
Good day to you all.
I recently installed Ubuntu 9.10 on another partition, separate from my 9.04 installation.
Unfortunately, my 9.04 installation had /boot on a separate partition, and when i installed 9.10, I overwrote that /boot partition with the new one (which now runs GRUB2). I did however make a backup of everything that was in the old /boot partition.

The problem lies here: when GRUB2 'detected' my installations, it identified the kernel from 9.04, but it boots that kernel with the installation of 9.10. I would rather it boot the 9.04 install so I can transfer some docs, setting, emails, etc.

I tried just copying the messed up entry in GRUB2 and changing the UUID to point to the correct partition 9.04 is on, but it says "you must run the kernel first" (or something to that extent)

Since I still have my old /boot backup, should I just copy it into the 9.04 partition's /boot folder and try to chainload it. Would that work?

Or is there another way of doing this, where I can just boot straight into 9.04.

Here's my fdisk with appended UUID's and Lables


xxx@xxx:~$ sudo fdisk -l | grep sdc
Disk /dev/sdc: 160.0 GB, 160000000000 bytes
/dev/sdc1 * 1 65 522081 83 Linux "Boot" 4094425e-60ca-4c54-9c26-27ff10307c3e
/dev/sdc2 66 5222 41423602+ 7 HPFS/NTFS 4094425e-60ca-4c54-9c26-27ff10307c3e
/dev/sdc3 5223 7833 20972857+ 83 Linux "Ubuntu" f39cba46-8609-4fc0-a969-c81ee1d2be18
/dev/sdc4 7834 19452 93329617+ 5 Extended
/dev/sdc5 7834 10444 20972826 83 Linux "Aux" 4ade736c-5557-434f-8046-170b306eb7cc
/dev/sdc6 10445 10705 2096451 82 Linux swap / Solaris d171f6a3-21bb-41e6-a919-221edcea5c71
/dev/sdc7 10706 18799 65015023+ 83 Linux "Data" baec14e1-2b15-40be-a789-0fe1f4a7727a
/dev/sdc8 18800 19452 5245191 83 Linux "Install" 855f1148-9c73-49e6-9184-55a6518a1ea6
xxx@xxx:~$
sdc is my installation disk, I don't know why this order was chosen.



sdc1 is /boot
sdc3 is / for Ubuntu 9.10
sdc5 is / for Ubuntu 9.04
sdc7 is my data drive (housing /home for my 9.10 installation)
and here's the contents of grub.cfg from GRUB2


#
# 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=(hd2,3)
search --no-floppy --fs-uuid --set f39cba46-8609-4fc0-a969-c81ee1d2be18
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=1024x768
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-15-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd2,1)
search --no-floppy --fs-uuid --set 4094425e-60ca-4c54-9c26-27ff10307c3e
linux /vmlinuz-2.6.31-15-generic root=UUID=f39cba46-8609-4fc0-a969-c81ee1d2be18 ro vga=792 splash quiet splash
initrd /initrd.img-2.6.31-15-generic
}
menuentry "Ubuntu, Linux 2.6.31-15-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd2,1)
search --no-floppy --fs-uuid --set 4094425e-60ca-4c54-9c26-27ff10307c3e
linux /vmlinuz-2.6.31-15-generic root=UUID=f39cba46-8609-4fc0-a969-c81ee1d2be18 ro single vga=792 splash
initrd /initrd.img-2.6.31-15-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=(hd2,1)
search --no-floppy --fs-uuid --set 4094425e-60ca-4c54-9c26-27ff10307c3e
linux /vmlinuz-2.6.31-14-generic root=UUID=f39cba46-8609-4fc0-a969-c81ee1d2be18 ro vga=792 splash quiet splash
initrd /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=(hd2,1)
search --no-floppy --fs-uuid --set 4094425e-60ca-4c54-9c26-27ff10307c3e
linux /vmlinuz-2.6.31-14-generic root=UUID=f39cba46-8609-4fc0-a969-c81ee1d2be18 ro single vga=792 splash
initrd /initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.28-16-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd2,1)
search --no-floppy --fs-uuid --set 4094425e-60ca-4c54-9c26-27ff10307c3e
linux /vmlinuz-2.6.28-16-generic root=UUID=f39cba46-8609-4fc0-a969-c81ee1d2be18 ro vga=792 splash quiet splash
initrd /initrd.img-2.6.28-16-generic
}
menuentry "Ubuntu, Linux 2.6.28-16-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd2,1)
search --no-floppy --fs-uuid --set 4094425e-60ca-4c54-9c26-27ff10307c3e
linux /vmlinuz-2.6.28-16-generic root=UUID=f39cba46-8609-4fc0-a969-c81ee1d2be18 ro single vga=792 splash
initrd /initrd.img-2.6.28-16-generic
}
### END /etc/grub.d/10_linux ###

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

### BEGIN /etc/grub.d/22_invaders ###
menuentry "GRUB Invaders" {
insmod ext2
set root=(hd2,1)
search --no-floppy --fs-uuid --set 4094425e-60ca-4c54-9c26-27ff10307c3e
multiboot /invaders
}
### END /etc/grub.d/22_invaders ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows XP Ultimate (on /dev/sdc2)" {
insmod ntfs
set root=(hd2,2)
search --no-floppy --fs-uuid --set c240372240371d1b
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.
menuentry "Ubuntu 9.04" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd2,1)
search --no-floppy --fs-uuid --set 4ade736c-5557-434f-8046-170b306eb7cc
linux /vmlinuz-2.6.28-16-generic root=UUID=4ade736c-5557-434f-8046-170b306eb7cc ro vga=792 splash quiet splash
initrd /initrd.img-2.6.28-16-generic
}
menuentry "Ubuntu 9.04 (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd2,1)
search --no-floppy --fs-uuid --set 4ade736c-5557-434f-8046-170b306eb7cc
linux /vmlinuz-2.6.28-16-generic root=UUID=4ade736c-5557-434f-8046-170b306eb7cc ro single vga=792 splash
initrd /initrd.img-2.6.28-16-generic
}
### END /etc/grub.d/40_custom ###
Here's my old grub-legacy menu.lst from the now-gone /boot partition


title Ubuntu 9.04, on /dev/sdc3
uuid 1dc48dda-4cc1-433e-b6b3-804df11d92d8
kernel /vmlinuz-2.6.28-16-generic root=UUID=60ccf990-cdc9-400b-9725-29f0da002f80 ro splash vga=792
initrd /initrd.img-2.6.28-16-generic
quiet

title --- 2.6.28-16-generic (recovery mode)
uuid 1dc48dda-4cc1-433e-b6b3-804df11d92d8
kernel /vmlinuz-2.6.28-16-generic root=UUID=60ccf990-cdc9-400b-9725-29f0da002f80 ro single
initrd /initrd.img-2.6.28-16-generic

title Ubuntu 9.04, on /dev/sdc5
uuid 1dc48dda-4cc1-433e-b6b3-804df11d92d8
kernel /vmlinuz-2.6.28-16-generic root=UUID=4ade736c-5557-434f-8046-170b306eb7cc ro splash vga=792
initrd /initrd.img-2.6.28-16-generic
quiet

title --- 2.6.28-16-generic (recovery mode)
uuid 1dc48dda-4cc1-433e-b6b3-804df11d92d8
kernel /vmlinuz-2.6.28-16-generic root=UUID=4ade736c-5557-434f-8046-170b306eb7cc ro single
initrd /initrd.img-2.6.28-16-generic

title Ubuntu 9.04 on /dev/sdc5
uuid 1dc48dda-4cc1-433e-b6b3-804df11d92d8
kernel /vmlinuz-2.6.28-15-generic root=UUID=4ade736c-5557-434f-8046-170b306eb7cc ro splash vga=792
initrd /initrd.img-2.6.28-15-generic
quiet

title --- 2.6.28-15-generic (recovery mode)
uuid 1dc48dda-4cc1-433e-b6b3-804df11d92d8
kernel /vmlinuz-2.6.28-15-generic root=UUID=4ade736c-5557-434f-8046-170b306eb7cc ro single
initrd /initrd.img-2.6.28-15-generic


title Ubuntu 9.04, memtest86+
uuid 1dc48dda-4cc1-433e-b6b3-804df11d92d8
kernel /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/sdc2
title Windows XP Ultimate
rootnoverify (hd2,1)
savedefault
##map (hd0) (hd2)
##map (hd2) (hd0)
chainloader +1
I hope this helps with info aggregation. Let me know if it is even possible to boot into my old 9.04 install.

And as always, thanks for taking the time to look into this.

darkod
November 28th, 2009, 10:44 PM
First step is to see if:
sudo update-grub

will help. But it doesn't seem so. The confusion seems to be that you overwrote your /boot for 9.04. Where is it supposed to find the kernel files now? They were in /boot. Also your new /boot now has different UUID because it was reformatted I guess.

Are you sure it's loading the 9.04 kernel? Where is that kernel now, in sdc5?

crazyness003
November 28th, 2009, 10:49 PM
Thanks for the quick response.

somehow update-grub (or grub-mkconfig) copied the old kernel images onto the new /root and points them to the UUID for the 9.10 partition.
What I tried doing is copying those entries and pointing them to the UUID for the 9.04 partition. I'm still experimenting, and trying to find out if I can get this done myself, but help is always welcome.

I'll report back in any case

darkod
November 28th, 2009, 10:52 PM
One fix you could try is copy the not working entry for 2.6.28 from grub.cfg into /etc/grub.d/40_custom where you can make custom entries. It should allow you to change the UUID to point to sdc5 like you need. Running update-grub will add that custom entry in grub.cfg

If that works at least you could boot 9.04 and you can deal with the wrong automatic entries later.

crazyness003
November 28th, 2009, 11:14 PM
I figured it out. Stupid mistake on my part.

After repeated attempts resulting in failure, I decided to try anything. I copied my backup of old /boot into the /boot folder of my 9.04 install, then tried to fiddle with grub-mkconfig. The script detected the contents of the /boot folder of the 9.04 partition and auto-loaded the in.

Now i can successfully boot into both partitions.

The only thing was that it gave me an error during boot, something about a UUID, but it let me ignore and continue with boot as normal. I'll look into it in more detail.

Bottom line, if you preserved your old /boot folder and put it back in /boot (of your old partition install); grub-mkconfig (since update-grub was depreciated) will automagically load up that in the grub2 menu.
It identifies it by root=/dev/sd~~, but not by UUID.

Thnaks for the help darkod.

darkod
November 28th, 2009, 11:16 PM
Doesn't sound like I helped much, but you're welcomed. :)

bluesscream
November 28th, 2009, 11:44 PM
I would rather it boot the 9.04 install so I can transfer some docs, setting, emails, etc.
From your new karmic you will have access by mounting the partition contenting your old user directory as well as jaunty's filesystem - or did you store your emails, settings and docs in the overwritten boot partition?:p
I see you figured it out and demostrated another time the importance of making backups before such actions;)