[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 Carlos De Maine changed: What|Removed |Added CC||carlosdema...@gmail.com Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #11 from Carlos De Maine --- this is now working. neon's calamares-settings package had to be adjusted to use the calamares initramfscfg module. tested in neon release. will be snapshot(ted) to neon user very soon (TM) and a new iso spun up. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 --- Comment #10 from Michael "manchicken" Stemle, Jr. --- Here's everything I've found so far: ## Stuff that is fine - the `/etc/crypttab` looks fine - the `/etc/fstab` looks fine - the keyfile _is_ present and _can_ unlock the filesystems - the swap partition appears to be good, but in mapper form (which makes sense since it's an encrypted partition) ## Stuff that doesn't appear to be fine - the `initramfs.conf` seems to be missing from the ISO - the `luksbootkeyfile.conf` seems to be missing from the ISO - I still get error `Failed to enable swap for devices: ['/dev/sda3']`, but it may be a red herring I'm continuing to dig, but even after I place the two config files above and re-run the installer, the system still won't boot. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 Andreas changed: What|Removed |Added CC||hoheneg...@web.de --- Comment #9 from Andreas --- 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- 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.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 --- Comment #8 from Michael "manchicken" Stemle, Jr. --- Created attachment 166670 --> https://bugs.kde.org/attachment.cgi?id=166670=edit This is the session log from the install into my VM -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 Michael "manchicken" Stemle, Jr. changed: What|Removed |Added CC||he...@mikestemle.com --- Comment #7 from Michael "manchicken" Stemle, Jr. --- Created attachment 19 --> https://bugs.kde.org/attachment.cgi?id=19=edit Here's some analysis that I did -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 ssni...@gmail.com changed: What|Removed |Added CC||ssni...@gmail.com --- Comment #6 from ssni...@gmail.com --- Most recent user iso is broken on boot when installing with encryption!!! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 Chris Moore changed: What|Removed |Added CC||ch...@mooreonline.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 ricksanchez137c changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||ricksanchez1...@proton.me --- Comment #5 from ricksanchez137c --- (In reply to spiesant from comment #1) > Addendum: it looks like others are experiencing the same - multiple posts > about this on Reddit in the past 5 days: > https://www.reddit.com/r/kdeneon/comments/1aenouy/ > kde_neon_wont_boot_after_fresh_install_cryptsetup/ I can confirm this is happening when I install KDE neon using a recent ISO. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 --- Comment #4 from Metal450 --- More reports of this here: https://discuss.kde.org/t/disk-encryption-not-working-on-recent-neon-isos-but-is-working-on-older-images/9505 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 l...@lukeco.com changed: What|Removed |Added CC||l...@lukeco.com --- Comment #3 from l...@lukeco.com --- (In reply to Ioannis Panagiotopoulos from comment #2) > Can confirm the bug. Tried today to install it on some new machines but > after installation and successful password prompt, it failed to boot. We use > the default setup with no custom configuration (we use the 'use full disk' > option with the 'system encryption' enabled). The iso version was > 'neon-user-20240208-0715' and we verified the signature before writing it to > media. Can we at least get a link to the last good iso until the fix? Same exact process and issue here. Confirmed on testing ISO from today. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 Ioannis Panagiotopoulos changed: What|Removed |Added CC||yiannisp...@hotmail.com --- Comment #2 from Ioannis Panagiotopoulos --- Can confirm the bug. Tried today to install it on some new machines but after installation and successful password prompt, it failed to boot. We use the default setup with no custom configuration (we use the 'use full disk' option with the 'system encryption' enabled). The iso version was 'neon-user-20240208-0715' and we verified the signature before writing it to media. Can we at least get a link to the last good iso until the fix? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 --- Comment #1 from Metal450 --- Addendum: it looks like others are experiencing the same - multiple posts about this on Reddit in the past 5 days: https://www.reddit.com/r/kdeneon/comments/1aenouy/kde_neon_wont_boot_after_fresh_install_cryptsetup/ -- You are receiving this mail because: You are watching all bug changes.
