https://bugs.kde.org/show_bug.cgi?id=480856
Andreas <hoheneg...@web.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hoheneg...@web.de
--- Comment #9 from Andreas <hoheneg...@web.de> ---
I can report that the Reddit workaround
https://www.reddit.com/r/kdeneon/comments/1aenouy/kde_neon_wont_boot_after_fresh_install_cryptsetup/
works (where I replaced /dev/nvme0n1p2 with my root partition path inferred
from, e.g., partitionmanager)
-------------------
On the running system, out of curiosity I re-added the keyfile to the key slots
of my two encrypted partitions by calling this:
sudo cryptsetup luksAddKey /dev/nvme0n1p2 /crypto_keyfile.bin
To my surprise when checking sudo cryptsetup luksDump /dev/nvme0n1p2 before and
after adding of the keyfile, I found out that the new key slot data does not
match any of the old slots. It looks like the keyfile was not added correctly
to the slots before.
Also I put the /crypto_keyfile.bin back into the /etc/crypttab (replacing the
none's) but did not add back the keyscript=/bin/cat. I read in the man page of
crypttab that the third parameter is the keyfile. I didn't see the need to add
the keyscript at all.
sudo update-initramfs -c -k all
and reboot
------------
This can be done after booting the installed system as follows from an
(initramfs) prompt
https://discuss.kde.org/t/disk-encryption-not-working-on-recent-neon-isos-but-is-working-on-older-images/9505/4
-------------
cryptsetup luksOpen /dev/disk/by-id/[deviceid] luks-<uuid>
and enter the password. Then run
exec run-init /root /sbin/init /root/dev/console
-------------
--
You are receiving this mail because:
You are watching all bug changes.
