Re: grub access

[Melissa Golter]

thank you for your reply, suggestion.

Perhaps I should note more carefully that these are SCSI hard drives (i
have been told there is no master-slave business going on with them)? Or
mebbe this is not what you meant? 

Also, hd with SCSI id 0 has win2k on it, and I don't know enuf to futz
with having a non-win drive in *command* so-to-speak... 

In any case, mebbe what is really the problem is that somehow the linux os
was mistaken for a win os, and the boot-up sequences are different, hence
it won't boot up.  I don't know where to change all the references to that
mistake:

Do you (anyone) know all the places that need to change in order to make
the boot-recognition change for this linux drive?

On Sun, 9 Nov 2003, Thierry Laronde wrote:

> Hello,
> 
> On Sun, Nov 09, 2003 at 10:12:38AM -0600, Melissa Golter wrote:
> > 
> > To Whom:
> > 
> > the other day I was able to use GRUB to boot between 2 hard drives
> > SCSI hard drive ID 0; 8GB; OS is win2k
> > SCSI hard drive ID 1; 8GB; OS is rh9.0
> > The GRUB version/boot situation was working well.
> > 
> > Yesterday I added a third hard drive (SCSI hard drive ID 2, 18.3GB) and
> > overwrote the original GRUB with a copy (same GRUB, same version off the 
> > same rh9 rpm discs).
> > 
> 
> The problem is that GRUB accesses the hard disks in the order the BIOS
> affects the ID numbers, that is you are not sure that the order you have
> apparently (hard disks 1, 2 and 3) matches the BIOS order.
> 
> At a guess I suggest to try to boot from (hd2), meaning that perhaps 1
> and 3 are primaries and leasted before the slaves, that is that the
> second disk has becomed the third one (for GRUB).
> 
> At least you can try.
> 
> Cheers,
> -- 
> Thierry Laronde (Alceste) <address@hidden>
> Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C
> 

# 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 (hd2,0)
#          kernel /vmlinuz-version ro root=/dev/sdd2
#          initrd /initrd-version.img
#boot=/dev/sdb
default=2
timeout=10
splashimage=(hd2,0)/grub/splash.xpm.gz
password --md5 $1$eFYlutTv$HAVMouWUcPkj7EUtydINh1
title rh9DB (2.4.20-8smp)
        root (hd2,0)
        kernel /vmlinuz-2.4.20-8smp ro root=LABEL=/1 hda=ide-scsi
        initrd /initrd-2.4.20-8smp.img
title rh9DB-up (2.4.20-8)
        root (hd2,0)
        kernel /vmlinuz-2.4.20-8 ro root=LABEL=/1 hda=ide-scsi
        initrd /initrd-2.4.20-8.img
title DOS
        rootnoverify (hd0,0)
        chainloader +1
#title rh7-3YG
#       rootnoverify (hd1,1)
#       chainloader +1
title rh7-3YG (2.4.20-8smp)
        root (hd1,0)
        kernel /vmlinuz-2.4.20-8smp ro root=LABEL=/1 hda=ide-scsi
        initrd /initrd-2.4.20-8smp.img
title rh7-3YG-up (2.4.20-8)
        root (hd1,0)
        kernel /vmlinuz-2.4.20-8 ro root=LABEL=/1 hda=ide-scsi
        initrd /initrd-2.4.20-8.img