Comment 6 for bug 22460

I agree with Andy, obviously, since his first suggestion is identical to the one I made in my initial description. Except I also think the user should be able to run the fsck during session 29 in order to avoid it the next boot.

About letting the user know how to cancel it, I also agree. In any case the way it is done now at boot is horrible, a ASCII progress bar and lots of technical jargon. I'd propose changing the usplash progress bar to track the fsck progress and give the user a better description of what's happening (something simple), and also do a screen clear so the other boot messages are not shown during the check.

Anyway, maybe you could link to the forum thread here for reference, Andy?