UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future")
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
util-linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Binary package hint: mountall
I get "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY" on booting, then it fails to start or provide me a shell.
I had this happening since some days already: the first boot would tell me that fsck failed, but a reboot (straight after pressing Ctrl-D) went through without any problems.
Now (IIRC) Ctrl-D did not do anything. I've used Alt-SysRq-K, which caused a kernel panic ("trying to kill init").
I'm not sure if all that FAIL is caused by "Superblock last mount time is in the future". It's mentioned in the e2fsprogs changelog at least:
* E2fsck will now print much fuller information when the last mount
time or last written time is in the future, since most people can't
seem to believe their distribution has buggy init scripts, or they
have a failed CMOS/RTS clock battery.
WORKAROUND:
Adding the following to "[options]" in /etc/e2fsck.conf, running update-initramfs and rebooting fixed it for me:
buggy_init_scripts = 1
description: | updated |
affects: | ubuntu → mountall (Ubuntu) |
affects: | mountall (Ubuntu) → linux (Ubuntu) |
affects: | mountall (Ubuntu) → util-linux (Ubuntu) |
Running fsck manually:
ubuntu@ubuntu:/mnt$ sudo fsck /dev/md0
fsck 1.40.8 (13-Mar-2008)
e2fsck 1.40.8 (13-Mar-2008)
/dev/md0 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/md0: 68/50200 files (10.3% non-contiguous), 90611/200704 blocks