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
Do we know what might be broken with the creating the UEFI boot images? I gather we could extra compose logs if needed?
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.
where are we on this? it's the last unmodified blocker now, afaict. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
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.
anaconda-13.41-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.41-1.fc13
This fix is in and has been confirmed.