User Tools

Site Tools


general:linux:kexec_automatic_unlock_luks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
general:linux:kexec_automatic_unlock_luks [2025/06/12 10:54] sunkangeneral:linux:kexec_automatic_unlock_luks [2025/06/12 10:57] (current) sunkan
Line 7: Line 7:
 In addition to the above also create a key-file for the boot system so there should be key-files for both the encrypted devices (partitions) In addition to the above also create a key-file for the boot system so there should be key-files for both the encrypted devices (partitions)
  
-Also if cryptsetup fails with the device being in use but you have unmounted /boot then try to stop/restart all the namespace mounts liste with **lsns -t mnt**+Also if cryptsetup fails with the device being in use but you have unmounted /boot then try to stop/restart all the namespace mounts listed with **lsns -t mnt** 
 + 
 +To load the kernel manually (seems to be necessary for the time being) and the perform a kexec "reboot" \\ 
 +More details here https://github.com/systemd/systemd/issues/15029 
 +<code> 
 +kexec --load --initrd=/initrd.img --reuse-cmdline /vmlinuz 
 +systemctl kexec 
 +</code> 
 + 
general/linux/kexec_automatic_unlock_luks.1749725660.txt.gz · Last modified: 2025/06/12 10:54 by sunkan

Donate Powered by PHP Valid HTML5 Valid CSS Run on Debian Driven by DokuWiki