Fedora Account System
Red Hat Associate
Red Hat Customer
A new installation of f44, on either a VM or bare bones, creates a grubenv file that contains this. ---- env_block=512+1 saved_entry=65691051db24416796e541a46c278d5b-6.19.14-300.fc44.x86_64 menu_auto_hide=1 boot_success=1 ---- The very first line has the env_block variable that triggers an error at the beginning of boot to flash on screen. Reproducible: Always Steps to Reproduce: 1.install f44 (new clean install) 2.boot 3. Actual Results: At the beginning of boot there are 2 lines flashed about an error in the grubenv file Expected Results: errors of this type should not appear on a new installation Additional Information: I have made 2 different installations using the newly released iso for fedora 44 workstation. One was in a VM, and the second was bare bones on a new machine. In both cases each boot began showing the noted error messages. This thread https://discussion.fedoraproject.org/t/grub-error-with-new-fedora-44-install/189848/12 lead me to investigate the content of the grubenv file with `sudo grub2-editenv - list` and on both systems I saw the data shown in the details above. I then used `sudo grub2-editenv - unset env_block` and on both systems the error messages disappeared. It appears that something in the initial setup installation is creating an invalid entry in the grubenv file which triggers the error warning.
This appears to be copied over from the Live System. To check, run these commands sudo mount -r Fedora-Workstation-Live-44-1.7.x86_64.iso /mnt sudo mount -r /mnt/LiveOS/squashfs.img /mnt sudo cat /mnt/boot/grub2/grubenv sudo umount /mnt sudo umount /mnt The grubenv from the Live System does indeed also contain the "env_block=512+1" plus a entry for "saved_entry=". Obviously, it is too late to fix this as this would require a new iso to be generated.
This appears to be duplicate of 457333
I could remove the error message with sudo grub2-editenv - unset env_block
I believe this is a duplicate of bug 2457333 *** This bug has been marked as a duplicate of bug 2457333 ***
(In reply to Villy Kruse from comment #2) > This appears to be duplicate of 457333 indeed, it is a duplicate. As seen on the original report, we have not found the root cause yet and that env_block variable **should not be present** on file systems not supporting the latter, e.g. as today, all except btrfs.
(In reply to Leo Sandoval from comment #5) > (In reply to Villy Kruse from comment #2) > > This appears to be duplicate of 457333 > > indeed, it is a duplicate. > > As seen on the original report, we have not found the root cause yet and > that env_block variable **should not be present** on file systems not > supporting the latter, e.g. as today, all except btrfs. I would think the issue comes from kiwi and the configuration files used by kiwi. As far as I can see, the KDE version doesn't have this issue.
(In reply to Villy Kruse from comment #6) > (In reply to Leo Sandoval from comment #5) > > (In reply to Villy Kruse from comment #2) > > > This appears to be duplicate of 457333 > > > > indeed, it is a duplicate. > > > > As seen on the original report, we have not found the root cause yet and > > that env_block variable **should not be present** on file systems not > > supporting the latter, e.g. as today, all except btrfs. > > I would think the issue comes from kiwi and the configuration files used by > kiwi. As far as I can see, the KDE version doesn't have this issue. regarding kiwi, see https://github.com/OSInside/kiwi/issues/2986 It is not clear to me if KDE versions are impacted or not..
(In reply to Leo Sandoval from comment #7) > (In reply to Villy Kruse from comment #6) > > (In reply to Leo Sandoval from comment #5) > > > (In reply to Villy Kruse from comment #2) > > > > This appears to be duplicate of 457333 > > > > > > indeed, it is a duplicate. > > > > > > As seen on the original report, we have not found the root cause yet and > > > that env_block variable **should not be present** on file systems not > > > supporting the latter, e.g. as today, all except btrfs. > > > > I would think the issue comes from kiwi and the configuration files used by > > kiwi. As far as I can see, the KDE version doesn't have this issue. > > regarding kiwi, see https://github.com/OSInside/kiwi/issues/2986 > > It is not clear to me if KDE versions are impacted or not.. grubenv found in Fedora-KDE-Desktop-Live-44-1.7.x86_64.iso contains # GRUB Environment Block # WARNING: Do not edit this file by tools other than grub-editenv!!! saved_entry=b972505d158f4637b4467345ec041324-6.19.10-300.fc44.x86_64 #############################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################[ Thus no env_block entry
I disagree with comment 8 I performed the steps ----- sudo mount -r Fedora-Workstation-Live-44-1.7.x86_64.iso /mnt sudo mount -r /mnt/LiveOS/squashfs.img /mnt sudo cat /mnt/boot/grub2/grubenv with the result # GRUB Environment Block # WARNING: Do not edit this file by tools other than grub-editenv!!! env_block=512+1 saved_entry=4189730cf6c94d60bf67890447d58a3b-6.19.10-300.fc44.x86_64 ############################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################# The env_block entry is definitely there in the copy on the live media iso. Those commands were provided in the forum post https://discussion.fedoraproject.org/t/grub-error-with-new-fedora-44-install/189848/16
Comment 9 is meant to show the difference between comment 8 about KDE live media and Workstation live media.
(In reply to Leo Sandoval from comment #5) > indeed, it is a duplicate. Sorry, was it your intention that you reopened this bug? Shouldn't we merge both discussions into a single place?
(In reply to Kamil Páral from comment #11) > (In reply to Leo Sandoval from comment #5) > > indeed, it is a duplicate. > > Sorry, was it your intention that you reopened this bug? Shouldn't we merge > both discussions into a single place? I was not my intention. I believe the was a miss-collision from my side, so the close/duplicate state (that you set) got overwritten with my comment. Sorry for the noise.
*** This bug has been marked as a duplicate of bug 2457333 ***