You are not logged in.
Pages: 1
Had this problem ever since I removed another hard disk drive.
% uname -a
Linux arch-pc 6.17.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 24 Nov 2025 15:21:09 +0000 x86_64 GNU/Linux
% systemd-analyze
Startup finished in 3.709s (kernel) + 5.123s (initrd) + 2min 1.110s (userspace) = 2min 9.943s
graphical.target reached after 2min 1.110s in userspace.
% systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @2min 1.110s
└─multi-user.target @2min 1.110s
└─smb.service @2min 910ms +199ms
└─network-online.target @2min 908ms
└─NetworkManager-wait-online.service @1min 31.021s +5.874s
└─NetworkManager.service @1min 30.690s +328ms
└─basic.target @1min 30.690s
└─dbus-broker.service @1min 30.647s +30ms
└─dbus.socket @1min 30.643s +40us
└─sysinit.target @1min 30.641s
└─systemd-update-utmp.service @1min 30.619s +21ms
└─systemd-tmpfiles-setup.service @1min 30.509s +108ms
└─local-fs.target @1min 30.501s
└─tmp.mount @1min 30.408s +92ms
└─systemd-journald.socket
└─system.slice
└─-.slice
% systemd-analyze blame
2min 163ms systemd-networkd-wait-online.service
5.874s NetworkManager-wait-online.service
5.576s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpm-tpm0.device
5.576s dev-tpm0.device
5.560s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
5.560s dev-ttyS2.device
5.558s dev-ttyS0.device
5.558s sys-devices-pnp0-00:04-00:04:0-00:04:0.0-tty-ttyS0.device
5.556s dev-ttyS1.device
5.556s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
5.555s dev-tpmrm0.device
5.555s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
5.553s dev-ttyS3.device
5.553s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
5.545s sys-module-configfs.device
5.544s sys-module-fuse.device
5.506s dev-sdb.device
5.506s dev-disk-by\x2dpath-pci\x2d0000:04:00.1\x2data\x2d2.0.device
5.506s sys-devices-pci0000:00-0000:00:02.1-0000:04:00.1-ata2-host1-target1:0:0-1:0:0:0-block-sdb.device
5.506s dev-disk-by\x2ddiskseq-2.device
5.506s dev-disk-by\x2did-ata\x2dST4000DM004\x2d2U9104_ZW61HRG2.device
5.506s dev-disk-by\x2dpath-pci\x2d0000:04:00.1\x2data\x2d2.device
5.506s dev-disk-by\x2did-wwn\x2d0x5000c500e7f1725e.device
5.450s dev-disk-by\x2dlabel-8TB.device
5.450s dev-disk-by\x2dpartuuid-387e09bd\x2d171e\x2d41e2\x2da67e\x2dac68d63bf34e.device
5.450s dev-disk-by\x2dpath-pci\x2d0000:04:00.1\x2data\x2d1.0\x2dpart-by\x2duuid-b35f4bd1\x2d0603\x2d4731\x2d865a\x2dafebb3292d1d.device
5.450s dev-disk-by\x2did-ata\x2dWDC_WD80EFPX\x2d68C4ZN0_WD\x2dRD39GZAG\x2dpart1.device
5.450s dev-sda1.device
5.450s dev-disk-by\x2dpath-pci\x2d0000:04:00.1\x2data\x2d1.0\x2dpart-by\x2dpartnum-1.device
5.450s dev-disk-by\x2dpath-pci\x2d0000:04:00.1\x2data\x2d1.0\x2dpart-by\x2dpartuuid-387e09bd\x2d171e\x2d41e2\x2da67e\x2dac68d63bf34e.device
5.450s dev-disk-by\x2duuid-b35f4bd1\x2d0603\x2d4731\x2d865a\x2dafebb3292d1d.device
5.450s dev-disk-by\x2dpath-pci\x2d0000:04:00.1\x2data\x2d1.0\x2dpart1.device
5.450s dev-disk-by\x2ddiskseq-1\x2dpart1.device
5.450s dev-disk-by\x2dpath-pci\x2d0000:04:00.1\x2data\x2d1\x2dpart1.device
5.450s sys-devices-pci0000:00-0000:00:02.1-0000:04:00.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device
5.450s dev-disk-by\x2did-wwn\x2d0x50014ee216ed13a0\x2dpart1.device
5.450s dev-disk-by\x2dpath-pci\x2d0000:04:00.1\x2data\x2d1.0\x2dpart-by\x2dlabel-8TB.device
5.446s dev-disk-by\x2did-wwn\x2d0x50014ee216ed13a0.device
5.446s dev-disk-by\x2ddiskseq-1.device
5.446s dev-disk-by\x2dpath-pci\x2d0000:04:00.1\x2data\x2d1.0.device
5.446s sys-devices-pci0000:00-0000:00:02.1-0000:04:00.1-ata1-host0-target0:0:0-0:0:0:0-block-sda.device
Offline
Is there a reference to the old drive in fstab?
Offline
Solved it. The problem was with the UUID of a swap partition.
Last edited by kwab (2025-12-12 14:06:43)
Offline
Pages: 1