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

Re: Dual-booting F7 and WinXP on separate harddisks

McGuffey, David C. wrote:
> This should be easy.
> I had an NTFS formatted hard disk (hd1) start to fail on me and decided
> now was the time to convert to Linux. I can't completely give up WinXP
> because of some of the programs the rest of my family needs for which
> there is no Linux substitute.  My plan is to eventually move WinXP into
> a VMware virtual machine on top of Linux (have been doing that for
> several years to perform os hardening and other security-related
> activities).  For now, I need to dual-boot, while I get Linux all ready
> to go.
> I successfully backed up all the data on the old NTFS formatted disk
> (hd1) and pulled it out. There are still programs and data on the
> remaining good drive (hd0) that must be kept until I can move them into
> the virtual machine.
> Bought a new 320 GB EIDE disk and installed it as MASTER and moved the
> previous MASTER (a 160 GB EIDE disk that booted WinXP) to SLAVE. That
> made the old hd0 hd1 and the new disk hd0. Without any OS installed on
> the new hd0, the machine continued to boot WinXP from hd1.
> I installed Fedora 7 on hd0 F7 and it successfully boots.  However, when
> I try to tell grub (through the grub menu) to boot the "other" OS, it
> echos the last line "chainloader +1" and dies.  Apparently it can't find
> the WinXP boot loader in the MBR of hd1. When I disconnect the cable
> from the new hd0 and power back up, WinXP boots.  When I reconnect the
> drive and power back up, Linux boots.  I can force this behavior in the
> BIOS by removing the new hd from the boot device list.
If the chain loader was not finding the XP boot loader, it would
complain about an invalid format. (I have run into that before.) It
is more likely that the XP boot loader is trying to load from the
wrong place.

> Several years ago, I had RH Linux 7.2 in a dual-boot mode with Win NT
> 4.0, but it was all on one hd, each os with their own partition(s), one
> MBR, all managed by lilo.  That install went mostly automatic and I
> didn't have to tweak any settings in the BIOS or lilo...it all just
> worked.
> I've looked at a bunch of dual-boot guidance but I'm not finding what I
> need to deal with two separate hd each with their own os and MBR. Maybe
> it is there, I'm just not understanding it.
> This should be easy...what do I need to do to get grub to chainload
> WinXP on hd1?
You may need to tell Grub to swap the drives, so XP is still on the
BIOS drive it was installed on. I suspect that the XP boot loader is
trying to load from the wrong drive/partition.

> Copies of /boot/grub.conf and output from df and parted are provided
> below. The only change I made to grub.conf was to up the timeout from 5
> to 10 seconds.
> BTW, it is interesting to me that the drives are physically EIDE but the
> output of df and parted show them as scsi.  I expected to see them as
> hda and hdb, not sda and sdb. Why is that?
With F7, all IDE drives are treated as SCSI drives.
> # 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/sda6
> #          initrd /initrd-version.img
> #boot=/dev/sda
> default=0
> timeout=10
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title Fedora (
> 	root (hd0,0)
> 	kernel /vmlinuz- ro root=LABEL=/ rhgb quiet
> 	initrd /initrd-
> title Fedora (2.6.21-1.3194.fc7)
> 	root (hd0,0)
> 	kernel /vmlinuz-2.6.21-1.3194.fc7 ro root=LABEL=/ rhgb quiet
> 	initrd /initrd-2.6.21-1.3194.fc7.img
> title Other
> 	rootnoverify (hd1,0)
	map (hd0) (hd1)
	map (hd1) (hd0)
> 	chainloader +1
Try adding the two instructions above to your config and see if that
fixes the problem.


  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

Attachment: signature.asc
Description: OpenPGP digital signature

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