mythbuntu-bugs team mailing list archive

[Stefan Pappalardo <stefan.pappalardo@xxxxxx>]

I think there won't be a fix because ubuntu switches to upstart, which
is not affected by this bug.

-- 
Boot failed to complete after fsck
https://bugs.launchpad.net/bugs/83831
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.

Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Invalid
Status in NULL Project: Invalid
Status in Usplash: New
Status in “sysvinit” package in Ubuntu: Confirmed

Bug description:
Binary package hint: upstart

After a large upgrade, having been away from home for a few weeks, I rebooted.  Two of my filesystems (/ and /home) were due for an automatic fsck based on elapsed time (180 days).  usplash timed out and progress was displayed on the console.  Both checks completed without problems, but after the fsck of /home completed, there was no further output on the console, and X didn't come up.  After waiting a few minutes, sysrq+t revealed a 'sleep' process running.  I checked various consoles, none of which had output except the one where the fscks had run (I forget which it was).

I gave up and pressed control+alt+delete, which resulted in a couple of messages from upstart about rc scripts exiting with signal 15, and then (surprisingly) X started, and the system did not reboot.  I rebooted it by hand, and the next boot was OK.