Chainloader +1 not booting XP

[Laglure]

Hello,

I just installed Fedora on a separate HD. I currently have 3 HD, HD1 with XP, HD2 as storage and back up, and HD3 with Fedora. Now, I have Grub set up to boot both and HD3 as the primary drive and Grub does allow me to choose which OS (XP being Other) but when I boot "Other" I get a prompt listing the HD and Chainloader +1 but then nothing happens, the screen just hangs on this screen. I cannot enter text and I am at a loss. Now I can go into Bios and choose which drive to boot from and get XP working fine and go back and choose Fedora so I am guessing it's something with Grub since the HDs are fine and booting works. I am new to Linux and I no idea how to approach fixing this problem.

Thanks for the help.
Steve

[Zotter]

Post the output from these two commans:

cat /boot/grub/grub.conf
and
fdisk -l (lower case 'L')

[Laglure]

Hello,

Now, I may be running commands wrong but I opened a terminal and ran those commands.
For cat /boot/grub/grub.conf
I received "Permission Denied" I am logged on admin and have full access.
For fdisk -l
I recived a "command not found"

I don't know if that helps you or if I did something wrong entering the commands.

Steve

[helidude20]

Not sure but, on my system FC5 I have to do /sbin/fdisk -l as root. Not sure as to why. It's a setting somewhere I'm sure.

[jpmills]

login as superuser, su, and print out your /boot/grub/menu.lst

Its a simple fix once you do

[bob]

Actually, you need to log in as 'su -' (full root) to do the 'fdisk -l'.

[Laglure]

Hello,

First thanks for the help and second sorry for the long reply time. Here are the results of the commands.

sbin/fdisk -l Command
Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 594 24321 190595160 7 HPFS/NTFS
/dev/sda2 1 593 4763241 b W95 FAT32

Partition table entries are not in disk order

Disk /dev/sdb: 300.0 GB, 300069052416 bytes
255 heads, 63 sectors/track, 36481 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 36481 293033601 7 HPFS/NTFS

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

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 13 104391 83 Linux
/dev/sdc2 14 274 2096482+ b W95 FAT32
/dev/sdc3 275 19457 154087447+ 8e Linux LVM

cat /boot/grub/grub.conf Command
# 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/sdc
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.15-1.2054_FC5smp)
root (hd0,0)
kernel /vmlinuz-2.6.15-1.2054_FC5smp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.15-1.2054_FC5smp.img
title Other
rootnoverify (hd1,1)
chainloader +1

[bob]

Did you install FC by removing the other two drives? It looks that way since grub has called Fedora Core (hd0,0) when it's actually (hd2,0). Don't change that though! You may have to map the drives as described here: http://www.fedorajim.homelinux.com/ but first why not change that 'Other' to (hd1,0) and see if that works. Since * indicates a boot at both sda and sdb, it's a bit difficult to tell which one is really the Windows boot. Should be either (hd1,0) or (hd2,0) but not sure which one. If you've actually installed as described in the link, you'll need to map the drives as shown, but you might have to play with the numbers. Normallly, sda=hd0, sdb=hd1, sdc=hd3 but in this case grub is booting Fedora as hd0 when it's sdc, so the numbering sequence is a bit mixed.

In any case, save a copy of your original grub.conf before you start messing around so you can always go back to the beginning. Then make changes and note your results. It will take a try or two, but you'll have it booting shortly.

[Laglure]

Thanks Bob,

I'll try to sort this out tonight. The drive with XP is partitioned and based on what you said, I think Grub is trying to boot the recovery partition and not the actually XP partition on that HD. When I installed I did have all the drives connected because I thought something like might happen if I didn't but it appears to have gone awry anyway. Thanks again and I'll let everyone know if it worked.

Steve