[partitionmanager] [Bug 463555] Add mount point for a LUKS encrypted partition will lead to booting into emergency mode
https://bugs.kde.org/show_bug.cgi?id=463555 --- Comment #5 from Uwe Köhler --- Hmm, I have been using Linux since 1997 and I am an early adopter of KDE. I really like it and might be putting up with that, but a normal user will be really frustrated. The way I did it had nothing to do with initramfs, but with /etc/crypttab and sudo cryptsetup luksAddKey /dev/nvme0n1p9 /var/root2/crypto_keyfile.bin. I believe that leaving the system not booting is way worse than simply not allowing to set a mount point for encrypted partitions. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 463555] Add mount point for a LUKS encrypted partition will lead to booting into emergency mode
https://bugs.kde.org/show_bug.cgi?id=463555 --- Comment #4 from Andrius Štikonas --- (In reply to Uwe Köhler from comment #3) > Hmmm, come to thinks about it: Maybe the answer is in your question. To > mount the encrypted partition, you have to take more steps than just > changing the fstab. Otherwise the partition cannot be mounted and the boot > process ends up in the emergency mode. I do have a precise protocol of the > steps I had to o manually to get it working, if that helps. Oh indeed, I think the source for the mount was missing because it was not decrypted (which could be done by e.g. initramfs on boot). Not sure what's the best way to proceed. Running those extra steps would be way beyond scope of KDE Partition Manager, as it depends a lot on how system is configured... We could disable mounts for encrypted partitions but it's also not ideal. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 463555] Add mount point for a LUKS encrypted partition will lead to booting into emergency mode
https://bugs.kde.org/show_bug.cgi?id=463555 --- Comment #3 from Uwe Köhler --- Hmmm, come to thinks about it: Maybe the answer is in your question. To mount the encrypted partition, you have to take more steps than just changing the fstab. Otherwise the partition cannot be mounted and the boot process ends up in the emergency mode. I do have a precise protocol of the steps I had to o manually to get it working, if that helps. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 463555] Add mount point for a LUKS encrypted partition will lead to booting into emergency mode
https://bugs.kde.org/show_bug.cgi?id=463555 --- Comment #2 from Uwe Köhler --- Sorry, i didn't expect this behaviour at all and did not safe fstab before. After the problem I completely re-installed Neon since I only learned how to add the partition manually later. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 463555] Add mount point for a LUKS encrypted partition will lead to booting into emergency mode
https://bugs.kde.org/show_bug.cgi?id=463555 --- Comment #1 from Andrius Štikonas --- It would be helpful if you could attach /etc/fstab file before and after it was edited with KDE Partition Manager. -- You are receiving this mail because: You are watching all bug changes.
