always check disk for error upon starting

[Zhang Weiwu]

Binary package hint: upstart

Samsung X10 with Ubuntu 10.10, a new installation. Ubuntu booting always check disk for error.

While it always happen to me, I am not sure if this would happen with a clean shutdown, as I never managed to. I suffer from the phenomenon of not possible to clean shutdown, as described in #629919. Although I can successfully reboot (also a phenomenon of #629919) but successful reboot results a disk check anyway.

That's all information I can provide. The splash screen concealed other information that might be useful, like which partition is being checked (can it be the dual-boot windows partition?) and what reason it is checked (not clean shut down? something wrong with the clock that make upstart think check haven't been done in a decade or so?).

I'll provide other info on requests.

[Clint Byrum (clint-fewbar)]

Hello Zhang, thank you for taking the time to file this bug report and help us make Ubuntu better!

I believe this is actually the function of 'mountall', not upstart, and will rell re-assign it as such.

One simple thing that might cause this is the existence of a file, /forcefsck . If that file exists, then fsck will happen on every system boot.

If that file exists, can you try removing it and rebooting?

It should actually always be removed when mountall is stopped for the reboot, but there may be a bug in that.

Marking Incomplete pending response from Zhang.

Setting Importance to Medium as this would be a fairly important problem for any user that it might affect.

[Zhang Weiwu (zhangweiwu)]

Thanks. I followed advice of another Ubuntu user to remove the 'splash quiet' tag from grub.cfg to have the following discovery:

- every time boots it says file system was not cleanly shut down that a check is forced.
- every time when I shut down the PC (strangely now I can shut down the PC) the last message on the screen is:
-> umount / : file system busy

Both messages are according to my memory, thus not exact, but the time is too short to write down the messages.

So the case look obvious to me now, that for some reason the root file system could not be successfully umounted when shut down.

I don't have /forcefsck file.

[Zhang Weiwu (zhangweiwu)]

Reading the description of #616287 I am pretty sure now that this bug I report is a duplicate of #616287 thus I marked this bug invalid.