Comment 1 for bug 58834

I'm not sure it's a duplicate, the problem here is not the lack of info on screen, the problem is fsck being killed by something (upstart?) and causing an endless reboot sequence. It actually happened with 0.1.X when info was displayed, fsck reached 85-90% aprox and the system rebooted.

By the way, I agree that the relevant info on screen will help (https://launchpad.net/bugs/58609)