On 15/12/16 11:37, Michael Biebl wrote:
> Am 15.12.2016 um 07:31 schrieb Daniel Pocock:
>
>> Please look more closely ... 3 lines after that it says the fsck has
>> "Started" and then it gives another line about "cgroup is empty"
>>
>> Could that just be a fault with re-ordering the log entries in
Am 15.12.2016 um 07:31 schrieb Daniel Pocock:
> Please look more closely ... 3 lines after that it says the fsck has
> "Started" and then it gives another line about "cgroup is empty"
>
> Could that just be a fault with re-ordering the log entries in
> journald? Or maybe it is starting fsck
On 15/12/16 00:29, Michael Biebl wrote:
> Am 07.12.2016 um 17:36 schrieb Daniel Pocock:
>> I've observed this problem again today
>>
>> Looking more closely, I noticed that it started to fsck the mount
>> just before it tried to mount it. It didn't appear to wait for
>> fsck to finish:
>
>
Am 07.12.2016 um 17:36 schrieb Daniel Pocock:
> I've observed this problem again today
>
> Looking more closely, I noticed that it started to fsck the mount just
> before it tried to mount it. It didn't appear to wait for fsck to finish:
Fwiw, the log you provided doesn't seem to confirm that.
Am 07.12.2016 um 17:36 schrieb Daniel Pocock:
> Control: tags -1 - moreinfo
>
> I've observed this problem again today
>
> Looking more closely, I noticed that it started to fsck the mount just
> before it tried to mount it. It didn't appear to wait for fsck to finish:
>
>
>
>
> Dec 03
Control: tags -1 - moreinfo
I've observed this problem again today
Looking more closely, I noticed that it started to fsck the mount just
before it tried to mount it. It didn't appear to wait for fsck to finish:
Dec 03 10:51:37 systemd[1]: Started File System Check on
