/boot/grub2/grubenv is missing after rear recover

Solution Verified - Updated -

Issue

  • /boot/grub2/grubenv is missing after rear recover.
  • Even though system can boot without /boot/grub2/grubenv, the following error output in messages files frequently.
systemd[118744]: Starting Mark boot as successful...
grub2-set-bootflag[119441]: Error canonicalizing /boot/grub2/grubenv filename: No such file or directory
systemd[118744]: grub-boot-success.service: Main process exited, code=exited, status=1/FAILURE
systemd[118744]: grub-boot-success.service: Failed with result 'exit-code'.
systemd[118744]: Failed to start Mark boot as successful.
  • Install a new kernel, /boot/efi/EFI/redhat/grubenv is not updated, hence the system always boots into the old kernel by default. Even if grubby --default-kernel shows the new kernel is the default.
  • ReaR 2.4 doesn't have this issue.

Environment

  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9
  • ReaR 2.6
  • SELinux disabled
  • UEFI

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content