Grub not working with fedora / Vista dual boot

Thaidog · 01-25-2009, 01:43 PM

I did a fresh install of Fedora Core 10 32bit on my Caompaq Presario AMD 64 laptop which originally only had Vista ultimate 64bit.

When I go in to grub and choose windows I get a screen that says:

Windows failed to start...

file: \windows\system32\winload.exe

status: 0xc0000225

Info: The selected entry could not be loaded because the application is missing or corrupt.

Any ideas on how to fix this?

Gins · 01-25-2009, 02:23 PM

You should post the menu.lst file here.
Are you using GRUB or something else?
I know Windows has a bootloader too.

CJS · 01-25-2009, 03:35 PM

In order to get a clearer picture of your setup related to your booting problem, how about downloading the Boot Info Script to your desktop, and then do the following as root user, but replace <username> with your username:

Code:

bash /home/<username>/Desktop/boot_info_script*.sh

That will create a "RESULTS.txt" file in the same directory from where the script is run, namely your desktop; please copy/paste the contents of that file to your next post. That will help clarify your setup and hopefully what your problem might be.

Thaidog · 01-25-2009, 05:38 PM

Quote:

Originally Posted by CJS

In order to get a clearer picture of your setup related to your booting problem, how about downloading the Boot Info Script to your desktop, and then do the following as root user, but replace <username> with your username:

Code:

bash /home/<username>/Desktop/boot_info_script*.sh

That will create a "RESULTS.txt" file in the same directory from where the script is run, namely your desktop; please copy/paste the contents of that file to your next post. That will help clarify your setup and hopefully what your problem might be.

RESULTS.txt - http://www.tyler.mcadams.com/RESULTS.txt

also here is some more info:

Code:

[root@F500 ~]# cat /boot/grub/menu.lst
# 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,1)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,1)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.27.9-159.fc10.i686)
	root (hd0,1)
	kernel /vmlinuz-2.6.27.9-159.fc10.i686 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
	initrd /initrd-2.6.27.9-159.fc10.i686.img
title Fedora (2.6.27.5-117.fc10.i686)
	root (hd0,1)
	kernel /vmlinuz-2.6.27.5-117.fc10.i686 ro root=UUID=edb79d29-c9fa-4840-b822-01636366fe88 rhgb quiet
	initrd /initrd-2.6.27.5-117.fc10.i686.img
title Other
	rootnoverify (hd0,0)
	chainloader +1

Code:

[root@F500 ~]# fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xce5973cb

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        8406    67521163+   7  HPFS/NTFS
/dev/sda2   *        8407        8431      200812+  83  Linux
/dev/sda3            8432        9729    10426185   8e  Linux LVM

CJS · 01-25-2009, 05:52 PM

The drive you show with "fdisk -l" in your post does not appear to be the same one that the Boot Info Script reported; they both have different disk signatures, and your fdisk output shows sda1 as being an NTFS partition, whereas the script only shows two linux partitions. Did you run the script on exactly the same drive as what you show with fdisk?

If Vista is on sda1, then your current Grub entry should be fine. Since I don't know what your setup really looks like though since the script reports what looks like a different drive, I'm not sure if Vista is really on sda1. Can you run the script again with your Vista drive attached? Or is it an error with the script, did you have the Vista drive attached?