[Bug 912558] Re: log.c Assert failed - err=>number == EIO

[James Hunt]

If you have this problem, it would be *very* helpful to use if you could
run the attached script on your system.

Please report back if you got any output from the script. If the script
produces no output, you should not have a problem.

Process:

1) download script to your system.
2) chmod 755 find_missing_commands.sh
3) ./find_missing_commands.sh
4) report back results on this bug.

Thanks very much!

** Attachment added: "find_missing_commands.sh"
   https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/912558/+attachment/2660435/+files/find_missing_commands.sh

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

Title:
  log.c Assert failed - err=>number == EIO

Status in “upstart” package in Ubuntu:
  Confirmed
Status in “upstart” source package in Precise:
  Confirmed

Bug description:
  Whilst booting, init has an issue and causes a core dump -> kernel
  panic.

  Appending --no-log to the kernel cmd line allows a successful boot.

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