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

[Kaulbach]

The pastebin from posting number 2 is mine, and yes the same problem. I manually wrote down from the kernel panic screen then transcribed it to a file while in recovery mode, used pastebinit to post.
Installing the upstart version mentioned earlier, it finally allowed me to boot normally.
Previously it would say it's doing a core dump but could never find one on the disk.
Also when booting to recovery mode, issuing: shutdown -h now would give the same kernel panic.
Posting number 10 at http://ubuntuforums.org/showthread.php?s=55d242cb643cf1b8293c27b55351e73e&t=1904842 seems to offer a possible solution with:
dpkg -l |awk ‘/^rc/ {print $2}’ |xargs sudo dpkg --purge

to clear out old conf files

-- 
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