On Fri, 2006-01-13 at 00:02 -0500, oleksandr korneta wrote:
> Hello,
>
> I have 2 hard drives in my box with linux and windows on hda and hdb
> respectfully. My grub is on mbr of hda. And windows loader is on mbr of
> hdb. I can boot with no problems into windows when I set hdb to be
> master drive. However when I try to boot into windows from current
> configuration the only message I get is
>
> chainloader +1
>
> which is the string from the grub.conf
> Nothing more happens.
>
> # grub.conf generated by anaconda
> #
> # 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 (hd0,0)
> # kernel /vmlinuz-version ro root=/dev/hda3
> # initrd /initrd-version.img
> #boot=/dev/hda
> default=0
> timeout=10
> splashimage=(hd0,0)/grub/splash.xpm.gz
> #hiddenmenu
> title Fedora Core (2.6.14-1.1637_FC4)
> root (hd0,0)
> # kernel /vmlinuz-2.6.14-1.1637_FC4 ro root=LABEL=/1 vga=792
> kernel /vmlinuz-2.6.14-1.1637_FC4 ro root=LABEL=/1
> initrd /initrd-2.6.14-1.1637_FC4.img
> title w2k
> rootnoverify (hd1,0)
> chainloader +1
>
> # end of grub.conf
>
Try mapping the drives as follows
title w2k
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1
I had a similar issue and found that the Windows drive has to believe
it is the master drive (thus the mapping lines) but grub still has to
use the device as defined in /boot/grub/device.map (thus the
rootnoverify line does not change.)
Once I had figured out that intricacy I was able to do what you are trying.
This seems to come from installing Windows on the master drive then
moving it to the slave position on the controller. If you install
windows on the drive in the slave position with another drive in the
master position the mapping seems to not be necessary.
>
> and here is the content of my boot.ini
>
> [boot loader]
> timeout=3
> default=multi(0)disk(1)rdisk(1)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
> Professional" /fastdetect
>
> I tried to change the partition number here from 0 to 1to tell the OS
> that it is actually on the slave drive.
>
> I suspect that for some reason windows does not like to have its
> bootloader on a slave drive. This is just a pure guess (assuming that
> everything I've done is ok). But if it is true, is there any workaround
> or do I have to replace my grub with ntldr like the fellow couple
> threads above?
>
>
> --
> regards,
> Oleksandr Korneta
>
> /The nice thing about standards is that there are so many to choose from./
>
