[Bug 506727] Re: upstart fails to start system into multiuser mode

Curtis Hovey curtis.hovey at canonical.com
Fri Nov 11 21:24:27 UTC 2011


** No longer affects: null

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/506727

Title:
  upstart fails to start system into multiuser mode

Status in “mountall” package in Ubuntu:
  Fix Released

Bug description:
  
  Unfortunately I am not able to get upstart to start my system.

  Initially this was because of #505530, but with the supplied patch
  applied, mountall succeeds and I am no longer dropped into 'mountall-
  shell.conf'

  Instead the system boots, Upstart runs but it never gets to the point
  where it goes to runlevel 2 (i.e. start rc RUNLEVEL=2).

  Unfortunately I do not know of any way I can capture the output of
  '/sbin/init -v --debug' (which might have some clues); even booting
  the system with 'init=/bin/bash' and then trying to redirect things
  does not work.

  The only way I have been able to bring my system up is by:
   - booting with 'init=/bin/bash'
   - modifying /etc/init/mountall.conf and placing in its 'post-script script' the line 'start tty2'
   - logging in and running X (manually in failsafe mode, normal mode does not work).

  The kernel version is 2.6.32-9-generic (2.6.32-10-generic fails to
  boot) and upstart is 0.6.3-11

  What would be really useful is a command line option to tell you what
  upstart (init) would run, in what order, but not actually do it. What
  would also be useful is something to indicate which jobs had already
  been run.

  Any debugging assistance would be greatly appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/506727/+subscriptions




More information about the foundations-bugs mailing list