| Summary: | Systemd-fsck fails on "Superblock last time mount is in future" error | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Michal Vyskocil <mvyskocil> |
| Component: | general | Assignee: | Lennart Poettering <lennart> |
| Status: | RESOLVED NOTOURBUG | QA Contact: | |
| Severity: | blocker | ||
| Priority: | high | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | The generated core dump | ||
Same issue, the problem is upon shutdown the local time (CET) is stored in the CMOS clock, it is however regarded as UTC time when the system boots, presumably due to the BIOS setting `System time is UTC'. Now ANY mount attempt on ANY disk will complain about the superblock from the future, and only booting it from a live-distro lets us fix this issue *ONCE* (by running fsck manually and shutting down without dumping the system time to the CMOS) because the next time we reboot the computer the funny dance will start again, because the wrong CMOS time is used again. All sane distributions patch this out of e2fsck. The error cause simply makes no sense. This should fix in e2fsck, not in systemd. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 48178 [details] The generated core dump Once upon a time, when my CMOS batter said hello and my system had wrong system time, I booted, because thought the ntp server will correct that from me during boot, so I don't need to care. However the boot ends up very quickly with (I use systed.log_level=debug) <31>systemd[1]: Installed new job fsck@dev-disk-by-id\x2did-ata\x2dST3250410AS_6RY03RYA-part5 as 235 <31>systemd[1]: Installed new job media-sda5.mount/stop as 236 <31>systemd[1]: Installed new job sound.target/stop as 237 <31>systemd[1]: Enqueued job emergency.target/start as 141 <31>systemd[1]: Assertion 'j->installed' failed at src/manager.c:1202, fsck@... <27>systemd[1]: Caught <ABRT>, dumped core as pid 654. <30>systemd[1]: Executing crash shell in 10s... <30>systemd[1]: succesfully spawned crash shall as pid 660. <30>systemd[1]: Freezing execution. <27>systemd-fsck[631]: Failed to start unit: Did not not receive the reply or ... <27>systemd-cgroups-agent[661]: Failed to get D-Bus connection: Failed to c... However no crash shell appeared, even if I boot with init=/bin/systemd systemd.log_level=debug systemd.dump_core=true systemd.crash_shell=true systemd.crash_chvt=1 So I have started my systemd with systemd.unit=emergency.target and try to run fsck manually # fsck /dev/sda5 fsck from util-linux 2.19.1 e2fsck 1.41.14 (22-Dec-2010) Superblock last mount time (Wed Jun 15 13:11:59 2011, now = Sun May 15 02:01:30 2011) is in the future. Fix[y]? n ... So I went to BIOS, setup the correct time and system started well. Used systemd-28 on openSUSE 12.1.