Hi Phil,
sorry for taking so long to reply. Some more data below...
On Thu, 13 May 2004 13:55:11 -0400
Phil Schaffner <Philip.R.Schaffner@xxxxxxxx> wrote:
> Why do you believe "GRUB thinks boot partition is on (hd0,2) even
> though it has been installed on (hd0,0)"? If you run grub
> interactively as root, does it find things that should be in /boot on
> (hd0,2)?
>
> Example - (from my FC1 system):
> [root@radar0 root]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda3 18577596 8242504 9391276 47% /
> /dev/sda1 46633 26180 18045 60% /boot
> /dev/sdb5 25331720 7051776 16993140 30% /alt
> /dev/sdb1 132207 13809 111572 12% /alt/boot
> /dev/sdc1 321298188 201297100 120001088 63% /raid0
> /dev/sdc2 164486068 68511016 87619648 44% /raid
> none 1552272 0 1552272 0% /dev/shm
> /dev/sda6 6854352 4647060 2207292 68% /dos
> /dev/sda2 8193148 4982400 3210748 61% /w2k
>
> [root@radar0 root]# grub
> Probing devices to guess BIOS drives. This may take a long time.
>
> GRUB version 0.93 (640K lower / 3072K upper memory)
>
> [ Minimal BASH-like line editing is supported. For the first word,
> TAB
> lists possible command completions. Anywhere else TAB lists the
> possible
> completions of a device/filename.]
>
> grub> find /grub/stage1
> (hd0,0) # this is /boot for FC1
> (hd1,0) # this is /alt/boot - old RH9 /boot
>
> grub> find /boot/grub/stage1
>
> Error 15: File not found # only found if no /boot partition
>
> grub> find /etc/fstab
> (hd0,2) # this is / for FC1
> (hd1,4) # this is /alt - or / for RH9 fallback
>
> grub>
Ok, here's what I have:
[root@tissot root]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda2 10080520 3452280 6116172 37% /
/dev/hda1 101086 6341 89526 7% /boot
/dev/hda5 12096724 4694580 6787660 41% /local
none 257300 0 257300 0% /dev/shm
/dev/hda3 15343136 8 15343128 1% /win
[root@tissot root]# grub
[...]
grub> find /grub/stage1
(hd0,0)
grub> find /boot/grub/stage1
Error 15: File not found
grub> find /etc/fstab
(hd0,1)
GRUB's output here seems to be consistent, but IIRC it is not the same
output I get after a reboot.
I don't have physical access to the machine right now, but I will see if
I can reboot it tomorrow and gather this same info.
> > device.map only has "(hd0) /dev/hda". Should it have anything else?
>
> Hard to say, do you have more disks? - see below...
Nope, only /dev/hda.
> This shows hda, but is it the only disk? "fdisk -l" should show all
> the disks if you don't specify /dev/xxx.
Sorry, I should have been more specific, it's only /dev/hda indeed.
[...]
> Not enough info provided to get a clue. Should also have asked for
> output of df and /etc/fstab, as well as /boot/grub/grub.conf
Ok, df output is printed above. The others follow:
[root@tissot root]# cat /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
LABEL=/local /local ext3 defaults 1 2
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda3 /win vfat defaults 0 0
/dev/hda6 swap swap defaults 0 0
/dev/hdb4 /mnt/zip auto noauto,owner,kudzu 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
[root@tissot root]# cat /boot/grub/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/hda2
# initrd /initrd-version.img
#boot=/dev/hda1
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Fedora Core (2.4.22-1.2188.nptl)
root (hd0,0)
kernel /vmlinuz-2.4.22-1.2188.nptl ro root=LABEL=/ hdc=ide-scsi rhgb noapic acpi=off
initrd /initrd-2.4.22-1.2188.nptl.img
title DOS
rootnoverify (hd0,2)
chainloader +1
Hope this info helps you understand what's wrong with my installation
(or with my understanding of how GRUB should work).
Thks again for spending some time on this.
Best,
Andre
--
Andre Oliveira da Costa
