Work-arounds for this problem:
= Work-Around 1 =
Boot with '--no-log' on kernel command-line.
EFFECT: This will disable all job log output. This is potentially rather
extreme, so users may wish to use work-around 2 below.
= Work-Around 2 =
1) Boot with '--no-log' on kernel command-line.
2) Disable the flush-early-job-log job:
echo manual | sudo tee /etc/init/flush-early-job-log job.override
3) Reboot.
EFFECT: This will throw away data that jobs produce before the disk
becomes writeable, which tends to be minimal since only a very few jobs
start this early in the boot process.
File /etc/init/flush-early-job-log job.override should be deleted once a
fix for this bug is available in Ubuntu.
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New => Fix Committed
** Changed in: upstart
Status: Fix Committed => In Progress
** Changed in: upstart
Importance: Undecided => High
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096531
Title:
After touch /forcefsck and reboot: Assertion failed in
log_clear_unflushed
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1096531/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
