Created attachment 572397 [details] anaconda traceback and debug info Description of problem: On a box that already has an existing UEFI grub2 boot of Fedora 17, then fresh install of Fedora-17-Beta-RC1-x86_64-DVD onto another existing [empty] partition crashes, and makes the box unbootable. Version-Release number of selected component (if applicable): anaconda-17.14 How reproducible: haven't tried Steps to Reproduce: 1. Fresh install Fedora-17-Beta-RC1-x86_64-DVD onto an existing empty partition on a box which already has another Fedora 17 system. 2. 3. Actual results: anaconda 17.14 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1514, in add_efi_boot_target boot_efi = self.storage.mountpoints["/boot/efi"] File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1535, in install self.add_efi_boot_target() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1551, in write self.install() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2337, in writeBootloader anaconda.bootloader.write() File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 383, in dispatch self.dir = self.steps[self.step].target(self.anaconda) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 247, in go_forward self.dispatch() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1201, in nextClicked self.anaconda.dispatch.go_forward() File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback self.intf.icw.nextClicked() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1221, in handleRenderCallback self.currentWindow.renderCallback() KeyError: '/boot/efi' and attempting to re-boot the box hangs without bringing up grub2. Expected results: success: box with two bootable systems (each on own partition) Additional info:
Created attachment 572398 [details] storage.log
Created attachment 572399 [details] anaconda.log
Created attachment 572400 [details] program.log
Created attachment 572401 [details] syslog
If reproducible, then I suggest that either this bug blocks F17 Beta, or the Release Notes carries a big warning about data destruction.
What kind of partition layout did you select? Did you choose manual partitioning or one of the automatic options? If automatic, which one? If manual, what layout did you go with? Thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Custom layout, choose existing 15GiB partition as root (/), no other partitions chosen for processing by anaconda. [The .log files should confirm this?] The [one only] drive has a GPT partition table, and the layout is approximately [from my memory; current damaged state hinders access]: partition 1 200MB FAT[16 ?] EFI System Partition partition 2 60GB FAT32 [empty; space for that other OS] partition 3 1GB swap partition 4 15GB ext4 old Fedora 17 partition 5 15GB ext4 new Fedora 17 followed by about 400GB of unallocated space. There is some unallocated space, usually small, between some of the partitions due to alignment, room for expansion, etc. The new partition 5 was created by gparted running under the old Fedora 17. I pre-allocate partitions (and then use the installer to format them only) because in years gone by this was a convenient way to get exact size and alignment.
You need an EFI system partition to have a valid EFI install. A single / partition is not a valid layout for an EFI install. I think we already have a bug for adjusting manual partitioning to enforce this, somewhere... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
The fact that anaconda doesn't create a new EFI bootloader entry for multiple Fedora EFI installs, but instead overwrites the previous one, is https://bugzilla.redhat.com/show_bug.cgi?id=759303 . You hit a combination of #748209 and #759303, I believe. *** This bug has been marked as a duplicate of bug 748209 ***