Comment 6 for bug 2017929

I can reproduce this bug by force powering off my machine (holding down the power button) and immediately starting it again. If I delay starting it, the bug does not seem to occur (but this is after a handful of attempts).

I get the bug whether I power off kernel from 5.15.0-71 or 5.15.0-70. I also got the bug when I powered off Clonezilla's version of Lunar Lobster. Therefore I believe the bug is to do with booting into kernel 5.15.0-71. In all cases I am able to boot into kernel 5.15.0-70 successfully.

It might be helpful to know whether other affected users can reproduce the bug by this method.

As far as I can tell these failed boots are not registering in the journal as they do not appear to be listed in the output of "journalctl --list-boots". As GRUB itself does not seem to keep logs, I am not sure what other diagnostic information to provide.

Focal's kernel 5.4.0-148.165 also contains one of the two changes that are in 5.15.0-71. I might be able to try to reproduce this bug there.