[systemd-bugs] [Bug 89383] systemd-219 can't mount devices

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Apr 23 09:02:20 PDT 2015


https://bugs.freedesktop.org/show_bug.cgi?id=89383

--- Comment #6 from Bastien Traverse <bastien at esrevart.net> ---
Another use case to complement the report:

- system is a home server running Arch linux, full disk encrypted with
dmcrypt/LUKS and remotely unlocked via dropbear_initrd_encrypt [1]
- it was updated today with the latest systemd packages
({lib}systemd{-sysvcompat} 219-5) and latest linux-lts (3.14.39), therefore the
initramfs was rebuilt with mkinitcpio.

What happens: after rebooting I am locked out at the initramfs stage with the
following error messages:

- on client trying to ssh in dropbear_initrd:
    Device /dev/disk/by-id/wwn-<redacted_id>-part3 doesn't exist or access
denied.

- on server:
   Running systemd 219
(dropbear initialization sequence, everything is ok)
    Starting dropbear
    [123] Apr 23 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

If I don't try to login via SSH there is a 15 seconds delay between [123] line
and the first ERROR; there is no mean whatsoever to unlock dropbear locally as
used to be the case ("enter passphrase for
/dev/disk/by-id/wwn-<redacted_id>-part" used to be displayed).

My kernel command line is BOOT_IMAGE=/vmlinuz-linux-lts
root=/dev/mapper/lvm-archroot rw quiet
cryptdevice=/dev/disk/by-id/wwn-<redacted_id>-part3:crypt
ip=192.168.1.xxx::192.168.1.254::arch-medion:eth0:none

[1]
https://wiki.archlinux.org/index.php/Dm-crypt/Specialties#Remote_unlocking_of_the_root_.28or_other.29_partition

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150423/600dda18/attachment.html>


More information about the systemd-bugs mailing list