fstab(5) should document that root filesystem is always checked with "force fsck"

mountall certainly does honour the "check" flag in /etc/fstab

Could you add --debug to the exec line in /etc/init/mountall.conf, touch /forcefsck, then reboot - after the boot attach /var/log/boot.log

Also please attach your /etc/fstab

Thanks

sorry for late reply, here my fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=4ef1693c-be99-4410-9d39-4c9136259de2 / ext3 errors=remount-ro 0 0
# swap was on /dev/sda5 during installation
UUID=6212b8ca-c27a-4861-80ee-cf41b296caa2 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

temp@pp /home/ingo/temp@pp vboxsf noauto 0 0

boot.log attached

This is intended behaviour for the root filesystem, and matches historical behaviour of Ubuntu since the dawn of time

(see bug #435707)

Then this has to bee assigned to 'man fstab', which says:

... If the sixth field is not present or zero, a value of zero
      is returned and fsck will assume that the filesystem does not need to
      be checked.

not only fstab(5) is affeccted, but fsck(8) as well, which states:

"After that, filesystems will be
              checked in the order specified by the fs_passno (the sixth)
              field in the /etc/fstab file. Filesystems with a fs_passno
              value of 0 are skipped and are not checked at all. Filesystems
              with a fs_passno value of greater than zero will be checked in
              order, with filesystems with the lowest fs_passno number being
              checked first.

The / filesystem always gets 0 for pass in /etc/fstab as its check is special and running fsck -A *must not* check / or you get filesystem corruption.

There are even more "oddities" with fsck in Lucid:

By default during installation additional filesystems selected for auto-mount will receive a "1" in column 6 of fstab, even if they are vfat (i.e. Win partitions). This results in enormous boot delays of Lucid, because those FAT-filesystems will be checked on every boot.

Correctly filesystems not native in Linux should be checked with the system they belong to - Win in this case.
This means, they either should be set to "0" in fstab column 6, or fsck options during boot should be modified.

And - of course to trace such unexpected beheaviour fsck/mountall shoud log its activities in

/var/log/fsck/checkfs

Bump.

Any news when this behavior is fixed?