[Pkg-systemd-maintainers] Bug#745390: systemd: fails to recognize that LVM2 device nodes are already present and accessible

Dominik Brodowski linux at dominikbrodowski.net
Mon Apr 21 10:25:59 BST 2014


Package: systemd
Version: 204-8

In my custom initramfs, the device nodes for /dev/vg0/home and /dev/vg0/swap
are created. After the boot process is handed over to systemd, it enters an
emergency shell: The (autogenerated) systemd-cryptsetup at home.service and
systemd-cryptsetup at swap.service want dev-vg0-home.device and
dev-vg0-swap.device to be ready, but "systemctl status dev-vg0-home.device"
and "systemctl status dev-vg0-swap.device" shows they are inactive -- even
though the device nodes at /dev/vg0/home and /dev/vg0/swap actually exists!

A workaround for this bug was to create dummy device units:

$ touch /etc/systemd/system/dev-vg0-home.device
$ touch /etc/systemd/system/dev-vg0-var.device

lvm2 is at version 2.02.104-2, so the issue noted at
https://wiki.debian.org/systemd (which is said to be solved in lvm2 >=
2.02.104-1 ) seems to be different.

Many thanks for taking a look at this issue.

Best,
	Dominik




More information about the Pkg-systemd-maintainers mailing list