You are not logged in.
Hi all.
I have been using using arch for a while with no issue recently i updated my system and after powering on
my laptop i noticed that arch linux got a bit laggy and taking some more time then usual to load up apps.
here is what i tried:
1. diabled picom
2. cleared package cache with pacman -Sc
3. disabled baloo for plama kde.
yet it still a bit laggy and apps taking up more time then it used to load up apps
here is some info about my system:
OS: Arch Linux x86_64
Host: HP EliteBook 8560p (A0001D02)
Kernel: Linux 6.11.4-arch1-1
Uptime: 30 mins
Packages: 1304 (pacman), 6 (flatpak)
Shell: zsh 5.9
Display (LVDS): 1366x768 @ 60 Hz in 16"
WM: dwm (X11)
Theme: Breeze-Dark [GTK2], Breeze [GTK3]
Icons: breeze-dark [GTK2/3/4]
Font: Noto Sans (10pt) [GTK2/3/4]
Cursor: breeze (24px)
Terminal: konsole 24.8.2
Terminal Font: JetBrainsMono Nerd Font (10pt, Medium)
CPU: Intel(R) Core(TM) i7-2620M (4) @ 3.40 GHz
GPU: AMD Radeon HD 6400M/7400M Series [Discrete]
Memory: 1.61 GiB / 15.57 GiB (10%)
Swap: 0 B / 4.00 GiB (0%)
Disk (/): 67.56 GiB / 297.09 GiB (23%) - btrfs
Local IP (enp0s25): 192.168.0.103/24
and output of systemd-analyze critical-chain
graphical.target @35.433s
└─multi-user.target @35.433s
└─libvirtd.service @29.910s +5.521s
└─network.target @29.909s
└─wpa_supplicant.service @29.705s +202ms
└─basic.target @26.990s
└─dbus-broker.service @26.584s +397ms
└─dbus.socket @26.567s
└─sysinit.target @26.349s
└─systemd-update-done.service @26.280s +68ms
└─ldconfig.service @19.580s +6.695s
└─local-fs.target @19.577s
└─boot.mount @18.802s +775ms
└─systemd-fsck@dev-disk-by\x2duuid-5F02\x2dC498.service @17.320s +1.480s
└─dev-disk-by\x2duuid-5F02\x2dC498.device @17.318s
Offline
Please use code tags for such output, https://bbs.archlinux.org/help.php#bbcode .
└─systemd-fsck@dev-disk-by\x2duuid-5F02\x2dC498.service @17.320s +1.480s
└─dev-disk-by\x2duuid-5F02\x2dC498.device @17.318s
What kind of device is that disk ?
ldconfig.service also seems to take rather long .
Please post the outputs of systemd-analyze and systemd-analyze blame .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
What kind of device is that disk ?
If it's the stock disk, then it's a 7200 rpm SATA HDD. If that's the case, I'd spend 20 bucks on an SSD.
Online
Please use code tags for such output, https://bbs.archlinux.org/help.php#bbcode .
└─systemd-fsck@dev-disk-by\x2duuid-5F02\x2dC498.service @17.320s +1.480s └─dev-disk-by\x2duuid-5F02\x2dC498.device @17.318s
What kind of device is that disk ?
ldconfig.service also seems to take rather long .
Please post the outputs of systemd-analyze and systemd-analyze blame .
output of systemd-analyze
Startup finished in 11.814s (kernel) + 28.415s (userspace) = 40.229s
graphical.target reached after 28.411s in userspace.
and output of systemd-analyze blame:
30.201s upower.service
8.810s dev-sda2.device
7.208s ldconfig.service
2.608s NetworkManager.service
2.492s lvm2-monitor.service
1.886s systemd-vconsole-setup.service
1.872s systemd-journal-flush.service
1.578s systemd-tmpfiles-setup-dev-early.service
1.276s systemd-journal-catalog-update.service
1.186s systemd-modules-load.service
1.092s udisks2.service
1.017s systemd-udevd.service
1.011s systemd-remount-fs.service
841ms systemd-fsck@dev-disk-by\x2duuid-5F02\x2dC498.service
810ms systemd-sysusers.service
692ms systemd-tmpfiles-setup.service
657ms systemd-zram-setup@zram0.service
556ms dev-zram0.swap
506ms user@1000.service
496ms dev-hugepages.mount
494ms sys-kernel-tracing.mount
490ms systemd-random-seed.service
469ms polkit.service
460ms systemd-tmpfiles-clean.service
411ms dbus-broker.service
397ms lm_sensors.service
390ms systemd-backlight@backlight:acpi_video0.service
Last edited by nopencil (2024-10-19 12:19:09)
Offline
Lone_Wolf wrote:What kind of device is that disk ?
If it's the stock disk, then it's a 7200 rpm SATA HDD. If that's the case, I'd spend 20 bucks on an SSD.
everything was running smoothly on that HDD i have been using it for sometime until after an update and everything seemed to slow down. why?
is it because of KDE plasma or graphic drivers?
Offline
the disk adds up to a regular 320gb - and from the rest of the hardware we can assume it is a hdd - and as this is a mobile platform we also can assume it's a 5400rpm one
i wiuldn't bother to invest even a cheap ssd here
Offline
Also check dmesg resp. the journal for IO errors and your drive w/ https://wiki.archlinux.org/title/SMART ("smartctl -a", the overall health status is more or less meaningless for this)
Edit: in case it's not clear - I don't think this is because "HDD slow lol" I think it's because "HDD dying, backup your stuff!"
Last edited by seth (2024-10-19 12:37:21)
Offline
Also check dmesg resp. the journal for IO errors and your drive w/ https://wiki.archlinux.org/title/SMART ("smartctl -a", the overall health status is more or less meaningless for this)
Edit: in case it's not clear - I don't think this is because "HDD slow lol" I think it's because "HDD dying, backup your stuff!"
Yeah, sorry for the late reply i took your advice and was making back up:
output of smartctl -a /dev/sda : http://0x0.st/Xl8v.txt
it does says that overall health is fine:
SMART overall-health self-assessment test result: PASSED
EDIT: but then again you said it was useless.
output of dmesg : http://0x0.st/Xl8y.txt
and journalctl : http://0x0.st/Xl8Y.txt
Last edited by nopencil (2024-10-19 13:26:42)
Offline
There're no obvious IO errors, everything just moves at a glacial pace, but
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 465
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 445
says you'll need a new drive, in particular if the number keeps going up.
Edit: actually, couple of days ago (the journal goes back to semptember and is 34MB)
Oct 14 14:49:20 archlinux kernel: I/O error, dev sda, sector 2500352 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Oct 14 14:52:00 archlinux kernel: I/O error, dev sda, sector 12427104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Oct 14 14:52:00 archlinux kernel: I/O error, dev sda, sector 2679872 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 34351032 op 0x0:(READ) flags 0x80700 phys_seg 22 prio class 0
Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 123436224 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 18249784 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 18434248 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 36087880 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 11093656 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 2362272 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 2343232 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 2315008 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 11814320 op 0x0:(READ) flags 0x0 phys_seg 7 prio class 0
You need a new disk.
Last edited by seth (2024-10-19 13:34:50)
Offline
There're no obvious IO errors, everything just moves at a glacial pace, but
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 465 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 445
says you'll need a new drive, in particular if the number keeps going up.
Edit: actually, couple of days ago (the journal goes back to semptember and is 34MB)
Oct 14 14:49:20 archlinux kernel: I/O error, dev sda, sector 2500352 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Oct 14 14:52:00 archlinux kernel: I/O error, dev sda, sector 12427104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Oct 14 14:52:00 archlinux kernel: I/O error, dev sda, sector 2679872 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 34351032 op 0x0:(READ) flags 0x80700 phys_seg 22 prio class 0 Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 123436224 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 18249784 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 18434248 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 36087880 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 11093656 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 2362272 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 2343232 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 2315008 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Oct 14 14:54:08 archlinux kernel: I/O error, dev sda, sector 11814320 op 0x0:(READ) flags 0x0 phys_seg 7 prio class 0
You need a new disk.
Do you think i can work with this drive for 5 or 6 more days?
for personal reasons i have to keep using this one for couple of days before get back to city and get a new, its only slightly slughish for now.
Offline
Don't trust it, store every data you care about (also) on an external storage (directly, no copying from the broken drive)
Pay some attention to the reallocation count, the faster that goes up, the more dire it gets.
Offline