Bug 750853

Summary:	protective MBR isn't marked bootable, system refuses to boot
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	anaconda-maint-list, jonathan, rvokal, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-03 22:40:59 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 Bill Nottingham 2011-11-02 14:55:14 UTC

Description of problem:

I did a live install off of a desktop image from last week. (Don't have the specific date)

I did custom partitioning of a blank drive:
- 2MB bios boot
- 25GB / - ext4
- 500MB swap
- 200+GB (the rest) /srv - btrfs

It used GPT partitioning. My machine boots with BIOS, not EFI.

The protective MBR did not have the bootable flag set. Because of this, the system failed to boot, with "No bootable device found". I went into the live medium, set the flag, and now the system boots.

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

anaconda-16.22-1.fc16, in a live image from sometime last week

How reproducible:

Happened once, have not tried to reproduce yet.

Comment 1 Bill Nottingham 2012-02-03 22:40:59 UTC


*** This bug has been marked as a duplicate of bug 754850 ***