maximal mount count but no fsck

[Ernst Zlo]

Binary package hint: mountall

I'm running Karmic on VirtualBox.
While messages tell me, "warning: maximal mount count reached, running e2fsck is recommended" nothing happens for several boots to solve this problem.

There is either no fsck launched automatically or if it is launched, it doesn't reset the counter.
Some warning on the boot screen disappears that fast, that I (and I assume nobody else) can read it. I'm not able to get a screenshot either <g>

And if I could read, it would be of no use anyway:
I'm not thrown back in a maintainance shell as expected.
There is no warning in GNOME after boot - which means IMHO that the "normal" user will never see this warning.

I have 2 harddisks (one for Ubuntu, one for data) and an additional VirtualBox drive, (shared directory) which is mounted with fstab during startup.

I include a file with the warnings of the last 4 boots and the complete protocol of the very last boot.

ProblemType: Bug
Architecture: i386
Date: Thu Oct 22 09:52:18 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20091008)
Package: mountall 0.2.5
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: mountall
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gnome-settings-daemon:1381): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1381): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1413): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1453): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Johan Kiviniemi (ion)]

Is the sdb5 partition in /etc/fstab?

[Ernst Zlo (ernst-zlo)]

Yes:
# /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 defaults 0 0
# / was on /dev/sda1 during installation
UUID=11e3384a-80a9-4d33-8206-8d44e91dd9c1 / ext4
errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=f9311fd5-da18-41c0-9648-4cc6e1316210 none swap sw
0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0
0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0
0
# zlo zlo zlo zlo zlo zlo zlo zlo zlo zlo zlo zlo zlo zlo zlo zlo
extras /media/xtra vboxsf uid=1000,gid=1000,rw 0 0
/dev/sdb5 /media/daten ext4 rw,nosuid,nodev,uhelper=devkit 0 0

Am Donnerstag, den 22.10.2009, 08:23 +0000 schrieb Johan Kiviniemi:
> Is the sdb5 partition in /etc/fstab?
>

[Johan Kiviniemi (ion)]

You have a zero value in the fs_passno field. Quoting the fstab(5) man page:

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.

If setting it to a number greater than zero doesn’t fix the problem, please reopen the bug.

[Ernst Zlo (ernst-zlo)]

Thank you, it's gone! Sorry for the trouble!