Bug 589680 - UEFI boot images are not being created correctly.
UEFI boot images are not being created correctly.
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
13
All Linux
low Severity medium
: ---
: ---
Assigned To: Peter Jones
Fedora Extras Quality Assurance
:
Depends On:
Blocks: F13Blocker/F13FinalBlocker
  Show dependency treegraph
 
Reported: 2010-05-06 13:07 EDT by Peter Jones
Modified: 2013-01-10 00:56 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-10 20:05:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter Jones 2010-05-06 13:07:18 EDT
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 14:09:37 EDT
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 14:16:21 EDT
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-06 22:25:07 EDT
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-06 22:41:59 EDT
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 03:42:34 EDT
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-10 20:05:02 EDT
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.