Thufir wrote:
The slave hard drive on my box is dual boot windows/linux. The master
also has linux. This makes for three OS's. Only the master hard drive
is booting at the moment, which I'd like to fix. All data has been
backed up.
When I attempt to boot windows I get an excerpt from
/boot/grub/grub.conf as follows:
title Other
rootnoverify (hd1,0)
chainloader +1
Other meaning windows (which I should change). Prior to installing
linux to the master, windows on the slave booted fine. However, linux
on the slave didn't boot. To expedite things I just went ahead and
installed linux on the master, as that seemed easiest at the time.
I know that grub can be edited, but I don't how it should be changed.
Perhaps this is related to the MBR on hdb? I don't mind re-installing
windows to hdb, I wanted to repartition anyhow.
If windows was installed originally with the drive as the master, it has
a boot.ini file that has information regarding references to the master
drive location. You can edit this file after reading about all of the
meanings for rdisk, etc used in the file to reference the secondary disk
instead.
It is also possible to add entries to the grub.conf file so Windows
thinks that it is the primary drive by fooling BIOS. There was much
discussion over the years regarding this tactic. I do not recall the
calls to grub.
Regarding getting your second Linux installation to boot. It is possible
to install grub for the secondary version of Linux to the boot partition
(EXAMPLE: install grub to /dev/hdb2) and then chainload this
installation by adding something like the below to your primary disk
version of grub. Then the secondary installation should boot from there.
Ideas, not a really detailed reply.
title Gentoo
rootnoverify (hd1,1)
chainloader +1
Jim
--
"What are we going to do tonight, Bill?"
"Same thing we do every night Steve, try to take over the world!"
