[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Not able to map hd1->hd0 for booting Windows on hd1
From: |
Jason Rennie |
Subject: |
Not able to map hd1->hd0 for booting Windows on hd1 |
Date: |
Wed, 21 Jul 2004 09:14:19 -0400 |
User-agent: |
Mutt/1.5.6+20040523i |
Hello,
I have the following disk set-up:
/dev/hda1 * 20GB Debian Sarge (mounted as /)
/dev/hda2 2GB Swap Space
/deb/hdb1 * 40GB Windows XP
I've followed the grub instructions for DOS/Windows. This is what the
entry for Windows looks like in my /boot/grub/menu.lst:
title Windows
map (hd0) (hd1)
map (hd1) (hd0)
root (hd0,0)
makeactive
chainloader +1
boot
But, whenever grub runs the "root (hd0,0)" command, grub sees the
linux partition:
Filesystem type is ext2fs, partition type 0x83
which is the filesystem and partition type of hd0,0. When grub tries
to boot it reports "Error 13: Invalid or unsupported executable
format". If I instead do "root (hd1,0)", grub sees the windows
partition:
Filesystem type unknown, partition type 0x7
But it hangs when it tries to boot (doesn't even get to the windows
splash screen). I see the same filesystem/partition type output if I
do not include the map commands. So, it seems that the "map" commands
are not doing what they are supposed to do.
If I disconntect the linux drive and hook up the windows drive as
master, the machine boots Windows.
I've looked through the existing bug list. This is not the same as
bug #486. No other bugs looked relevant.
I'm using grub (GNU GRUB 0.95), the version that currently comes with
Debian Sarge.
Machine Specs
-------------
Processor: Intel Celeron 2.8GHz
IDE Interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC
Bus Master IDE (rev 6)
Host bridge: VIA Technologies, Inc. P4M266 Host Bridge (rev 0)
/proc/ide/hda/model: Maxtor 6E030L0
/proc/ide/hda/geometry: physical 59582/16/63 logical 3738/255/63
/proc/ide/hdb/model: Maxtor 6E040L0
/proc/ide/hdb/geometry: physical 79656/16/63 logical 4998/255/63
Please send me e-mail if you think there are things I should try in
order to debug the problem.
Thanks for looking at this,
Jason
- Not able to map hd1->hd0 for booting Windows on hd1,
Jason Rennie <=