Am 23.04.2015 um 17:37 schrieb Michael Biebl: > Am 23.04.2015 um 12:32 schrieb Peter Rajnoha:
>> And check the udevd log if there's a blkid call in there >> and if it exports the ID_FS_TYPE=LVM2_member. > > I've attached the debug log. > > I guess the relevant part is: > > Apr 23 17:32:54 debian systemd-udevd[1462]: IMPORT '/sbin/blkid -o udev > -p -u noraid /dev/md0' /lib/udev/rules.d/63-md-raid-arrays.rules:29 > Apr 23 17:32:54 debian systemd-udevd[1464]: starting '/sbin/blkid -o > udev -p -u noraid /dev/md0' > Apr 23 17:32:54 debian systemd-udevd[1462]: '/sbin/blkid -o udev -p -u > noraid /dev/md0' [1464] exit with return code 2 > > Any idea, why blkid fails? Apparently this comes from a custom Debian patch to mdadm [1] which doesn't really make sense to me, since blkid is actually a builtin in Debian's udev. Reverting that patch, i.e. using the blkid builtin, I get ID_FS_TYPE=LVM2_member properly set. Still no luck though: The lvm udev rules don't activate the pvcan service via SYSTEMD_WANTS and the LV is still inactive. I'm getting lost here. Michael [1] https://anonscm.debian.org/cgit/pkg-mdadm/mdadm.git/tree/debian/patches/use-external-blkid.diff -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
