Hi, not sure if this is a bug with many
partitions/big drives or a combination of the two..or simply some error on my
part.
I just installed rh 8.0 on a western digital 80gig
hard drive, asus cusl2 mb, one 3com nic, 1 agp card.. Now that i got it
installed,
it won't seem to boot off of the hard drive. When booting off of the hdd it just hangs with "GRUB" at the top of the screen. I made a boot disk that it boots off of with no problems. I am posting the syslinux.conf from the boot disk and the grub.conf from the hdd. Hopefully someone can tell me what i'm doin wrong. I also tossed in my fstab to give some further info. 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/hda default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Linux (2.4.18-14) root (hd0,0) kernel /vmlinuz-2.4.18-14 ro root=LABEL=/ hdc=ide-scsi initrd /initrd-2.4.18-14.img syslinux.cfg: default linux
prompt 1 display boot.msg timeout 100 label linux kernel vmlinuz append initrd=initrd.img hdc=ide-scsi root=/dev/hda2 The thing that strikes me as strange is that on the bootdisk, root is set
to /dev/hda2 / is mounted on the second partition on /dev/hda wouldn't this be
/dev/hda1 and /boot is mounted on the first partition which i thought was
/dev/hda0 (doesn't redhat follow the normal "start at 0" convention?
Either way, it doesn't seem like EITHER syntax is right. The grub.conf has
root set at (0,0) which seems like it should be (0,1) and as i say,
syslinux.cfg has it at /dev/hda2 which seems like it should be at
/dev/hda1. One additional thing i found odd is that right in the commented
out section of the grub.conf, it mentions that since i'm using a /boot
partition, all files are relative to /boot/ so why then do the kernel and
vmlinuz sections point to a file with a leading / wouldn't it be like in
the syslinux.cfg where there is nothing or perhaps a ./ in front of the
files?
Here is the fstab:
LABEL=/
/
ext3 defaults 1
1
LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 LABEL=/export /export ext3 defaults 1 2 LABEL=/home /home ext3 defaults 1 2 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 LABEL=/tmp /tmp ext3 defaults 1 2 LABEL=/usr /usr ext3 defaults 1 2 LABEL=/var /var ext3 defaults 1 2 LABEL=/var/log /var/log ext3 defaults 1 2 LABEL=/var/spool /var/spool ext3 defaults 1 2 /dev/hda10 swap swap defaults 0 0 /dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0 /dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0 fdisking /dev/hda shows that the /boot system IS the first partiton and that / IS the second partition by comparing partition sizes. Thanks again.
Aaron
|
_______________________________________________ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub