> Here's a question for you. I Debian earlier on a machine at home that has > SATA drives. The SATA drives are configured as IDE-3 and IDE-4 Master's. > It installs fine, but when it boots, GRUB apparently can't find the config > file. It defaults to a text mode prompt GRUB>. It I enter > > root (hd2,0) > configfile grub/grub.conf > > it pops up the normal graphical GRUB menu and boots fine. > Internally, (hd2,0) is /dev/sda1. I tried setup (hd2) and that didn't make > any difference. So, it seems that GRUB can read the MBR from the drive, > but can't or won't look for config file on the same drive. Have you seen > anything like this?
If you boot from an SATA drive, then the boot loader and the GRUB shell will number your drives differently. This seems very likely to be your problem. Here are the notes that I made about this: The disk numbers may be different in the GRUB shell than in menu.lst: - The boot loader takes drives in the BIOS boot order, so the boot drive (currently /dev/sda) becomes (hd0). - The GRUB shell puts all IDE drives before all SCSI drives, so /dev/hda becomes (hd0) and /dev/sda becomes (hd1). (See the GRUB info, sec. 15.3) So, if I boot from a SCSI (SATA) drive, the numbering will be different. To make them agree, I can run grub as 'grub --device-map=/boot/grub/device.map', where I've edited /boot/grub/device.map to enforce the boot order on the disk numbers. (This also makes GRUB start faster, since it doesn't spend time trying to probe the BIOS boot order.) My /boot/grub/device.map is below. Good luck, Andrew. $ cat /boot/grub/device.map # I switched the order of /dev/sda and /dev/hda here to match # the BIOS boot order (and hence the numbering for the boot loader, # and in menu.lst). (fd0) /dev/fd0 (hd0) /dev/sda (hd1) /dev/hda -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
