![]() |
Issue with booting Manjaro from encrypted NVMe drive on pbp - Printable Version +- PINE64 (https://forum.pine64.org) +-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111) +--- Forum: Linux on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=114) +--- Thread: Issue with booting Manjaro from encrypted NVMe drive on pbp (/showthread.php?tid=17838) |
Issue with booting Manjaro from encrypted NVMe drive on pbp - Cs137 - 01-19-2023 I am trying to operating a pbp with a system booted from an encrypted NVMe drive, but I stuck at the same step and would appreciate any help:
I append the following options via the `extlinux.conf` file: Code: cryptdevice=UUID=<ID-OF-NVME-DEV>:<LABEL-AS-APPEARS-IN-MAPPER>:allow-discards root=/mnt/mapper/<LABEL-AS-APPEARS-IN-MAPPER>/ rootflags=subvol=@ rw rootwait audit=0 plymouth.ignore-serial-consoles The ID, label and subvolume I use is the correct one, but I have to admit that I am unexperienced so far regarding btrfs. The fact that I am not prompted for the passphrase indicates me that the hook is either not implemented correctly in the initramfs, or not called correctly.`mkinitcpio` did not show an irregular behaviour during the creation of the initramfs (build via chroot from within the system I try to boot). In another approach I tried the `enrcypt` hook instead of `plymouth-encrypt` which did also not succeed. Moreover, I read here that one should use`plymouth-encrypt` if plymouth is in use, which is the case for Manjaro. Something that I recognised is that the initramfs is not build using the kernel sources of the system: Code: mkinitcpio -p linux Code: cat proc/version I would be happy for any hint that might be helpful to solve my issue. RE: Issue with booting Manjaro from encrypted NVMe drive on pbp - juliamenendez - 08-18-2023 I think you should check the initramfs hooks: Confirm that the necessary hooks Code: plymouth, plymouth-encrypt, and lvm2 are correctly included in the initramfs. You mentioned that you built the initramfs using mkinitcpio from within the system. Make sure that the hooks are specified in the /etc/mkinitcpio.conf file. You can check the contents of this file to ensure that the hooks are listed correctly. |