Fedora Linux Support Community & Resources Center
  #1  
Old 13th December 2008, 11:59 PM
ysNoi's Avatar
ysNoi Offline
Registered User
 
Join Date: Oct 2008
Location: Laguna, Philippines
Posts: 23
Edit my grub to boot Fedora 9 : Need Help

Hello...!

I've already tested my Fedora 9 to run on my reg but uninstalled it a month ago...!

I already installed successfully my Fedora 9 on my hd3, 0 (correct me if I'm wrong) but I forgot how to edit the grub of my Ubuntu to add the option where I could choose to boot Fedora.

Can anyone help me edit my grub? I'm using the Ubuntu grub..!

For reference, here is my /sbin/fdisk -l report :

ysnoi@ysNoi:~$ sudo /sbin/fdisk -l
[sudo] password for ysnoi:

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8bb28bb2

Device Boot Start End Blocks Id System
/dev/sda1 * 1 6438 51713203+ 7 HPFS/NTFS
/dev/sda2 6439 6836 3196935 82 Linux swap / Solaris
/dev/sda3 6837 13558 53994465 83 Linux
/dev/sda4 13559 19457 47383717+ 83 Linux

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xf6a8f6a8

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 6581 52861851 83 Linux
/dev/sdb2 6582 19457 103426470 f W95 Ext'd (LBA)
/dev/sdb5 6582 19457 103426438+ 7 HPFS/NTFS

Disk /dev/sdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x22462246

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 6842 54958333+ 83 Linux
/dev/sdc3 6843 14669 62870377+ 7 HPFS/NTFS
/dev/sdc4 14670 30401 126367290 f W95 Ext'd (LBA)
/dev/sdc5 14670 30401 126367258+ 7 HPFS/NTFS
ysnoi@ysNoi:~$

Thanks in advanced...!
__________________
"Don't fix it if it ain't broken, don't break it if you can't fix it."
Reply With Quote
  #2  
Old 14th December 2008, 12:40 AM
stoat Offline
Registered User
 
Join Date: Jun 2006
Posts: 7,551
Quote:
Originally Posted by ysNoi

I already installed successfully my Fedora 9 on my hd3, 0 (correct me if I'm wrong) but I forgot how to edit the grub of my Ubuntu to add the option where I could choose to boot Fedora.
Hello ysNoi,

Well, your fdisk is showing only three drives. So if that is all there are, then Fedora could not be on (hd3,0). Remember that GRUB device notation uses numbers that start counting with zero. So the drives listed in your posted fdisk report would be (hd0), (hd1), and (hd2). See what I mean?

If you chose to install Fedora's GRUB boot loader in the first sector of the Fedora boot partition, then you can use the chainloader command like you did the last time you did this. Example...
Code:
title Fedora 9
chainloader (hdx,y)+1
You change x & y to the drive & partition of the Fedora boot partition or whatever partition has the kernels and GRUB files.

If the Ubuntu version of the grub package is version 0.97-21 or later, and its GRUB boot loader was installed or re-installed with that version, then you can also try using the configfile command. Example...
Code:
title Fedora 9
configfile (hdx,y)/boot/grub/grub.conf
Finally, you can directly boot the Fedora 9 kernel and initial ramdisk by simply copying the title, root, kernel, and initrd command lines from the Fedora grub.conf to the Ubuntu menu.lst file. The GRUB version thing applies for this method, too (important and cannot be ignored for this to work). This method is nice if you don't want to go through a second menu or countdown and boot the system directly from Ubuntu's GRUB menu. It's disadvantage is that it has to be repeated after each Fedora kernel update (fairly often).

Last edited by stoat; 14th December 2008 at 12:57 AM.
Reply With Quote
  #3  
Old 14th December 2008, 01:06 AM
ysNoi's Avatar
ysNoi Offline
Registered User
 
Join Date: Oct 2008
Location: Laguna, Philippines
Posts: 23
Quote:
Originally Posted by stoat View Post
Hello ysNoi,

Well, your fdisk is showing only three drives. So if that is all there are, then Fedora could not be on (hd3,0). Remember that GRUB device notation uses numbers that start counting with zero. So the drives listed in your posted fdisk report would be (hd0), (hd1), and (hd2). See what I mean?
Oh I see, so I got it installed from hd2. Actually you already told me about this before but I just forgot. I tried to find my previous post here before but I can't find. Thanks for refreshing my mind.

Quote:
Originally Posted by stoat View Post
If you chose to install Fedora's GRUB boot loader in the first sector of the Fedora boot partition, then you can use the chainloader command like you did the last time you did this. Example...
Code:
title Fedora 9
chainloader (hdx,y)+1
You change x & y to the drive & partition of the Fedora boot partition or whatever partition has the kernels and GRUB files.
Yes I chose installing Fedora's Grub boot loader in the first sector of the Fedora boot partition..!

Trying now.! Many thanks again..!
__________________
"Don't fix it if it ain't broken, don't break it if you can't fix it."
Reply With Quote
  #4  
Old 14th December 2008, 01:48 AM
ysNoi's Avatar
ysNoi Offline
Registered User
 
Join Date: Oct 2008
Location: Laguna, Philippines
Posts: 23
siR, I already tested but I freezes on "Starting Up"...

Is there any problem in my installation?

Here is what I did :

# 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=a5f3bace-f758-4152-bed2-3c41ead77a28 ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)

## 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 Ubuntu 8.04.1, kernel 2.6.24-22-generic
root (hd0,3)
kernel /boot/vmlinuz-2.6.24-22-generic root=UUID=a5f3bace-f758-4152-bed2-3c41ead77a28 ro quiet splash
initrd /boot/initrd.img-2.6.24-22-generic
quiet

title Ubuntu 8.04.1, kernel 2.6.24-22-generic (recovery mode)
root (hd0,3)
kernel /boot/vmlinuz-2.6.24-22-generic root=UUID=a5f3bace-f758-4152-bed2-3c41ead77a28 ro single
initrd /boot/initrd.img-2.6.24-22-generic


### 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 an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, kernel 2.6.27-9-server
root (hd0,2)
kernel /boot/vmlinuz-2.6.27-9-server root=UUID=e30dda43-d75d-498e-bfc5-5c59a2787b5f ro quiet splash
initrd /boot/initrd.img-2.6.27-9-server
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, kernel 2.6.27-9-server (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.27-9-server root=UUID=e30dda43-d75d-498e-bfc5-5c59a2787b5f ro single
initrd /boot/initrd.img-2.6.27-9-server
savedefault
boot


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


title Fedora 9
chainloader (hd2,1)+1
__________________
"Don't fix it if it ain't broken, don't break it if you can't fix it."
Reply With Quote
  #5  
Old 14th December 2008, 02:14 AM
stoat Offline
Registered User
 
Join Date: Jun 2006
Posts: 7,551
Quote:
Originally Posted by ysNoi

title Fedora 9
chainloader (hd2,1)+1
Okay. That would try to execute the boot sector code of the second partition on the third hard drive. But according to your fdisk report...

Quote:
Originally Posted by ysNoi

Disk /dev/sdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x22462246

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 6842 54958333+ 83 Linux
/dev/sdc3 6843 14669 62870377+ 7 HPFS/NTFS
/dev/sdc4 14670 30401 126367290 f W95 Ext'd (LBA)
/dev/sdc5 14670 30401 126367258+ 7 HPFS/NTFS
...the only possible candidate for being Fedora on the third drive is /dev/sdc1 which GRUB should identify as (hd2,0) not (hd2,1). In fact, technically, there isn't an (hd2,1) on the third drive.

Try it again with (hd2,0) in the Fedora section of the Ubunut menu.lst.

P.S.: Hey, I didn't invent this GRUB and OS naming and numbering scheme.
Reply With Quote
  #6  
Old 16th December 2008, 01:26 AM
ysNoi's Avatar
ysNoi Offline
Registered User
 
Join Date: Oct 2008
Location: Laguna, Philippines
Posts: 23
siR, I still can't work to boot my Fedora 9...!

Anyways, I have a fresh partition and a fresh install of Fedora 9 (the previous was deleted).

I quiet understand that I have installed my new Fedora 9 on the 1st Partition of the second hard disk and I think I installed it completely. So far, I already edited my ubuntu menu.lst like this :
Code:
title Fedora
chainloader (hd1,0)+1
added at the bottom as I know I have it on the 1st partition of the second hard disk.

Please take a look on my new /sbin/fdisk -l report below :

ysnoi@ysNoi:~$ sudo /sbin/fdisk -l
[sudo] password for ysnoi:

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8bb28bb2

Device Boot Start End Blocks Id System
/dev/sda1 * 1 6438 51713203+ 7 HPFS/NTFS
/dev/sda2 6439 6836 3196935 82 Linux swap / Solaris
/dev/sda3 6837 13558 53994465 83 Linux
/dev/sda4 13559 19457 47383717+ 83 Linux

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xf6a8f6a8

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 3904 31358848+ 83 Linux
/dev/sdb2 3905 10482 52837785 7 HPFS/NTFS
/dev/sdb3 10483 19457 72091687+ f W95 Ext'd (LBA)
/dev/sdb5 10483 19457 72091656 7 HPFS/NTFS

Disk /dev/sdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x22462246

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 6842 54958333+ 7 HPFS/NTFS
/dev/sdc2 6843 14669 62870377+ 7 HPFS/NTFS
/dev/sdc3 14670 30401 126367290 f W95 Ext'd (LBA)
/dev/sdc5 14670 30401 126367258+ 7 HPFS/NTFS
ysnoi@ysNoi:~$

Also, I included the menu.lst of my Ubuntu for further info :

# 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=a5f3bace-f758-4152-bed2-3c41ead77a28 ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)

## 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 Ubuntu 8.04.1, kernel 2.6.24-22-generic
root (hd0,3)
kernel /boot/vmlinuz-2.6.24-22-generic root=UUID=a5f3bace-f758-4152-bed2-3c41ead77a28 ro quiet splash
initrd /boot/initrd.img-2.6.24-22-generic
quiet

title Ubuntu 8.04.1, kernel 2.6.24-22-generic (recovery mode)
root (hd0,3)
kernel /boot/vmlinuz-2.6.24-22-generic root=UUID=a5f3bace-f758-4152-bed2-3c41ead77a28 ro single
initrd /boot/initrd.img-2.6.24-22-generic

title Ubuntu 8.04.1, kernel 2.6.24-19-generic
root (hd0,3)
kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=a5f3bace-f758-4152-bed2-3c41ead77a28 ro quiet splash
initrd /boot/initrd.img-2.6.24-19-generic
quiet

title Ubuntu 8.04.1, kernel 2.6.24-19-generic (recovery mode)
root (hd0,3)
kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=a5f3bace-f758-4152-bed2-3c41ead77a28 ro single
initrd /boot/initrd.img-2.6.24-19-generic

title Ubuntu 8.04.1, memtest86+
root (hd0,3)
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 Professional
root (hd0,0)
savedefault
makeactive
chainloader +1


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, kernel 2.6.27-9-server (on /dev/sda3)
root (hd0,2)
kernel /boot/vmlinuz-2.6.27-9-server root=UUID=e30dda43-d75d-498e-bfc5-5c59a2787b5f ro quiet splash
initrd /boot/initrd.img-2.6.27-9-server
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, kernel 2.6.27-9-server (recovery mode) (on /dev/sda3)
root (hd0,2)
kernel /boot/vmlinuz-2.6.27-9-server root=UUID=e30dda43-d75d-498e-bfc5-5c59a2787b5f ro single
initrd /boot/initrd.img-2.6.27-9-server
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, kernel 2.6.27-7-server (on /dev/sda3)
root (hd0,2)
kernel /boot/vmlinuz-2.6.27-7-server root=UUID=e30dda43-d75d-498e-bfc5-5c59a2787b5f ro quiet splash
initrd /boot/initrd.img-2.6.27-7-server
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, kernel 2.6.27-7-server (recovery mode) (on /dev/sda3)
root (hd0,2)
kernel /boot/vmlinuz-2.6.27-7-server root=UUID=e30dda43-d75d-498e-bfc5-5c59a2787b5f ro single
initrd /boot/initrd.img-2.6.27-7-server
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, memtest86+ (on /dev/sda3)
root (hd0,2)
kernel /boot/memtest86+.bin
savedefault
boot


title Fedora
chainloader (hd1,0)+1

When I choose to boot Fedora on the grub (upon restart), the OS that works is Windows XP though I know it was installed on the 1st partition of the 1st hard disk (hd0,0) while I already input the chainloader (hd1,0) on the title Fedora. Is there anything weird on my set-up? What should I do? Please help me. Please...!

I got No problem booting my three OS on the 1st Hard Disk. The only problem is I could not boot my Fedora 9 OS. I really want it running to learn also this OS.

Hope I could still be helped...! Thanks so much in advanced.
__________________
"Don't fix it if it ain't broken, don't break it if you can't fix it."
Reply With Quote
  #7  
Old 16th December 2008, 06:21 PM
stoat Offline
Registered User
 
Join Date: Jun 2006
Posts: 7,551
Well, sometimes GRUB and the OS don't name drives the way we expect. Try rebooting and when you see the Ubuntu GRUB menu, press "c" to get the grub> prompt. Then enter these commands at the grub> prompt...
Code:
find /grub/stage1
find /boot/grub/stage1
Do both commands. Ignore error messages. One or both will produce results. Those are all of your Linux boot partitions (or partitions with kernels and GRUB files). You already know the Ubuntu boot partitions. The one left over will be Fedora's. If you installed GRUB in the first sector of the Fedora boot partition, then use what you just learned to correct the Ubuntu menu.lst file and boot Fedora.
Reply With Quote
  #8  
Old 17th December 2008, 02:16 PM
ysNoi's Avatar
ysNoi Offline
Registered User
 
Join Date: Oct 2008
Location: Laguna, Philippines
Posts: 23
On
Code:
find /grub/stage1
, the result is file not found.

On
Code:
find /boot/grub/stage1
, the result is (hd0,2), (hd0,3) and (hd2,0).

I tried to input next to grub> prompt the ff:

grub> chainloader (hd2,0)+1
grub> boot

but it keeps coming back on the grub prompt.
__________________
"Don't fix it if it ain't broken, don't break it if you can't fix it."
Reply With Quote
  #9  
Old 17th December 2008, 02:51 PM
stoat Offline
Registered User
 
Join Date: Jun 2006
Posts: 7,551
Well, some ideas that come to mind after reading that...
  1. If it's immediately returning to the Ubuntu grub> prompt with an error message, then maybe GRUB was never really installed in the first sector of (hd2,0) when Fedora was installed. For this, I would try re-installing Fedora's GRUB boot loader in the first sector of the Fedora boot partition (hd2,0). Use the Fedora DVD and linux rescue or a Super Grub Disk.

  2. If Fedora is starting to boot (kernel and initial ramdisk load), but soon stops at a new grub> prompt before presenting the Fedora GRUB menu, then maybe the Fedora GRUB boot loader is busted or the grub.conf is misconfigured. For this, I would examine the Fedora grub.conf file for a gross misconfiguration and/or re-install the GRUB boot loader in the first sector of the Fedora boot partition.

Last edited by stoat; 17th December 2008 at 03:27 PM.
Reply With Quote
  #10  
Old 23rd December 2008, 02:50 PM
ysNoi's Avatar
ysNoi Offline
Registered User
 
Join Date: Oct 2008
Location: Laguna, Philippines
Posts: 23
Hi siR stoat...!

Sorry for the late reply, I was just a bit busy in the company...!

Anyway, I already did what you suggested re-installing Fedora's GRUB boot loader in the first sector of the Fedora boot partition (hd2,0) but I got no luck until I came to decide repartitioning the same HD and re-installing the fedora OS. After the new installation, I got the same problem where WindowsXP boots instead of Fedora.

FYI, here is my Fdisk report:

ysnoi@ysNoi:~$ sudo /sbin/fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8bb28bb2

Device Boot Start End Blocks Id System
/dev/sda1 * 1 6438 51713203+ 7 HPFS/NTFS
/dev/sda2 6439 6836 3196935 82 Linux swap / Solaris
/dev/sda3 6837 13558 53994465 83 Linux
/dev/sda4 13559 19457 47383717+ 83 Linux

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xf6a8f6a8

Device Boot Start End Blocks Id System
/dev/sdb1 1 5306 42620413+ 7 HPFS/NTFS
/dev/sdb2 5307 12114 54685260 f W95 Ext'd (LBA)
/dev/sdb3 12115 19457 58982647+ 7 HPFS/NTFS
/dev/sdb5 * 5307 12114 54685228+ 83 Linux

Disk /dev/sdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x22462246

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 6842 54958333+ 7 HPFS/NTFS
/dev/sdc2 6843 14669 62870377+ 7 HPFS/NTFS
/dev/sdc3 14670 30401 126367290 f W95 Ext'd (LBA)
/dev/sdc5 14670 30401 126367258+ 7 HPFS/NTFS

I installed the Fedora on the same HD but on the other partition.

For my menu.lst report ;

# 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=a5f3bace-f758-4152-bed2-3c41ead77a28 ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)

## 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 Ubuntu 8.04.1, kernel 2.6.24-22-generic
root (hd0,3)
kernel /boot/vmlinuz-2.6.24-22-generic root=UUID=a5f3bace-f758-4152-bed2-3c41ead77a28 ro quiet splash
initrd /boot/initrd.img-2.6.24-22-generic
quiet

title Ubuntu 8.04.1, kernel 2.6.24-22-generic (recovery mode)
root (hd0,3)
kernel /boot/vmlinuz-2.6.24-22-generic root=UUID=a5f3bace-f758-4152-bed2-3c41ead77a28 ro single
initrd /boot/initrd.img-2.6.24-22-generic

title Ubuntu 8.04.1, kernel 2.6.24-19-generic
root (hd0,3)
kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=a5f3bace-f758-4152-bed2-3c41ead77a28 ro quiet splash
initrd /boot/initrd.img-2.6.24-19-generic
quiet

title Ubuntu 8.04.1, kernel 2.6.24-19-generic (recovery mode)
root (hd0,3)
kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=a5f3bace-f758-4152-bed2-3c41ead77a28 ro single
initrd /boot/initrd.img-2.6.24-19-generic

title Ubuntu 8.04.1, memtest86+
root (hd0,3)
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 Professional
root (hd0,0)
savedefault
makeactive
chainloader +1


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, kernel 2.6.27-9-server (on /dev/sda3)
root (hd0,2)
kernel /boot/vmlinuz-2.6.27-9-server root=UUID=e30dda43-d75d-498e-bfc5-5c59a2787b5f ro quiet splash
initrd /boot/initrd.img-2.6.27-9-server
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, kernel 2.6.27-9-server (recovery mode) (on /dev/sda3)
root (hd0,2)
kernel /boot/vmlinuz-2.6.27-9-server root=UUID=e30dda43-d75d-498e-bfc5-5c59a2787b5f ro single
initrd /boot/initrd.img-2.6.27-9-server
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, kernel 2.6.27-7-server (on /dev/sda3)
root (hd0,2)
kernel /boot/vmlinuz-2.6.27-7-server root=UUID=e30dda43-d75d-498e-bfc5-5c59a2787b5f ro quiet splash
initrd /boot/initrd.img-2.6.27-7-server
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, kernel 2.6.27-7-server (recovery mode) (on /dev/sda3)
root (hd0,2)
kernel /boot/vmlinuz-2.6.27-7-server root=UUID=e30dda43-d75d-498e-bfc5-5c59a2787b5f ro single
initrd /boot/initrd.img-2.6.27-7-server
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda3.
title Ubuntu 8.10, memtest86+ (on /dev/sda3)
root (hd0,2)
kernel /boot/memtest86+.bin
savedefault
boot


title Fedora 9
chainloader (hd1,4)+1

I still hope to have this OS work, please examine my problem...!

Thank you so much for guiding...!

PS : Merry Christmas
__________________
"Don't fix it if it ain't broken, don't break it if you can't fix it."
Reply With Quote
  #11  
Old 23rd December 2008, 03:07 PM
stoat Offline
Registered User
 
Join Date: Jun 2006
Posts: 7,551
  1. The following is known to be true (from your Ubuntu menu.lst)...
    title Microsoft Windows XP Professional
    root (hd0,0)

    title Ubuntu 8.10, kernel 2.6.27-9-server (on /dev/sda3)
    root (hd0,2)

    title Ubuntu 8.04.1, kernel 2.6.24-22-generic
    root (hd0,3)
  2. Those are known to be on /dev/sda from the fdisk report.

  3. The fdisk report also shows that the only other Linux partition on your three drives is /dev/sdb5.

  4. Therefore these are the only possibilities for Fedora in grub.conf...
    (hd1,4)
    (hd2,4)
  5. You already tried (hd1,4) with the chainloader command and it didn't work.

  6. So now try (hd2,4).

  7. If that also does not work, then you did not install GRUB in the first sector of the Fedora boot partition and the chainloader command will not work for you.




P.S.: If it turns out that nothing works with the chainloader command for whatever reason, you can always boot the Fedora kernel and initial ramdisk directly from the Ubuntu menu.lst. To do that, you would boot Ubuntu, mount the Fedora partition, open the grub.conf file with a text editor, copy the entry for booting Fedora (title, root, kernel, and initrd command lines), and paste that into Ubuntu's menu.lst just like it is in the grub.conf. That should always work, and it's nice because you don't have to go through Fedora's splash screen or menu. The only problem with it is that it must be repeated when the Fedora kernel gets updated.




P.P.S.: Another option is to try the configfile command in the Ubuntu menu.lst. It doesn't require that GRUB be installed in the first sector of the Fedora boot partition like the chainloader command does. But it does require a grub.conf file to exist. It would be written like this...
title Fedora
configfile (hdx,y)/boot/grub/grub.conf

Last edited by stoat; 23rd December 2008 at 06:20 PM.
Reply With Quote
  #12  
Old 6th January 2009, 02:19 AM
ysNoi's Avatar
ysNoi Offline
Registered User
 
Join Date: Oct 2008
Location: Laguna, Philippines
Posts: 23
I still can't get into chainloader command siR. I also tried the configfile but I also got the same result.

Anyway, I would like to try to open the grub.conf file in Fedora partition with a text editor but may I know how to do it siR..? I tried to drag it in text editor but it says "Could not open the file /media/disk/boot/grub/grub.conf." "You do not have the permissions necessary to open the file".

Be lated happy New Year..!
__________________
"Don't fix it if it ain't broken, don't break it if you can't fix it."
Reply With Quote
Reply

Tags
boot, edit, fedora, grub

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
possible to edit /boot/grub/grub.conf from live cd? mailman1175 Using Fedora 4 29th December 2008 01:28 AM
Dual boot-- how to edit grub.conf and change the sequense??? petercn Using Fedora 11 12th October 2007 05:48 AM
Edit Grub Boot Sequence pzd6tl Installation and Live Media 5 14th September 2006 07:58 PM
edit grub file - fedora 5 tazdog Installation and Live Media 2 10th May 2006 04:26 AM
edit boot/grub/menu lst johnboy1967 Using Fedora 3 29th December 2004 03:09 AM


Current GMT-time: 07:55 (Monday, 20-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat