[arch-general] System terribly slow
Santiago Forero
santiago at forero.xyz
Sat Dec 4 00:32:38 UTC 2021
Hey, have you tried booting any live system from a USB drive? If it works
better then it might be a problem with your HDD.
Cheers
On Fri, Dec 3, 2021, 7:07 PM riveravaldez via arch-general <
arch-general at lists.archlinux.org> wrote:
> Hi,
>
> I'm looking for some advice trying to pinpoint why or where my system has
> becoming almost unusable slow. Searching the web I've found some hints
> but nothing precise enough. Maybe it's a failing HDD, but I'm first posting
> what I have until now in the hope someone can give some advice.
>
> Superficial symptoms are a general slowness. I'm using just IceWM and
> `startx` to initialize the GUI, and even logging into my account previous
> to
> that takes almost a minute to get done. Then any application I launch takes
> minutes to just start (from IceWM to firefox, from qtox to pcmanfm or
> geany,
> etc.). Even navigate the folders tree with pcmanfm takes 10 or more seconds
> just to show any folder content...
>
> Hope some of this helps:
>
> $ sudo journalctl -b -exp3
> -- Journal begins at Thu 2021-12-02 23:59:31 -03, ends at Fri
> 2021-12-03 19:50:29 -03. --
> dic 03 00:48:43 arch kernel: sd 0:0:0:0: [sda] Asking for cache data failed
> dic 03 00:48:43 arch kernel: sd 0:0:0:0: [sda] Assuming drive cache:
> write through
> dic 03 00:50:39 arch libvirtd[592]: cannot open directory
> '/home/dell/Software/VMs/TrisquelMini8': No existe el fichero o el
> directorio
> dic 03 00:50:39 arch libvirtd[592]: error interno: Falló al iniciar
> automáticamente el grupo de almacenamiento 'TrisquelMini8': cannot
> open directory '/home/dell/Softwar>
> dic 03 00:50:41 arch libvirtd[592]: No se encontró 'dmidecode' en
> ruta: No existe el fichero o el directorio
> dic 03 00:50:57 arch libvirtd[592]: No se encontró 'dmidecode' en
> ruta: No existe el fichero o el directorio
> dic 03 00:56:40 arch systemd[1]: Failed to start Disk Manager.
> Subject: A start job for unit udisks2.service has failed
> Defined-By: systemd
> Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
> A start job for unit udisks2.service has finished with a failure.
>
> The job identifier is 1072 and the job result is failed.
>
> $ systemctl --state=failed
> UNIT LOAD ACTIVE SUB DESCRIPTION
> 0 loaded units listed.
>
> $ systemd-analyze
> Startup finished in 11.038s (kernel) + 1min 31.352s (userspace) = 1min
> 42.391s
> graphical.target reached after 1min 31.352s in userspace
>
> $ systemd-analyze blame
> 37.946s polkit.service
> 29.248s dev-sda1.device
> 28.827s systemd-tmpfiles-clean.service
> 24.692s udisks2.service
> 15.936s systemd-journal-flush.service
> 14.228s systemd-hwdb-update.service
> 13.930s ldconfig.service
> 13.502s upower.service
> 12.881s ufw.service
> 8.830s user at 1000.service
> 7.556s systemd-tmpfiles-setup-dev.service
> 7.280s avahi-daemon.service
> 7.275s bluetooth.service
> 7.262s iwd.service
> 6.067s systemd-logind.service
> 6.058s systemd-machined.service
> 5.825s systemd-tmpfiles-setup.service
> 5.123s systemd-sysusers.service
> 4.569s systemd-udevd.service
> 4.511s systemd-resolved.service
> 4.281s systemd-networkd.service
> 3.724s systemd-journal-catalog-update.service
> 3.415s systemd-fsck at dev-disk-by
> \x2duuid-1d72b82c\x2d9c58\x2d4f57\x2d97a3\x2de29ff35a5632.service
> 2.959s systemd-modules-load.service
> 2.557s lm_sensors.service
> 2.503s systemd-random-seed.service
> 2.389s systemd-backlight at backlight:acpi_video0.service
> 1.983s
> dev-disk-by\x2duuid-84c91978\x2da09c\x2d4087\x2db60d\x2d86730d142f63.swap
> 1.967s systemd-backlight at leds:dell::kbd_backlight.service
> 1.563s systemd-timesyncd.service
> 1.457s systemd-update-utmp.service
> 1.287s systemd-udev-trigger.service
> 1.278s systemd-rfkill.service
> 1.219s alsa-restore.service
> 1.164s systemd-sysctl.service
> (...)
>
> $ systemctl status polkit.service
> ● polkit.service - Authorization Manager
> Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
> Active: active (running) since Fri 2021-12-03 00:50:28 -03; 19h ago
> Docs: man:polkit(8)
> Main PID: 613 (polkitd)
> Tasks: 12 (limit: 6993)
> Memory: 18.9M
> CPU: 1.032s
> CGroup: /system.slice/polkit.service
> └─613 /usr/lib/polkit-1/polkitd --no-debug
>
> dic 03 00:49:50 arch systemd[1]: Starting Authorization Manager...
> dic 03 00:50:05 arch polkitd[613]: Started polkitd version 0.120
> dic 03 00:50:26 arch polkitd[613]: Loading rules from directory
> /etc/polkit-1/rules.d
> dic 03 00:50:26 arch polkitd[613]: Loading rules from directory
> /usr/share/polkit-1/rules.d
> dic 03 00:50:28 arch polkitd[613]: Finished loading, compiling and
> executing 6 rules
> dic 03 00:50:28 arch systemd[1]: Started Authorization Manager.
> dic 03 00:50:28 arch polkitd[613]: Acquired the name
> org.freedesktop.PolicyKit1 on the system bus
>
> $ systemctl status dev-sda1.device
> ● dev-sda1.device - Hitachi_HTS545025B9A300 ROOT
> Follows: unit currently follows state of
>
> sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device
> Loaded: loaded
> Active: active (plugged) since Fri 2021-12-03 00:49:12 -03; 19h ago
> Device:
> /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
>
> Notice: journal has been rotated since unit was started, output may be
> incomplete.
>
> $ systemctl status systemd-tmpfiles-clean.service
> ○ systemd-tmpfiles-clean.service - Cleanup of Temporary Directories
> Loaded: loaded
> (/usr/lib/systemd/system/systemd-tmpfiles-clean.service; static)
> Active: inactive (dead) since Fri 2021-12-03 01:03:52 -03; 19h ago
> TriggeredBy: ● systemd-tmpfiles-clean.timer
> Docs: man:tmpfiles.d(5)
> man:systemd-tmpfiles(8)
> Process: 1473 ExecStart=systemd-tmpfiles --clean (code=exited,
> status=0/SUCCESS)
> Main PID: 1473 (code=exited, status=0/SUCCESS)
> CPU: 185ms
>
> dic 03 01:03:23 arch systemd[1]: Starting Cleanup of Temporary
> Directories...
> dic 03 01:03:52 arch systemd[1]: systemd-tmpfiles-clean.service:
> Deactivated successfully.
> dic 03 01:03:52 arch systemd[1]: Finished Cleanup of Temporary Directories.
>
> $ systemctl status udisks2.service
> ● udisks2.service - Disk Manager
> Loaded: loaded (/usr/lib/systemd/system/udisks2.service;
> disabled; vendor preset: disabled)
> Active: active (running) since Fri 2021-12-03 00:59:51 -03; 19h ago
> Docs: man:udisks(8)
> Main PID: 1129 (udisksd)
> Tasks: 5 (limit: 6993)
> Memory: 3.2M
> CPU: 23.045s
> CGroup: /system.slice/udisks2.service
> └─1129 /usr/lib/udisks2/udisksd
>
> dic 03 00:59:26 arch systemd[1]: Starting Disk Manager...
> dic 03 00:59:26 arch udisksd[1129]: udisks daemon version 2.9.4 starting
> dic 03 00:59:51 arch systemd[1]: Started Disk Manager.
> dic 03 00:59:54 arch udisksd[1129]: Acquired the name
> org.freedesktop.UDisks2 on the system message bus
>
> $ systemctl status systemd-journal-flush.service
> ● systemd-journal-flush.service - Flush Journal to Persistent Storage
> Loaded: loaded
> (/usr/lib/systemd/system/systemd-journal-flush.service; static)
> Active: active (exited) since Fri 2021-12-03 00:48:59 -03; 19h ago
> Docs: man:systemd-journald.service(8)
> man:journald.conf(5)
> Process: 283 ExecStart=journalctl --flush (code=exited,
> status=0/SUCCESS)
> Main PID: 283 (code=exited, status=0/SUCCESS)
> CPU: 15ms
>
> dic 03 00:48:43 arch systemd[1]: Starting Flush Journal to Persistent
> Storage...
> dic 03 00:48:59 arch systemd[1]: Finished Flush Journal to Persistent
> Storage.
>
> $ systemctl status systemd-hwdb-update.service
> ● systemd-hwdb-update.service - Rebuild Hardware Database
> Loaded: loaded
> (/usr/lib/systemd/system/systemd-hwdb-update.service; static)
> Active: active (exited) since Fri 2021-12-03 00:48:57 -03; 19h ago
> Docs: man:hwdb(7)
> man:systemd-hwdb(8)
> Process: 279 ExecStart=systemd-hwdb update (code=exited,
> status=0/SUCCESS)
> Main PID: 279 (code=exited, status=0/SUCCESS)
> CPU: 1.746s
>
> dic 03 00:48:57 arch systemd[1]: Finished Rebuild Hardware Database.
>
> $ journalctl -b -u systemd-journald.service
> -- Journal begins at Thu 2021-12-02 23:59:31 -03, ends at Fri
> 2021-12-03 20:49:18 -03. --
> dic 03 00:48:43 arch systemd-journald[271]: Journal started
> dic 03 00:48:43 arch systemd-journald[271]: Runtime Journal
> (/run/log/journal/431f639f382e4bad8a43628868f2fc6c) is 8.0M, max
> 292.4M, 284.4M free.
> dic 03 00:48:44 arch systemd-journald[271]: Time spent on flushing to
> /var/log/journal/431f639f382e4bad8a43628868f2fc6c is 7.561088s for 798
> entries.
> dic 03 00:48:44 arch systemd-journald[271]: System Journal
> (/var/log/journal/431f639f382e4bad8a43628868f2fc6c) is 16.0M, max
> 2.4G, 2.4G free.
>
> $ journalctl -b -u
> systemd-fsck at dev-disk-by
> \\x2duuid-1d72b82c\\x2d9c58\\x2d4f57\\x2d97a3\\x2de29ff35a5632.service
> -- Journal begins at Thu 2021-12-02 23:59:31 -03, ends at Fri
> 2021-12-03 20:52:36 -03. --
> dic 03 00:49:18 arch systemd[1]: Starting File System Check on
> /dev/disk/by-uuid/1d72b82c-9c58-4f57-97a3-e29ff35a5632...
> dic 03 00:49:21 arch systemd-fsck[485]: HOME: limpio, 208781/13107200
> ficheros, 37165716/52398592 bloques
> dic 03 00:49:21 arch systemd[1]: Finished File System Check on
> /dev/disk/by-uuid/1d72b82c-9c58-4f57-97a3-e29ff35a5632.
>
> $ journalctl --verify
> PASS: /var/log/journal/431f639f382e4bad8a43628868f2fc6c/user-1000.journal
> 3b84d8: Data object's entry array not sorted
> File corruption detected at
> /var/log/journal/431f639f382e4bad8a43628868f2fc6c/system.journal:915878
> (of 16777216 bytes, 56%).
> FAIL: /var/log/journal/431f639f382e4bad8a43628868f2fc6c/system.journal
> (Mensaje erróneo)
>
> $ journalctl --disk-usage
> Archived and active journals take up 24.0M in the file system.
>
> Maybe it's pertinent to mention that I've just cleaned up
> /var/log/journal to rule
> out storage issues.
>
> Any help will be most welcome.
>
> Thanks a lot in advance.
>
More information about the arch-general
mailing list