Le samedi 12 janvier 2013, vous avez écrit : > 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.
This issue happened all the time as long at the BIOS time is < to the latest boot time (and as such the last mount time appears to be in the future). I never noticed any fsck problem before (and use systemd since several monthes). The last message I've seen it was the fsck error. unfortunately and obviously have no logs, so I dont remember the exact words. Anyway, neither CTRL-C or CTRL-D allowed me to get a shell. In case of such error, there should be a way to get back control. -- Mathieu Roy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
