Eu postei anteriormente sobre uma inicialização lenta (aqui: . Corrigi vários problemas mais tarde e reduzi o tempo de inicialização para cerca de 44 segundos em tempo real.
Estatísticas mostram - systemd-analyze blame
15.388s dev-sda6.device
13.143s systemd-udevd.service
12.946s apparmor.service
12.702s dns-clean.service
11.912s systemd-sysctl.service
9.753s systemd-resolved.service
9.667s systemd-timesyncd.service
9.532s systemd-update-utmp.service
2.985s NetworkManager.service
2.673s udisks2.service
2.533s systemd-tmpfiles-setup.service
2.106s accounts-daemon.service
2.000s networkd-dispatcher.service
1.645s rsyslog.service
1.425s grub-common.service
1.337s iio-sensor-proxy.service
1.283s systemd-modules-load.service
1.230s thermald.service
1.186s console-setup.service
1.001s keyboard-setup.service
977ms nginx.service
879ms rng-tools.service
862ms gdm.service
842ms gpu-manager.service
806ms avahi-daemon.service
746ms fwupd.service
727ms apache2.service
722ms systemd-tmpfiles-setup-dev.service
630ms packagekit.service
614ms systemd-remount-fs.service
537ms dev-mqueue.mount
535ms dev-hugepages.mount
535ms sys-kernel-debug.mount
438ms tlp.service
428ms networking.service
408ms systemd-journal-flush.service
368ms systemd-logind.service
307ms colord.service
295ms systemd-journald.service
263ms ufw.service
239ms systemd-random-seed.service
222ms polkit.service
154ms [email protected]
151ms dev-disk-by\x2duuid-72e62aa6\x2deefa\x2d49e1\x2daba3\x2d858b0e7dfbd3.swap
129ms systemd-backlight@backlight:intel_backlight.service
106ms upower.service
91ms kmod-static-nodes.service
90ms apport.service
78ms bolt.service
71ms wpa_supplicant.service
60ms systemd-udev-trigger.service
54ms speech-dispatcher.service
46ms setvtrgb.service
30ms alsa-restore.service
24ms kerneloops.service
20ms rtkit-daemon.service
11ms plymouth-read-write.service
11ms systemd-user-sessions.service
10ms pppd-dns.service
6ms ureadahead-stop.service
5ms systemd-update-utmp-runlevel.service
4ms plymouth-quit-wait.service
2ms sys-kernel-config.mount
2ms sys-fs-fuse-connections.mount
systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @22.088s
└─multi-user.target @22.087s
└─nginx.service @21.108s +977ms
└─network.target @21.098s
└─NetworkManager.service @18.112s +2.985s
└─dbus.service @17.368s
└─basic.target @17.325s
└─paths.target @17.324s
└─acpid.path @17.323s
└─sysinit.target @17.272s
└─swap.target @17.272s
└─dev-disk-by\x2duuid-72e62aa6\x2deefa\x2d49e1\x2daba3\x2d858b0e7dfbd3.swap @17.121s +151ms
└─dev-disk-by\x2duuid-72e62aa6\x2deefa\x2d49e1\x2daba3\x2d858b0e7dfbd3.device @17.120s
cat /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>
# / was on /dev/sda6 during installation
UUID=bcf11c88-ce96-4951-88a1-51e39c7240db / ext4 errors=remount-ro 0 1
# swap was on /dev/sda7 during installation
UUID=72e62aa6-eefa-49e1-aba3-858b0e7dfbd3 none swap sw 0 0
blkid não me dá nenhuma saída
Por que dev-sda6.device demora tanto? E o dns-clean.service também. Há algo que eu possa fazer para melhorar isso?
Perdoe-me se este parecer ser um post duplicado, mas houve muitas alterações significativas que fiz após o meu post anterior. Então achei que seria melhor criar um novo.