Grub loader problems in FC5

[ne...@celticbear.com]

I try to install FC5 on my system as a dual-bbot with WinXP Pro
(already installed) and get the error on boot up:

Booting 'Fedora Core (2.6.15-1.2054_FC5)'
root (hd2,0)
filesystem type is fat, partition type 0xc
Kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=/dev/sdb1 rhgb quiet
Error 15: File not found

When I change /boot/grub/menu.1st to say (hd2,1) or (hd2,2) I get the
error
Error 22: No such partition

Here's how I have it set up:

IDE drive 1 (/dev/hda) is just a spare data drive.
SATA drive 1 (/dev/sba) has my WinXP install (which I can boot into
using the grub boot menu just fine.)
SATA drive 2 (/dev/sdb) has the partitions in the following order:
/boot (swap) /

I tried booting up in "linux rescue" and doing a "grub-install
/dev/hda" and sda and sdb, all three, and each one gives me positive
feedback and shows my "map" file contents seemingly OK, but I still
can't boot.

Here's my /boot/grub/grub.conf

default=0
timeout=5
Splashimage=(hd2,0) /grub/splashimage.xpm.gz
hiddenmenu
title Fedora Core (2.6.15-1.2054_FC5)
root (hd2,0)
kernel /vmlinux-2.6.15-1.2054_FC5 ro root=/dev/sdb1 rhgd quiet
initrd /initrd-2.6.15-1.2054_FC5.img
title WinXP
rootnoverify (hd0,0)
chainloader +1

It doesn't make sense to me.
Those kernel and initrd files are found in my /boot partition which
should be (hd2,0), no?

Any ideas?
Thanks!
Liam

[Bill Waddington]

On 29 Apr 2006 14:08:02 -0700, "ne...@celticbear.com"
<ne...@celticbear.com> wrote:

If you can boot XP on your 1st SATA drive as (hd0,0) perhaps your 2nd
SATA drive is (hd1,0). Try root (hd1,0) in your Fedora Core grub
title. If that works, change your splashimage too :)

Maybe grub (BIOS?) is enumerating your drives differently than the
Fedora installer did when it set up grub.conf

Bill
--
William D Waddington
william.w...@beezmo.com
"Even bugs...are unexpected signposts on
the long road of creativity..." - Ken Burtch

[ne...@celticbear.com]

Well, that did the trick!
I should have tried that, if nothing than out of desperation. But I
should have caught the logic seeing Windows was set to 0,0.
Oddly, my /boot/grub/device.map shows:
[root@localhost grub]# cat device.map
# this device map was generated by anaconda
(hd0) /dev/hda
(hd1) /dev/sda
(hd2) /dev/sdb

Which is what kept my thinking stuck on hd2,0.
That and the bias that IDE comes before SATA. =/

So, should I change the device.map? Will having it set like that cause
some problems?

Thanks!
Liam

[Bill Waddington]

On 29 Apr 2006 18:22:54 -0700, "ne...@celticbear.com"
<ne...@celticbear.com> wrote:

>
>Bill Waddington wrote:
>> On 29 Apr 2006 14:08:02 -0700, "ne...@celticbear.com"
>> <ne...@celticbear.com> wrote:
>>
>> >I try to install FC5 on my system as a dual-bbot with WinXP Pro

[grub.conf was screwed up]

>> If you can boot XP on your 1st SATA drive as (hd0,0) perhaps your 2nd
>> SATA drive is (hd1,0). Try root (hd1,0) in your Fedora Core grub
>> title. If that works, change your splashimage too :)
>>
>> Maybe grub (BIOS?) is enumerating your drives differently than the
>> Fedora installer did when it set up grub.conf
>>
>Well, that did the trick!
>I should have tried that, if nothing than out of desperation. But I
>should have caught the logic seeing Windows was set to 0,0.
>Oddly, my /boot/grub/device.map shows:
>[root@localhost grub]# cat device.map
># this device map was generated by anaconda
>(hd0) /dev/hda
>(hd1) /dev/sda
>(hd2) /dev/sdb

I should leave this to someone who knows grub better...

Strange that grub.conf says that XP is hd0 (1st SATA) but device.map
says hd0 is your PATA drive.

I don't use a device.map when I set up grub. IIRC, it is only used
when BIOS and linux (or grub??) disagree on drive enumeration. In
your case it seems that they agree but anaconda didn't think so and
set up grub.conf and the device map incorrectly.

My WAG is that it's an anaconda issue. Does it still play nice if
you eliminate the device.map file (w/the new grub.conf)? Just curious.

[ne...]

On Sat, 29 Apr 2006 at 21:08 GMT, ne...@celticbear.com eloquently wrote:
[...]

> SATA drive 2 (/dev/sdb) has the partitions in the following order:
> /boot (swap) /
>
> I tried booting up in "linux rescue" and doing a "grub-install
> /dev/hda" and sda and sdb, all three, and each one gives me positive
> feedback and shows my "map" file contents seemingly OK, but I still
> can't boot.
>
> Here's my /boot/grub/grub.conf
>
> default=0
> timeout=5
> Splashimage=(hd2,0) /grub/splashimage.xpm.gz
> hiddenmenu
> title Fedora Core (2.6.15-1.2054_FC5)
> root (hd2,0)

The line above means root (/) is the first partition on
the third drive found. I the quoted text above root (/)
is the third partition. Try root (hd2,2) and see whether
this works.

N.Emile...
--
Registered Linux User # 125653 (http://counter.li.org) | Please remove
Certified: 75% bastard, 42% of which is tard. | '.invalid'
http://www.thespark.com/bastardtest | to reply.
Switch to: http://www.speakeasy.net/refer/190653