fsck fails under upstart

[Quim Calpe]

When a fsck is scheduled at boot time, fsck can't complete the process and the system reboots, dunno if upstart respawns any process because of it take too long.

In a worst case scenario, filesystem is marked as unclean, and every boot will try to fsck the partition and will fail rebooting, resulting in an unbootable system. I had to boot from Dapper LiveCD and fsck my root partition.

Tried to login and kill fsck before it is respawned or fails, but killing it also reboots the system.

It can be reproduced forcing fsck at boot with 'sudo touch /forcefsck' and rebooting

Thanks!

[Quim Calpe (quimcalpe)]

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)

[Scott James Remnant (Canonical) (canonical-scott)]

As noted in the other bug, it's perfectly normal for the checkfs script to reboot if it cannot open a sulogin shell. That's all that's happening here.

[Quim Calpe (quimcalpe)]

Ok then, sorry for the inconvenience