LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 02-07-2006, 04:54 PM   #1
you
LQ Newbie
 
Registered: Jan 2006
Distribution: Kubuntu 5.10
Posts: 2

Rep: Reputation: 0
Tri-Boot Problem, Kubuntu, XP, and Server 2003


Hey all, I am having problems tri-booting my machine. I am trying to get:

Windows XP Home
Windows Server 2003
Kubuntu 5.10

Installed on the same hard drive. Here is the problem. After researching, it seemed best if installed the OS's in that order, which I did. XP Home and Kubuntu worked fine with this, but Server 2003 didn't like it, giving me the error message:

Windows could not start because the following file is missing or currupt:
<Windows root>\system32\ntoskrnl.exe.
Please re-install a copy of the above file

Where I am a bit confused is how Kubuntu can work fine, and it see the Windows loader, how XP can load correctly, but 2003 not. I have verified that the ntoskrnl.exe is still there and seems to be uncorrupted. I have also looked at the boot.ini file, and it seems to be in order and correct partitions and everything (to the best of my knowledge). It works correctly when only XP and 2003 are installed, not sure where to go from here?

I appreciate the help, if I need to provide some more info, please let me know.

Thanks.
 
Old 02-08-2006, 07:32 AM   #2
bigrigdriver
LQ Addict
 
Registered: Jul 2002
Location: East Centra Illinois, USA
Distribution: Debian Squeeze
Posts: 5,796

Rep: Reputation: 323Reputation: 323Reputation: 323Reputation: 323
Sounds like a problem folks have when dual booting any version of windoze and Linux. If win isn't on the first partition of the first drive, it will balk as cooperating with the bootloader.

