Re: "grub" command works, but GRUB boot loader hangs

[Jeremy Katz]

On Sunday, August 05 2001, Ben Liblit said:
> Recall that this system has a SCSI controller with two drives, one of
> which is ordinarily used as the boot drive.  There's also an old IDE
> drive hanging off the secondary channel, a SCSI CD-ROM, and a floppy
> tape drive controller.  (For more complete details, see
> <http://mail.gnu.org/pipermail/bug-grub/2001-August/005353.html> for
> my original message, or 
> <http://mail.gnu.org/pipermail/bug-grub/2001-August/005360.html> for a
> shorter configuration summary produced by "fdisk -l".)

So, to clarify, in your BIOS, you have boot order set to something like
"A/SCSI/C" or something similar to that (depending of course on BIOS
manufacturer and how they decided they wanted to denote things).  Also,
what does /boot/grub/device.map look like?
 
> First off, the floppy tape drive controller is not relevant.  I can
> remove the card and nothing changes.  I thought that perhaps this
> controller was causing the extra "(fd1)" floppy drive to be detected,
> but apparently that's not where it's coming from.

Since you are running Roswell and therefore have a recent kudzu, can you
get the output of `/usr/sbin/kudzu -p -c FLOPPY`?  

> Unplugging the secondary master IDE hard drive has no effect.  This is
> surprising, because when GRUB is working correctly it should detect
> this drive and make it available.

Actually, depending on your BIOS boot order and the contents of the
device.map, this drive may not actually be accessible.

Thanks,

Jeremy