Can't get grub to boot Windows 2000

FUBAR · 2005-03-16 14:13:22

I've just finished installed Windows 2000 on the primary partition of my 3rd harddisk, which is the second harddisk connected to my onboard RAID-controller.
The disks connected to the RAID-controller aren't in a RAID-array, there just connected to it as if they were to an onboard IDE-controller.
I've got one disk connected to the onboard IDE-controller which has a small /boot partition. Grub sits in the MBR of this disk so I can boot into Linux.

My harddisck are all full, i.e. there's no room for extra partitions. To make room for Windows, I simply changed the partition type of the Linux-partition on (hd2, 0) to FAT32 and started the installation. I had to connect another harddisk to the IDE-controller because Windows needed another (non RAID-controller disk I guess) disk to write a few files to before I could proceed with the installation. I simply replaced my (hd0) with a small disk I had laying around so I could install Windows. The install went fine, I even installed SP4 and when I had to reboot I switched off the computer and put back my regular (hd0).
I then booted into Linux and changed grub's menu.lst to be able to boot Windows 2000:

#Windows 2000
title=Windows 2000
rootnoverify=(hd2,0)
chainloader +1
makeactive

I reinstalled grub to the MBR of (hd0) and rebooted. I can still boot into Linux without any problems, but when I try to boot Windows 2000 I'm presented with grub's bash-like CLI. And I can't figure things out from there.

My partitions

[15:04:16] fubar@ferro:~ $ fdisk -l    

Disk /dev/hda: 60.0 GB, 60040544256 bytes
16 heads, 63 sectors/track, 116336 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1          78       39280+  83  Linux
/dev/hda2              79      116336    58594032   83  Linux

Disk /dev/hde: 61.4 GB, 61492838400 bytes
16 heads, 63 sectors/track, 119150 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hde1               1       24220    12206848+  83  Linux
/dev/hde2           24512      119150    47698056    5  Extended
/dev/hde3           24221       24511      146664   82  Linux swap / Solaris
/dev/hde5           24512      117211    46720768+  fd  Linux raid autodetect
/dev/hde6          117212      119150      977224+  fd  Linux raid autodetect

Partition table entries are not in disk order

Disk /dev/hdg: 61.4 GB, 61492838400 bytes
16 heads, 63 sectors/track, 119150 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdg1   *           1       24220    12206848+   c  W95 FAT32 (LBA)
/dev/hdg2           24512      119150    47698056    5  Extended
/dev/hdg3           24221       24511      146664   82  Linux swap / Solaris
/dev/hdg5           24512      117211    46720768+  fd  Linux raid autodetect
/dev/hdg6          117212      119150      977224+  fd  Linux raid autodetect

Partition table entries are not in disk order

Grub is installed to hda's MBR and hda1 holds /boot. Windows 2000 is installed on /dev/hdg1.

I tried running fixmbr from Windows 2000's install CD which gives me a warning about another (incompatible, duh ) bootloader being installed and I have to put in "yes, I'm sure, please destroy the evil bootloader". It says it succeeded installing the bootloader but after I try booting from disc, I get a boot error: not even a bootloader is started!
I reinstalled grub and now I can boot Linux but I still get grub's CLI when I try to boot Windows 2000. How do I fix this?

If there's no other way, I'm even willing to make a Windows 2000 boot CD to boot Windows from (if that's even possible).

FUBAR · 2005-03-16 17:40:18

Screw this, I'm moving my RAID'ed disks to the onboard IDE-controller. This is probably way easier.

phrakture · 2005-03-16 18:06:41

hmmm I can check my grub settings.. but what I think is going on is that the "chainloader" command cannot find the win2k bootloader to chain to

FUBAR · 2005-03-16 19:45:57

Well, I've moved around my harddisks:

hda -> hde
hde -> hda
hdg -> hdc

After reconfiguring grub to reflect the changes I'd made, it wouldn't boot anymore: kernel panic, can't mount root fs.

I moved over to lilo (thx Maveric-i686 ) and now Arch is alive and kicking again!

I'm going to install Windows 2000 tomorrow (I've fucked around enough for one day) on /dev/hda1. That should keep it from complaining about bootloaders and stuff.

skoal · 2005-03-16 22:36:41

I believe all you need to do is use the 'map' option in 'menu.lst'. I think you would use:

map (hd0) (hdx)
map (hdx) (hd0)

Replace 'x' with the drive for win2k, and put those lines before 'chainloader'...

* I think I had to do that once when I had 2000 on my slave IDE. Don't know if that will help for RAID.

ssba · 2005-07-16 23:55:38

FUBAR wrote:

#Windows 2000
title=Windows 2000
rootnoverify=(hd2,0)
chainloader +1
makeactive

Try making it rootnoverify (hd2,0) instead of rootnoverify=(hd2,0). (take out the

FUBAR · 2005-07-20 10:03:02

Hehe, too late. I'm running Arch and Win2k next to each other now with LILO. It's working fine.

Arch Linux

#1 2005-03-16 14:13:22

Can't get grub to boot Windows 2000

#2 2005-03-16 17:40:18

Re: Can't get grub to boot Windows 2000

#3 2005-03-16 18:06:41

Re: Can't get grub to boot Windows 2000

#4 2005-03-16 19:45:57

Re: Can't get grub to boot Windows 2000

#5 2005-03-16 22:36:41

Re: Can't get grub to boot Windows 2000

#6 2005-07-16 23:55:38

Re: Can't get grub to boot Windows 2000

#7 2005-07-20 10:03:02

Re: Can't get grub to boot Windows 2000

Board footer