LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   Please help! Windows won't boot from grub. (https://www.linuxquestions.org/questions/fedora-35/please-help-windows-wont-boot-from-grub-183558/)

dhrivnak 05-19-2004 11:48 PM

Please help! Windows won't boot from grub.
 
I just installed FC2 on my 'big' computer. I already had WinXP on the primary drive (hda). I put Fedora on hdb. During the install, I chose to use grub, and it saw windows and stuff, so I thought it would be ok. Got Fedora all configured, and decided to try Windoze to make sure it still works. No luck! When I choose it in grub, it simply goes to a black screen and displays the information from /etc/grub.conf that is under the "windows" data. Here are 2 grub.conf files I tried (I've been doing a lot of googling to no avail).

-----after the install-------
# 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 (hd1,0)
# kernel /vmlinuz-version ro root=/dev/hdb2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd1,0)/grub/splash.xpm.gz
title Fedora Core 2
root (hd1,0)
kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.5-1.358.img
title Windows XP
rootnoverify (hd0,0)
chainloader +1


------after googling-------------(same errors)
default=0
timeout=10
splashimage=(hd1,0)/grub/splash.xpm.gz
title Fedora Core 2
root (hd1,0)
kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.5-1.358.img
title Windows XP
unhide (hd0,0)
hide (hd0,1)
rootnoverify (hd0,0)
chainloader +1
makeactive
boot


Any help would be GREATLY appreciated! My email and music and stuff is still on the Windows drive, and it is NTFS, so I can't access it from Linux....

Ed-MtnBiker 05-20-2004 12:53 AM

For your reading:
http://bugzilla.redhat.com/bugzilla/....cgi?id=115980

Follow all the links and references for a thorough reading.

wiraone 05-20-2004 01:48 AM

Exactly the same installer bug that I've experienced .. follow the instruction on how to recover it back .. or .. just do like what I did .. reformat everything and go back to FC1 :D

motub 05-20-2004 07:38 AM

Quote:

My email and music and stuff is still on the Windows drive, and it is NTFS, so I can't access it from Linux....
No Fedora expert here, but is there some reason that you can't mount the partition with at least your music so that you could play it? Mail is, of course, a slightly different story, but you would be able to import it into a Linux client, or (if you use Mozilla or Thunderbird under both OSes), you could move the mail folder to a small FAT32 area if you have one available, and then it would be available to Linux and to Windows as well when you get back into it.

Does Fedora 2 not include NTFS read support? I thought that was half of the point of the thing, but I could be mistaken, as I don't follow Fedora closely.

dhrivnak 05-20-2004 12:12 PM

THANKS!
 
Thank you to everyone who replied! I ended up changing the HD access mode to LBA, as mentioned in one of the bugzilla reports, and it worked!

Thanks again - you guys are what makes Linux as great as it is!

Bambino 05-20-2004 01:22 PM

Hey,

Do you mind posting EXACLY what you did to make it work?
We are a lot of users having the same problem, and still havent been able to solve it...

Thanks in advance :)
Bambino

Ed-MtnBiker 05-20-2004 01:31 PM

I've been reading through bugzilla, and following some of the other threads on this bug. The best "workaround" is to change your BIOS setting from either "auto" or "C/H/S" to "LBA" for the hard drive. Apparently Kernel 2.6 prefers to address the world with LBA and *something* corrupts the partition table in the process. I'd say if you can't change that setting in your BIOS and can't afford to lose your XP partition, then hold off until more is understood about this problem.

Many people are quoting a workaround that says, "boot from your XP cd and fixmbr". Many other people are also saying this doesn't repair the partition and allow booting.

I'm actually *very* disappointed that Fedora was released with this bug. It sure takes the "community" out of the "community-oriented" distro. I'm all for it being a testbed for RHEL, but there are a lot of things that are annoying (mp3 support, usb pen drive automount, disabled NTFS read support, my Olympus Stylus 300 STILL not supported, SELinux, this bug). I've only used RH distros since 6.2, but now I'm thinking about trying out Gentoo and maybe a few others. I've read the threads on the RH devel mailing list, and I was really disappointed at the tone and nature of the responses.

I'm happy to deal with bugs that have workarounds, but this is *serious*. It doesn't happen on all boards & systems--and be thankful if you have a system that just works.

I'm sorry for my rant, but this is something so serious that I can't give my buddes a copy of the FC2 CDs, and say "go for it, you won't mess anything up."

dhrivnak 05-20-2004 05:19 PM

This is what I did:

