I’m 99% sure I already changed that. In a chroot environtment, I did…
# changed */crypto_keyfile.bin* to *none* as password on /etc/crypttab line
# comented the line *KEYFILE_PATTERN=/crypto_keyfile.bin* on /etc/cryptsetup-initramfs/conf-hook
update-initramfs -u -k all
update-grub
And the same options are used to add key as before and the keyfile is really the same that is stored in the initramfs? Probably better to rebuild it with mkinitcpio.
That root= kernel parameter is wrong because it needs to point to the container name as in /dev/mapper/xxxx which will be used to mount the root filesystem after the container is decrypted…
I don’t know which options are used during installation - I tried to dig a bit but didn’t find any lead.
I was unable to find anything in the initramfs - just the kernel
I found that strange - probably the wrong file. But I didn’t see another candidate.
Unfamiliar with Ubuntu.
If you open your encrypted container as for example Encrypted using the crypttab or luksopen command then:
You would need:
linux /boot/vmlinuz-5.15.0-58-generic root=/dev/mapper/Encrypted ro quiet splash $vt_handoff
And also use the same /dev/mapper/Encrypted in your /etc/fstab …
Otherwise you are NOT using the contents inside the encrypted container as root file system…
This has nothing todo with which distro you use, it is how you mount the root filesystem that is inside an encrypted container…
I posted on a KDE neon forum two hours ago. By the moment no answer.
PD: I tried to install Manjaro Linux on Virtualbox (kde and xcfe edtions) but after setup calamares installer crashes on both systems but this is another topic.