Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Does win2003 have the same restriction as other forms of windows, that windows can only boot from the first drive? Booting xp when calling win2003 from grub makes it sound like that is the case for win2003.
If this is the case, then use the grub map commands to fool win2003 into thinking it’s on the first drive.
title Windows Server 2003
map (hd0) (hd2)
map (hd2) (hd0)
rootnoverify (hd0,0) # this may need to be rootnoverify (hd2,0)
I can never remember which rootnoverify is correct after mapping the drives, so if (hd0,0) doesn’t work, try (hd2,0).
These and other good info can be found in the Grub Manual (http://www.gnu.org/software/grub/manual/grub.html). It’s always a good idea to make a grub boot floppy to speed up the testing/configuration when having grub problems (see “Creating a GRUB boot floppy”).
An alternative method for getting two forms of windows and linux to boot is to use BootMagic, which is part of the Symantec PartitionMagic package.
Martin0: If you are asking how to install windows on the second drive with FC3 on the first drive, then you will save yourself a lot of headaches by (1) disconnecting the FC3 drive (i.e., physically disconnect either the power or IDE cable), (2) installing windows on the extra drive and then (3) reconnecting the FC3 drive as the first drive, in that order.
That way, windows will be happy during the installation and you will not alter the Grub modified MBR on the FC3 drive. The bonus to doing it this way is that you can select the second drive as the first bootable BIOS drive and boot into Win2003 directly without involving Grub, if you want or ever need to.
I have set up several dual boot systems this way and it really gives you a nice back door into windows when something goes wrong on the linux drive.
Thanks WhatsHisName, I've taken the short cut you suggest. This works in getting my Windows 2003 installed. Unfortunately when I go back to linux (having restored my original primary IDE drive), I find I need to restore my master boot record. Once I restore the MBR, get my modified grub boot menu, I can then boot linux again. Also I can boot Windows 2003 instead. But once I boot Windows my MBR gets corrupted again.
I think I have no choice but to make Windows 2003 my permanent physical primary IDE, and use the NTLDR boot loader instead of grub :-(
Grub administration is a little easier if you have windows on the first drive, but you should be able to put it on the second drive. It is fairly easy to start the Grub boot process from windows by modifying c:\boot.ini.
The reason for your MBR problem isn’t obvious to me. There may be some oddity about win2003. Check at the BIOS level whether the first bootable hard drive is the one containing FC3. While you had one drive disconnected, the hard drive boot order might have changed.
So I'm going ahead with making Win2003 disk IDE1 and Linux FC3 disk IDE2.
One question now is how change where grub is installed on my FC3 disk. Is was in the mbr, but I think it now needs to be in the 1st sector of /boot.
Would things work if I just swapped the two disks physically and copied the FC3 mbr to a file on my Win disk and referenced that file from ntldr boot.ini? Ie is there something in the mbr that knows (thinks) it is IDE0?
Interestingly, if I control the IDE device to boot from in my BIOS setup, I can switch between Windows and Linnux without any corruption. This implies I either made a mistake with my grub config or (I feel more likely) the modes in grub config don't have the same effect as modifying the BIOS throuh setup.