- boot computer
- go into BIOS
- go to the section that shows the HDs
- go into the menu for the HD
- change 'access mode' from 'auto' to 'LBA'

Of course, this may be a bit different depending on your BIOS...

Hope that helps!

wiraone 05-20-2004 05:59 PM

Quote:

Originally posted by Ed-MtnBiker
I've been reading through bugzilla, and following some of the other threads on this bug. The best "workaround" is to change your BIOS setting from either "auto" or "C/H/S" to "LBA" for the hard drive. Apparently Kernel 2.6 prefers to address the world with LBA and *something* corrupts the partition table in the process. I'd say if you can't change that setting in your BIOS and can't afford to lose your XP partition, then hold off until more is understood about this problem.

I don't think it is the kernel .. but most probably more on FC2/Grub specific .. I don't have problem running kernel 2.6.6 on FC1 .. definitley it wasn't the kernel that 'corrupts' the partition table ..

Ed-MtnBiker 05-20-2004 06:07 PM

Quote:

Originally posted by wiraone
I don't think it is the kernel .. but most probably more on FC2/Grub specific .. I don't have problem running kernel 2.6.6 on FC1 .. definitley it wasn't the kernel that 'corrupts' the partition table ..
You're definitely right. Apparently this issue is also showing up in Mandrake 10, and one of the other big distros. Likely suspects seem to be GRUB and parted, but I haven't read anything where someone quotes some code and says, "THIS is the problem!"

I just hope it gets resolved soon!

windeath 05-20-2004 06:42 PM

This is unbelievable!!!! I have just had to reformat my entire 80Gb and reinstall WinXP. I have been through http://bugzilla.redhat.com/bugzilla...g.cgi?id=115980 and am still dumb founded. I am lucky in what was on my HDD wasn't all that important (mind you I think my wife is about ready to divorce me) but this is just bulls&*t. FC1 was an absolute dream to install I have had NO issue at all with any part of FC1 but I'm looking at FC2 with dagger eyes at this stage.

I'm bloody furious with what I'm having to do just to get an OS installed. Please don't get me wrong I can't stand the clunkiness of XP, but by God it's nowhere near as frustrating just to get on the hard drive and booting.

Now that thats out of the way, I'm going to try the LBA change tonight and see if that works.....if not another post will be forth coming with more expletives.

rberry88 05-20-2004 07:01 PM

You guys do know that you could just boot with your WinXP installation disc and instead of installing Windows again just go to recovery and type in "fix boot" without the quotes. This will correct how Grub passes off to Windows at boot time. If you really screw things up, you can also do "fix mbr" from the recovery console and then re-install Grub and configure to your liking.

I don't see it as a problem with FC2, pretty much all distros have this problem if something quirky happens when Grub attempts to pass of booting to Windows. Its more to do with Windows wanting to be in the mbr and not wanting to share with Grub.

Just my 2 cents.

rberry88

Ed-MtnBiker 05-20-2004 07:39 PM

Quote:

Originally posted by rberry88
You guys do know that you could just boot with your WinXP installation disc and instead of installing Windows again just go to recovery and type in "fix boot" without the quotes. This will correct how Grub passes off to Windows at boot time. If you really screw things up, you can also do "fix mbr" from the recovery console and then re-install Grub and configure to your liking.

The Bugzilla reports seem to say that that XP cannot repair itself in this situation, such as the report below:
http://bugzilla.redhat.com/bugzilla/...i?id=115980#c9

windeath 05-20-2004 07:52 PM

Tried that rberry88...no effect.

rberry88 05-21-2004 12:30 AM

Okay, by reading the bugzilla posting from the link you provided it seems it pretty much only affects the users that are setting up Linux partitions when installing FC2 (or FC1) for that matter.

If you were previously dual booting with WinXP and FC1 and you are doing a upgrade then I would do just that, upgrade. Don't re-partition your drive(s) on an upgrade because that is what, it seems, is causing the problem -- if you want to re-partition your drive then you should first back up (onto disc) the info that you want carried over and do a fresh install and partition accordingly.

If you did a normal "upgrade" (i.e. no repartition, just update grub etc) then there would be no reason for the geometry readings on the partitions/drives to change which seems to be the common denominator of this problem. If you read the last few entries in that bugzilla link then you will see that the problem has been minimized to these instance (upgrade w/ re-partition) otherwise the simple "pop in the WinXP install (recovery) CD and fix boot or fix mbr" has worked fine for the others that have encountered this problem with a "normal upgrade".

rberry88


All times are GMT -5. The time now is 11:58 PM.