Re: Not able to map hd1->hd0 for booting Windows on hd1

[Jason Rennie]

On Wed, Jul 21, 2004 at 03:36:25PM +0200, Marco Gerards wrote:
> > But, whenever grub runs the "root (hd0,0)" command, grub sees the
> > linux partition:
> >
> >  Filesystem type is ext2fs, partition type 0x83
> 
> It seems that mapping was not required and that your second harddrive
> was reported by the BIOS as the first.

I don't think the entry to boot Debian would work if that were the case:

title           Debian GNU/Linux, kernel 2.4.26-1-686 
root            (hd0,0)
kernel          /boot/vmlinuz-2.4.26-1-686 root=/dev/hda1 ro 
initrd          /boot/initrd.img-2.4.26-1-686
savedefault
boot

Also, when I run "root (hd0,0)" w/o map, I get the same output:

 Filesystem type is ext2fs, partition type 0x83

I think the problem is with map, not with my BIOS.  The map commands
seem not to be doing anything.  Or, maybe there is a problem with my
BIOS interpreting the map command.

> > 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
> 
> Perhaps you are using a NTFS partition.  In that case you should use
> rootnoverify instead of root.

Yes, I think it is an NTFS partition (Windows XP), but rootnoverify
doesn't work either.  i.e. if I change my Windows entry to:

title Windows
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd0,0)
makeactive
chainloader +1
boot

Grub reports "Error 13: Invalid or unsupported executable format" when
it tries to boot.

Any other ideas?

Jason