[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #19591] GRUB dual-boot configuration fails with Fedora Core 6

From: Steve Burtchin
Subject: [bug #19591] GRUB dual-boot configuration fails with Fedora Core 6
Date: Tue, 17 Apr 2007 08:43:11 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20060911 SUSE/ Firefox/

Follow-up Comment #2, bug #19591 (project grub):

_The same problem was observed with FC6 (kernel 2.6.20-1.2933.fc6) installed
on a new HDD with grub-0.97-13 and on an older PC where FC6 was installed on
the same HDD with grub-0.95-3 and FC3 (kernel 2.6.12-1.1381_FC3)._

In my experience on my Compaq Deskpro EN the *map* command definitely did not
perform as described in the GRUB manual.  I found it to be very buggy.  The
disks were swapped or not swapped depending on how they were looked at.  With
some Microsoft operating systems, disks formatted when they were remapped were
only accessible when booted with the disks remapped.  Likewise when disks were
not remapped.  When swapped, Windows 98 would assign drive letters as
expected, then assign drive letters again to the same partitions as if the
disks had not been swapped (but applications still percieved the disks as
being swapped).

I have only ever used GRUB 0.97, but I am wondering if when you installed FC6
here, the grub-0.95-3 was possibly overwritten with 0.97.  From the
description of your problem, it sounds like upgrading to the latest version
of GRUB is what caused the problem to surface.  If this is the case, then I
suspect a bug was introduced into *map* since the version of GRUB supplied
with FC3.

Rather than use the *map* command to swap disks in BIOS, I have found it to
be much simpler and more reliable to boot Microsoft operating systems on
whatever BIOS device they are physically located without attempting to fool
them.  This is easily accomplished by changing the "Drive ID" in the boot
sector to the actual BIOS number for that disk.

At least on my computer, use of *makeactive* has been entirely
inconsequential for all Microsoft operating systems from DOS 5.0 thru Windows
2000.  Is it ever needed?  For what?

This system would dual boot until I performed a Microsoft Update
and a NAV LiveUpdate last week and rebooted (something I've done for months
and never had a problem with).

I think you are referring to Norton Anti-Virus.  AV software may write
checksums, etc. anywhere on the HDD not normally used by a filesystem.  The
62 sectors following partition tables are usually free for proprietary uses
like this.  GRUB uses some of these sectors too.  Could be your AV has
overwritten part of the GRUB code.  Have you tried reinstalling GRUB?  From a
GRUB command line:

grub> root (hd#,#) --- ie. where the GRUB binaries are ("/boot/grub")
grub> setup (hd0)  --- assuming you want GRUB in the MBR

I'm not sure if this will install with your menu.lst.  You will have to read
up on that, or install from Linux.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]