Bug 1678718

Summary:	Grub shows an error message when booting standard kernel in Fedora Rawhide (soon 30).
Product:	[Fedora] Fedora	Reporter:	Lukas Ruzicka <lruzicka>
Component:	grub2	Assignee:	Peter Jones <pjones>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	30	CC:	fmartine, lkundrak, pjones, sumitkbhardwaj
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-15 09:53:52 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:
Embargoed:

Description Lukas Ruzicka 2019-02-19 13:11:34 UTC

Description of problem:

When Grub boots the kernel, it shows an error message:

Error: ../../grub-core/fs/fshelp.c:257:file '/loader/entries/' not found

After a second (or so), the message disappears and the system starts normally. However, such error message is confusing for the users, because it looks important.

I talked to Jan Hlaváč and he thinks that the reason why the error message was displayed is because my setup does not use a standalone /boot partition.

[root@f30-modular test]# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sr0     11:0    1  629M  0 rom  /run/media/test/Fedora-WS-dvd-x86_64-rawh
vda    252:0    0   12G  0 disk 
└─vda1 252:1    0   12G  0 part /

Version-Release number of selected component (if applicable):

grub2-common-2.02-70.fc30.noarch

How reproducible:

Always

Steps to Reproduce:
1. Make a disk layout using only one, root, partition.
2. Install Fedora Rawhide (20190217)
3. Boot.

Actual results:

Error message is shown.

Expected results:

No error message should be visible if it does not affect the boot process. Such message should go into the logs.

Comment 1 Sumit Bhardwaj 2019-05-07 12:37:53 UTC

+1. I am also getting this on a fully updated Fedora 30 Workstation x86_64 that has been upgraded from Fedora 29 Workstation.

There are no after-effects of this error, system boots properly.

Comment 2 Javier Martinez Canillas 2019-05-15 09:53:52 UTC


*** This bug has been marked as a duplicate of bug 1699761 ***