Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a question regarding grub, linux (fedora) and windows server 2003. I have a 2 drive system. I installed fedora on hda. After that, I installed windows server 2003 on hdd (slave on ide2). I had to scarf the page partition from linux to complete the install, but, I have linux back to normal, and now have windows server 2003 solely on the secondary slave.
I'm trying to get grub to boot server2003. I have the following entry in my grub.conf file:
title Windows Server 2003
map (hd3) (hd0)
map (hd0) (hd3)
rootnoverify (hd0,0)
makeactive
chainloader +1
I get a series of errors based on what I use in rootnoverify. (tried hd0, and hd3)
Question 1: When you use map, i.e. make hd3 look like hd0, does rootnoverify need the *original*, or the *mapped* hd?
Question 2: Due to the way windows likes to do things, it installed it's boot loader on hd0. I coppied the boot.ini, ntdetect, etc from the swap partition to the root directory of hd3, remade the swap partition and linux is happy. Do I need to in essence, make hd3 hd0, and install windows server, then re-cable, then deal with grub?
finally figured it out! The drive is the secondary slave, but only the *second* hard drive. Therefore, map (hd0,hd1) map (hd1,h0) worked!.
Now, for the next question:
Does this mapping actually affect the drive information? I.E. do I modiy boot.ini as if it's booting from the first drive? Or modify it for the actual scenario?
Apparently, map(hd1,hd0) does an actual hardware map. So the final grub configuration is as follows:
title Windows Server 2003
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1
Then, the last remaining problem is that since windoze is required to be installed on primary controller, server 2003 still thought my linux swap file (the one I cannablized to do the install) was still there. After remaking the swap file a few times, I finally disable disk0 in the hardware profile. Now, Windows server 2003 boots cleanly from grub, and does not do a chdsk on what is my linux swap partition!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.