Request for help - GRUB - MultiBooting issue/question

[neville.sequeira 0]

First off, I have found highly useful and valuable information at this site - thanks everyone.

 

Is there a recommended way (or a way at all) to setup GRUB and NTLDR (Windows XP) boot loaders such that one can jump between them in either direction?

 

I don't know if my problem is because I use a SATA drive, and/or if I have something erroneously specified in my GRUB config file; but with the following setup, I get the 'Bootpart ... ... GRUB _' screen if I try to get back to GRUB/Linux once I have jumped from GRUB to the Windows boot screen.

1. Windows XP was installed first on a SATA drive

2. Linux was installed second on an IDE drive set as primary master.

3. In BIOS boot order, the IDE drive comes before the SATA drive (have tried playing with this order - but not sure if this interplays with how specifically I have specified the contents of GRUB config file)

4. When installing Fedora Core 4, I have selected defaults to the most part. Specifically, two partitions: /boot (GRUB installed here) and '/' (everything else installed here)

 

Again, this is not a critical issue for me right now because, from GRUB, I am able to boot into Fedora Core 4 as well as go to Windows boot screen. But, I would really love to be able to go back to GRUB boot loader screen once I have navigated to Windows boot loader screen from GRUB. Any help would be greatly appreciated.

 

Thanks in advance,

-Neville

 

P.S. Unfortunately, I do not have a floppy drive.

 

[danleff 0]

Quote:

Is there a recommended way (or a way at all) to setup GRUB and NTLDR (Windows XP) boot loaders such that one can jump between them in either direction?

Technically yes, but practically, no. Why?

You have Fedora set up on the ide drive set to boot Grub.

If I understand your post correctly, you have Windows on sata, where the Windows bootloader resides.

If you read the recent posts on this subject, changing the boot order works as you have the system set up now, but the better
solution would be to correct grub and not switch the first drive designations in the bios.

Changing the first detected drive in the bios confuses Grub, as it needs to detect the different OS' on your system, as Grub was originally configured. Changing the boot order in the bios negates the correct designations Grub has given to your drives and partitions to properly boot the system, as they are mapped by Grub originally.

The same goes for the Windows bootloader. The boot.ini file is also set up to detect the booting of the actual Windows partition, dependent on the boot order in the bios when Windows was installed.

As you probably saw in the other posts, I am not happy with Fedora's Grub set-up when the default partitioning scheme is selected, namely, a /boot partition is used, rather than altering the MBR.

My system currently has the MBR on it's ide drive and Windows on the sata drive. But, I am using the SuSE's Grub to boot my system.

If you are up for it, post the contents of your menu.lst or Grub.conf file and the device.map and we can give it a go.

[neville.sequeira 0]

Danleff, thanks for responding. Below are the contents of the three files you mentioned.

 

Contents of /boot/grub/menu.lst ...

# grub.conf generated by anaconda

#

# Note that you do not have to rerun grub after making changes to this file

# NOTICE: You have a /boot partition. This means that

# all kernel and initrd paths are relative to /boot/, eg.

# root (hd0,0)

# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00

# initrd /initrd-version.img

#boot=/dev/hda1

default=0

timeout=90

splashimage=(hd0,0)/grub/splash.xpm.gz

#hiddenmenu

title Windows XP boot menu (cannot return to GRUB)

map (hd0) (hd1)

map (hd1) (hd0)

rootnoverify (hd1,1)

chainloader +1

title Fedora Core (2.6.11-1.1369_FC4)

root (hd0,0)

kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 ide=nodma rhgb quiet

initrd /initrd-2.6.11-1.1369_FC4.img

 

 

Contents of /etc/grub.conf ...

# grub.conf generated by anaconda

#

# Note that you do not have to rerun grub after making changes to this file

# NOTICE: You have a /boot partition. This means that

# all kernel and initrd paths are relative to /boot/, eg.

# root (hd0,0)

# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00

# initrd /initrd-version.img

#boot=/dev/hda1

default=0

timeout=90

splashimage=(hd0,0)/grub/splash.xpm.gz

#hiddenmenu

title Windows XP boot menu (cannot return to GRUB)

map (hd0) (hd1)

map (hd1) (hd0)

rootnoverify (hd1,1)

chainloader +1

title Fedora Core (2.6.11-1.1369_FC4)

root (hd0,0)

kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 ide=nodma rhgb quiet

initrd /initrd-2.6.11-1.1369_FC4.img

 

 

Contents of /boot/grub/device.map ...

# this device map was generated by anaconda

(fd0) /dev/fd0

(hd0) /dev/hda

(hd1) /dev/sda

 

[danleff 0]

...and Windows will using from Grub, as it stands now?

 

First of all, thanks for posting this, as it helps me see what Fedora is doing, as several folks have had trouble getting Fedora to dual boot Windows with this particular scheme.

 

Let me clarify a little on what you want to do, as I may have misunderstood.

 

If Windows boots via grub, you have a dual boot system.

 

Are you looking to switch over to the sata drive as the first boot device at some point? if so, I see your point. You can use the Windows bootloader to add Linux later on.

 

Trying to set up the system to add linux to the windows bootloader and boot the system via the ide (pata) drive also is complicated and I would not recommend doing this on your primary system.

 

Usually you do one or the other. There is no reason to do both, unless you intend to change the first boot device to the sata drive at some point.

[neville.sequeira 0]

Danleff, thanks for responding. I see your point. Yes, currently I am able to dual boot starting from GRUB's boot screen. For now, I will get back to using my system in that fashion and get back to other intricate boot related aspects at a later point.

I think I got a little over involved into booting for a while there.

 

Keep up the good work on this forum.