Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1698227 - Upgrade from f29 to 30, grub.cfg not configured correctly
Summary: Upgrade from f29 to 30, grub.cfg not configured correctly
Keywords:
Status: CLOSED DUPLICATE of bug 1652806
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 30
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-09 20:56 UTC by Denis
Modified: 2019-04-15 16:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-15 16:31:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
grub2-mkconfig output with set -x on /etc/grub.d/10_linux (51.14 KB, text/plain)
2019-04-09 20:56 UTC, Denis 		no flags Details
View All

Description Denis 2019-04-09 20:56:49 UTC 
Created attachment 1553942 [details]
grub2-mkconfig output with set -x on /etc/grub.d/10_linux

Description of problem:
Performed upgrade from f29.
After restart, upgrade to 30 finished.
Another restart to boot to 30 , finished with grub cli.

Booted livecd , mount boot filesystem of f30, 
on /boot/grub2/grub.cfg I don't see any linux entries.
While I used grub.cfg.rpmsave(from f29) and edit for new f30 kernel , 
I success to get grub prompts with all kernels.

I checked with  vm(kvm) with i386 architecture  on same hardware , get same problem with grub


Version-Release number of selected component (if applicable):
# rpm -qa |grep grub2
grub2-tools-efi-2.02-75.fc30.x86_64
grub2-pc-2.02-75.fc30.x86_64
grub2-tools-2.02-75.fc30.x86_64
grub2-common-2.02-75.fc30.noarch

# blkid 
/dev/sda1: UUID="6862CDCC62CD9F66" TYPE="ntfs" PARTUUID="8a4fa448-01"
/dev/sda2: UUID="73f7fb36-cae5-42a6-9e28-1453b2b5ba87" TYPE="ext4" PARTUUID="8a4fa448-02"
/dev/sda5: UUID="6f4b9d93-93d7-4d89-8026-792df097e8df" TYPE="ext4" PARTUUID="8a4fa448-05"
/dev/sda6: UUID="9d52362d-6861-4643-bda1-7fc0cc904fed" TYPE="swap" PARTUUID="8a4fa448-06"
/dev/sdb1: LABEL="data" UUID="50b89c82-5226-49ab-abc2-1f8f7b748f58" TYPE="xfs" PARTLABEL="data" PARTUUID="abb58879-745a-4c9d-b79e-992f5a0da949"
/dev/sdc1: LABEL="D" UUID="6A0499760499464B" TYPE="ntfs" PARTUUID="7a624086-01"
/dev/sdc2: UUID="6f3b5d13-3023-4951-906c-890a5c614e4e" TYPE="ext4" PARTUUID="7a624086-02"



How reproducible:
Upgrade from fedora 29 to 30

Steps to Reproduce:
1. Upgrade from f29 to 30
2. 
3.

Actual results:


Expected results:


Additional info:
Comment 1 Denis 2019-04-09 21:43:34 UTC 
Also while updating kernel, there is no new entry on grub
Comment 2 Denis 2019-04-09 21:59:02 UTC 
After some searching, found this page
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault

Change in /etc/default/grub
to
GRUB_ENABLE_BLSCFG=false

solves the issue with updating kernels to grub.cfg

