You are not logged in.
Pages: 1
This appears to be related to systemd 220. I have it reproducing on two systems.
On startup, immediately after the root file system is mounted, I get running udev cleanup hook for about 30s, then systemd appears to start and everything is normal:
[ 4.627881] XFS (sda2): Mounting V4 Filesystem
[ 4.654095] XFS (sda2): Starting recovery (logdev: internal)
[ 4.678539] XFS (sda2): Ending recovery (logdev: internal)
[ 34.771184] systemd[1]: systemd 220 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
[ 34.777662] systemd[1]: Detected architecture x86-64.
What's with the 30s delay?
Last edited by DebauchedSloth (2015-05-30 09:24:47)
Offline
Please use code tags when pasting terminal output.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
I had this problem recently.
related: https://www.mail-archive.com/systemd-de … 31806.html
"After you do enough distro research, you will choose Arch."
Offline
Seems to be fixed in 220-3.
Offline
Pages: 1