Fix might well be as simple as adding "After=grub-common.service" to /lib/systemd/system/grub-initrd-fallback.service - it's worked for one boot so far, which is obviously not a great test of a race condition :) It does seem to lead to sequential ordering of the two jobs, though:
Jan 08 20:31:26 asr-host systemd[1]: Starting LSB: Record successful boot for GRUB... Jan 08 20:31:26 asr-host grub-common[1816]: * Recording successful boot for GRUB Jan 08 20:31:27 asr-host grub-common[1816]: ...done. Jan 08 20:31:27 asr-host systemd[1]: Started LSB: Record successful boot for GRUB. Jan 08 20:31:27 asr-host systemd[1]: Starting GRUB failed boot detection... Jan 08 20:31:27 asr-host systemd[1]: grub-initrd-fallback.service: Succeeded. Jan 08 20:31:27 asr-host systemd[1]: Finished GRUB failed boot detection. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
