Boot loop after correct luks key

[w4rdl0rd]

Hi,
I did a fresh install of qubes 4.2.4 and had at first multiple problems with my sys-usb.
After solving them I’m now getting stuck in a boot loop.
When I enter a correct luks keyphrase it starts but when the loading bar reaches approximately half it shuts down and I have to enter the keyphrase again. It goes on indefinitely. When it first occurred I just did a fresh install, but it is now the third time that it is happening.
After a fresh install, shutting down and booting multiple times, the error did not occur. Only after multiple hours of inactivity does this happen.

When I can type in my passphrase and press esc, all the startup checked are shown that everything is okay.

The last messages are:
[ok] Finished modprobelconf igfs service - Load Kernel Module configfs…
[ok] Finished modprobelconf igfs.service - Load Kernel Module configfs.
[ok] Finished systemd-udev-trigger service - Coldplug All udev Devices.

After that it just reboots and begins again.

[ChrisA]

Hi w4rl0rd

Can you try and edit the GRUB boot options like this:

Kernel-latest 6.13.6 boot loop

Do you see any crash message on the screen, even briefly? If so, you can append panic=0 to vmlinuz options and/or noreboot to xen options to keep the message longer on the screen. Or at least better see what is the last message before the crash… You said the last line is about modprobe configfs. Can you check in a log from earlier boot what was the next module loaded? And maybe try to exclude it? There is also a hope crash message got saved to efi pstore. Check /var/lib/systemd/pstore and /sys…

?

[w4rdl0rd]

Hi Chris,

unfortunately after making some other changes all files related to grub were deleted? or are unavailable. After a restart I had only the option to get to my uefi settings. Now I’m doing a fresh install again, maybe next time it happens again I’ll try these changes. Thanks

[ChrisA]

Hi w4rl0rd

A trick with the installer:

1. Load GRUB from the Qubes Install medium, as when you install Qubes OS
2. When you see the GRUB boot menu, hit c to get to the grub>-prompt
3. type configfile ( and hit tab – you should see a list of available drives. If you only see one, it’s probably just the install medium … but if you have more than one (say hd0 and hd1), you might be able to load the GRUB menu from the harddrive.

On a test machine, I have (hd1,gpt1)/efi/ so I can load the GRUB menu from the harddrive with:

configfile (hd1,gtp1)/efi/qubes/grub.cfg

[w4rdl0rd]

Hi Chris,
thank you for your tip. After installing everything again I tried this: Kernel-latest 6.13.6 boot loop

The problem seems solved, apparently updating kernel-latest to kernel-latest-6.13.8-1.qubes.1.fc37.x86_64 from kernel-latest-6.13.7-1.qubes.1.fc37.x86_64 helped in solving it.

Thanks, again. Have a nice week

[ChrisA]

Hi w4rl0rd

Nice that you got it to work!!

If possible, would you mark your post as the solution – in case others with a similar problem should stumble upon these posts, looking for a solution?