booted hirsute instance and observed the race: $ journalctl -u grub-initrd-fallback -u grub-common -- Journal begins at Tue 2021-02-16 18:28:59 UTC, ends at Tue 2021-02-16 18:29:30 UTC. -- Feb 16 18:29:06 ip-172-31-7-49 systemd[1]: Starting Record successful boot for GRUB... Feb 16 18:29:06 ip-172-31-7-49 systemd[1]: Starting GRUB failed boot detection... Feb 16 18:29:06 ip-172-31-7-49 sh[528]: grub-editenv: error: invalid environment block. Feb 16 18:29:06 ip-172-31-7-49 systemd[1]: Started Record successful boot for GRUB. Feb 16 18:29:06 ip-172-31-7-49 systemd[1]: grub-initrd-fallback.service: Succeeded. Feb 16 18:29:06 ip-172-31-7-49 systemd[1]: Finished GRUB failed boot detection.
Upgraded to $ dpkg-query -W grub-efi-arm64 grub-efi-arm64-signed grub-efi-arm64-bin grub-efi-arm64 2.04-1ubuntu40 grub-efi-arm64-bin 2.04-1ubuntu40 grub-efi-arm64-signed 1.161+2.04-1ubuntu40 Rebooted twice Observed $ journalctl -b -u grub-initrd-fallback -u grub-common Feb 16 18:33:22 ip-172-31-7-49 systemd[1]: Starting Record successful boot for GRUB... Feb 16 18:33:22 ip-172-31-7-49 systemd[1]: Started Record successful boot for GRUB. Feb 16 18:33:22 ip-172-31-7-49 systemd[1]: Starting GRUB failed boot detection... Feb 16 18:33:22 ip-172-31-7-49 systemd[1]: grub-initrd-fallback.service: Succeeded. Feb 16 18:33:22 ip-172-31-7-49 systemd[1]: Finished GRUB failed boot detection. Notice how one job starting & started; before the next one does starting & finished. Thus they are are now run in sequence. Rather than having two Starting messages back to back -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910815 Title: race on boot between multiple invocations of grub-editenv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1910815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