But , still all upgrades from 29 to 30 will probably fail with booting to new F30
Comment 3 Javier Martinez Canillas 2019-04-10 07:38:44 UTC 
(In reply to Denis from comment #2)
> After some searching, found this page
> https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
> 
> Change in /etc/default/grub
> to
> GRUB_ENABLE_BLSCFG=false
> 
> solves the issue with updating kernels to grub.cfg
>

Yes, you need to install the grubby-deprecated package though for new kernel entries to be added in grub.cfg if you disable the BLS support. Do you have BLS snippets in /boot/loader/entries ?

> But , still all upgrades from 29 to 30 will probably fail with booting to
> new F30

Not all upgrades. I just tested upgrading from 29 to 30 in both legacy BIOS and EFI installs and worked correctly. I wonder what went wrong in your case.
Comment 4 Denis 2019-04-10 16:06:15 UTC 
(In reply to Javier Martinez Canillas from comment #3)
 
> Yes, you need to install the grubby-deprecated package though for new kernel
> entries to be added in grub.cfg if you disable the BLS support. Do you have
> BLS snippets in /boot/loader/entries ?
Yes, I have snippets
# ls -al /boot/loader/entries 
total 20
drwx------ 2 root root 4096 Mar 28 18:30 .
drwxr-xr-x 3 root root 4096 May  4  2018 ..
-rw-r--r-- 1 root root  379 Apr 10 00:57 5422efcd9d6949a8b2d1493ceacf17bf-0-rescue.conf
-rw-r--r-- 1 root root  245 Mar 27 23:05 5422efcd9d6949a8b2d1493ceacf17bf-5.0.5-300.fc30.x86_64.conf
-rw-r--r-- 1 root root  245 Apr  3 18:13 5422efcd9d6949a8b2d1493ceacf17bf-5.0.6-300.fc30.x86_64.conf



> Not all upgrades. I just tested upgrading from 29 to 30 in both legacy BIOS
> and EFI installs and worked correctly. I wonder what went wrong in your case.

I'm running with legacy BIOS mode. Both KVM host and VM had same issue after upgrading from 29 to 30.
What else I can check ?
Comment 5 Javier Martinez Canillas 2019-04-10 16:11:33 UTC 
(In reply to Denis from comment #4)
> (In reply to Javier Martinez Canillas from comment #3)
>  
> > Yes, you need to install the grubby-deprecated package though for new kernel
> > entries to be added in grub.cfg if you disable the BLS support. Do you have
> > BLS snippets in /boot/loader/entries ?
> Yes, I have snippets
> # ls -al /boot/loader/entries 
> total 20
> drwx------ 2 root root 4096 Mar 28 18:30 .
> drwxr-xr-x 3 root root 4096 May  4  2018 ..
> -rw-r--r-- 1 root root  379 Apr 10 00:57
> 5422efcd9d6949a8b2d1493ceacf17bf-0-rescue.conf
> -rw-r--r-- 1 root root  245 Mar 27 23:05
> 5422efcd9d6949a8b2d1493ceacf17bf-5.0.5-300.fc30.x86_64.conf
> -rw-r--r-- 1 root root  245 Apr  3 18:13
> 5422efcd9d6949a8b2d1493ceacf17bf-5.0.6-300.fc30.x86_64.conf
> 
> 
> 
> > Not all upgrades. I just tested upgrading from 29 to 30 in both legacy BIOS
> > and EFI installs and worked correctly. I wonder what went wrong in your case.
> 
> I'm running with legacy BIOS mode. Both KVM host and VM had same issue after
> upgrading from 29 to 30.
> What else I can check ?

Do you remember what was the Fedora release that was originally installed on those?

Also, can you please try the following from the grub prompt:

grub> set debug=blscfg
grub> insmod blscfg
grub> blscfg
Comment 6 Denis 2019-04-10 21:32:32 UTC 
(In reply to Javier Martinez Canillas from comment #5)
> (In reply to Denis from comment #4)
> > (In reply to Javier Martinez Canillas from comment #3)
>
> Do you remember what was the Fedora release that was originally installed on
> those?
Vm installed as F21.
Host , I don't remember. Maybe 18 , maybe earlier version
 
> Also, can you please try the following from the grub prompt:
> 
> grub> set debug=blscfg
> grub> insmod blscfg
> grub> blscfg

I get from grub cli , when no kernel entries
error: can't find command `blscfg'
Comment 7 Javier Martinez Canillas 2019-04-10 22:45:37 UTC 
(In reply to Denis from comment #6)
> (In reply to Javier Martinez Canillas from comment #5)
> > (In reply to Denis from comment #4)
> > > (In reply to Javier Martinez Canillas from comment #3)
> >
> > Do you remember what was the Fedora release that was originally installed on
> > those?
> Vm installed as F21.
> Host , I don't remember. Maybe 18 , maybe earlier version
>  
> > Also, can you please try the following from the grub prompt:
> > 
> > grub> set debug=blscfg
> > grub> insmod blscfg
> > grub> blscfg
> 
> I get from grub cli , when no kernel entries
> error: can't find command `blscfg'

I see, so then what seems to have failed is the copy of the blscfg module from /usr/lib/grub/i386-pc/blscfg.mod to the /boot/grub2/i386-pc/ directory. Could you please try copying the blscfg module there and then try to execute the blscfg command again?

If you still have issues there, you may try to update your GRUB core with grub2-install /dev/sda (or whatever is your block device where GRUB was installed).
Comment 8 Denis 2019-04-11 21:36:51 UTC 
> I see, so then what seems to have failed is the copy of the blscfg module
> from /usr/lib/grub/i386-pc/blscfg.mod to the /boot/grub2/i386-pc/ directory.
> Could you please try copying the blscfg module there and then try to execute
> the blscfg command again?
> 
> If you still have issues there, you may try to update your GRUB core with
> grub2-install /dev/sda (or whatever is your block device where GRUB was
> installed).

I had /boot/grub2/i386-pc/blscfg.mod 
But when I copied new blscfg.mod from /usr/lib/grub/i386-pc/blscfg.mod to /boot/grub2/i386-pc/ it fixed grub menu entries

Had only ls output on two different blscfg.mod
Bad:
ll /tmp/sda1/grub2/i386-pc/blscfg.mod
-rw-r--r--. 1 root root 3020 Feb 20 22:57 /tmp/sda1/grub2/i386-pc/blscfg.mod

Good:
ll /tmp/sda3/usr/lib/grub/i386-pc/blscfg.mod
-rw-r--r-- 1 root root 14012 Apr 12 00:25 /tmp/sda3/usr/lib/grub/i386-pc/blscfg.mod
Comment 9 Javier Martinez Canillas 2019-04-12 11:36:23 UTC 
(In reply to Denis from comment #8)
> > I see, so then what seems to have failed is the copy of the blscfg module
> > from /usr/lib/grub/i386-pc/blscfg.mod to the /boot/grub2/i386-pc/ directory.
> > Could you please try copying the blscfg module there and then try to execute
> > the blscfg command again?
> > 
> > If you still have issues there, you may try to update your GRUB core with
> > grub2-install /dev/sda (or whatever is your block device where GRUB was
> > installed).
> 
> I had /boot/grub2/i386-pc/blscfg.mod 
> But when I copied new blscfg.mod from /usr/lib/grub/i386-pc/blscfg.mod to
> /boot/grub2/i386-pc/ it fixed grub menu entries
> 

Thanks for the info. So then the problem was that the blscfg module was not correctly copied, not that it was copied but didn't work?
Comment 10 Denis 2019-04-12 15:42:41 UTC 
(In reply to Javier Martinez Canillas from comment #9)
> 
> Thanks for the info. So then the problem was that the blscfg module was not
> correctly copied, not that it was copied but didn't work?

The module was before copy, but didn't worked.
By (ll) output there is different sizing of module on two directories
Comment 11 Javier Martinez Canillas 2019-04-12 15:48:32 UTC 
(In reply to Denis from comment #10)
> (In reply to Javier Martinez Canillas from comment #9)
> > 
> > Thanks for the info. So then the problem was that the blscfg module was not
> > correctly copied, not that it was copied but didn't work?
> 
> The module was before copy, but didn't worked.
> By (ll) output there is different sizing of module on two directories

Yes, there was a blscfg module before (from F19 by looking at the grub2 package git logs) but there were a lot of fixes and also EFI support added in the latest versions. So the one you had there probably is what was installed on the original installation.
Comment 12 Javier Martinez Canillas 2019-04-15 16:31:37 UTC 

*** This bug has been marked as a duplicate of bug 1652806 ***
Note You need to log in before you can comment on or make changes to this bug.