Thanks Rick. Can you please also send the /boot/grub/device.map list also?
When you boot, which disk the bios setup boots from? Is it /dev/sdb?
Regards

-----Original Message-----
From: Rick Forrister [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 08, 2003 5:17 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: dual boot


On Thu, 5 Jun 2003 13:09:07 -0400
"Nathan ViswaNathan" <[EMAIL PROTECTED]> wrote:

Nathan, here's my current (and working) /boot/grub/grub.conf for my
configuration.  Note that I've got 4 drives; /dev/hda & /dev/hdb are
allocated for Windows 2k, which my wife needs for work.  /dev/sda has one
linux install on it, /dev/sdb has another.  As configured, all works.  No
need to reinstall grub, just edit the grub.conf file.

On problem I had was that when I installed the second linux install I ended
up in a position where nothing but win2k could be booted.  The answer to
that was to use the edit capability, hitting "e" when the grub boot screen
came up.  I put in the lines from the "title RH 9" below manually, hit "b"
for boot, and all was well from there.

rickf


----- TEAR HERE -------------
# grub.conf generated by anaconda - and edited by me to make it work!
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd3,0)
#          kernel /vmlinuz-version ro root=/dev/sdb2
#          initrd /initrd-version.img
#boot=/dev/hda
default=1
timeout=10
splashimage=(hd3,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-20.1.1995.2.2.nptl)
        root (hd3,0)
        kernel /vmlinuz-2.4.20-20.1.1995.2.2.nptl ro root=LABEL=/1
        initrd /initrd-2.4.20-20.1.1995.2.2.nptl.img
title RH 9
        root (hd2,0)
        kernel /vmlinuz-2.4.20-6 ro root=LABEL=/
        initrd /initrd-2.4.20-6.img
title Winows 2000
        rootnoverify (hd0,0)
        chainloader +1
----- TEAR HERE ---------------

>
> Hi Rick,
>
> Can you post device.map and grub.conf for both of your linux systems to
boot
> W2K?
> I am running 2 linux and 1 w2k systems.
> I am having problems to boot w2k from each linux system. Currently I boot
> w2k by changing the bios boot sequence as Grub is not working foe=r w2k!
>
> My config:
>
>
> Hardware Setup:
> hda1 - w2k (30gb) (prim mastr) - one w2k partition.
> hdb1 - rh8 test version with grub in 1st sector of / partition. (not using
> /boot partition) (120 gb) (prim Slave)
> hdc2 - rh8 prod version with grub in 1st sector of / partition. (not using
> /boot partition) (120 gb) (sec mastr). hdc1 is dos partition.
> cd-rw (sec slave)
>
> 1. Bios set to boot from hdc2 to boot prod rh8: rh8 boots OK. w2k does not
> boot.
> device map:
> hd0  /dev/hdc  << note
> hd1  /dev/hda
> hd2  /dev/hdb
>
> grub.conf:
> rh8: root (hd0,1)  works
> w2k: what statements I have to use here? What grub created does not work.
> Tried many combinations!
>
> 2. Bios set to boot from hdb1 to boot test rh8:  rh8 boots OK. w2k does
not
> boot.
> device map:
> hd0  /dev/hdb  << note
> hd1  /dev/hda
> hd2  /dev/hdb
>
> grub.conf:
> rh8: root (hd0,0)  works
> w2k: what statements I have to use here? What grub created does not work.
> Tried many combinations!
>
> 3. Bios set to boot from hda1 to boot w2k:        w2k boots OK. Do not
need
> to boot rh8 from this environment.
> Works OK.
>
> 4. I do not undersatnd the documentation on map statement. What does it
do?
> After many frustrating trial error the following statements worked for
item
> 1 above to boot W2K. I do not understand the logic why it worked.
>          (A)       (B)           << what is A and B. Which one is
> root=(hd1,0) used under rh8 booting?
> map (hd0,0) (hd1,0)
> map (hd1,0) (hd2,0)
> map (hd2,1) (hd0,1)
> #What each of above map accomplish?
> rootnoverify (hd1,0) << points to A or B?
> rootnoverify (hd2,0)
> #Why no rootnoverify for (hd0,1)?
> #what each of above rootnoverify accomplish?
> chainloader +1
>
> (Tho it works, am I overkilling with redundant statements?)
>
> 5. Trying hard to make item 2 above work! No luck! Need help to understand
> the logic of item 4 to continue.
>
> Nathan
>
>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
>  2. Re: dual boot (Rick Forrister)
>
> Message: 2
> Date: Thu, 5 Jun 2003 09:06:20 -0700
> From: Rick Forrister <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: dual boot
> Organization: Minimal
> Reply-To: [EMAIL PROTECTED]
>
> On Wed, 4 Jun 2003 23:09:41 -0700 (PDT)
> redhatdaemon <[EMAIL PROTECTED]> wrote:
>
> > does anyone know of a good HOWTO on creating a dual boot win2000/redhat
> box?
> > i've done it before w/ 98, but i just can't seem to get 2000 to work.
>
> My system here has two Linux installs and Windows 2000 on it, runs grub,
and
> has been fine.  Only thing I found necessary is that I had to install Win
2k
> first, and be careful about the space it has available to it.  To acheive
> that, I first partitioned the drive space using a DOS boot disk, then
> installed W2K, then started installing Linux.
>
> This works fine if you are installing only (1) linux system and W2K.
> Multiple linux installs fall foul of a problem with the Red Hat install
> scripts, where the second linux install gets a stanza in grub.conf that is
> appropriate for a windows system, not a linux system.  I had to manually
> edit the grub.conf file to make it all work.
>
> Another alternative is to use Partition Magic/Boot Magic, which I've used
> with good success in the past.
>
> rickf
>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>


-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list

Reply via email to