After touch /forcefsck and reboot: Assertion failed in log_clear_unflushed
Bug #1096531 reported by
Blair Zajac
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Fix Released
|
High
|
James Hunt | ||
upstart (Ubuntu) |
Fix Released
|
High
|
James Hunt | ||
Bug Description
I made a copy of raring-
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: upstart 1.6.1-1ubuntu1
ProcVersionSign
Uname: Linux 3.7.0-7-generic x86_64
ApportVersion: 2.7-0ubuntu2
Architecture: amd64
Date: Sun Jan 6 06:39:07 2013
MarkForUpload: True
ProcEnviron:
TERM=screen
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
Changed in upstart: | |
status: | In Progress → Fix Committed |
Changed in upstart (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in upstart: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The one issue with the KVM image is that it'll hang for 2 minutes upon boot and not tell you its 'ubuntu' user password.
I can reproduce this using the daily server ISO:
- Download rsync:/ /cdimages. ubuntu. com/cdimage/ ubuntu- server/ daily/current/ raring- server- amd64.iso server- amd64.iso
- Start VirtualBox
- Make a new VM with the raring-
- Do a minimal install
- Reboot into the new OS
- sudo touch /forcefsck
- sudo /sbin/shutdown -r now