Discussion:
problems with systemd hooks and encrypted root partition
(too old to reply)
Christian Rebischke
2017-07-11 00:45:58 UTC
Permalink
Raw Message
Hello,
Does somebody else have problems with systemd hooks and an encrypted
root partition? I want to use systemd-boot with systemd hooks for my
whole boot process. Systemd-boot with the normal hooks works fine but
when I try to use systemd hooks I can't get through the cryptsetup
password prompt because it always jumps into emergency mode after 2
seconds.


My hooks line looks like this:

HOOKS="base systemd autodetect modconf block keyboard sd-vconsole sd-encrypt filesystems fsck"

My boot entry for systemd-boot looks like this:

title motoko-lts
linux /vmlinuz-linux-lts
initrd /initramfs-linux-lts.img
options rd.luks.uuid=1aa50d23-d139-4367-b552-448a1b14b086 rd.luks.name=71f4088d-e06f-43b2-818f-7a34de921460 root=71f4088d-e06f-43b2-818f-7a34de921460 rw

And my `sudo blkid` output is this one:

/dev/sda1: UUID="DBC6-90A0" TYPE="vfat" PARTLABEL="EFI" PARTUUID="aad19313-36df-4433-98ec-3fc310181629"
/dev/sda2: UUID="1aa50d23-d139-4367-b552-448a1b14b086" TYPE="crypto_LUKS" PARTLABEL="Root" PARTUUID="720f9c51-6861-418e-90d4-622295937c39"
/dev/mapper/root: UUID="71f4088d-e06f-43b2-818f-7a34de921460" TYPE="ext4"


Here is screenshot:

https://paste.archlinux.de/HMZn/

Best regards,

Chris
Christian Rebischke
2017-07-11 01:10:15 UTC
Permalink
Raw Message
Post by Christian Rebischke
Hello,
[..]
Problem solved.. sorry for the noise. My boot entry was incorrect.
Correct entry looks like this now (for current kernel):

title motoko
linux /vmlinuz-linux
initrd /initramfs-linux.img
options rd.luks.uuid=1aa50d23-d139-4367-b552-448a1b14b086 rd.luks.name=71f4088d-e06f-43b2-818f-7a34de921460=Root root=UUID=71f4088d-e06f-43b2-818f-7a34de921460 rw
Loading...