I have got a similar problem as #118. I install Arch Linux as a VirtualBox guest system. Once up and running, I install systemd to replace the default initscripts startup system. After restarting, I am thrown into 'emergency mode' and am greeted by random modprobe messages (see the attached screenshot). Going from there, I can login as root but all mounts save for the system partition seem to have failed. If I press Ctrl+D twice or try "systemctl default" as suggested, I get multiple "worker [XXX] did not accept message -1" lines.
If I switch back to the initscripts system, the system boots fine. Most curiously, the host system is also running Arch Linux with systemd and it never failed during boot. ** Attachment added: "archlinux-systemd-udev.png" https://bugs.launchpad.net/ubuntu/+source/udev/+bug/647404/+attachment/2610682/+files/archlinux-systemd-udev.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/647404 Title: Udev worker error during boot "worker [XX] did not accept message -1 (Connection refused), kill it To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/647404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
