Your message dated Sun, 17 Mar 2019 10:24:09 +0100 with message-id <00a135b7-d912-26b3-2273-de239aa5c...@debian.org> and subject line Re: systemd: timed out waiting for lvm devices has caused the Debian Bug report #758808, regarding systemd: timed out waiting for lvm devices to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 758808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: systemd Version: 208-8 Severity: normal Hi, after removing the "quiet" kernel boot option, I see the following message before I'm dropped into emergency mode: [ TIME ] Timed out waiting for device dev-mapper-volumegroup/x2dhome.device. [DEPEND] Dependency failed for /home [DEPEND] Dependency failed for Local File Systems. Here is my fstab: --%<----------------------------------------------------------------------- # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 /dev/mapper/volumegroup-root / ext4 errors=remount-ro 0 1 UUID=ac034ff5-d28a-4ad1-8bac-97d554395e3e /boot ext2 defaults 0 2 /dev/mapper/volumegroup-home /home ext4 defaults 0 2 /dev/mapper/volumegroup-swap none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 cgroup /sys/fs/cgroup cgroup defaults 0 0 tmpfs /tmp tmpfs nodev,nosuid,size=8G 0 0 tmpfs /run tmpfs nodev,nosuid,size=8G 0 0 tmpfs /var/lib/schroot/unpack/ tmpfs nodev,nosuid,size=8G 0 0 -->%----------------------------------------------------------------------- My lvm2 version is 2.02.109-1 Here is the "udevadm info" output for /dev/mapper/volumegroup-home: --%<----------------------------------------------------------------------- P: /devices/virtual/block/dm-3 N: dm-3 L: 50 E: DEVNAME=/dev/dm-3 E: DEVPATH=/devices/virtual/block/dm-3 E: DEVTYPE=disk E: DM_NAME=volumegroup-home E: DM_STATE=ACTIVE E: DM_TABLE_STATE=LIVE E: DM_TYPE=raid 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: DM_UUID=LVM-ZrtPTxYRO88LRxfFiUfqELhK7tE4YTTNBfnUKnN3SCnNObmn0Hg0EkyGAIqVHMvJ E: MAJOR=253 E: MINOR=3 E: SUBSYSTEM=block E: USEC_INITIALIZED=42402 -->%----------------------------------------------------------------------- If I boot with sysvinit then everything works as expected. Downgrading to systemd 204-14 also makes everything work again [1]. So this is probably a regression between 204-14 and 206-8. Here is the output of "journalctl -alb" [2]. Thanks for your help! cheers, josch [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755581#10 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;filename=journalctl_alb;att=1;bug=755581 -- Package-specific info: -------------- systemd-delta: -------------- [EXTENDED] /lib/systemd/system/cups.socket -> /etc/systemd/system/cups.socket.d/cupsd-listen.conf 1 overridden configuration files found. -------------- Contents of /var/lib/systemd/deb-systemd-helper-enabled: -------------- ==> /var/lib/systemd/deb-systemd-helper-enabled/cups.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/cups.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/virtlockd.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/virtlockd.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/gpsd.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/gpsd.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/cups.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/virtlockd.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/gpsd.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/lvm2-lvmetad.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/binfmt-support.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/binfmt-support.service ==> /var/lib/systemd/deb-systemd-helper-enabled/cups.path.dsh-also <== /etc/systemd/system/multi-user.target.wants/cups.path ==> /var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation-early.service.dsh-also <== /etc/systemd/system/local-fs.target.wants/lvm2-activation-early.service ==> /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/rsyslog.service /etc/systemd/system/syslog.service ==> /var/lib/systemd/deb-systemd-helper-enabled/sysinit.target.wants/lvm2-lvmetad.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/apt-cacher-ng.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/apt-cacher-ng.service ==> /var/lib/systemd/deb-systemd-helper-enabled/gpsd.service.dsh-also <== /etc/systemd/system/sockets.target.wants/gpsd.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation.service.dsh-also <== /etc/systemd/system/local-fs.target.wants/lvm2-activation.service ==> /var/lib/systemd/deb-systemd-helper-enabled/syslog.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/lvm2-lvmetad.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/lvm2-lvmetad.socket /etc/systemd/system/sysinit.target.wants/lvm2-lvmetad.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/libvirt-guests.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/libvirt-guests.service ==> /var/lib/systemd/deb-systemd-helper-enabled/haproxy.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/haproxy.service ==> /var/lib/systemd/deb-systemd-helper-enabled/cron.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/cron.service ==> /var/lib/systemd/deb-systemd-helper-enabled/libvirt-bin.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/libvirt-bin.service ==> /var/lib/systemd/deb-systemd-helper-enabled/virtlockd.service.dsh-also <== /etc/systemd/system/sockets.target.wants/virtlockd.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/libvirt-bin.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/apt-cacher-ng.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/binfmt-support.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/haproxy.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/libvirt-guests.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cron.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups.path <== ==> /var/lib/systemd/deb-systemd-helper-enabled/cups.service.dsh-also <== /etc/systemd/system/sockets.target.wants/cups.socket /etc/systemd/system/multi-user.target.wants/cups.path /etc/systemd/system/printer.target.wants/cups.service ==> /var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation-early.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/printer.target.wants/cups.service <== -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.2 ii libacl1 2.2.52-1 ii libaudit1 1:2.3.7-1 ii libblkid1 2.20.1-5.8 ii libc6 2.19-7 ii libcap2 1:2.22-1.2 ii libcap2-bin 1:2.22-1.2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.6-1 ii libgcrypt11 1.5.3-4 ii libkmod2 18-1 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.3-1 ii libsystemd-daemon0 208-8 ii libsystemd-journal0 208-8 ii libsystemd-login0 208-8 ii libudev1 208-6 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.2 ii udev 208-6 ii util-linux 2.20.1-5.8 Versions of packages systemd recommends: pn libpam-systemd <none> Versions of packages systemd suggests: pn systemd-ui <none> -- no debconf information
--- End Message ---
--- Begin Message ---Hi Johannes On Thu, 21 Aug 2014 16:33:40 +0200 Johannes Schauer <j.scha...@email.de> wrote: > Package: systemd > Version: 208-8 > Severity: normal > > Hi, > > after removing the "quiet" kernel boot option, I see the following > message before I'm dropped into emergency mode: > > [ TIME ] Timed out waiting for device dev-mapper-volumegroup/x2dhome.device. > [DEPEND] Dependency failed for /home > [DEPEND] Dependency failed for Local File Systems. > > Here is my fstab: > > --%<----------------------------------------------------------------------- > # <file system> <mount point> <type> <options> <dump> <pass> > proc /proc proc defaults 0 0 > /dev/mapper/volumegroup-root / ext4 errors=remount-ro 0 > 1 > UUID=ac034ff5-d28a-4ad1-8bac-97d554395e3e /boot ext2 defaults > 0 2 > /dev/mapper/volumegroup-home /home ext4 defaults 0 2 > /dev/mapper/volumegroup-swap none swap sw 0 0 > /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > cgroup /sys/fs/cgroup cgroup defaults 0 0 > tmpfs /tmp tmpfs nodev,nosuid,size=8G 0 0 > tmpfs /run tmpfs nodev,nosuid,size=8G 0 0 > tmpfs /var/lib/schroot/unpack/ tmpfs nodev,nosuid,size=8G > 0 0 > -->%----------------------------------------------------------------------- > > My lvm2 version is 2.02.109-1 > > Here is the "udevadm info" output for /dev/mapper/volumegroup-home: > > --%<----------------------------------------------------------------------- > P: /devices/virtual/block/dm-3 > N: dm-3 > L: 50 > E: DEVNAME=/dev/dm-3 > E: DEVPATH=/devices/virtual/block/dm-3 > E: DEVTYPE=disk > E: DM_NAME=volumegroup-home > E: DM_STATE=ACTIVE > E: DM_TABLE_STATE=LIVE > E: DM_TYPE=raid > 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: > DM_UUID=LVM-ZrtPTxYRO88LRxfFiUfqELhK7tE4YTTNBfnUKnN3SCnNObmn0Hg0EkyGAIqVHMvJ > E: MAJOR=253 > E: MINOR=3 > E: SUBSYSTEM=block > E: USEC_INITIALIZED=42402 > -->%----------------------------------------------------------------------- > > If I boot with sysvinit then everything works as expected. > > Downgrading to systemd 204-14 also makes everything work again [1]. So this is > probably a regression between 204-14 and 206-8. > > Here is the output of "journalctl -alb" [2]. I'm going to close this old bug report as a lot has changed in lvm2 and systemd between 2014 and 2019 so it's unlikely that the issue you've seen back then still applies and atm this bug report only seems to attract spammers like in [1] Johannes, if you still encounter problems with a current version of systemd (i.e. v232 or better v241) in combination with lvm2/cryptsetup, please let us know. Regard [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758808#199 -- 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
--- End Message ---
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers