Hi,
On Wed, 14 Nov 2007 08:25:50 +0000
Mick <[EMAIL PROTECTED]> wrote:
> > I know the drive is OK cause it boots when the boot
> > order in the BIOS starts with the first drive.
>
> Grub *should* be able to see what BIOS sees, but clearly this is not the case
> here. Have you tried reinstalling Grub in the MBR?
That most likely won't help since what's installed there only stages
the "real" grub binaries which will be most likely the same ones.
>From what maxim wrote so far it really looks like the BIOS moves the
entry for the HD on the first controller "out of sight" somehow. So
probably the BIOS feature of booting off the second controller is the
problem here. We can't solve this on the level of grub or the OS, so
the only option seems to be to properly install grub to the first HD.
I would start with a grub floppy disk or boot CD(-RW) and look what
devices that sees when booting. In order to have grub list disks, you
enter "root (" and press TAB. The same goes for partitions after the
setting device and a comma (e.g. "(hd0," + TAB).
If all devices are seen, then set root (as indicated above) to the
partition holding the grub stages (i.e. partition of /boot in Gentoo
or /lib/grub/i386-pc/). Then have grub write the MBR using
"setup (hd0)". Note that this will overwrite the Windows MBR, which
will make it unbootable at that point. So better before doing that --
from Linux -- backup the MBR:
"dd if=/dev/hda of=/backup-mbr-hda bs=512 count=1" so you can write it
back later.
-hwh
--
[EMAIL PROTECTED] mailing list
