Am Sonntag, den 11.09.2011, 16:13 +0200 schrieb Thomas Meyer: > by the way this is what the autofs4 driver prints with DEBUG on: > > [ 80.647981] systemd[1]: Startup finished in 3s 172ms 670us (kernel) + 1min > 15s 79ms 379us (initrd) + 2s 395ms 847us (userspace) = 1min 20s 647ms 896us. > [ 177.543865] pid 1: autofs4_fill_super: starting up, sbi = ffff8800374d5f00 > [ 177.543876] pid 1: autofs4_fill_super: pipe fd = 17, pgrp = 1 > [ 177.543887] SELinux: initialized (dev autofs, type autofs), uses > genfs_contexts > [ 177.544336] pid 1: autofs4_d_manage: dentry=ffff880037be16c0 / > [ 177.544728] pid 1: autofs4_d_manage: dentry=ffff880037be16c0 / > [ 177.544744] pid 1: autofs4_dentry_release: releasing ffff880037be1780 > [ 202.609293] pid 434: autofs4_d_manage: dentry=ffff880037be16c0 / > [ 202.609298] pid 434: autofs4_d_automount: dentry=ffff880037be16c0 / > [ 202.609301] pid 434: autofs4_mount_wait: waiting for mount name=/ > [ 202.609307] pid 434: autofs4_wait: new wait id = 0x00000001, name = > ffff880037be16c0, nfy=1 > [ 202.609309] > [ 202.609312] pid 434: autofs4_notify_daemon: wait id = 0x00000001, name = > ffff880037be16c0, type=5 > [ 202.615889] pid 1: autofs4_d_manage: dentry=ffff880037be16c0 / > [ 202.713641] pid 435: autofs4_d_manage: dentry=ffff880037be16c0 / > [ 202.714362] pid 435: autofs4_d_manage: dentry=ffff880037be16c0 / > [ 202.714559] SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses > genfs_contexts > [ 202.714740] pid 435: autofs4_d_manage: dentry=ffff880037be16c0 / > [ 210.649091] pid 434: autofs4_mount_wait: mount wait done status=-4 >
yes, there seems to be a problem with the autofs4 mounts. I just found a way to boot into a working system with an x86_64 kernel and a x86 userland by omitting all automounts! 1.) boot into systemd emergency mode 2.) start all *.mount points that have an corresponding *.automount unit: i.e.: # systemctl start dev-hugepages.mount # systemctl start dev-mqueue.mount # systemctl start proc-sys-fs-binfmt_misc.mount # systemctl start sys-kernel-debug.mount # systemctl start sys-kernel-security.mount (make sure to not have any automount in your /etc/fstab (with comment=systemd.automount) 3.) start graphical target # systemctl start graphical.target This will boot into a working system at least with my Fedora 15 installation. mfg thomas _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
