On Mar 17, 2014, at 2:13 PM, pgaltieri . <pgalti...@gmail.com> wrote:

> On Mon, Mar 17, 2014 at 12:56 PM, Chris Murphy <li...@colorremedies.com> 
> wrote:
> 
> On Mar 17, 2014, at 1:37 PM, "pgaltieri ." <pgalti...@gmail.com> wrote:
> 
> > Here's the output
> >
> > BootCurrent: 0015
> > Timeout: 0 seconds
> > BootOrder: 
> > 0000,0001,0016,0013,0014,0015,0012,0010,0011,0019,001A,001B,0017,0018
> > Boot0000* fedora    
> > HD(1,800,fa000,a37591b8-de99-44c3-9eb8-e7de6f28d62d)File(\EFI\fedora\grubx64.efi)
> 
> 
> Chris,
>   sorry about the second command.  Here's the output:
> 
> 17:43:20,191 INFO program: Running... efibootmgr
> 17:43:20,519 INFO program: Running… efibootmgr -c -w -L Fedora -d /dev/sda -p 
> 1 -l \EFI\fedora\shim.efi

OK try this from the rescue DVD, 

chroot /mnt/sysimage
efibootmgr -b 0000 -B
efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \\EFI\\fedora\\shim.efi
exit
reboot

That should first delete the bogus 0000 entry, and then add the prior one that 
points to shim.efi, and then you should be able to boot. And then get on with 
the real problem which is being dropped at emergency.target.


Chris Murphy
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Reply via email to