tags 697962 + moreinfo unreproducible thanks On 12.01.2013 07:02, Mathieu Roy wrote: > Le samedi 12 janvier 2013, Michael Biebl a écrit : >> On 12.01.2013 04:30, Michael Biebl wrote: >> >>> 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. >> >> Just want to rule out that the fsck isn't a red herring. >> If you fsck your file system with the rescue media, is the system >> booting correctly again? > > Yeah. No problem. > I could have set the BIOS time to something in the future, it would have > worked too.
I just tried that: set back the bios clock for a few hours. During the next reboot I got a fsck which reported that the file system was modified in the future and systemd successfully mounted and continued. So I can not reproduce your problem. > >> What happens, when you modify the bios clock after that? I.e. is this a >> problem which you can reproduce reliably. > > I dont like so much rebooting and all, so I havent tried once more. But it > actually happening to me twice: first time I change the time in the BIOS, but > that was just a workaround. Second time I decided best to boot over a rescue > media (PXE actually) so it will actually mount with a correct time. Since the problem is not reproducible here, we will a need more verbose debug log from you. Please follow the instruction in the wiki I posted earlier. What kind of partition setup do you use? Which file systems? (post your fstab). -- 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
