bootloader blues

[Glenn Johnson]

Jimmy Montague wrote:
> So Stephen: I understand you pulled the strap off the Master drive, 
> booted from CD-ROM, and installed FC5 on the Slave. You also told Grub 
> to install itself on the Slave (which, because the Master was absent 
> from the strap, was the only option the installer listed). Then you 
> put the strap back on the Master drive, booted your machine -- and 
> what? It seems to me that the system would then boot from the Master 
> drive just as it always did, ignoring the Slave and the Grub file 
> installed there.
>
> Correct me if I'm wrong, please, but (in doing so) please explain WHY 
> I'm wrong. I'm not saying I won't try your solution. I'm saying that, 
> at this point, your solution mystifies me. I can't see how it would work.
>
> Jimmy
>
> Stephen Esquibel wrote:
>> I had a similar problem.  I believe that it had to do with the MBR on 
>> the drive (either one)  see the bugzilla report and see if my 
>> solution helps at all.
>>
>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188111
>>
>> On 4/13/06, *Jimmy Montague* <rhetoric101 at att.net 
>> <mailto:rhetoric101 at att.net>> wrote:
>>
>>     Thanks Stephen. I tried that already. When I tried to boot the
>>     system,
>>     the BIOS told me it couldn't find an OS.
>>
>>     Jimmy
>>
>>     Stephen Esquibel wrote:
>>     > Try changing your BIOS to boot from the Linux drive rather than 
>> the
>>     > Windows one.  Then have the Grub, which is already installed 
>> there,
>>     > choose the OS.
>>     >
>>     > Just a thought.
>>     >
>>     > On 4/13/06, *Jimmy Montague* <rhetoric101 at att.net
>>     <mailto:rhetoric101 at att.net>
>>     > <mailto: rhetoric101 at att.net <mailto:rhetoric101 at att.net>>> wrote:
>>     >
>>     >     Tim wrote:
>>     >     > On Thu, 2006-04-13 at 08:41 -0500, Jimmy Montague wrote:
>>     >     >
>>     >     >> So my problem is that, having installed Core 5, I can't
>>     boot Core 5
>>     >     >> because the boot loader seems to have installed itself 
>> on the
>>     >     Linux
>>     >     >> drive INSTEAD of on the Windoze drive. That's to say that,
>>     >     whenever I
>>     >     >> boot the system, the Windoze boot loader appears INSTEAD
>>     of the
>>     >     Grub
>>     >     >> boot loader. My attempts to repair and/or reinstall Core 5
>>     >     yield the
>>     >     >> same result.
>>     >     >>
>>     >     >> Anyone got a solution?
>>     >     >>
>>     >     >
>>     >     > Install GRUB to the right place...
>>     >     >
>>     >     > Well, that is what you need to do, and you can work out 
>> how to
>>     >     do this
>>     >     > from the GRUB info file (the man file is quite
>>     abbreviated).  If you
>>     >     > can't follow it, and/or want more specific help, supply more
>>     >     information
>>     >     > about how your drives are on your system.  Post us the 
>> output
>>     >     from the
>>     >     > following command, issued as the root user:  fdisk -l
>>     >     >
>>     >     > (That's a letter l, not a number 1.)
>>     >     >
>>     >     >
>>     >     Tim:
>>     >
>>     >     Read this post in a full-screen window.
>>     >
>>     >     My system has two 40g Maxtor ide drives. Both are on the
>>     primary
>>     >     strap.
>>     >     One is jumpered Master; the other is Slave.
>>     >
>>     >     Windoze is on the Master drive. FC5 is installed on the Slave.
>>     >     Sorry: I
>>     >     can't decipher the MAN page. I don't know how to copy
>>     bootloader
>>     >     to the
>>     >     MBR of the Windoze drive..
>>     >
>>     >     When I ran fdisk -l, as you suggested, here is the result:
>>     >
>>     >     Disk/dev/hda: 40.0 GB, 40027029504 bytes
>>     >     255 heads, 63 sectors/track/ 4866 cylinders
>>     >     units = cylinders of 16065 * 512 = 8225280 bytes
>>     >
>>     >     Disk/dev/hdb: 40.0 GB, 40027029504 bytes
>>     >     255 heads, 63 sectors/track/ 4866 cylinders
>>     >     units = cylinders of 16065 * 512 = 8225280 bytes
>>     >
>>     >     Device       Boot       Start
>>     >     End      Blocks          Id      System
>>     >     dev/hda1      *             1
>>     >     4865    39078081      7      HPFS/NTFS
>>     >
>>     >     dev/hdb1      *            1            13          
>> 104391        83
>>     >     Linux
>>     >     dev/hdb2                   14         4866   38981722+    8e
>>     >     Linux LVM
>>     >
>>     >
>>     >     --
>>     >     fedora-list mailing list
>>     >     fedora-list at redhat.com <mailto:fedora-list at redhat.com>
>>     <mailto:fedora-list at redhat.com <mailto:fedora-list at redhat.com>>
>>     >     To unsubscribe:
>>     >     https://www.redhat.com/mailman/listinfo/fedora-list
>>     <https://www.redhat.com/mailman/listinfo/fedora-list>
>>     >     <https://www.redhat.com/mailman/listinfo/fedora-list>
>>     >
>>     >
>>     >
>>     
>> ------------------------------------------------------------------------
>>
>>     >
>>     > No virus found in this incoming message.
>>     > Checked by AVG Free Edition.
>>     > Version: 7.1.385 / Virus Database: 268.4.1/309 - Release Date:
>>     4/11/2006
>>     >
>>
>>     --
>>     fedora-list mailing list
>>     fedora-list at redhat.com <mailto:fedora-list at redhat.com>
>>     To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>>
>>
>> ------------------------------------------------------------------------
>>
>> No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.1.385 / Virus Database: 268.4.1/309 - Release Date: 4/11/2006
>>   
>
With the Windows drive as master and the Linux drive as slave, boot from 
the Fedora cd, choose rescue mode and follow the prompts. When you get 
to the command prompt type chroot  /mnt/sysimage as told. Then type 
grub-install /dev/hda. Reboot the computer (without the cd of course).