Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 589680 - UEFI boot images are not being created correctly.
Summary: UEFI boot images are not being created correctly.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F13Blocker, F13FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2010-05-06 17:07 UTC by Peter Jones
Modified: 2013-01-10 05:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-11 00:05:02 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Peter Jones 2010-05-06 17:07:18 UTC 
Description of problem: efiboot.img and boot.iso are being created with UEFI boot images that don't actually have any data in them:

sd 36:0:0:0: [sdb] 1957888 512-byte logical blocks: (1.00 GB/956 MiB)
sd 36:0:0:0: [sdb] Assuming drive cache: write through
 sdb: unknown partition table

Version-Release number of selected component (if applicable): anaconda-13.39-1
Comment 1 James Laska 2010-05-06 18:09:37 UTC 
Do we know what might be broken with the creating the UEFI boot images?  I gather we could extra compose logs if needed?
Comment 2 Peter Jones 2010-05-06 18:16:21 UTC 
Well, I'm doing composes here in my attempts to fix the problem; I think it's related to tools like dmsetup and parted switching to making /dev/mapper nodes via the udev rules instead of doing it themselves. Thus, since we're in a chroot, and not bind mounting /dev (as I've always recommended we do in the past, but hey, nobody listens), udev does it at the wrong place.
Comment 3 Adam Williamson 2010-05-07 02:25:07 UTC 
where are we on this? it's the last unmodified blocker now, afaict.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 4 Jesse Keating 2010-05-07 02:41:59 UTC 
There is a patch upstream that has been acked.  It just needs to be git am'd and cherry picked over to the F13 branch and then a new anaconda built.
Comment 5 Fedora Update System 2010-05-07 07:42:34 UTC 
anaconda-13.41-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/anaconda-13.41-1.fc13
Comment 6 Jesse Keating 2010-05-11 00:05:02 UTC 
This fix is in and has been confirmed.
Note You need to log in before you can comment on or make changes to this bug.