On Wed, 12 May 2004 11:06:08 -0400
Phil Schaffner <Philip.R.Schaffner@xxxxxxxx> wrote:
> Have also used GRUB since it became the default, and it has a lot more
> functionality than LILO at the cost of additional complexity. Have
> multi-booted with GRUB and various combinations of
> RH/Fedora/other-distros and Windoze 98/Me/W2K/XP on various partitions
> and 1st/2nd/3rd... disks. There have been a number of threads on
> these issues in recent weeks/months.
>
> Problems usually occur when GRUB/BIOS see disks in different order[s]
> at boot and on the running system, and finding the right way to trick
> Bill's OSs into thinking they have the environment they want when it's
> really the way you want things set up. Having the correct combination
> of /boot/grub/device.map and "map (hdM) (hdN)" commands in
> /boot/grub/grub.conf, sometimes using detective work ("find" command
> is often helpful) in grub interactive mode in both environments
> (with/without device.map), will usually do the trick.
Mmh... that sounds very interesting... this really looks like it could
solve my problem (for some reason, GRUB thinks boot partition is on
(hd0,2) even though it has been installed on (hd0,0) and /etc/grub.conf
has "root(hd0,0)" on it.
device.map only has "(hd0) /dev/hda". Should it have anything else?
Any new ideas will be much appreciated...
> If you want some help debugging, post some specifics from "fdisk -l",
> GRUB config files, errors, and how you want things to work.
Here it is:
[root@tissot root]# fdisk -l /dev/hda
Disk /dev/hda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 1288 10241437+ 83 Linux
/dev/hda3 1289 3200 15358140 c Win95 FAT32 (LBA)
/dev/hda4 3201 4870 13414275 f Win95 Ext'd (LBA)
/dev/hda5 3201 4730 12289693+ 83 Linux
/dev/hda6 4731 4860 1044193+ 82 Linux swap
(please notice I am not the OP)
Best,
Andre
--
Andre Oliveira da Costa
