System takes far too long to boot, 140 seconds

Issues & Assistance
1

Hello! At some point, my system began taking too long to boot. I ran systemd-analyze blame and systemd-analyze critical-chain as seen in this post Booting and login too slow after latest update - #5 by Narayanan, but I am a simple, GUI level Linux user, and I can’t make sense of the outputs. Help me, please! Thank you!

garuda-inxi

System:
Kernel: 6.10.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=3b12eb2c-8483-407c-8d5e-e3753bb0f932 rw rootflags=subvol=@
quiet rd.luks.uuid=9ef8855a-d41e-4e3b-860a-eca23739126c quiet
rd.udev.log_priority=3 vt.global_cursor_default=0
rd.luks.uuid=fd6ddec5-eac7-4ca8-8815-d373d6d7aa1e
resume=/dev/mapper/luks-fd6ddec5-eac7-4ca8-8815-d373d6d7aa1e loglevel=3
ibt=off
Desktop: KDE Plasma v: 6.1.4 tk: Qt v: N/A info: frameworks v: 6.5.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: SAMSUNG product: 300V3Z/300V4Z/300V5Z v: 0.1
serial: <superuser required> Chassis: type: 9 v: 0.1
serial: <superuser required>
Mobo: SAMSUNG model: 300V3Z/300V4Z/300V5Z v: FAB1
serial: <superuser required> uuid: <superuser required> UEFI: Phoenix
v: 00FU date: 07/05/2011
CPU:
Info: model: Intel Core i3-2310M bits: 64 type: MT MCP arch: Sandy Bridge
gen: core 2 level: v2 built: 2010-12 process: Intel 32nm family: 6
model-id: 0x2A (42) stepping: 7 microcode: 0x2F
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 1123 high: 2100 min/max: 800/2100 scaling:
driver: intel_cpufreq governor: schedutil cores: 1: 798 2: 798 3: 2100
4: 798 bogomips: 16761
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Samsung Co driver: i915 v: kernel arch: Gen-6 code: Sandybridge
process: Intel 32nm built: 2011 ports: active: VGA-1 off: LVDS-1
empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0116 class-ID: 0300
Device-2: Silicon Motion WebCam SCB-1100N driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.4:3
chip-ID: 2232:1008 class-ID: 0e02
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: crocus gpu: i915 display-ID: 0
Monitor-1: VGA-1 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus wayland:
drv: crocus x11: drv: crocus
API: OpenGL v: 4.5 compat-v: 3.3 vendor: intel mesa v: 24.1.6-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 3000 (SNB
GT2) device-ID: 8086:0116 memory: 1.46 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 3 device: 0 type: cpu name: llvmpipe (LLVM
18.1.8 256 bits) driver: mesa llvmpipe v: 24.1.6-arch1.1 (LLVM 18.1.8)
device-ID: 10005:0000 surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: Samsung Co driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:1c20 class-ID: 0403
API: ALSA v: k6.10.6-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Centrino Wireless-N 130 driver: iwlwifi v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:0896
class-ID: 0280
IF: wlp1s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Samsung Co driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel Centrino Advanced-N 6230 Bluetooth adapter driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 2-1.3:3
chip-ID: 8086:0189 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 3.0 lmp-v: 5
status: discoverable: no pairing: no
Drives:
Local Storage: total: 465.76 GiB used: 349.24 GiB (75.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: HN-M500MBB
size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: 0001 scheme: GPT
Partition:
ID-1: / raw-size: 457.23 GiB size: 457.23 GiB (100.00%)
used: 349.24 GiB (76.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-9ef8855a-d41e-4e3b-860a-eca23739126c
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 728 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 457.23 GiB size: 457.23 GiB (100.00%)
used: 349.24 GiB (76.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-9ef8855a-d41e-4e3b-860a-eca23739126c
ID-4: /var/log raw-size: 457.23 GiB size: 457.23 GiB (100.00%)
used: 349.24 GiB (76.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-9ef8855a-d41e-4e3b-860a-eca23739126c
ID-5: /var/tmp raw-size: 457.23 GiB size: 457.23 GiB (100.00%)
used: 349.24 GiB (76.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-9ef8855a-d41e-4e3b-860a-eca23739126c
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 7.67 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 50.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 8 GiB available: 7.67 GiB used: 3.7 GiB (48.3%)
Processes: 234 Power: uptime: 1h 31m states: freeze,standby,mem,disk
suspend: deep avail: s2idle,shallow wakeups: 0 hibernate: platform
avail: shutdown, reboot, suspend, test_resume image: 3.05 GiB
services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd
v: 256 default: graphical tool: systemctl
Packages: pm: pacman pkgs: 1398 libs: 384 tools: octopi,paru,trizen
Compilers: gcc: 14.2.1 Shell: garuda-inxi default: Bash v: 5.2.32
running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2024-08-25
Last full system update: 2024-08-26 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

systemd-analyze blame

1min 19.815s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1min 19.815s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartnum-1.device
1min 19.815s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2duuid-31CC\x2d69BA.device
1min 19.815s dev-sda1.device
1min 19.815s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device
1min 19.815s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart1.device
1min 19.815s dev-disk-by\x2did-wwn\x2d0x50024e9205dc92e0\x2dpart1.device
1min 19.815s dev-disk-by\x2dpartuuid-55be686e\x2d0905\x2dc343\x2da7ef\x2d936a42ff34bb.device
1min 19.815s dev-disk-by\x2did-ata\x2dSAMSUNG_HN\x2dM500MBB_S2RSJ9FB816383\x2dpart1.device
1min 19.815s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart1.device
1min 19.815s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartuuid-55be686e\x2d0905\x2>
1min 19.815s dev-disk-by\x2duuid-31CC\x2d69BA.device
1min 15.246s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda.device
1min 15.246s dev-disk-by\x2did-wwn\x2d0x50024e9205dc92e0.device
1min 15.246s dev-disk-by\x2did-ata\x2dSAMSUNG_HN\x2dM500MBB_S2RSJ9FB816383.device
1min 15.246s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0.device
1min 15.246s dev-sda.device
1min 15.246s dev-disk-by\x2ddiskseq-1.device
1min 15.246s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.device
1min 14.215s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
1min 14.215s dev-ttyS1.device
1min 14.211s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
1min 14.211s dev-ttyS2.device
1min 14.208s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
1min 14.208s dev-ttyS0.device
1min 14.188s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
1min 14.188s dev-ttyS3.device
1min 13.450s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda3.device
1min 13.450s dev-disk-by\x2did-ata\x2dSAMSUNG_HN\x2dM500MBB_S2RSJ9FB816383\x2dpart3.device
1min 13.450s dev-disk-by\x2duuid-fd6ddec5\x2deac7\x2d4ca8\x2d8815\x2dd373d6d7aa1e.device
1min 13.450s dev-disk-by\x2ddiskseq-1\x2dpart3.device
1min 13.450s dev-disk-by\x2did-wwn\x2d0x50024e9205dc92e0\x2dpart3.device
1min 13.450s dev-sda3.device
1min 13.450s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart3.device
1min 13.450s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartnum-3.device
1min 13.450s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart3.device
1min 13.450s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartuuid-f6f3ad84\x2d355f\x2>
1min 13.450s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2duuid-fd6ddec5\x2deac7\x2d4ca>
1min 13.450s dev-disk-by\x2dpartuuid-f6f3ad84\x2d355f\x2dfa4b\x2d8317\x2d08965763a2f1.device
1min 13.420s dev-disk-by\x2dpartlabel-root.device
1min 13.420s dev-disk-by\x2ddiskseq-1\x2dpart2.device
1min 13.420s dev-disk-by\x2duuid-9ef8855a\x2dd41e\x2d4e3b\x2d860a\x2deca23739126c.device
1min 13.420s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart2.device
1min 13.420s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2duuid-9ef8855a\x2dd41e\x2d4e3>
1min 13.420s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartuuid-777cafdf\x2d573b\x2>
1min 13.420s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartnum-2.device
1min 13.420s dev-disk-by\x2did-wwn\x2d0x50024e9205dc92e0\x2dpart2.device
1min 13.420s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart2.device
1min 13.420s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda2.device
1min 13.420s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartlabel-root.device
1min 13.420s dev-disk-by\x2dpartuuid-777cafdf\x2d573b\x2dcd45\x2db9a2\x2d7a7385499bf9.device
1min 13.420s dev-sda2.device
1min 13.420s dev-disk-by\x2did-ata\x2dSAMSUNG_HN\x2dM500MBB_S2RSJ9FB816383\x2dpart2.device
1min 11.415s sys-module-fuse.device
1min 11.402s sys-module-configfs.device
26.424s systemd-remount-fs.service
24.175s initrd-switch-root.service
21.295s ldconfig.service
19.353s firewalld.service
13.466s lvm2-monitor.service
12.849s dracut-initqueue.service
10.418s systemd-cryptsetup@luks\x2d9ef8855a\x2dd41e\x2d4e3b\x2d860a\x2deca23739126c.service
10.408s systemd-cryptsetup@luks\x2dfd6ddec5\x2deac7\x2d4ca8\x2d8815\x2dd373d6d7aa1e.service
6.975s NetworkManager.service
6.454s ModemManager.service
4.279s garuda-pacman-snapshot-reject.service
4.049s power-profiles-daemon.service
4.044s polkit.service
3.943s systemd-vconsole-setup.service
3.018s udisks2.service
2.507s systemd-udevd.service
2.347s upower.service
2.335s systemd-journal-catalog-update.service
2.132s systemd-oomd.service
2.102s systemd-binfmt.service
1.648s bluetooth.service
1.514s grub-btrfs-snapper.service
1.468s systemd-tmpfiles-setup.service
1.464s systemd-tmpfiles-clean.service
1.461s garuda-pacman-lock.service
1.395s systemd-tmpfiles-setup-dev-early.service
1.179s avahi-daemon.service
1.023s systemd-udev-trigger.service
933ms [email protected]
919ms systemd-journald.service
853ms wpa_supplicant.service
844ms systemd-udev-load-credentials.service
840ms dbus-broker.service
710ms systemd-sysusers.service
662ms systemd-modules-load.service
638ms dev-hugepages.mount
637ms dev-mqueue.mount
636ms sys-kernel-debug.mount
635ms sys-kernel-tracing.mount
613ms dracut-shutdown.service
571ms sys-fs-fuse-connections.mount
533ms systemd-fsck@dev-disk-by\x2duuid-31CC\x2d69BA.service
499ms dev-zram0.swap
466ms systemd-logind.service
434ms var-cache.mount
418ms [email protected]
390ms systemd-random-seed.service
387ms systemd-journal-flush.service
376ms boot-efi.mount
352ms dracut-pre-udev.service
308ms systemd-sysctl.service
262ms logrotate.service
248ms systemd-hostnamed.service
222ms systemd-user-sessions.service
205ms dracut-cmdline.service
201ms home.mount
1min 19.815s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1min 19.815s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartnum-1.device
1min 19.815s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2duuid-31CC\x2d69BA.device
1min 19.815s dev-sda1.device
1min 19.815s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device
1min 19.815s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart1.device
1min 19.815s dev-disk-by\x2did-wwn\x2d0x50024e9205dc92e0\x2dpart1.device
1min 19.815s dev-disk-by\x2dpartuuid-55be686e\x2d0905\x2dc343\x2da7ef\x2d936a42ff34bb.device
1min 19.815s dev-disk-by\x2did-ata\x2dSAMSUNG_HN\x2dM500MBB_S2RSJ9FB816383\x2dpart1.device
1min 19.815s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart1.device
1min 19.815s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartuuid-55be686e\x2d0905\x2>
1min 19.815s dev-disk-by\x2duuid-31CC\x2d69BA.device
1min 15.246s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda.device
1min 15.246s dev-disk-by\x2did-wwn\x2d0x50024e9205dc92e0.device
1min 15.246s dev-disk-by\x2did-ata\x2dSAMSUNG_HN\x2dM500MBB_S2RSJ9FB816383.device
1min 15.246s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0.device
1min 15.246s dev-sda.device
1min 15.246s dev-disk-by\x2ddiskseq-1.device
1min 15.246s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.device
1min 14.215s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
1min 14.215s dev-ttyS1.device
1min 14.211s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
1min 14.211s dev-ttyS2.device
1min 14.208s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
1min 14.208s dev-ttyS0.device
1min 14.188s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
1min 14.188s dev-ttyS3.device

systemd-analyze critical-chain

graphical.target @1min 50.358s
└─sddm.service @1min 50.358s
└─systemd-user-sessions.service @1min 50.130s +222ms
└─network.target @1min 50.128s
└─wpa_supplicant.service @1min 49.273s +853ms
└─basic.target @1min 18.901s
└─dbus-broker.service @1min 18.051s +840ms
└─dbus.socket @1min 18.037s
└─sysinit.target @1min 18.013s
└─systemd-update-done.service @1min 17.977s +35ms
└─ldconfig.service @56.676s +21.295s
└─local-fs.target @56.662s
└─boot-efi.mount @56.284s +376ms
└─systemd-fsck@dev-disk-by\x2duuid-31CC\x2d69BA.service @55.748s +533ms
└─dev-disk-by\x2duuid-31CC\x2d69BA.device
2

Welcome :slight_smile:

Post full log from terminal, please.

New, defect, removed device?

Post also

lsblk -f
cat /etc/fstab
1 Like
3

Thank you for your promt answer!
No new or removed devices. Don’t know if any defect one, all works well, apart for the boot time (140 seconds), and the fact that system freezes for 2-3 seconds in applications.

sudo journalctl -b

aug 26 14:38:07 Lenovo-V510 kernel: Linux version 6.10.6-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 14.2.1 2>
aug 26 14:38:07 Lenovo-V510 kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=3b12eb2c-848>
aug 26 14:38:07 Lenovo-V510 kernel: Disabled fast string operations
aug 26 14:38:07 Lenovo-V510 kernel: reserving inaccessible SNB gfx pages
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-provided physical RAM map:
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000008efff] usable
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-e820: [mem 0x000000000008f000-0x000000000008ffff] ACPI NVS
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-e820: [mem 0x0000000000090000-0x000000000009ffff] usable
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000aabeefff] usable
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-e820: [mem 0x00000000aabef000-0x00000000aaeeefff] reserved
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-e820: [mem 0x00000000aaeef000-0x00000000aaf9efff] ACPI NVS
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-e820: [mem 0x00000000aaf9f000-0x00000000aaffefff] ACPI data
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-e820: [mem 0x00000000aafff000-0x00000000aaffffff] usable
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-e820: [mem 0x00000000f80f8000-0x00000000f80f8fff] reserved
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
aug 26 14:38:07 Lenovo-V510 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000024fdfffff] usable
aug 26 14:38:07 Lenovo-V510 kernel: NX (Execute Disable) protection: active
aug 26 14:38:07 Lenovo-V510 kernel: APIC: Static calls initialized
aug 26 14:38:07 Lenovo-V510 kernel: e820: update [mem 0xa6e52018-0xa6e62057] usable ==> usable
aug 26 14:38:07 Lenovo-V510 kernel: extended physical RAM map:
aug 26 14:38:07 Lenovo-V510 kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000008efff] usable
aug 26 14:38:07 Lenovo-V510 kernel: reserve setup_data: [mem 0x000000000008f000-0x000000000008ffff] ACPI NVS
aug 26 14:38:07 Lenovo-V510 kernel: reserve setup_data: [mem 0x0000000000090000-0x000000000009ffff] usable
aug 26 14:38:07 Lenovo-V510 kernel: reserve setup_data: [mem 0x0000000000100000-0x00000000a6e52017] usable
aug 26 14:38:07 Lenovo-V510 kernel: reserve setup_data: [mem 0x00000000a6e52018-0x00000000a6e62057] usable
aug 26 14:38:07 Lenovo-V510 kernel: reserve setup_data: [mem 0x00000000a6e62058-0x00000000aabeefff] usable
aug 26 14:38:07 Lenovo-V510 kernel: reserve setup_data: [mem 0x00000000aabef000-0x00000000aaeeefff] reserved

lsblk -f

NAME                        FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1                      vfat   FAT32       31CC-69BA                             298,7M     0% /boot/efi
├─sda2                      crypto 1           9ef8855a-d41e-4e3b-860a-eca23739126c
│ └─luks-9ef8855a-d41e-4e3b-860a-eca23739126c
│                           btrfs              3b12eb2c-8483-407c-8d5e-e3753bb0f932  106,3G    76% /var/cache
│                                                                                                  /home
│                                                                                                  /var/log
│                                                                                                  /var/tmp
│                                                                                                  /root
│                                                                                                  /srv
│                                                                                                  /
└─sda3                      crypto 1           fd6ddec5-eac7-4ca8-8815-d373d6d7aa1e
└─luks-fd6ddec5-eac7-4ca8-8815-d373d6d7aa1e
swap   1     swap  153476ce-b4a0-456e-88e3-c8aac2967642
sr0
zram0                                                                                              [SWAP]

cat /etc/fstab

File: /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=31CC-69BA                            /boot/efi      vfat    defaults,noatime 0 2
/dev/mapper/luks-9ef8855a-d41e-4e3b-860a-eca23739126c /              btrfs   subvol=/@,defaults,noatime,compre
ss=zstd 0 0
/dev/mapper/luks-9ef8855a-d41e-4e3b-860a-eca23739126c /home          btrfs   subvol=/@home,defaults,noatime,co
mpress=zstd 0 0
/dev/mapper/luks-9ef8855a-d41e-4e3b-860a-eca23739126c /root          btrfs   subvol=/@root,defaults,noatime,co
mpress=zstd 0 0
/dev/mapper/luks-9ef8855a-d41e-4e3b-860a-eca23739126c /srv           btrfs   subvol=/@srv,defaults,noatime,com
press=zstd 0 0
/dev/mapper/luks-9ef8855a-d41e-4e3b-860a-eca23739126c /var/cache     btrfs   subvol=/@cache,defaults,noatime,c
ompress=zstd 0 0
/dev/mapper/luks-9ef8855a-d41e-4e3b-860a-eca23739126c /var/log       btrfs   subvol=/@log,defaults,noatime,com
press=zstd 0 0
/dev/mapper/luks-9ef8855a-d41e-4e3b-860a-eca23739126c /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,com
press=zstd 0 0
#/dev/mapper/luks-fd6ddec5-eac7-4ca8-8815-d373d6d7aa1e swap           swap    defaults   0 0
4

Sorry, I don’t understand anything about encrypted hard disks.

5

It was encrypted from the beginning and worked fine for a long time.

6

This could be the culprit.
Just a shot in the dark. This is a very old but still open systemd issue:

After May 2023, 2 weeks ago a new user complained.
Systemd has been recently updated to 256.5-1 on the 18-Aug-2024. Maybe, if you still have a snapshot before that update, you could give it a chance if this is really the culprit.

3 Likes
7

This problem began some months ago. It hasn’t bothered me much back then, but the boot time kept increasing. If I were to pinpoint something, I’d day all sorts of changes in behavior began some weeks after the switch to Plasma 6.

8

I don’t understand the meaning of these errors. Perhaps, some of them might be the culprit in the boot lag.

journalctl -b -p3 --no-pager

sep 04 13:07:10 Lenovo-V510 kernel: Bluetooth: hci0: unexpected event for opcode 0x0000
sep 04 13:07:50 Lenovo-V510 bluetoothd[862]: Failed to set mode: Failed (0x03)
sep 04 13:10:25 Lenovo-V510 systemd[1500]: Failed to start Profile-sync-daemon.
sep 04 13:10:55 Lenovo-V510 bluetoothd[862]: Failed to set mode: Failed (0x03)
sep 04 13:10:56 Lenovo-V510 bluetoothd[862]: Failed to set mode: Failed (0x03)
sep 04 13:10:56 Lenovo-V510 org_kde_powerdevil[1850]: busno=3, sleep-multiplier =  1,30. Testing for supported feature 0x10 returned Error_Info[DDCRC_DPMS_ASLEEP in ddc_write_read_with_retry, causes: ENXIO]
sep 04 13:11:51 Lenovo-V510 kwin_wayland[1549]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
sep 04 13:11:56 Lenovo-V510 plasmashell[1815]: aurorae: Couldn't find QML Decoration  ""
sep 04 13:52:05 Lenovo-V510 kwin_wayland[1549]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
sep 04 14:23:59 Lenovo-V510 kwin_wayland[1549]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
sep 04 14:24:49 Lenovo-V510 kwin_wayland[1549]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
sep 04 14:28:55 Lenovo-V510 kwin_wayland[1549]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
sep 04 14:30:13 Lenovo-V510 kwin_wayland[1549]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
sep 04 15:07:24 Lenovo-V510 kwin_wayland[1549]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
sep 04 15:14:23 Lenovo-V510 kwin_wayland[1549]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
sep 04 15:19:47 Lenovo-V510 kwin_wayland[1549]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
sep 04 15:40:51 Lenovo-V510 bluetoothd[862]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free unit: getpeername: Transport endpoint is not connected (107)
sep 04 15:41:09 Lenovo-V510 sudo[29450]:     nikola : a password is required ; TTY=pts/0 ; PWD=/home/nikola ; USER=root ; COMMAND=/usr/bin/true
9

What does not work that you are trying to make the journal?

Copy interesting warnings or mistakes for you and enter them in the search engine of your trust.

That’s what everyone is doing here, because nobody knows everything.

systemd-analyze
systemd-analyze blame
systemd-analyze critical-chain
4 Likes
10

the system works well, except for the boot lag, so I guess these errors could be disregarded.
i’ve seen the journalctl -b -p3 --no-pager command in another post and tried it myself, as i am trying all the ways that could yield any hints about what is causing the boot lag

My system’s boot time was 34 seconds, then something happened and it went up to 140 seconds.

11

@Nikola I have moved post to your already open topic on this matter. In the future, please do not make duplicate threads of already open Issues & Assistance topics that you have made. Instead please just post any new information to those topics.

3 Likes