This is excerpts from the GNU GRUB manual. The manual suggests that you may have a problem with the device map in /boot/grub (this maybe where it is located). It says that GRUB doesn't know how to translate from bios disk to OS designations so it uses the device map in the grub directory. So Ashley you might check that out to see if it is corrupted or contains hdb which is causing a problem when you remove the device.
The grub manual is located at http://www.gnu.org/manual/grub/index.html GRUB features ============= Recognize multiple executable formats Support non-Multiboot kernels Load multiples modules Load a configuration file Provide a menu interface Have a flexible command-line interface Support multiple filesystem types Support multiple filesystem types transparently, plus a useful explicit blocklist notation. The currently supported filesystem types are "BSD FFS", "DOS FAT16 and FAT32", "Minix fs", "Linux ext2fs", "ReiserFS", "JFS", "XFS", and "VSTa fs". *Note Filesystem::, for more information. Support automatic decompression Access data on any installed device Support reading data from any or all floppy or hard disk(s) recognized by the BIOS, independent of the setting of the root device. Be independent of drive geometry translations Unlike many other boot loaders, GRUB makes the particular drive translation irrelevant. A drive installed and running with one translation may be converted to another translation without any adverse effects or changes in GRUB's configuration. Detect all installed RAM Support Logical Block Address mode In traditional disk calls (called "CHS mode"), there is a geometry translation problem, that is, the BIOS cannot access over 1024 cylinders, so the accessible space is limited to at least 508 MB and to at most 8GB. GRUB can't universally solve this problem, as there is no standard interface used in all machines. However, several newer machines have the new interface, Logical Block Address ("LBA") mode. GRUB automatically detects if LBA mode is available and uses it if available. In LBA mode, GRUB can access the entire disk. Support network booting GRUB is basically a disk-based boot loader but also has network support. You can load OS images from a network by using the "TFTP" protocol. Support remote terminals Errors reported by the Stage 1 ============================== The general way that the Stage 1 handles errors is to print an error string and then halt. Pressing `<CTRL>-<ALT>-<DEL>' will reboot. The following is a comprehensive list of error messages for the Stage 1: Hard Disk Error The stage2 or stage1.5 is being read from a hard disk, and the attempt to determine the size and geometry of the hard disk failed. Floppy Error The stage2 or stage1.5 is being read from a floppy disk, and the attempt to determine the size and geometry of the floppy disk failed. It's listed as a separate error since the probe sequence is different than for hard disks. Errors reported by the Stage 1.5 ================================ The general way that the Stage 1.5 handles errors is to print an error number in the form `Error NUM' and then halt. Pressing `<CTRL>-<ALT>-<DEL>' will reboot. The error numbers correspond to the errors reported by Stage 2. *Note Stage2 errors::. Errors reported by the Stage 2 ============================== The general way that the Stage 2 handles errors is to abort the operation in question, print an error string, then (if possible) either continue based on the fact that an error occurred or wait for the user to deal with the error. The following is a comprehensive list of error messages for the Stage 2 (error numbers for the Stage 1.5 are listed before the colon in each description): -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
