On Wed, 20 Apr 2011 16:35:51 +0200 Christian Hesse <[email protected]> wrote:
> On Wed, 20 Apr 2011 16:04:55 +0200 > Lennart Poettering <[email protected]> wrote: > > > On Wed, 20.04.11 12:12, Christian Hesse ([email protected]) wrote: > > > > > > > > On Tue, 19 Apr 2011 17:02:51 +0200 Albert Strasheim > > > <[email protected]> wrote: > > > > Hello again > > > > > > > > I had the same problem again today trying to start a service. > > > > > > Hello everybody, > > > > > > I have the same problem on a number of Arch Linux Systems. The > > > boot process stalls untill dev-{vg-{home,swap},bt-boot}.device > > > times out after three minutes. After the system has booted /home > > > and /boot are not mountet, swap is not activated. Running > > > "systemctl start dev-vg-home.device" times out after three > > > minutes as well, however I can mount the filesystems manually. > > > > Sounds like LVM borkage. > > > > Note that you need an up-to-date LVM with udev support enabled and > > it must be the same version in your initrd as in your main system. > > This is lvm2-2.02.84-1 and udev-167-1. lvm2 is compiled with these > options (among others): > > --with-udevdir=/lib/udev/rules.d/ --enable-udev_sync > --enable-udev_rules > > So I assume everything should be fine. My initrd is up to date. > > Any ideas how to debug this? Ok, got one step further I think. The scripts in my initrd call $ /sbin/vgchange --sysinit -a y I think this breaks udev in any way? After calling $ vgchange -a n && vgchange -a y everything seems to work fine. I can run $ systemctl start dev-bt-boot.device without any delay. So what is acting the wrong way? -- Schoene Gruesse Chris _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
