Description of problem: Install fedora rawhide 11.10.2012 on Macbook air mid 2012 (5.2). Choose automatic disk partitioning. Version-Release number of selected component: anaconda-18.14-1.fc18.x86_64 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8 kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.14 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1617, in add_efi_boot_target : raise BootLoaderError("failed to set new efi boot target") : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1622, in install : self.add_efi_boot_target() : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1652, in install : super(MacEFIGRUB, self).install() : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1638, in write : self.install() : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2205, in writeBootLoader : storage.bootloader.write() : File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 122, in doInstall : writeBootLoader(storage, payload, instClass) : File "/usr/lib64/python2.7/threading.py", line 504, in run : self.__target(*self.__args, **self.__kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 87, in run : threading.Thread.run(self, *args, **kwargs) :BootLoaderError: failed to set new efi boot target
Created attachment 626498 [details] File: anaconda-tb
Created attachment 626499 [details] File: environ
Created attachment 626500 [details] File: type
Created attachment 626501 [details] File: storage.log
Created attachment 626502 [details] File: version
Created attachment 626503 [details] File: program.log
Created attachment 626504 [details] File: product
Created attachment 626505 [details] File: anaconda.log
Created attachment 626506 [details] File: hashmarkername
Created attachment 626507 [details] File: packaging.log
Created attachment 626508 [details] File: cmdline_file
Created attachment 626509 [details] File: release
Created attachment 626510 [details] File: messages
Created attachment 626511 [details] File: other involved packages
Tried installing F18 Beta RC1 using default partitioning with LVM on my MacBook Pro 9,1 Package: anaconda-18.29.2-1.fc18.x86_64 OS Release: Fedora release 18
So, what is your result?
Sorry, please ignore the comment.
It didn't work - ie. after rebooting and holding down alt / option no Fedora partition was recognised - I then tried re-installing using the same options but got a slightly different bug - https://bugzilla.redhat.com/show_bug.cgi?id=880143 - so instead of failing to set new EFI boot target, this time it failed to remove the old one - so far I haven't yet rebooted (am writing this from within the live environment still) but will see if it is bootable this time....
Nope that also failed - as noted on bug #880143 am going to try a non LVM install to see if that works any better.
So this is probably similar to bug #873629 - basically there is some invalid looking entry(s) in the EFI boot manager table so efibootmgr bails with an error - any ideas how to clean these entries up?
Since this works fine in F17, I think we just need to find the regression.
I think the problem is that the more recent kernels are stricter about what is considered an invalid variable and so they disallow things they were previously allowed in F17 http://lkml.indiana.edu/hypermail/linux/kernel/1205.0/01460.html The real question is whether it's detecting false positives or not, ie. Perhaps the entries are valid but the kernel now thinks they are invalid.
After more investigation it seems this is probably a dupe of bug #873629 since it looks like the problem is not in anaconda but in either efibootmgr / kernel.
A new efibootmgr that doesn't crash would prevent this issue, but it would be nice if anaconda also was more resilient. A failing efibootmgr is not fatally fatal. It is usually possible to boot the system anyway ... but it become much harder when the installer crashes before creating grub.cfg. A failing efibootmgr invocation should IMO only cause a heavy warning.
Error encountered whilst trying to install Fedora 18 Beta (x86_64) DVD. Error occurs whilst booting natively and EFI boot options from DVD, but also after booting DVD via rEFIT Package: anaconda-18.29.2 OS Release: Fedora release 18-Beta