Bug 1404467

Summary:	updating to grub2-2.02-0.38 yield unbootable UEFI system for some configurations; grub2-efi
Product:	[Fedora] Fedora	Reporter:	Robert <redhat-bz>
Component:	grub2	Assignee:	Peter Jones <pjones>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	24	CC:	lkundrak, martineau, pjones
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-08 19:26:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Robert 2016-12-13 22:22:28 UTC

Description of problem:

A routine upgrade from grub2-2.02-0.34 to grub2-2.02-0.38 has caused by system to be unbootable. More specifically, I find that it waits at the grub prompt, unable to find it's configuration file.

While in this state, if I supply the command "configfile (hd1,gpt5)/grub2/grub.cfg", the machine will boot as before (to the less expect reader, you will have different values for hdX & gptX for this work around).

While in this state, I tried to 'dnf reinstall grub2-efi' (as such I would expect to solve the normal "can't find the config file" state), but to no avail.

Running this command (which effectively back-steps to v0.34) temporarily restores boot-ability:

sudo dnf --disablerepo=updates distro-sync grub\*

My primary concern is that a simple oversight (like a change in the grub config file location) might yield people's computers unusable, that they would not be able to work around a grub prompt.

Version-Release number of selected component (if applicable):
grub2 x86_64 1:2.02-0.38.fc24 updates 4.1 M
grub2-efi x86_64 1:2.02-0.38.fc24 updates 825 k
grub2-efi-modules x86_64 1:2.02-0.38.fc24 updates 3.6 M
grub2-tools x86_64 1:2.02-0.38.fc24 updates 7.9 M

How reproducible:
Seemingly 100% on my machine, don't know how wide an effect this is at large.

Steps to Reproduce:
1. (from some assumedly special, yet working configuration)
2. dnf update
3. reboot

Actual results:
The system halts at the grub prompt (assumedly, not able to find it's configuration file).

Expected results:
A routine update should not render the computer unbootable, it should boot as before.

Additional info:
I boot off of a mdraid & bcache device.

Comment 1 Mat Martineau 2016-12-20 19:33:47 UTC

I observed this behavior on a fresh install of Fedora 25, using UEFI boot on x86_64.

1. Install Fedora 25 from the .iso
2. Boot the newly installed OS
3. Install updates (dnf update; dnf upgrade), which includes grub2 packages and a new kernel
4. Reboot
5. System boots to the "Shim UEFI key management" screen, then can't find a boot device


To work around this, I had to install the grub2 updates separately:

1. Install Fedora 25 from the .iso
2. Boot the newly installed OS
3. Install only grub2 updates (dnf update; dnf upgrade grub*)
4. Reboot
5. Install the remaining updates
6. Reboot
7. All is well

Comment 2 Fedora End Of Life 2017-07-26 00:05:00 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-08-08 19:26:41 UTC

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.