On Wednesday 14 November 2007, Hans-Werner Hilse wrote: > 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.
Sure, unless something is corrupted in the Grub stages files? I wasn't sure
on the circumstances under which the IDE controller in question was fried.
> 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.
Are BIOS' that 'intelligent' these days?
> 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.
/The only time that I have experience a similar problem was after a drive
ribbon was hot unplugged mid-flight. The controller was not fried, not was
the drive, but it took sometime to get it going again. Ultimately an
investigation revealed that the jumpers at the back of the drives were not
effective (cable select would just not work)./
> 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.
Alternatively, use a MS Windows installation CD, boot into Recovery Console
and run fixmbr on the correct drive. It will reinstall the NTLDR boot code
in the MBR and you'll be able to natively boot it again. If you mess up the
MS Windows *partition* boot record because instead of hd0 you typed hd0,1
then the command you want is fixboot. I just hate reinstalling MS Windows -
it feels sort of wasted time! ;-)
HTH.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
