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

[VinDSL]

I'm having this issue as well, on my Ubu 12.04 alpha 1 install.  It
happened after the 5-Jan-2011 update(s).  I'm performing forensics now.

The --no-log workaround (above) allowed me to boot into Ubu 12.04

I might also mention...

I have two kernels installed on this machine - Linux 3.1 & Linux 3.2 -
and this init bug caused a kernel panic in both of them.

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

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