Bug ID 1096072
Summary systemd hangs on initrd-switch-root.service for 1.5 minutes when booting
Classification openSUSE
Product openSUSE Distribution
Version Leap 15.0
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Basesystem
Assignee bnc-team-screening@forge.provo.novell.com
Reporter alarrosa@suse.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Created attachment 772558 [details]
journalctl --system --since "1 hour ago"

After upgrading my Leap 42.3 system to Leap 15.0 it takes very long to boot up.
Of that time, around 1.5 minutes (1:34) is spent on initrd-switch-root.service
while it seems the system is doing nothing (at least the hard disk light stops
blinking for all that time).

The system stops just after:

Jun 05 18:32:41 geeko systemd[1]: Switching root.
Jun 05 18:32:41 geeko systemd-journald[154]: Journal stopped

And then continues with:
Jun 05 18:34:16 geeko systemd-journald[154]: Received SIGTERM from PID 1
(systemd).
Jun 05 18:34:16 geeko kernel: systemd: 20 output lines suppressed due to
ratelimiting
Jun 05 18:34:16 geeko kernel: EXT4-fs (sda6): re-mounted. Opts: acl,user_xattr
Jun 05 18:34:16 geeko systemd-journald[414]: Journal started
Jun 05 18:34:16 geeko systemd-journald[414]: Runtime journal
(/run/log/journal/f7cb102c5d6c079fd36e51615215ef87) is 8.0M, max 383.4M, 375.4M
free.
Jun 05 18:32:43 geeko systemd[1]: systemd 234 running in system mode. (+PAM
-AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT
-GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN
default-hierarchy=hybrid)
Jun 05 18:32:43 geeko systemd[1]: Detected architecture x86-64.
Jun 05 18:32:43 geeko systemd[1]: Set hostname to <geeko>.
Jun 05 18:34:13 geeko systemd[1]: system-generators terminated by signal ALRM.
Jun 05 18:34:16 geeko apparmor.systemd[420]: Restarting AppArmor
Jun 05 18:34:13 geeko systemd[1]: Execution failed: Protocol error

Note the systemd log from 18:32:43 being written after other logs from 18:34:16
and the "Execution failed: Protocol error" message which might be related.

I tried enabling debug-shell.service, but that is started after systemd
unfreezes. I attach the full output of journalctl --system --since "1 hour
ago". Btw, for some reason, in this system, journalctl only shows the journal
logs from the current boot, never showing logs from previous boots. 

Also, just in case it rings a bell, I also have this problem on the same
system: https://bugzilla.opensuse.org/show_bug.cgi?id=1096050


You are receiving this mail because: