Arch Linux

sas

Member

Registered: 2009-11-24

Posts: 155

sd-encrypt hook fails to work since last package upgrade

I have a relatively new Arch Linux system with an encrypted root partition unlocked via the sd-encrypt hook, which has worked fine until now.

But since yesterday's pacman -Syu, it refuses to boot. Instead of the password prompt, it's now showing me a 90-second timeout (photo) for...

A start job is running for dev-mapper-cryptroot.device

...and then dropping me into the emergency shell (photo).

---------------------------

When booting from a second, unencrypted Arch Linux disk, I can successfully open the encrypted disk like so:

$  cryptsetup open /dev/sda2 cryptroot
$  mount /dev/mapper/cryptroot /mnt

This is what my block devices look like when I do:

$  lsblk -o NAME,MOUNTPOINT,UUID
NAME          MOUNTPOINT UUID
sda                      
├─sda1                   7a030038-a7f4-4913-aeaa-93b40a71fdda
└─sda2                   2ab03f08-0f36-4074-a21b-4c31fb44d5c1
  └─cryptroot /mnt       4d5057a0-8e33-4ad2-bd36-00a4d7638b93
sdb                      dca0ae3e-a218-4e12-bd52-a2e08d24eb9e
├─sdb1        /boot      0dd78c54-f38b-44d3-a104-406bffefc43f
└─sdb2        /          ec09e9a5-36df-4ac7-b1d5-3f1b5e9ad9c5

I can then chroot into /mnt and everything there looks fine to me.
Here are various config snippets from inside the chroot:

---------------------------

/etc/crypttab: Empty.

/etc/fstab:

# /dev/mapper/cryptroot
UUID=4d5057a0-8e33-4ad2-bd36-00a4d7638b93       /               ext4            rw,relatime,data=ordered        0 1

# /dev/sdb1
UUID=7a030038-a7f4-4913-aeaa-93b40a71fdda       /boot           ext4            rw,relatime,data=ordered        0 2

/boot/syslinux/syslinux.cfg (relevant part):

LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND rw rd.luks.name=2ab03f08-0f36-4074-a21b-4c31fb44d5c1=cryptroot root=/dev/mapper/cryptroot
    INITRD ../initramfs-linux.img

/etc/mkinitcpio.conf (relevant line):

HOOKS=(base systemd autodetect block modconf keyboard sd-encrypt filesystems fsck)

/var/log/pacman.log (relevant lines):

[2017-12-16 16:33] [ALPM] upgraded systemd (235.38-2 -> 236.0-1)
[2017-12-16 16:33] [ALPM] upgraded linux (4.14.5-1 -> 4.14.6-1)

---------------------------

What could be preventing it from unlocking the encrypted partition on boot?
Any help would be greatly appreciated.

---

my AUR packages ~~ my community contributions

sas

Member

Registered: 2009-11-24

Posts: 155

Re: sd-encrypt hook fails to work since last package upgrade

After downgrading systemd from 236.0-1 [testing] to 235.38-4 [core], it works again.

I've filed a bug report.

---

my AUR packages ~~ my community contributions

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: sd-encrypt hook fails to work since last package upgrade

Well, um, thanks? Try to remember to check for existing bug reports first though...

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)