Hi,
On 29-11-15 01:28, Michael Biebl wrote:
Can you boot with systemd.debug-shell on the kernel command line, and
then switch to tty9 while the fsck is running and attach strace to the
fsckd and fsck process?
I want to try this, but for some reason, grub always boots, even if I
keep SHIFT
On 29-11-15 01:28, Michael Biebl wrote:
Am 29.11.2015 um 00:12 schrieb Manuel Bilderbeek:
How can I help?
Describe your setup in as much detail as possible. LVM, RAID, fstab etc.
No RAID, no LVM. I've got a HDD and an SSD. I'm now booting from the SSD.
$ cat /etc/fstab
# /etc/fstab: static
Hi again,
On 15-11-15 10:06, Michael Biebl wrote:
I saw some workaround and suggestions, but is there already a direction of a
solution of this issue?
I'm afraid not. Not being able to reproduce this issue (on my side)
makes this harder.
Can you reproduce the issue reliably?
As I wrote
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) +
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.
