[Bug 1006304] BootLoaderError: failed to set new efi boot target

[Robert Moskowitz]

On 12/31/2013 08:00 PM, Chris Murphy wrote:
> On Dec 31, 2013, at 5:34 PM, Chris Murphy <lists at colorremedies.com> wrote:
>> Since you only have Fedora to boot, the simplest fix might be to delete all of the NVRAM entries, and hope that in a reboot or two, it does sufficient garbage collection that you can then try another installation.
> Confirmed. Sorta.
>
> The program.log info is buried in the anaconta-tb, so looking at that I see you have a bunch of NVRAM entries you probably don't need:
>
> 17:08:21,590 INFO program: BootOrder: 0005,0006,0007,0008,0009
> 17:08:21,590 INFO program: Boot0000  Setup
> 17:08:21,591 INFO program: Boot0001  Boot Menu
> 17:08:21,591 INFO program: Boot0002  Diagnostic Splash Screen
> 17:08:21,592 INFO program: Boot0003  Rescue and Recovery
> 17:08:21,593 INFO program: Boot0004  Startup Interrupt Menu
> 17:08:21,594 INFO program: Boot0005* USB CD
> 17:08:21,595 INFO program: Boot0006* USB FDD
> 17:08:21,596 INFO program: Boot0007* ATA HDD0
> 17:08:21,596 INFO program: Boot0008* USB HDD
> 17:08:21,597 INFO program: Boot0009* PCI LAN

Oh, lots more information.  I will try all of this tomorrow.  I really 
need to get busy in the honeydo patch now...  ;)
>
> Thing is, I can't tell you want you can get rid of. If you efibootmgr -v it will give their verbose listings and in theory you can replace them based on that information, should they need to be replaced. Better would be a firmware setup option to reset NVRAM but that seems rare outside of Apple hardware.
>
> Pick one that seems unlikely to be used ever again for deletion, after you issue and save the results from efibootmgr -v, and then use the form:
>
> efibootmgr -b 000x -B
>
> Where x is the entry you want to remove. That will delete that entry. Open question how many of these you need to delete to release enough space in NVRAM, one or two? And another question on how long it takes for the firmware to go garbage collection and actually make space available in NVRAM for a new entry.
>
> Next, try:
>
> efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \\EFI\\fedora\\shim.efi
>
> And see if you get an error; and you can also reissue efibootmgr -v to see if that entry is now in NVRAM to confirm. If there's no error, and if the entry is present in NVRAM, remove it with efibootmgr -b xxxx -B. Then try to install Fedora 20 again and hopefully this time it takes.
>
>
>
> Minor observation on your bug 1006304 entries: 1. for program.log you actually posted storage.log; 2. you set storage and program logs at least, to automatic rather than manually setting them to plain text. It's annoying that you have to explicitly tell BZ that what you're attaching is plain text, but you do. If you don't, then when people click on your attachments, they download instead of being viewable in the web browser.
>
>
>
> Chris Murphy