I'm also able to see this happening while using the linaro-nano image (just a minimal rootfs based on ubuntu oneiric).
The failsafe service will always be called, because of the upstart script dependencies: "start on filesystem and net-device-up IFACE=lo" This just exists so rc-sysinit.conf can also be called after failsafe: "start on (filesystem and static-network-up) or failsafe-boot" On my case I need to debug upstart to see why the static-network-up event wasn't available at the time failsafe-boot finished, still in progress. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/856810 Title: Boot hangs at "Booting system without full network configuration..." To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-ubuntu/+bug/856810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
