Pages : 1
#1 Le 21/03/2022, à 20:48
- lherbaux
disque dur lent
bonjour,
le démarrage de mon ubuntu met 2 minutes, ça me parait long.
comment puis-je corriger cela ?
merci d'avance.
à bientôt.
Hors ligne
#2 Le 21/03/2022, à 20:53
- xubu1957
Re : disque dur lent
Bonjour,
Montre, en te servant du Retour utilisable de commande :
systemd-analyze timesystemd-analyze blamesystemd-analyze critical-chainet :
ls -l /var/crashdpkg -l | grep -v ^iiConseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#3 Le 24/03/2022, à 20:30
- lherbaux
Re : disque dur lent
4.902s systemd-logind.service
4.902s wpa_supplicant.service
4.468s dev-loop8.device
4.101s gpu-manager.service
3.943s ModemManager.service
3.607s dev-loop14.device
3.545s smartmontools.service
3.361s dev-loop13.device
3.212s apport.service
3.123s systemd-journal-flush.service
2.760s dev-loop0.device
2.759s dev-loop5.device
2.758s dev-loop3.device
2.757s dev-loop2.device
2.755s dev-loop7.device
2.755s dev-loop4.device
2.755s dev-loop6.device
2.753s dev-loop9.device
2.709s dev-loop10.device
2.618s dev-loop11.device
2.608s dev-loop12.device
2.338s lightdm.service
2.334s plymouth-quit-wait.service
2.214s systemd-modules-load.service
1.997s rsyslog.service
1.814s grub-common.service
1.540s systemd-tmpfiles-setup-dev.service
1.503s alsa-restore.service
1.391s e2scrub_reap.service
1.313s dev-loop1.device
1.118s systemd-sysctl.service
1.019s apparmor.service
979ms systemd-resolved.service
754ms systemd-sysusers.service
730ms snapd.apparmor.service
702ms ifupdown-pre.service
695ms snap-bare-5.mount
640ms snap-chromium-1942.mount
632ms systemd-udevd.service
606ms swapfile.swap
589ms systemd-tmpfiles-setup.service
534ms grub-initrd-fallback.service
504ms systemd-random-seed.service
504ms snap-chromium-1944.mount
404ms networking.service
399ms snap-core18-2284.mount
379ms snap-core18-2344.mount
363ms keyboard-setup.service
336ms snapd.seeded.service
320ms snap-ubuntu\x2dmate\x2dwelcome-671.mount
285ms snap-core20-1361.mount
270ms systemd-journald.service
270ms systemd-udev-trigger.service
268ms openvpn.service
267ms snap-core20-1376.mount
266ms kerneloops.service
256ms upower.service
255ms snap-ubuntu\x2dmate\x2dwelcome-667.mount
244ms systemd-user-sessions.service
227ms snap-snapd-15177.mount
221ms systemd-rfkill.service
212ms ufw.service
199ms snap-gnome\x2d3\x2d38\x2d2004-99.mount
198ms pppd-dns.service
192ms snap-software\x2dboutique-54.mount
191ms setvtrgb.service
167ms user@1000.service
150ms snap-gtk\x2dcommon\x2dthemes-1519.mount
146ms snap-snapd-14978.mount
124ms systemd-timesyncd.service
122ms systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service
120ms systemd-remount-fs.service
108ms snap-mp3gain-52.mount
81ms plymouth-read-write.service
70ms systemd-update-utmp.service
69ms rtkit-daemon.service
63ms console-setup.service
63ms dev-hugepages.mount
62ms dev-mqueue.mount
62ms sys-kernel-debug.mount
61ms sys-kernel-tracing.mount
59ms boot-efi.mount
59ms kmod-static-nodes.service
56ms hddtemp.service
19ms user-runtime-dir@1000.service
15ms plymouth-start.service
6ms systemd-update-utmp-runlevel.service
4ms sys-fs-fuse-connections.mount
3ms sys-kernel-config.mount
886us snapd.socket
161us clean-mount-point@media-parent-Seagate\x20Expansion\x20Drive.service
...skipping...
146ms snap-snapd-14978.mount
124ms systemd-timesyncd.service
122ms systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service
120ms systemd-remount-fs.service
108ms snap-mp3gain-52.mount
81ms plymouth-read-write.service
70ms systemd-update-utmp.service
69ms rtkit-daemon.service
63ms console-setup.service
63ms dev-hugepages.mount
62ms dev-mqueue.mount
62ms sys-kernel-debug.mount
61ms sys-kernel-tracing.mount
59ms boot-efi.mount
59ms kmod-static-nodes.service
56ms hddtemp.service
19ms user-runtime-dir@1000.service
15ms plymouth-start.service
6ms systemd-update-utmp-runlevel.service
4ms sys-fs-fuse-connections.mount
3ms sys-kernel-config.mount
886us snapd.socket
161us clean-mount-point@media-parent-Seagate\x20Expansion\x20Drive.service
...skipping...
146ms snap-snapd-14978.mount
124ms systemd-timesyncd.service
122ms systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service
120ms systemd-remount-fs.service
108ms snap-mp3gain-52.mount
81ms plymouth-read-write.service
70ms systemd-update-utmp.service
69ms rtkit-daemon.service
63ms console-setup.service
63ms dev-hugepages.mount
62ms dev-mqueue.mount
62ms sys-kernel-debug.mount
61ms sys-kernel-tracing.mount
59ms boot-efi.mount
59ms kmod-static-nodes.service
56ms hddtemp.service
19ms user-runtime-dir@1000.service
15ms plymouth-start.service
6ms systemd-update-utmp-runlevel.service
4ms sys-fs-fuse-connections.mount
3ms sys-kernel-config.mount
886us snapd.socket
161us clean-mount-point@media-parent-Seagate\x20Expansion\x20Drive.service
...skipping...
146ms snap-snapd-14978.mount
124ms systemd-timesyncd.service
122ms systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service
120ms systemd-remount-fs.service
108ms snap-mp3gain-52.mount
81ms plymouth-read-write.service
70ms systemd-update-utmp.service
69ms rtkit-daemon.service
63ms console-setup.service
63ms dev-hugepages.mount
62ms dev-mqueue.mount
62ms sys-kernel-debug.mount
61ms sys-kernel-tracing.mount
59ms boot-efi.mount
59ms kmod-static-nodes.service
56ms hddtemp.service
19ms user-runtime-dir@1000.service
15ms plymouth-start.service
6ms systemd-update-utmp-runlevel.service
4ms sys-fs-fuse-connections.mount
3ms sys-kernel-config.mount
886us snapd.socket
161us clean-mount-point@media-parent-Seagate\x20Expansion\x20Drive.service
parent@parent:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @54.602s
└─multi-user.target @54.602s
└─blueman-mechanism.service @18.781s +35.820s
└─basic.target @18.731s
└─sockets.target @18.731s
└─snapd.socket @18.730s +886us
└─sysinit.target @18.678s
└─snapd.apparmor.service @17.947s +730ms
└─apparmor.service @16.925s +1.019s
└─local-fs.target @16.924s
└─boot-efi.mount @16.864s +59ms
└─systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service @16>
└─dev-disk-by\x2duuid-805D\x2d5E56.device @16.719s
...skipping...
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @54.602s
└─multi-user.target @54.602s
└─blueman-mechanism.service @18.781s +35.820s
└─basic.target @18.731s
└─sockets.target @18.731s
└─snapd.socket @18.730s +886us
└─sysinit.target @18.678s
└─snapd.apparmor.service @17.947s +730ms
└─apparmor.service @16.925s +1.019s
└─local-fs.target @16.924s
└─boot-efi.mount @16.864s +59ms
└─systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service @16>
└─dev-disk-by\x2duuid-805D\x2d5E56.device @16.719s
~
~
~
~
~
~
~
ESCOC
ted is printed after the "@" character.
ed after the "+" character.
35.820s
.947s +730ms
s +1.019s
4s
64s +59ms
isk-by\x2duuid-805D\x2d5E56.service @16.720s +122ms
uid-805D\x2d5E56.device @16.719s
~
~
~
~
~
~
~
ESCOD
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @54.602s
└─multi-user.target @54.602s
└─blueman-mechanism.service @18.781s +35.820s
└─basic.target @18.731s
└─sockets.target @18.731s
└─snapd.socket @18.730s +886us
└─sysinit.target @18.678s
└─snapd.apparmor.service @17.947s +730ms
└─apparmor.service @16.925s +1.019s
└─local-fs.target @16.924s
└─boot-efi.mount @16.864s +59ms
└─systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service @16>
└─dev-disk-by\x2duuid-805D\x2d5E56.device @16.719s
~
~
~
~
~
~
~
ESCOD
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @54.602s
└─multi-user.target @54.602s
└─blueman-mechanism.service @18.781s +35.820s
└─basic.target @18.731s
└─sockets.target @18.731s
└─snapd.socket @18.730s +886us
└─sysinit.target @18.678s
└─snapd.apparmor.service @17.947s +730ms
└─apparmor.service @16.925s +1.019s
└─local-fs.target @16.924s
└─boot-efi.mount @16.864s +59ms
└─systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service @16>
└─dev-disk-by\x2duuid-805D\x2d5E56.device @16.719s
~
~
~
~
~
~
~
...skipping...
~
~
~
~
~
~
~
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @54.602s
└─multi-user.target @54.602s
└─blueman-mechanism.service @18.781s +35.820s
└─basic.target @18.731s
└─sockets.target @18.731s
└─snapd.socket @18.730s +886us
└─sysinit.target @18.678s
└─snapd.apparmor.service @17.947s +730ms
└─apparmor.service @16.925s +1.019s
└─local-fs.target @16.924s
└─boot-efi.mount @16.864s +59ms
└─systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service @16>
└─dev-disk-by\x2duuid-805D\x2d5E56.device @16.719s
...skipping...
~
~
~
~
~
~
~
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @54.602s
└─multi-user.target @54.602s
└─blueman-mechanism.service @18.781s +35.820s
└─basic.target @18.731s
└─sockets.target @18.731s
└─snapd.socket @18.730s +886us
└─sysinit.target @18.678s
└─snapd.apparmor.service @17.947s +730ms
└─apparmor.service @16.925s +1.019s
└─local-fs.target @16.924s
└─boot-efi.mount @16.864s +59ms
└─systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service @16>
└─dev-disk-by\x2duuid-805D\x2d5E56.device @16.719s
...skipping...
~
~
~
~
~
~
~
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @54.602s
└─multi-user.target @54.602s
└─blueman-mechanism.service @18.781s +35.820s
└─basic.target @18.731s
└─sockets.target @18.731s
└─snapd.socket @18.730s +886us
└─sysinit.target @18.678s
└─snapd.apparmor.service @17.947s +730ms
└─apparmor.service @16.925s +1.019s
└─local-fs.target @16.924s
└─boot-efi.mount @16.864s +59ms
└─systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service @16>
└─dev-disk-by\x2duuid-805D\x2d5E56.device @16.719s
ESCOD
~
~
~
~
~
~
~
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @54.602s
└─multi-user.target @54.602s
└─blueman-mechanism.service @18.781s +35.820s
└─basic.target @18.731s
└─sockets.target @18.731s
└─snapd.socket @18.730s +886us
└─sysinit.target @18.678s
└─snapd.apparmor.service @17.947s +730ms
└─apparmor.service @16.925s +1.019s
└─local-fs.target @16.924s
└─boot-efi.mount @16.864s +59ms
└─systemd-fsck@dev-disk-by\x2duuid-805D\x2d5E56.service @16>
└─dev-disk-by\x2duuid-805D\x2d5E56.device @16.719s
~
parent@parent:~$ ls -l /var/crash
total 6332
-rw-r----- 1 parent whoopsie 4040856 mars 21 20:34 _usr_bin_atril.1000.crash
-rw-r----- 1 parent whoopsie 2438985 mars 23 20:23 _usr_bin_marco.1000.crash
parent@parent:~$ dpkg -l | grep -v ^ii
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom Version Architecture Description
+++-=====================================-===================================-============-===============================================================================
rc gnome-power-manager 3.32.0-2 amd64 power management tool for the GNOME desktop
rc gnome-screensaver 3.6.1-11ubuntu4 amd64 Screensaver and screen lock formerly used in GNOME
rc linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 amd64 Signed kernel image generic
rc linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1 amd64 Signed kernel image generic
rc linux-modules-5.13.0-30-generic 5.13.0-30.33~20.04.1 amd64 Linux kernel extra modules for version 5.13.0 on 64 bit x86 SMP
rc linux-modules-5.8.0-43-generic 5.8.0-43.49~20.04.1 amd64 Linux kernel extra modules for version 5.8.0 on 64 bit x86 SMP
rc linux-modules-extra-5.13.0-30-generic 5.13.0-30.33~20.04.1 amd64 Linux kernel extra modules for version 5.13.0 on 64 bit x86 SMP
rc linux-modules-extra-5.8.0-43-generic 5.8.0-43.49~20.04.1 amd64 Linux kernel extra modules for version 5.8.0 on 64 bit x86 SMP
rc magnus 1.0.3-1 all Very simple screen magnifier
rc onboard 1.4.1-2ubuntu7 amd64 Simple On-screen Keyboard
rc plank 0.11.89-1 amd64 Elegant, simple, clean dock
rc popularity-contest 1.69ubuntu1 all Vote for your favourite packages automatically
rc xscreensaver 5.42+dfsg1-1ubuntu1 amd64 Screensaver daemon and frontend for X11
parent@parent:~$ Dernière modification par lherbaux (Le 24/03/2022, à 20:31)
Hors ligne
#4 Le 24/03/2022, à 20:34
- xubu1957
Re : disque dur lent
Les retours sont incomplets.
Pour nettoyer :
Le 11/02/2017, moko138 a écrit :
Pour supprimer tous ces fichiers de configuration devenus sans objets et marqués "rc", et uniquement ces fichiers, exécute :
dpkg -l | awk '/^rc/{print $2}' | xargs -r sudo dpkg -P
Pour info, les précisions de nany, pour la commande de nettoyage
==============
Montre aussi :
snap list --allDernière modification par xubu1957 (Le 24/03/2022, à 20:36)
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#5 Le 24/03/2022, à 21:42
- lherbaux
Re : disque dur lent
snap list --all
Nom Version Révision Suivi Éditeur Notes
bare 1.0 5 latest/stable canonical✓ base
chromium 99.0.4844.74 1942 latest/stable canonical✓ désactivé
chromium 99.0.4844.82 1944 latest/stable canonical✓ -
core18 20211215 2284 latest/stable canonical✓ base,désactivé
core18 20220309 2344 latest/stable canonical✓ base
core20 20220215 1361 latest/stable canonical✓ base,désactivé
core20 20220304 1376 latest/stable canonical✓ base
gnome-3-38-2004 0+git.1f9014a 99 latest/stable canonical✓ -
gtk-common-themes 0.1-59-g7bca6ae 1519 latest/stable canonical✓ -
mp3gain 1.6.2 52 latest/stable dodeco -
snapd 2.54.4 15177 latest/stable canonical✓ snapd
snapd 2.54.3 14978 latest/stable canonical✓ snapd,désactivé
software-boutique 0+git.f633ffb 54 latest/stable/… flexiondotorg classic
ubuntu-mate-welcome 21.10.0-34571af9 667 latest/stable/… flexiondotorg désactivé,classic
ubuntu-mate-welcome 21.10.0-10c36ff9 671 latest/stable/… flexiondotorg classicHors ligne
#6 Le 24/03/2022, à 21:46
- xubu1957
Re : disque dur lent
Il faut les avis d'aidants plus techniques que moi.
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#7 Le 25/03/2022, à 09:08
- berserk
Re : disque dur lent
Bonjour
sudo apt install inxi && inxi lsb_release -decho $XDG_CURRENT_DESKTOPHors ligne
#8 Le 25/03/2022, à 09:51
- iznobe
Re : disque dur lent
Bonjour , il est evident que sans connaitre le materiel qui compose l' ordinateur , pincipalement le(s) disque(s) dur(s) et savoir sur quel disque l ' OS est installé , il est impossible de dire si c' est normal ou pas .
Mais deja , il semblerait que ca soit plutot pas trop normal de ce coté :
blueman-mechanism.service @18.781s +35.820sDernière modification par iznobe (Le 25/03/2022, à 09:54)
retour COMPLET et utilisable de commande
MSI Z490A-pro , i7 10700 , 32 GB RAM .
Hors ligne
Pages : 1