Univention Bugzilla – Bug 36233
maintenance shell after reboot due to fsck fail (mount date in the future)
Last modified: 2017-05-02 15:29:44 CEST
Created attachment 6192 [details] fsck fail screenshot On the next reboot after an installation of a slave system the system ends up in a maintenance shell because fsck failed. fsck failed because the last mount time of the rootfs is in the future. There are different date/time set up between installation and reboot → The master had a time in the past. The slave got the date from the master while running univention-system-setup.
For full text search: > Checking root file system > [....] Checking root gile system...fsck from util-linux 2.20.1 > /dev/mapper/vg_ucs-root: Superblock last mount time (Mon Oct 20 11:12:43 2014, > now = Fri Oct 3 13:34:53 2014) is in the future. > > /dev/mapper/vg_ucs-root: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. > (i.e., without -a or -p options) > fsck dies with exit status 4 > failed (code 4) > > [....] An automatic file system check (fsck) on the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode. ... > [....] The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D to terminate the maintenance shell and restart the system. ... Reproducer: : > /forcefsck date --set '2014-12-13 14:15:16+0200' reboot Fix: printf '[options]\nbroken_system_clock = true\n' > /etc/e2fsck.conf
r57212 | Bug #36233 base: ignore clock skew Package: univention-base-files Version: 4.0.6-1.178.201501091016 Branch: ucs_4.0-0 Scope: errata4.0-0 2014-12-15-univention-base-files.yaml The file system check now ignores clock skew problems, which previously required manual interaction. r57213 | Bug #36233 base: e2fsck clock skew YAML
(In reply to Philipp Hahn from comment #1) > Reproducer: > : > /forcefsck > date --set '2014-12-13 14:15:16+0200' hwclock --utc --systohc > reboot
Fix: OK, big time differences does not end up in maintenance shell anymore. Code: OK YAML: OK
<http://errata.univention.de/ucs/4.0/58.html>
*** Bug 27807 has been marked as a duplicate of this bug. ***