>From the description and comments it does not look like Upstart is doing
anything wrong here, though this may be a bug with the initscripts that
run fsck
** Changed in: upstart
Status: New => Invalid
** Package changed: upstart (Ubuntu) => sysvinit (Ubuntu)
--
Boot failed to complete after fsck
https://bugs.launchpad.net/bugs/83831
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
