[Mythbuntu-bugs] [Bug 83831] Re: Boot failed to complete after fsck
** No longer affects: null -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/83831 Title: Boot failed to complete after fsck Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Invalid Status in Usplash: Invalid Status in “sysvinit” package in Ubuntu: Invalid 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. To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/83831/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 83831] Re: Boot failed to complete after fsck
** Changed in: sysvinit (Ubuntu) Status: Confirmed => Invalid ** Changed in: usplash Status: New => Invalid -- 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: Invalid Status in “sysvinit” package in Ubuntu: Invalid 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. ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 83831] Re: Boot failed to complete after fsck
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. ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
