Public bug reported:
Binary package hint: e2fsprogs
My ext3 filesystem (originally created by Ubuntu Feisty, with a sequence
of upgrades since then) has currently been mounted over 30 times since
its last check, thus forcing a fsck on boot. If I skip the fsck with the
Esc key, everything continues as normal and the boot completes. However,
if I let fsck run, then:
- the fsck continues as normal until it reaches 89%
- the hard drive activity light goes off
- the hard drive makes a sound it normally only makes at system shutdown
(although I don't know for certain, it's probably the noise of the hard drive
being turned off altogether)
- after several minutes, the fsck progress continues to 90%
- the system then hangs thereafter.
This happens whether I try to boot normally or in recovery mode; in
recovery mode, this is what the bottom of the screen looks like when it
hangs (retyped by hand from the view on screen, so may possibly contain
typos; some of this information is almost certainly unrelated, but I
haven't edited the portion of the log in question):
init: bootchart main process (441) terminated with status 1
fsck from util-linux-ng 2.16
udevd[446]: NAME="%k" is superfluous and breaks kernel supplied names, please
remove it from /etc/udev/rules.d/60-kqemu.rules:1
WARNING: All config files need .conf: /etc/modprobe.d/kqemu, it will be ignored
in a future release
WARNING: All config files need .conf: /etc/modprobe.d/kqemu, it will be ignored
in a future release
WARNING: All config files need .conf: /etc/modprobe.d/kqemu, it will be ignored
in a future release
WARNING: All config files need .conf: /etc/modprobe.d/kqemu, it will be ignored
in a future release
init: bootchart post-stop process (450) terminated with status 1
os_part has been mounted 35 times without being checked, check forced
Filesystem checks are in progress (ESC to cancel):
[######################################################------]
At this point, pressing ESC to cancel the fsck doesn't work; ESC,
control-C, and control-backslash do nothing but echo on screen as ^[,
^C, ^\ respectively (they likewise do nothing outside recovery mode, as
the echo's aren't visible). Control-alt-delete does work from this
state, and causes the system to do a controlled shutdown and reboot; but
another fsck happens on the resulting reboot.
Suspiciously, the reboots aborted due to fsck hanging don't appear in
syslog at all (either that, or they do and I can't find them); only the
boots where I escaped the automatic fsck are shown.
Expected behaviour is for the fsck to complete and for the boot sequence
to continue. This drive has fscked correctly with Karmic before; the
only potentially relevant change to packages that I can remember is when
ureadahead was installed by the update manager (I run karmic-proposed).
Although this bug has similar symptoms to bug #387692, I think it's a
different bug; in that bug, the fsck actually completed and the system
hung immediately afterwards, whereas in this one, the fsck itself is
hanging.
ProblemType: Bug
Architecture: i386
Date: Tue Nov 24 18:02:10 2009
DistroRelease: Ubuntu 9.10
Package: e2fsprogs 1.41.9-1ubuntu3
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: e2fsprogs
Uname: Linux 2.6.31-15-generic i686
XsessionErrors:
(gnome-settings-daemon:2939): GLib-CRITICAL **: g_propagate_error: assertion
`src != NULL' failed
(gnome-settings-daemon:2939): GLib-CRITICAL **: g_propagate_error: assertion
`src != NULL' failed
(nautilus:3032): Eel-CRITICAL **: eel_preferences_get_boolean: assertion
`preferences_is_initialized ()' failed
(polkit-gnome-authentication-agent-1:3045): GLib-CRITICAL **:
g_once_init_leave: assertion `initialization_value != 0' failed
** Affects: e2fsprogs (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
Scheduled fsck during boot hangs at 90%, preventing boot sequence completing
https://bugs.launchpad.net/bugs/487744
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
