Bug 207208 – Installing FC6test3 corrupted Windows XP Pro's bootloader?

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 207208 - Installing FC6test3 corrupted Windows XP Pro's bootloader?

Summary:	Installing FC6test3 corrupted Windows XP Pro's bootloader?

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	grub (Show other bugs)
Sub Component:
Version:	6
Hardware:	All Linux

Priority	medium Severity urgent
Target Milestone:	---
Target Release:	---
Assigned To:	Peter Jones
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2006-09-19 17:55 EDT by Luke Hutchison
Modified:	2007-11-30 17:11 EST (History)
CC List:	0 users

See Also:
Fixed In Version:	fc6
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-11-02 00:21:17 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Luke Hutchison 2006-09-19 17:55:55 EDT

I just installed FC6test3 on a laptop that already dual-booted between Linux and
WinXP Pro.  I chose to overwrite the old Fedora install rather than update.  Now
I can't boot into WinXP.  I see two or three normal lines of grub output and
then a jumble of 10 or so high-bit-set characters.  The computer beeps and then
sits there.

I think I've seen this before a long time ago on Fedora, but I don't remember
how I fixed it.  What exactly got corrupted here?

Comment 1 Luke Hutchison 2006-10-09 17:29:51 EDT

I tried the Windows XP Recovery Console, and neither "fixboot" nor "fixmbr" was
able to fix the problem.

Comment 2 Luke Hutchison 2006-11-02 00:21:17 EST

I ended up re-installing XP and then putting FC6 final on the laptop.  This time
the MBR didn't get messed up, so I'm closing the bug.  Thanks.

Note You need to log in before you can comment on or make changes to this bug.