[systemd-devel] cannot start swap unit on lvm

Kay Sievers kay at vrfy.org
Thu Sep 13 05:28:23 PDT 2012


On Thu, Sep 13, 2012 at 2:23 PM, Lennart Poettering
<lennart at poettering.net> wrote:
> On Thu, 13.09.12 15:47, Alexey Shabalin (a.shabalin at gmail.com) wrote:
>
>> > Please check with "udevadm info
>> > /dev/disk/by-uuid/a8ce6981-1afd-4af6-8783-784b3c7a7d64" if the device is
>> > properly initialized and the systemd tag appears in TAGS=. Only then
>> > systemd will pick it up.
>> >
>> I see TAGS:
>>
>> P: /devices/virtual/block/dm-1
>> N: dm-1
>> E: DEVNAME=/dev/dm-1
>> E: DEVPATH=/devices/virtual/block/dm-1
>> E: DEVTYPE=disk
>> E: DM_UDEV_DISABLE_DISK_RULES_FLAG=1
>> E: DM_UDEV_DISABLE_OTHER_RULES_FLAG=1
>> E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1
>> E: MAJOR=253
>> E: MINOR=1
>> E: SUBSYSTEM=block
>> E: SYSTEMD_READY=0
>> E: TAGS=:systemd:
>> E: USEC_INITIALIZED=41372
>
> TAGS is there but the symlink to
> /dev/disk/by-uuid/a8ce6981-1afd-4af6-8783-784b3c7a7d64 is not known by
> udev. This usually indicates that your lvm installation is broken and
> doesn't properly integrate into udev (are you sure you enabled udev when
> building lvm?).
>
> But please bring this up with the LVM as this is hardly a systemd
> issue...

Existing symlinks, but missing symlink entries in the database often
indicates an initrd assembly, where the udev database did not survive
the transition to the real rootfs.

Kay


More information about the systemd-devel mailing list