Ask Your Question

Fedora 25 won't boot after update

asked 2017-05-30 23:00:46 -0500

OldFotoMan gravatar image

I'm running a Lenovo desktop, dual OP system with Win8 and Fedora. Fedora 24 (server edition) was originally installed, but the system automatically updated itself to Fedora 25 when doing suggested updates. Worked fine for several months, but the last time it suggested updates and I ran them, something malfunctioned and now it will not boot. If I use F12, I can go in and boot to Windows, but it will not boot to Fedora. All I get is a message that says:

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> _

No matter what I have tried, I cannot get past this screen to get it to do or run anything.

Any ideas or advice would certainly be extremely helpful and appreciated.

edit retag flag offensive close merge delete



same hard drive for both os, or separate drives? grub rescue is the prompt you are seeing, so the hard disk may have corruption issues. Here is a link, with detailed help, from a similar situation, i hope this helps

SteveEbey73701 gravatar imageSteveEbey73701 ( 2017-05-31 08:29:50 -0500 )edit

Same hard drive for both, separate partitions of course. One thing I forgot to mention though. For the past couple of weeks, which I think is about the time of my next to last update on Fedora, Fedora would no longer find, see, or read any of my Windows files or anything stored in Windows.

OldFotoMan gravatar imageOldFotoMan ( 2017-05-31 10:38:27 -0500 )edit

I am also having the same problem.

navdeep26 gravatar imagenavdeep26 ( 2017-06-13 11:31:37 -0500 )edit

1 Answer

Sort by » oldest newest most voted

answered 2017-05-31 10:33:18 -0500

cmurf gravatar image

There isn't enough information to help you fix this problem.

Create installation media for any Fedora product (any spin, netinstall, Workstation, KDE, doesn't matter). Boot it, and simply try to mount the boot volume. By default the boot volume is on its own plain partition, whereas if you did a custom setup it might be that /boot is just a directory on root in which case you need to mount root. I suggest mounting it to /mnt

If you have a network connection while booted with this installation media:

dmesg | fpaste

and post the URL here, I'd like to see what the kernel messages are. If you don't have a network connection:

dmesg > /mnt/root/dmesg.log

Now when you reboot your system you can

cat /root/dmesg.log | fpaste

and post the URL.

I suspect a particular bug related to updates and fast reboots where an updated grub.cfg is properly written but not fully committed to disk in a way that GRUB can find it. Just by mounting and umounting the volume fixes the problem (it flushes the journal to the file system).

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2017-05-30 23:00:46 -0500

Seen: 992 times

Last updated: May 31 '17