On 29 Dec 2023 23:29 +0100, from rich...@rosner-online.de (Richard Rosner): > For a fraction of a second it shows something about slot 0 open, that's it.
Well, that means that GRUB at least succeeds in opening the LUKS container. That's good; it means that we can rule out that part of the chain as the cause of your problems, as well as everything before it. I still don't have any good idea what might cause GRUB to simply reboot, though. Normally, if there is a critical problem, GRUB will drop you to a built-in Unix-esque command-line interface with a "grub>" prompt. You do mention that you regenerated the initrd, but the initrd doesn't really figure into GRUB; it comes into play after the kernel is loaded into memory, which itself happens past the boot menu which you don't get to. I know it likely won't point you toward what the actual problem is, but I would suggest booting off live media (a Debian installer written to a USB stick and running in rescue mode should do), unlock/mount/chroot/shell into your root file system, and run `grub-install -v --no-nvram --recheck` (possibly with additional parameters; see grub-install(8) for details) from there to reinstall the boot loader itself. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
