Hello,
I also ran into this problem while testing systemd a bit.
I booted the system using systemd and then rebooted it after some time.
After using the system for a few minutes / was remounted read-only
because of filesystem errors.
On reboot systemd-fsck announced an "unexpected inconsistency"
Package: systemd
Version: 44-11
Followup-For: Bug #697962
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
I just ran into the same problem. In my case, fsck said that a manual
fsck was required for my /home and stopped here. If I reboot, I get
the same problem over and over. The only way out
--- Begin Message ---
Le samedi 12 janvier 2013, vous avez écrit :
> On 12.01.2013 12:14, Mathieu Roy wrote:
> > Le samedi 12 janvier 2013, Michael Biebl a écrit :
> >> Since the problem is not reproducible here, we will a need more verbose
> >> debug log from you. Please follow the instruction in
On 12.01.2013 12:14, Mathieu Roy wrote:
> Le samedi 12 janvier 2013, Michael Biebl a écrit :
>> 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.
>
> I'll redo some test toying with the BIOS
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
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 getti
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
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
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
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 C
10 matches
Mail list logo
