Bug 473160

Summary:	Installer replaced MBR with unconfigured grub
Product:	[Fedora] Fedora	Reporter:	Philip Sherman <p.sherman>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10	CC:	anaconda-maint-list
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-05-18 15:35:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Philip Sherman 2008-11-26 20:41:23 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.4) Gecko/2008111317 Ubuntu/8.04 (hardy) Firefox/3.0.4

Installed Fedora 10 on IBM T40 laptop using custom configuration. /boot on /dev/sda2, root (/) on existing LVM drive. Specified NOT to install a boot loader. At end of installation, MBR contained an unconfigured grub which prohibited booting the machine. 

Problem fixed by restoring the original (pre Fedora 10) MBR. Existing grub.conf at /boot/grub (sda2) modified to include new Fedora 10 installation which booted ok.

Reproducible: Didn't try

Steps to Reproduce:
1.
2.
3.

Comment 1 Chris Lumens 2008-12-02 17:59:19 UTC

Please attach /var/log/anaconda.log and /var/log/anaconda.syslog to this bug report.  Thanks.

Comment 2 Philip Sherman 2008-12-04 19:47:33 UTC

Logs presently unavailable. I'll have to repeat the install to recreate them. It will be 5-7 days until I can do this.

Comment 3 Chris Lumens 2009-05-18 15:35:25 UTC

If you're able to reproduce this bug with F11, please reopen with the log files and we'll be able to work on debugging this one.  Major amounts of work have happened regarding partitioning and bootloader installation, so it's probably this bug is fixed.  Thanks.