Ubuntu
mountall package

No fsck progress when splash is disabled

Bug #605403 reported by Richard Griswold on 2010-07-14

This bug report is a duplicate of: Bug #540645: no fsck messages shown in details mode (no splash on cmdline). Edit Remove

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	mountall (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: mountall

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.

> lsb_release -r
Release: 10.04

> uname -a
Linux laptop 2.6.34-020634-generic #020634 SMP Mon May 17 19:27:49 UTC 2010 x86_64 GNU/Linux

2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.

> apt-cache policy mountall
mountall:
  Installed: 2.15
  Candidate: 2.15
  Version table:
*** 2.15 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
        100 /var/lib/dpkg/status
     2.14 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages

3) What you expected to happen

When splash is disabled and a filesystem check is forced, fsck reports the progress of the check.

4) What happened instead

When splash is disabled and a filesystem check is forced, fsck does not report the progress of the check, giving the appearance that the system is hung or in a tight loop (since the hard drive activity light is on). The system prints the following messages to the console, but nothing more until the check finished:

fsck from util-linux-ng 2.17.2
root has been mounted 40 times without being checked, check forced.

This problem was mentioned in comment 12 of bug #571707 (https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/571707/comments/12), but that bug was for a problem with plymouth, and in reading through the rest of the comments it does not appear that the fix for plymouth addressed this specific problem. This is also similar to bug #446596 (https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/446596), but that bug was for Karmic, and not Lucid, and was already fixed.

I've attached the boot.log for the system. In addition to the two messages above, the file also contains the final output of fsck. This also showed up on the console after fsck had finished it's checks.