So, which bootloader are you using? If grub, please post the lines from /etc/fstab relating to your partitions for win and Linux, as well as /boot/grub/menu.lst (or grub.conf if that's what your installation uses).

You could also edit the menu.lst entry for the server to look like this:
title Server (or whatever you call it)
rootnoverify (hd0,1)
map (hd0,0) (hd0,1)
map (hd0,1) (hd0,0)
makeactive
chainloader +1

Assuming the server is in the second partition of the drive, this should remap the partitions for win server to think it's on the first partition. Then grub would hand the boot process over to the win bootloader.
 
Old 02-09-2006, 11:03 PM   #3
you
LQ Newbie
 
Registered: Jan 2006
Distribution: Kubuntu 5.10
Posts: 2

Original Poster
Rep: Reputation: 0
Sorry I have taken a while to get back, work has been out of control this week.

Quote:
Originally Posted by bigrigdriver
So, which bootloader are you using? If grub, please post the lines from /etc/fstab relating to your partitions for win and Linux, as well as /boot/grub/menu.lst (or grub.conf if that's what your installation uses).
Code:
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>    <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda4       /               ext3    defaults,errors=remount-ro 0       1
/dev/hda1       /media/hda1     ntfs    defaults        0       0
/dev/hda5       /media/hda5     ntfs    defaults        0       0
/dev/hda3       none            swap    sw              0       0
/dev/hdc        /media/cdrom0   udf,iso9660 user,noauto     0       0
here is my /boot/grub/menu.lst

Code:
title		Ubuntu, kernel 2.6.12-9-386 
root		(hd0,3)
kernel		/boot/vmlinuz-2.6.12-9-386 root=/dev/hda4 ro quiet splash
initrd		/boot/initrd.img-2.6.12-9-386
savedefault
boot

title		Ubuntu, kernel 2.6.12-9-386 (recovery mode)
root		(hd0,3)
kernel		/boot/vmlinuz-2.6.12-9-386 root=/dev/hda4 ro single
initrd		/boot/initrd.img-2.6.12-9-386
boot

title		Ubuntu, memtest86+
root		(hd0,3)
kernel		/boot/memtest86+.bin  
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title		Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title		Windows NT/2000/XP (loader)
root		(hd0,0)
savedefault
makeactive
chainloader
Also, just for kicks, I am also posting my BOOT.INI just in case that could help...

Code:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect
Quote:
You could also edit the menu.lst entry for the server to look like this:
title Server (or whatever you call it)
rootnoverify (hd0,1)
map (hd0,0) (hd0,1)
map (hd0,1) (hd0,0)
makeactive
chainloader +1

Assuming the server is in the second partition of the drive, this should remap the partitions for win server to think it's on the first partition. Then grub would hand the boot process over to the win bootloader.
I tried this last method, and either i A)didn't enter it correctly or B)it isn't correct, because it didn't work (in fact, I had to go back and do a "fixmbr" in Windows and a fresh install of Kubuntu.

Also, I was reading on another post, is it correct that I could copy the /boot/vmlinuz-2.6.12-9-386 file to my C: drive and enter it into BOOT.INI and get it to work that way? As effective? Harder? Just curious.

Thanks for the advice so far, looking foward to your (or anyone else's) forthcoming advice.
 
Old 02-10-2006, 03:07 AM   #4
BinJajer
Member
 
Registered: Sep 2005
Location: Warsaw, Poland
Distribution: Slackware 10.2, Caldera OpenLinux 3.1, Corel Linux (Thanks xhi!), Debian GNU/HURD etc...
Posts: 296
Blog Entries: 1

Rep: Reputation: 30
Ho hum. Fix the MBR and get LOADLIN.exe.It's a windows executable for loading linux with the standard windows bootloader. It's by far the safest way to boot winblows. Since I have no windoes on my box, I can't say how efective this is.
 
Old 02-10-2006, 05:37 AM   #5
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
bigrigdriver's suggestion is not relevant in this case because the 3 OS are in the same drive. Thus re-map (hd1) and (hd0) has no meaning when there isn't a (hd1) in the PC.

I doubt if BinJaer's idea of using Loadin works at all with two NT versions of Windows while ignoring the following facts.

(1) Multiple Windows in the same drive can cause booting problem because only one primary partition can be made acive. Thus Win2003 must be booted by XP's NTldr if it has "NOT" been setup to boot up independent to a "C" drive.

(2) If XP has been booted successfully from (hd0,0) then this confirms it is in hda1. The only remaining NTFS partition is in hda5 which is the first logical partition. I am not sure if Win2003 is happy to be booted from anything other than a primary partition. Special hacking to Windows' MBR is needed to get a Windows boot from a logical partition. The problem could be with hda2 being an extended partition.

To me the hard disk has not been correctly partitioned to suit the 3 systems. After xp took up hda1 the owner installed Win2003 in a logical partition and so hda2 became the extended partition. The Linux was then installed into the remaining primary hda3 and hda4.

In installing the second Windows XP should have been hidden and so Win2003 can be installed independently into its own "C" drive in a primary partition. The Linux, with either Lilo or Grub, can then be installed in logical partitions and able to boot the two Windows by hiding one and unhiding+makeactive the other.

Using boot.ini would here be using Linux to dual-boot XP and Linux and then in XP the NTldr dual-boots XP and Win2003. This is a workable solution but I haven't seen one done with a MS system installed in a logical partition using the standard MS features. It is possible the scheme could work but that is a NTLDR problem and has nothing to do with Linux.

The 100+ systems link in my signature has Grub managing 3 Dos and 3 Windows (including XP and WIn2k) and therefore I know it work satisfactorily if installed independently. The XP's NTldr in my link actually boots its maximum capacity of 10 systems but they are Linux and not fellow MS systems.

Last edited by saikee; 02-10-2006 at 05:49 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem after boot in Kubuntu Breezy zoltrix Ubuntu 1 11-22-2005 11:02 PM
Problem connecting SAMBA to Windows 2003 Server Micro420 Linux - Networking 5 11-08-2005 04:53 PM
Install Kubuntu on computer with Windows Server 2003 DARabkin Linux - Software 3 05-06-2005 11:14 AM
Windows 2003 server & Fedora / GRUB wont boot win UrbanDEV Linux - Newbie 6 04-28-2004 10:34 AM
Setting up Windows 2003 Server and Redhat 8.0 Dual boot EVO VIII Chris Linux - Software 5 01-17-2004 08:04 PM


All times are GMT -5. The time now is 01:00 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration