I Need Help Dual Booting Fedora 7 + Ubuntu Feisty

[yusuo]

I've been using Ubuntu for bout 3 months now and wanted to try something different so I choose Fedora 7, Still havnt got the hang of rpm based gets a bit confusing going from Deb based but then again i'm a noob so never mind.
Anyway when i installed Ubuntu it deleted the grub booter and now I only have Fedora to choose from. I tried to edit it to add ubuntu and it did but everytime it tries to boot in it crashes on the boot up bar right at the beginning. I was wondering if anyone could help, heres a copy of both the /boot/grub/menu.lst i changed

Fedora:
-----------------------------------------------------------------
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,2)
# kernel /boot/vmlinuz-version ro root=/dev/sda3
# initrd /boot/initrd-version.img
#boot=/dev/sda
default=0
timeout=10
splashimage=(hd0,2)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.21-1.3194.fc7)
root (hd0,2)
kernel /boot/vmlinuz-2.6.21-1.3194.fc7 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.21-1.3194.fc7.img

title Ubuntu, kernel 2.6.20-16-generic
root (hd0,1)
kernel /boot/vmlinuz-2.6.20-16-generic root=LABEL=/
initrd /boot/initrd.img-1.6.20-16-generic
quiet
"menu.lst" 47L, 1563C 22,34 Top
-----------------------------------------------------------------
Ubuntu:
-----------------------------------------------------------------
title Ubuntu, kernel 2.6.20-16-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=a3a4bf10-4283-406a-8929-b209abe026b1 ro quiet splash
initrd /boot/initrd.img-2.6.20-16-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-16-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=a3a4bf10-4283-406a-8929-b209abe026b1 ro single
initrd /boot/initrd.img-2.6.20-16-generic

title Ubuntu, kernel 2.6.20-15-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=a3a4bf10-4283-406a-8929-b209abe026b1 ro quiet splash
initrd /boot/initrd.img-2.6.20-15-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=a3a4bf10-4283-406a-8929-b209abe026b1 ro single
initrd /boot/initrd.img-2.6.20-15-generic

title Ubuntu, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
quiet


title Fedora (2.6.21-1.3194.fc7)
root (hd0,2)
kernel /boot/vmlinuz-2.6.21-1.3194.fc7 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.21-1.3194.fc7.img

### END DEBIAN AUTOMAGIC KERNELS LIST
-----------------------------------------------------------------
There is a mistake somewhere in here that wont let it load. But I really dont know.

Heres my partition list
-----------------------------------------------------------------
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 9032 72549508+ 83 Linux
/dev/sda2 9543 9729 1502077+ 5 Extended
/dev/sda3 9033 9542 4096575 83 Linux
/dev/sda5 9543 9729 1502046 82 Linux swap / Solaris
-----------------------------------------------------------------

sda1 is the original ubuntu install
sda3 is my fedora one.

Please help me I dont wanna reinstall ubuntu just to get it back again

[MikeTbob]

It looks like you need to change this, shown in bold.

# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,2)
# kernel /boot/vmlinuz-version ro root=/dev/sda3
# initrd /boot/initrd-version.img
#boot=/dev/sda
default=0
timeout=10
splashimage=(hd0,2)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.21-1.3194.fc7)
root (hd0,2)
kernel /boot/vmlinuz-2.6.21-1.3194.fc7 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.21-1.3194.fc7.img

title Ubuntu, kernel 2.6.20-16-generic
root (hd0,1)
kernel /boot/vmlinuz-2.6.20-16-generic root=LABEL=/
initrd /boot/initrd.img-1.6.20-16-generic
quiet

To this

root (hd0,0)

[oz]

Welcome to the forums, yusuo!

Please don't post the same topic in multiple forums because it's against the forum rules:

http://www.linuxforums.org/forum/lin...ums-rules.html

Note that your duplicate threads have been deleted.

Regards,

oz

[devils casper]

Ubuntu doesn't use Partition Labels and its crashing only coz of that.
Fedora's grub.conf file should look like this

default=0
timeout=10
splashimage=(hd0,2)/boot/grub/splash.xpm.gz
#hiddenmenu
title Fedora (2.6.21-1.3194.fc7)
root (hd0,2)
kernel /boot/vmlinuz-2.6.21-1.3194.fc7 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.21-1.3194.fc7.img

title Ubuntu, kernel 2.6.20-16-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-16-generic root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.20-16-generic
quiet
savedefault
quiet

i deleted UUID from Ubuntu root coz sometimes it creates problems after Partition resize.
dont forget to put # sign before hiddenmenu line.

[engelbertus]

i tried some stuff with ubuntu and grub aswell, but havent figured out what goes wrong.

i did discover that if you use grub-install to install grub, it repleces (hdo,1) or /dev/hda etc to uuid's

i think that is logical, but i do not understand what a uuid is.. is it something that is being calculated from partition info? is is like a serialnumber written to the partition info?

i do think uuid could be handy if partition order changes , or even diskorder when you plug in usb disks ?

so that is why i would like to know what a uuid is, and when it is "set" and why it would change after partitionresize, is the resize program doing that? and why ?
how is uuid determined?

further i dont think using disklabels would cause problems, it just is when users change them that they could cause problems.

that is why i would say using uuids as a unique discription for a partition would be a very good solution, though the "cryptical" numbers dont realy mean anythng to users or admins.

[devils casper]

so that is why i would like to know what a uuid is, and when it is "set" and why it would change after partitionresize, is the resize program doing that? and why ?
how is uuid determined?

UUIDs are generated by vol_id. Whenever you change partition structure, UUIDs are also changed. Check manual of vol_id.