Hi,
On 14-11-15 14:09, Michael Biebl wrote:
And alternative could be, to attach the output of systemd-analyze and
"systemd-analyze blame" when such a long fsck happens.
I thought I had already done that, but here it is again in full.
$ systemd-analyze
Startup finished in 3.802s (kernel) + 9mi
Am 14.11.2015 um 13:54 schrieb Manuel Bilderbeek:
> Hi,
>
> On 14-11-15 13:49, Michael Biebl wrote:
>> Please keep in mind, that fsck for / and /usr is run in the initramfs
>> nowadays and systemd is not yet involved.
>> Can you boot and removing "quiet" from the kernel command line.
>> This shoul
Hi,
On 14-11-15 13:49, Michael Biebl wrote:
Please keep in mind, that fsck for / and /usr is run in the initramfs
nowadays and systemd is not yet involved.
Can you boot and removing "quiet" from the kernel command line.
This should give you more log messages from systemd.
OK, I'll try that.
I
Am 14.11.2015 um 13:23 schrieb Manuel Bilderbeek:
> Package: systemd
> Version: 227-2
> Followup-For: Bug #804910
>
> Hi,
>
> Strangely enough, today it happened again:
>
> [4.582220] input: HDA Intel Line Out Side as
> /devices/pci:00/:00:1b.
> 0/sound/card0/input17
> [4.582280
