Am 12.01.2013 04:16, schrieb Mathieu Roy: > Package: systemd > Version: 44-7 > Severity: normal > > Hi, > > The system partition had an erroneous last mount time (due to a misconfigured > BIOS time) in the future. At the point where fsck provide an error message, > there was no way to proceed either by getting a console and doing a manual > fsck (like CTRL-D) or simply disregard the error (like CTRL-C). > > I found no other option than to reboot with a rescue image. Quite painy just > for a so trivial fsck fix - with no real error on the disk. > > How come I did not get at least a shell access? (I tried single mode without > any effect) What did I miss?
So this issue only happened once, i.e. after the fsck? What was the last message you've seen? I did have a few kernel crashes in the past any never had a problem with systemd-fsck getting stuck in a way when reparing the file system. To get a more verbose boot, you can follow the instructions at [1] Michael [1] http://www.freedesktop.org/wiki/Software/systemd/Debugging -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
