Re: F28 server boots to the grub prompt even after dnf update and grub2-mkconfig

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm using UEFI.

On Tue, Oct 30, 2018 at 2:43 PM stan <stanl-fedorauser@xxxxxxxxxxx> wrote:
On Tue, 30 Oct 2018 11:28:36 -0600
linux guy <linuxguy123@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux