The relevant error seems to be "grub-editenv: error: invalid environment block" which both units emit when failing (grub-common.service and grub- initrd-fallback.service). In both cases grub-editenv is called to modify the content of /boot/grub/grubenv.
I suspect something sets values shortly before reboot and reaching those targets is supposed to unset them to indicate a successful boot. I am not sure how much the kernel is directly having an impact here. Other than maybe a different behavior on flushing pending writes on a filesystem... In the end it seems the grubenv file gets corrupted. It would be interesting to know whether after failing the following command still shows issues: "grub-editenv /boot/grub/grubenv list". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2136978 Title: grub2-common.service fails to load after cold reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2136978/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
