I have an up to date F28 server that boots to the grub prompt. This started after a failed dnf update. The computer will boot to an emergency mode command prompt if I set it up properly from the grub prompt. grub> set root=(lvm/fedora-root) grub> linuxefi (hd0,gpt2)/vmlinuz-0-rescue... grub> root=/dev/mapper/fedora-root grub>initrdefi (hd0,gpt2)/initramfs-0-rescue....img grub>boot I can get networking working #ls /sys/call/net <- find Ethernet device is enp3s0 # ifup enp3s0 # ping www.google.com Now update it # dnf update

Regenerate the grub2 config file # grub2-mkconfig Reboot # shutdown -r now It still boots to the grub prompt. Why does it boot to the grub prompt and what do I need to do to fix it ?

On Tue, 30 Oct 2018 11:28:36 -0600 linux guy <linuxguy123(a)gmail.com&gt; wrote: > I have an up to date F28 server that boots to the grub prompt. This > started after a failed dnf update. > > The computer will boot to an emergency mode command prompt if I set > it up properly from the grub prompt. > > grub> set root=(lvm/fedora-root) > grub> linuxefi (hd0,gpt2)/vmlinuz-0-rescue... > grub> root=/dev/mapper/fedora-root > grub>initrdefi (hd0,gpt2)/initramfs-0-rescue....img > grub>boot > > I can get networking working > #ls /sys/call/net <- find Ethernet device is enp3s0 > # ifup enp3s0 > # ping www.google.com > > Now update it > # dnf update Does dnf give any errors because of the interrupted update? > > Regenerate the grub2 config file > # grub2-mkconfig > > Reboot > # shutdown -r now > > It still boots to the grub prompt. > Why does it boot to the grub prompt and what do I need to do to fix > it ? Two things you should try. 1. If not already, remove rhgb and quiet from the kernel boot line so you can see the boot messages, and the final error that is throwing you into the grub prompt. 2. After getting the system up and before you reboot, look in the journal to see what is reported about the issue causing the drop to a grub prompt. journalctl -b will show the last boot. That you have to set the root manually suggests to me that the boot record isn't pointing to the right place. Correcting this is different for uefi and mbr, so you'll have to tell us which method you are using. I don't see how this could happen from an interrupted dnf update unless the disk was somehow corrupted, but it is what it is. Maybe you should try running a non destructive file system check to see that the file system is intact. If you have a rescue cd or usb, it is a lot easier to boot it and do these kinds of things from a separate fully functioning system. _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

On 11/26/18 7:56 PM, linux guy wrote: > It still boots to the grub prompt, even when I use -o /boot/grub2/grub.cfg That is still the wrong file. You need either /boot/efi/EFI/fedora/grub.cfg or /etc/grub2-efi.cfg which is a symlink to the first one. _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Interesting.  /boot/efi/EFI/fedora/grub.cfg didn't exist on my workstation.  But /etc/grub2-efi.cfg points to it !   /boot/efi existed, but it was empty.