Arch Linux

Description:

Despite  FS#44658  closure I still have to hold systemd packages (systemd, libsystemd and systemd-sysvcompat) to v218 so as to have a working initramfs and be able to boot a remotely unlocked machine (details at https://bugs.freedesktop.org/show_bug.cgi?id=89383#c6 and in  FS#44658  comments -- note that I have tried again today with systemd-219-6 and linux-4.0.4-1).

Therefore I'd like to request the backporting of what was pinpointed by Martin Pitt as the upstream fix for this issue, http://cgit.freedesktop.org/systemd/systemd/commit/?id=f62009410 (cf. https://bugs.freedesktop.org/show_bug.cgi?id=89383#c8) while waiting for a new upstream release.

Additional info:
* package version(s): {lib}systemd{-sysvcompat}-219-6

Steps to reproduce:

Configure a fully-encrypted and remotely-unlocked machine as described at https://wiki.archlinux.org/index.php/Dm-crypt/Specialties#Remote_unlocking_of_the_root_.28or_other.29_partition, make sure initramfs is built with systemd-219-6, reboot and watch error message preventing connexion and unlocking:

Running systemd 219
(dropbear initialization sequence, everything is ok)
Starting dropbear
[123] May 21 09:43:56 Running in background
(try to connect remotely via SSH)
Pubkey auth succeeded for 'root' with key XXX from 192.XXX
syslogin_perform_logout: logout(pts/0) returned an error: No such file or directory
Exit (root) Disconnect received
ERROR: device '/dev/mapper/lvm-archroot' not found. Skipping fsck.
ERROR: Unable to find rot device '/dev/mapper/lvm-archroot'
You are being dropped to a recovery shell