J'ai remarqué que mon Lubuntu 20.04 démarre lentement. Jusqu'à présent, j'ai lu quelques publications et je peux vous partager toutes ces informations que j'ai collectées:
# systemd-analyze blame
19.296s dev-sda5.device
18.412s snapd.service
17.480s networkd-dispatcher.service
16.627s accounts-daemon.service
15.142s udisks2.service
12.115s dev-loop13.device
11.692s NetworkManager-wait-online.service
11.054s dev-loop9.device
11.010s bluetooth.service
11.008s avahi-daemon.service
10.916s dev-loop14.device
10.872s dev-loop17.device
10.831s dev-loop8.device
10.798s dev-loop12.device
10.755s dev-loop19.device
10.734s NetworkManager.service
10.716s dundee.service
10.665s dev-loop16.device
10.638s dev-loop18.device
10.604s dev-loop15.device
10.604s dev-loop11.device
9.929s polkit.service
9.833s ofono.service
9.176s switcheroo-control.service
9.158s thermald.service
9.155s systemd-logind.service
9.051s wpa_supplicant.service
8.573s dev-loop10.device
7.504s dev-loop6.device
7.450s dev-loop7.device
7.439s dev-loop2.device
...La chaîne critique est:
# systemd-analyze critical-chain
graphical.target @50.502s
multi-user.target @50.502s
kerneloops.service @50.294s +207ms
network-online.target @50.270s
NetworkManager-wait-online.service @38.577s +11.692s
NetworkManager.service @27.837s +10.734s
dbus.service @27.833s
basic.target @27.480s
sockets.target @27.478s
snapd.socket @27.474s +3ms
sysinit.target @27.408s
snapd.apparmor.service @26.409s +998ms
apparmor.service @23.930s +2.464s
local-fs.target @23.929s
boot-efi.mount @23.880s +48ms
systemd-fsck@dev-disk-by\x2duuid-B86C\x2d1FC8.service @23.705s +155ms
dev-disk-by\x2duuid-B86C\x2d1FC8.device @23.704sfstab:
# sudo 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).
#
#
# / was on /dev/sda5 during installation
UUID=5376f975-326e-467b-b615-3c05494fc9c9 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
/swapfile none swap sw 0 0
UUID=B86C-1FC8 /boot/efi vfat umask=0077 0 1Et blkid montre:
sudo blkid
/dev/sda5: UUID="5376f975-326e-467b-b615-3c05494fc9c9" TYPE="ext4" PARTUUID="e2f7acbc-05"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda1: UUID="B86C-1FC8" TYPE="vfat" PARTUUID="e2f7acbc-01"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"lsbkl affiche également ceci:
#sudo lsbkl -f
# Il y a plus d'informations ici, mais je pense que ce n'est pas pertinent pour le moment.
#...
sda
sda1 vfat B86C-1FC8 511M 0% /boot/efi
sda2
sda5 ext4 5376f975-326e-467b-b615-3c05494fc9c9 806,9G 7% /
sr0 gnome-disks smart-data-1:
gnome-disks smart-data-2:
commande gratuite:
~$ free -h
total used free shared buff/cache available
Mem: 5,7Gi 853Mi 409Mi 119Mi 4,4Gi 4,4Gi
Swap: 2,0Gi 1,0Mi 2,0GiSavez-vous ce qui pourrait se passer? Je suppose que la partition sda1 ou le fichier swap pourraient en être responsables. Si c'est le cas, comment puis-je le réparer? Merci d'avance!
