Bug 769084 - preupgrade to F16 overwrites mbr when fedora was never in control of the mbr.
Summary: preupgrade to F16 overwrites mbr when fedora was never in control of the mbr.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-19 21:24 UTC by Kyle
Modified: 2012-07-19 20:46 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-19 20:46:36 UTC
Type: ---

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

Description Kyle 2011-12-19 21:24:09 UTC 
Description of problem: Fedora-grub was originally installed to a partition, leaving the mbr untouched. Previous upgrades to fedora only upgraded  (fedora)/boot/grub/, allowing the mbr to be maintained by the admin. With the upgrade from F14 to F16, grub2 was installed to the mbr, requiring a rewrite of the mbr to restore normal functionality.

As a result, when fedora is selected as the operating system to boot, the only option is the preupgrade to verne, or other (windows).

Version-Release number of selected component (if applicable): F14(grub legacy) > F16(grub2)



  
Actual results: grub2 installed to mbr.


Expected results: Fedora should operate within it's originally installed domain, in this case grub2 should have been installed to the partition boot record.
Comment 1 Mads Kiilerich 2012-04-16 22:48:35 UTC 
Anaconda told grub2 what to do.

I am sure anaconda asked and gave you the option of controlling where and if a new boot loader should be installed. It is possible that the default could have been chosen in a smarter way - I don't know.
Comment 2 Jesse Keating 2012-07-19 20:46:36 UTC 
Upgrades present the user a choice of what to do with the boot loader.  We don't do anything automatically.
Note You need to log in before you can comment on or make changes to this bug.