Bug 212863 - MBR installed incorrectly on upgrade
Summary: MBR installed incorrectly on upgrade
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: 6
Hardware: All Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-29 19:48 UTC by GeoffLeach
Modified: 2008-04-04 14:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-04 14:58:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
anaconda.log (195.60 KB, text/plain)
2006-10-30 20:20 UTC, GeoffLeach
no flags Details
anaconda.syslog (25.10 KB, text/plain)
2006-10-30 20:21 UTC, GeoffLeach
no flags Details
anaconda.xlog (46.51 KB, text/plain)
2006-10-30 20:21 UTC, GeoffLeach
no flags Details
device.map (82 bytes, text/plain)
2006-10-30 20:22 UTC, GeoffLeach
no flags Details

Description GeoffLeach 2006-10-29 19:48:05 UTC
Description of problem:upgrade installs grub on wrong MBR

Version-Release number of selected component (if applicable):0.97-13

How reproducible:always

Steps to Reproduce:
1.normal upgrade
Actual results: grub installed on MBR A

Expected results:grub installed on MBR C

Additional info: System has 4 disks. SCSI A and B, SATA C and D. FC5 install
shows disks in order ABCD, re-ordered to CDAB with MBR on C. FC6 upgrade was
perfect, except on reboot grub could not find conf file - presumably it was on
A. Suggest that upgrade state where MBR will be installed, and allow re-ordering
 of dirves (or just selection) as with install.

Comment 1 Jeremy Katz 2006-10-30 19:45:33 UTC
What is in /boot/grub/device.map and /var/log/anaconda*?

Comment 2 GeoffLeach 2006-10-30 20:20:34 UTC
Created attachment 139765 [details]

Comment 3 GeoffLeach 2006-10-30 20:21:20 UTC
Created attachment 139766 [details]

Comment 4 GeoffLeach 2006-10-30 20:21:57 UTC
Created attachment 139767 [details]

Comment 5 GeoffLeach 2006-10-30 20:22:45 UTC
Created attachment 139768 [details]

Comment 6 GeoffLeach 2006-10-30 20:27:59 UTC
FWIW, as this is _after_ install, after the failed upgrade. 

Why did I trash the upgrade?  One of the partitions on the second SATA drive
(which would be D in the above example) would not mount -- mount claimed that
the drive was busy, if I recall correctly.  There were also complaints about
that filesystem during boot. after the install, no problems were reported.

Comment 7 Bug Zapper 2008-04-04 04:15:19 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 8 GeoffLeach 2008-04-04 14:58:20 UTC
Not reproducable in F8

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