You are not logged in.
When I try to boot my "full disc" (not actually using an encrypted boot partition) encryption LVM scheme after install it gets to:
"A start job is running for /dev/ArchDisc/root" and then times out with the following error:
[TIME] Timed out waiting for device /dev/ArchDisc/root
[DEPEND] Dependency failed for Initrd Root Devicethen several more dependency failes and it starts the emergency shell
I followed the install guide steps to "Partition the Disks" for UEFI install. At that point I went to the dm-crypt/Encrypting an Entire disk guide using LVM on LUKS. I set up a partition scheme whereby
/dev/sda1is a 512MiB FAT32 partition mounted to
/bootfor the EFI. I then have 2 partitions in the cryptlvm drive
/dev/sda2, root (110GiB) and swap (8GiB).
I used the following hooks
HOOKS=(base systemd autodetect keyboard sd-vconsole modconf block sd-encrypt sd-lvm2 filesystems fsck) it doesn't have udev per the wiki example. Is this needed?
I also added to the EFI entry config for arch under options
rd.luks.name=/dev/sda2_crypto_LUKS_UUID_number_here=cryptlvm root=/dev/ArchDisc/rootI named the lvm group ArchDisc
it doesn't prompt me for the password at any point to unlock the encryption. Once back using the install disc, I can unlock the drive with
cryptsetup open /dev/sda2 cryptlvmwhere it asks me for the password and read the files.
I'm a bit stumped. I appreciate any advice where to look next!
Last edited by docinla (2019-03-09 06:43:29)
Offline
Argh. I figured it out!
In the instructions it says to use:
cryptdevice=UUID=device-UUID:cryptlvm root=/dev/MyVolGroup/rootIf using the sd-encrypt hook, the following need to be set instead:
rd.luks.name=device-UUID=cryptlvm root=/dev/MyVolGroup/rootI stupidly used a colon in the second instead of an = sign after the device-UUID. Changing it from a colon to an equals made it magically work. Anyways, now onto everything else! I'm sure I'll be back soon...
Last edited by docinla (2019-03-09 06:42:05)
Offline