Cannot escape from Boot time Disk Check

[B1ackcr0w]

Binary package hint: plymouth

Using Lucid i386 Desktop. Problem happens when normal boot is interrupted for regular disk check.

I get the message "Press C to escape Disk Checks in progress".

Pressing "C" does not interrupt the disk check. Pressing C has no effect at all. I have not found a workaround, there seems to be no option but to allow disk check to finish. A forced shutdown does not work, at next boot the check just starts again.

If check is left to finish, normal boot resumes with no other problems aparent.

[Steve Langasek (vorlon)]

Thank you for taking the time to report this bug and help to improve Ubuntu.

This looks like a duplicate of bug #571707, fixed in the mountall package in lucid-updates. Please check that you have mountall 2.15 installed.

[B1ackcr0w (b1ackcr0w)]

I think this bug is related to 57107, but is separate to it. 57107 is focussed of the speed of the disk check whereas my report was concerned with the fact that the disk check cannot be cancelled once it has started. if the two issues are caused by the same thing then this is a duplicate. But i filed this in case 57107 gets fixed but you still can't escape the disk check

[Steve Langasek (vorlon)]

Bug #571707 is *already* fixed. Please verify that you have the correct version of mountall installed.

[rupert (r-plumridge)]

This bug is NOT the same as 571707.

The bug behaviour is now different from described above and I believe the change is a result of the fix applied to fix bug 57107.

Some history - I experienced bug 571707 and this bug. fsck would take ages at around 85% and pressing C wouldn't exit out of it. I applied the fix as mention in 571707, which fixed that bug.

Now, however, if you try and exit the boot time disk check by pressing C, you get an error saying that serious errors were found on your disk and then various options to recover from this problem. At whatever time you press C, you get this message, and leaving fsck to run without interruption shows no disk errors.

[rupert (r-plumridge)]

The two fsck logs are completely empty (they say nothing yet logged), but the boot.log says something vaguely useful.

[Martin Erik Werner (arand)]

There are several bugs in this chain of events:
Bug #571707 concerns the stalling (slowing) of plymouth/mountall progress (the 70% thing), this also leads to plymouth/mountall not acknowledging the C for cancel.

Bug #577331 concerns the fact that the filesystem check, when cancelled sucessfully, cannot be ignored

Bug #582035 concerns the error reported by fsck (making plymouth display "serious errors")

The first two of those are already fixed, the last has been fixed upstream, and in Debian, but is not in ubuntu yet.

I think those three report cover all issues adressed here (and in many other duplicates floating around, unfortunately)

[rupert (r-plumridge)]

Ok dokes, I'll keep an eye on those bugs you mention and wait till the updates are pushed out - then I'll report back here if the problem still exists. Sounds like it was a right pita for the devs ;)

[rupert (r-plumridge)]

Just to confirm - this bug, as reported, is now fixed for me.