When I start System Monitor on GNOME 47,
I see that the ext4lazyinit process takes around 200% CPU time.
Only for about 10 seconds and the CPU temperature rises sharply.
Is that normal?
EDIT:
only when rngd.service is enabled…
and only on wayland…
Please usen only von langvitsh, und if zis langvitsh ist not Inglish, putten ihre post in ze korrekt langvitsh kategorie. Ozzervise, you vill be poppen ze blinkenlights of ze forum.
Solution:
the installed and running rngd.service prevented the system disk from being repaired… kernel: EXT4-fs error (device nvme0n1p3): ext4_orphan_get:1414: comm mount: bad orphan inode 24641602 and some more defects in journald warnings!
Well, there is a workaround, although it may not necessarily work in every case, especially not if there is severe damage.
If you add ro to the boot options in /etc/default/grub (and run update-grub), then the root fileystem will be mounted read-only for the fsck phase. It’ll get remounted read/write later by /etc/fstab anyway.
# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
# GRUB_ROOT_FS_RO=false
DONE NOW…
EDIT:
GRUB_ROOT_FS_RO=true
and removed fsck from /etc/mkinitcpio.conf
and sudo mkinitcpio -P && sudo update-grub
reboot.