On Sun, Nov 20, 2016 at 1:15 PM, peterlesterhuis@xxxxxxxxxx <peterlesterhuis@xxxxxxxxxx> wrote: > Hi, > After a Windows update my (dual boot) system won't boot into fedora anymore. > Somehow the grub bootloader doesn' t start. > > After booting this is what I see: > > Minimal Bash-like line editing is supported. For the first word TAB lists > possible command completions. Anywhere else TAB lists possible device or > file completions. > > grub>_ > > When I issue the command "exit" the Windows bootloader pops up. > > I googled on this subject, but found many completely different answers. > I would appreciate any suggestion. How can I recover my system? This suggests it's UEFI firmware, because exit causes the firmware to fallback to the next item in the boot order. But why does the firmware find grubx64.efi but not grub.cfg which is in the same path, just because Windows did an update? Kinda strange. For BIOS, I'd expect exit to fail because there's no fallback. Possibly the easiest way to handle this is with any F23-F25 netinstaller, and use the rescue boot option found in the troubleshooting submenu (of GRUB if in fact I'm correct and this computer has UEFI firmware; if I'm wrong, it'll have a syslinux/isolinux boot menu). The rescue option is supposed to find and assemble a Fedora installation per fstab, at /mnt/sysimage. Once it does that: # chroot /mnt/sysimage # ls -l /boot/efi/EFI/fedora Is there a grub.cfg? If so maybe # cat /boot/efi/EFI/fedora/grub.cfg | fpaste Or possibly we have a legacy linux on this computer, so maybe this is better # tree -L 3 /boot/efi/ | fpaste # efibootmgr -v | fpaste And just for grins # mv /boot/efi/EFI/fedora/grub.cfg /boot/efi/EFI/fedora/grub.cfg.old # grub2-mkconfig /boot/efi/EFI/fedora/grub.cfg # exit # reboot -f -- Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
