 |
 |
 |
 |
| Using Fedora General support for current versions. Ask questions about Fedora and it's software that do not belong in any other forum. |

3rd April 2007, 01:22 AM
|
 |
Registered User
|
|
Join Date: Dec 2004
Posts: 6

|
|
|
Fedora6/Win2K dual-boot problem
I have a dual-boot PC with FC6 & Win2K which has worked perfectly for a few weeks. Today I modified the grub.conf file so that Win2K would be the default OS selected. When I rebooted, I got the message "NTLDR.exe is missing, press any key to restart". I restored the grub.conf file to it's original state, but that didn't resolve the problem. Does anyone know if there's a way to fix this problem without having to do a complete reinstall of Windows? I'm a relative newbie to Linux, so please take that into consideration if describing a solution.
Thanks....
|

3rd April 2007, 01:28 AM
|
 |
Retired Community Manager
|
|
Join Date: Oct 2004
Location: The GTA, Ontario, Canada
Age: 54
Posts: 12,376

|
|
|
Hello:
Can you post the output of
cat /etc/grub.conf
and
fdisk -l
Seve
__________________
Registered Linux User: #384977
.................................................. ............
See the Links below for more Help and those much wanted extras ... :)
|

3rd April 2007, 01:38 AM
|
 |
Registered User
|
|
Join Date: Dec 2004
Posts: 6

|
|
|
Steve,
Below is the info you requested. One note: the grub.conf file on my system is in /boot/grub, not /etc. This was something the install did by default, I did not place it there. Thanks for your help.
Peter V.
# find / -type f -name 'grub.conf'
/boot/grub/grub.conf
# cat /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,6)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=15
splashimage=(hd0,6)/grub/splash.xpm.gz
#hiddenmenu
title Fedora Core (2.6.18-1.2798.fc6)
root (hd0,6)
kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.18-1.2798.fc6.img
title Windows 2000 Professional SP4
rootnoverify (hd0,1)
chainloader +1
#
# cls
# fdisk -l
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1277 9729 67898722+ f W95 Ext'd (LBA)
/dev/hda2 * 1 1276 10249438+ c W95 FAT32 (LBA)
/dev/hda5 1277 3826 20482843+ b W95 FAT32
/dev/hda6 5166 9729 36660298+ b W95 FAT32
/dev/hda7 3827 3839 104391 83 Linux
/dev/hda8 3840 5165 10651063+ 8e Linux LVM
Partition table entries are not in disk order
Disk /dev/hdc: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 * 2 14593 117210240 f W95 Ext'd (LBA)
/dev/hdc5 2 3826 30724281 b W95 FAT32
/dev/hdc6 3827 7651 30724281 b W95 FAT32
/dev/hdc7 7652 11475 30716248+ b W95 FAT32
/dev/hdc8 11476 14593 25045303+ b W95 FAT32
#
|

3rd April 2007, 02:51 AM
|
 |
Registered User
|
|
Join Date: Apr 2006
Location: Ohio, USA
Posts: 8,302

|
|
|
If your Win is on /dev/hda1, then the corrent grub name for it is (hd0,0).
Your rootnoverify line says (hd0,1).
|

3rd April 2007, 03:08 AM
|
 |
Registered User
|
|
Join Date: Dec 2004
Posts: 6

|
|
|
Close, but no cigar....
Steve,
I tried your suggestion and rebooted. At the grub menu, I selected Windows 2000, it then went to a black screen with the following text:
Booting Windows 2000
rootnotify(hd0,0)
chainloader +1
It is now hung there doing nothing. Any ideas?
|

3rd April 2007, 03:21 AM
|
|
Registered User
|
|
Join Date: Jan 2007
Location: New York City
Posts: 109

|
|
|
dont know if this is a typo, but it should be
rootnoverify(hd0,0)
not
rootnotify(hd0,0)
__________________
I am a figment of my own imagination.
Smolt Profile
|

3rd April 2007, 03:53 AM
|
 |
Registered User
|
|
Join Date: Dec 2004
Posts: 6

|
|
|
Unfortunately, it was a typo in the post, not in the grub.conf.
|

3rd April 2007, 04:09 AM
|
 |
Retired Community Manager
|
|
Join Date: Oct 2004
Location: The GTA, Ontario, Canada
Age: 54
Posts: 12,376

|
|
|
Hello:
If you still get a boot error, then you may have to repair the mbr of the windows disk and re-install grub.
You can do that with booting from the win disk and in the repair console when you come to the C:\
type
fixmbr
exit and reboot and see if windows boots okay. If it does, then you can re-install grub
boot from your FC install disc and type
linux rescue
follow along [do not require network] until the last prompt #
then type
chroot /mnt/sysimage
then type
fdisk -l
to confirm where everything is
then to install grub again on the mbr of /dev/hda [assuming that was original location ?]
grub-install --recheck /dev/hda
type exit when done and reboot and see how it goes.
Seve
__________________
Registered Linux User: #384977
.................................................. ............
See the Links below for more Help and those much wanted extras ... :)
|

3rd April 2007, 09:50 AM
|
 |
Registered User
|
|
Join Date: Dec 2004
Posts: 6

|
|
|
I followed your directions, but nothing's changed, I'm getting the same problem as before. Back to the drawing board. Thanks anyway....
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Current GMT-time: 03:11 (Saturday, 25-05-2013)
|
|
 |
 |
 |
 |
|
|