Démarrage lent
prune bleue Membre non connecté
-
- Voir le profil du membre prune bleue
- Inscrit le : 28/12/2008
- Groupes :
J'aimerais comprendre pourquoi et résoudre le problème.
J'ai fait la commande
Code :
systemd-analyze blame
J'ai obtenu:
Caché :
root@localhost prunebleue]# systemd-analyze blame
1min 29.722s mdmonitor.service
14.923s udisks2.service
14.432s mandriva-everytime.service
14.217s network-up.service
13.068s plymouth-quit-wait.service
12.197s dev-sda5.device
7.644s network.service
7.514s upower.service
6.419s shorewall.service
5.079s power-profiles-daemon.service
4.793s iio-sensor-proxy.service
4.773s systemd-udevd.service
4.599s polkit.service
4.385s avahi-daemon.service
4.343s dbus.service
4.023s rtkit-daemon.service
4.016s switcheroo-control.service
3.876s plymouth-start.service
3.021s systemd-journal-flush.service
2.435s systemd-tmpfiles-setup-dev-early.service
2.415s systemd-vconsole-setup.service
2.159s systemd-fsck@dev-disk-by\x2duuid-76133e0b\x2d3c2c\x2d48d3\x2db365\x2d73060bd1449d.service
1.999s systemd-random-seed.service
1.968s ModemManager.service
1.908s systemd-udev-trigger.service
1.804s systemd-fsck-root.service
1.738s nscd.service
lines 1-27...skipping...
1min 29.722s mdmonitor.service
14.923s udisks2.service
14.432s mandriva-everytime.service
14.217s network-up.service
13.068s plymouth-quit-wait.service
12.197s dev-sda5.device
7.644s network.service
7.514s upower.service
6.419s shorewall.service
5.079s power-profiles-daemon.service
4.793s iio-sensor-proxy.service
4.773s systemd-udevd.service
4.599s polkit.service
4.385s avahi-daemon.service
4.343s dbus.service
4.023s rtkit-daemon.service
4.016s switcheroo-control.service
3.876s plymouth-start.service
3.021s systemd-journal-flush.service
2.435s systemd-tmpfiles-setup-dev-early.service
2.415s systemd-vconsole-setup.service
2.159s systemd-fsck@dev-disk-by\x2duuid-76133e0b\x2d3c2c\x2d48d3\x2db365\x2d73060bd1449d.service
1.999s systemd-random-seed.service
1.968s ModemManager.service
1.908s systemd-udev-trigger.service
1.804s systemd-fsck-root.service
1.738s nscd.service
1.684s systemd-backlight@backlight:acpi_video0.service
1.655s media-windows.mount
1.633s mga-bg-res.service
1.547s systemd-networkd.service
1.285s user@0.service
1.241s systemd-resolved.service
1.158s dkms-autorebuild.service
1.074s dev-disk-by\x2duuid-9fe3a5b1\x2d3734\x2d47f5\x2d9d5d\x2d54c845af80ec.swap
1.011s systemd-networkd-persistent-storage.service
989ms systemd-tmpfiles-setup.service
909ms systemd-journald.service
869ms systemd-udev-load-credentials.service
849ms systemd-rfkill.service
822ms lightdm.service
778ms systemd-logind.service
737ms accounts-daemon.service
718ms systemd-modules-load.service
705ms systemd-timesyncd.service
641ms user@500.service
640ms modprobe@fuse.service
639ms cpupower.service
591ms home.mount
536ms modprobe@dm_mod.service
468ms mdmonitor-takeover.service
lines 1-51
453ms systemd-sysctl.service
451ms acpid.service
418ms dracut-shutdown.service
408ms gpm.service
353ms systemd-binfmt.service
272ms sys-kernel-debug.mount
271ms dev-hugepages.mount
271ms sys-kernel-tracing.mount
262ms modprobe@loop.service
257ms dev-mqueue.mount
175ms kmod-static-nodes.service
162ms modprobe@configfs.service
157ms user-runtime-dir@0.service
143ms systemd-update-utmp.service
124ms systemd-hostnamed.service
110ms user-runtime-dir@500.service
94ms sys-kernel-config.mount
85ms systemd-tmpfiles-setup-dev.service
79ms systemd-remount-fs.service
75ms proc-sys-fs-binfmt_misc.mount
74ms plymouth-read-write.service
63ms systemd-user-sessions.service
27ms sys-fs-fuse-connections.mount
23ms systemd-bootctl.socket
21ms tmp.mount
15ms systemd-ask-password.socket
15ms systemd-sysext.socket
10ms systemd-coredump.socket
2ms avahi-daemon.socket
2ms systemd-factory-reset.socket
1ms systemd-creds.socket
429us dbus.socket
114us systemd-journald.socket
104us systemd-machined.socket
101us systemd-journald-dev-log.socket
68us systemd-networkd-varlink.socket
67us systemd-importd.socket
67us systemd-resolved-monitor.socket
61us systemd-udevd-control.socket
58us systemd-udevd-varlink.socket
55us systemd-udevd-kernel.socket
53us nscd.socket
48us systemd-logind-varlink.socket
47us systemd-hostnamed.socket
45us systemd-resolved-varlink.socket
31us systemd-networkd.socket
29us systemd-rfkill.socket
1min 29.722s mdmonitor.service
14.923s udisks2.service
14.432s mandriva-everytime.service
14.217s network-up.service
13.068s plymouth-quit-wait.service
12.197s dev-sda5.device
7.644s network.service
7.514s upower.service
6.419s shorewall.service
5.079s power-profiles-daemon.service
4.793s iio-sensor-proxy.service
4.773s systemd-udevd.service
4.599s polkit.service
4.385s avahi-daemon.service
4.343s dbus.service
4.023s rtkit-daemon.service
4.016s switcheroo-control.service
3.876s plymouth-start.service
3.021s systemd-journal-flush.service
2.435s systemd-tmpfiles-setup-dev-early.service
2.415s systemd-vconsole-setup.service
2.159s systemd-fsck@dev-disk-by\x2duuid-76133e0b\x2d3c2c\x2d48d3\x2db365\x2d73060bd1449d.service
1.999s systemd-random-seed.service
1.968s ModemManager.service
1.908s systemd-udev-trigger.service
1.804s systemd-fsck-root.service
1.738s nscd.service
lines 1-27...skipping...
1min 29.722s mdmonitor.service
14.923s udisks2.service
14.432s mandriva-everytime.service
14.217s network-up.service
13.068s plymouth-quit-wait.service
12.197s dev-sda5.device
7.644s network.service
7.514s upower.service
6.419s shorewall.service
5.079s power-profiles-daemon.service
4.793s iio-sensor-proxy.service
4.773s systemd-udevd.service
4.599s polkit.service
4.385s avahi-daemon.service
4.343s dbus.service
4.023s rtkit-daemon.service
4.016s switcheroo-control.service
3.876s plymouth-start.service
3.021s systemd-journal-flush.service
2.435s systemd-tmpfiles-setup-dev-early.service
2.415s systemd-vconsole-setup.service
2.159s systemd-fsck@dev-disk-by\x2duuid-76133e0b\x2d3c2c\x2d48d3\x2db365\x2d73060bd1449d.service
1.999s systemd-random-seed.service
1.968s ModemManager.service
1.908s systemd-udev-trigger.service
1.804s systemd-fsck-root.service
1.738s nscd.service
1.684s systemd-backlight@backlight:acpi_video0.service
1.655s media-windows.mount
1.633s mga-bg-res.service
1.547s systemd-networkd.service
1.285s user@0.service
1.241s systemd-resolved.service
1.158s dkms-autorebuild.service
1.074s dev-disk-by\x2duuid-9fe3a5b1\x2d3734\x2d47f5\x2d9d5d\x2d54c845af80ec.swap
1.011s systemd-networkd-persistent-storage.service
989ms systemd-tmpfiles-setup.service
909ms systemd-journald.service
869ms systemd-udev-load-credentials.service
849ms systemd-rfkill.service
822ms lightdm.service
778ms systemd-logind.service
737ms accounts-daemon.service
718ms systemd-modules-load.service
705ms systemd-timesyncd.service
641ms user@500.service
640ms modprobe@fuse.service
639ms cpupower.service
591ms home.mount
536ms modprobe@dm_mod.service
468ms mdmonitor-takeover.service
lines 1-51
453ms systemd-sysctl.service
451ms acpid.service
418ms dracut-shutdown.service
408ms gpm.service
353ms systemd-binfmt.service
272ms sys-kernel-debug.mount
271ms dev-hugepages.mount
271ms sys-kernel-tracing.mount
262ms modprobe@loop.service
257ms dev-mqueue.mount
175ms kmod-static-nodes.service
162ms modprobe@configfs.service
157ms user-runtime-dir@0.service
143ms systemd-update-utmp.service
124ms systemd-hostnamed.service
110ms user-runtime-dir@500.service
94ms sys-kernel-config.mount
85ms systemd-tmpfiles-setup-dev.service
79ms systemd-remount-fs.service
75ms proc-sys-fs-binfmt_misc.mount
74ms plymouth-read-write.service
63ms systemd-user-sessions.service
27ms sys-fs-fuse-connections.mount
23ms systemd-bootctl.socket
21ms tmp.mount
15ms systemd-ask-password.socket
15ms systemd-sysext.socket
10ms systemd-coredump.socket
2ms avahi-daemon.socket
2ms systemd-factory-reset.socket
1ms systemd-creds.socket
429us dbus.socket
114us systemd-journald.socket
104us systemd-machined.socket
101us systemd-journald-dev-log.socket
68us systemd-networkd-varlink.socket
67us systemd-importd.socket
67us systemd-resolved-monitor.socket
61us systemd-udevd-control.socket
58us systemd-udevd-varlink.socket
55us systemd-udevd-kernel.socket
53us nscd.socket
48us systemd-logind-varlink.socket
47us systemd-hostnamed.socket
45us systemd-resolved-varlink.socket
31us systemd-networkd.socket
29us systemd-rfkill.socket
Est-ce vous voyez quelque chose qui causerait la lenteur du démarrage?
Papoteur Membre non connecté
-
- Voir le profil du membre Papoteur
- Inscrit le : 03/10/2011
- Groupes :
-
Modérateur
-
Équipe Mageia
-
Administrateur
-
Forgeron
On voit le premier service qui est très long et qui ne te sert à rien.
À partir du CCM, Système, Gérer les services, repère mdmonitor, et décoche la case "Au démarrage"
Je ne dis pas que ça va tout résoudre, mais c'est la première chose que je vois.
PS: c'est un service de surveillance d'un montage RAID des disques, ce que tu n'as pas.
nic80 Membre non connecté
-
- Voir le profil du membre nic80
- Inscrit le : 06/08/2018
- Groupes :
-
Modérateur
Effectivement si on n' a pas de raid, mdmonitor, lvm2 ( si on a pas de volume de ce type non plus) ne servent pas grand chose. un systemd-anlayze simple peut aussi donner des informations ( ici on ne voit sauf erreur que la partie userspace.
On peut aussi regarder au niveau des services "network". Pourrait il y avoir des cartes réseau qui ne seraient plus là ( type connexion de téléphone par usb). Chaque connexion ( même pour un besoin ponctuel) crée potentiellement une interface réseau que le script de démarrage essaye l' une après l'autre ( autant éliminer le superflu).
Quel est nom de la machine ? localhost ( ce n' est pas recommandé).
prune bleue Membre non connecté
-
- Voir le profil du membre prune bleue
- Inscrit le : 28/12/2008
- Groupes :
[root@localhost prunebleue]# systemd-analyze
Startup finished in 16.517s (kernel) + 1min 8.200s (userspace) = 1min 24.718s
graphical.target reached after 1min 8.192s in userspace.
Papoteur Membre non connecté
-
- Voir le profil du membre Papoteur
- Inscrit le : 03/10/2011
- Groupes :
-
Modérateur
-
Équipe Mageia
-
Administrateur
-
Forgeron
prune bleue Membre non connecté
-
- Voir le profil du membre prune bleue
- Inscrit le : 28/12/2008
- Groupes :
Je viens de rallumer mon ordinateur, je n'ai pas constaté de changement
J'ai refait systemd-analyze blame et j'obtiens ceci:
Caché :
16.198s systemd-journal-flush.service
13.796s mandriva-everytime.service
13.673s network-up.service
13.645s plymouth-quit-wait.service
9.483s dev-sda5.device
8.411s shorewall.service
7.481s upower.service
6.778s network.service
4.824s udisks2.service
4.144s iio-sensor-proxy.service
3.768s systemd-fsck@dev-disk-by\x2duuid-76133e0b\x2d3c2c\x2d48d3\x2db365\x2d73060bd1449d.service
3.709s polkit.service
3.670s avahi-daemon.service
3.612s dbus.service
3.248s mga-bg-res.service
2.953s systemd-resolved.service
2.914s rtkit-daemon.service
2.902s switcheroo-control.service
2.831s ModemManager.service
2.675s media-windows.mount
2.669s systemd-vconsole-setup.service
2.323s systemd-tmpfiles-setup-dev-early.service
2.283s power-profiles-daemon.service
2.199s systemd-fsck-root.service
2.096s systemd-udev-trigger.service
2.016s systemd-networkd.service
1.972s systemd-networkd-persistent-storage.service
1.874s user@0.service
1.804s systemd-udevd.service
1.779s dkms-autorebuild.service
1.504s home.mount
1.349s systemd-tmpfiles-setup.service
1.184s systemd-logind.service
1.171s accounts-daemon.service
1.129s systemd-journald.service
1.084s systemd-backlight@backlight:acpi_video0.service
1.079s modprobe@fuse.service
1.075s systemd-modules-load.service
1.039s systemd-udev-load-credentials.service
1.008s systemd-rfkill.service
993ms nscd.service
906ms modprobe@dm_mod.service
902ms lightdm.service
845ms mdmonitor-takeover.service
844ms acpid.service
816ms cpupower.service
806ms dracut-shutdown.service
796ms gpm.service
627ms plymouth-start.service
615ms user-runtime-dir@0.service
591ms user@500.service
559ms modprobe@loop.service
553ms systemd-binfmt.service
419ms modprobe@configfs.service
394ms tmp.mount
361ms systemd-random-seed.service
314ms dev-hugepages.mount
313ms dev-mqueue.mount
313ms plymouth-read-write.service
312ms sys-kernel-debug.mount
311ms sys-kernel-tracing.mount
279ms systemd-timesyncd.service
277ms kmod-static-nodes.service
196ms systemd-sysctl.service
149ms user-runtime-dir@500.service
147ms dev-disk-by\x2duuid-9fe3a5b1\x2d3734\x2d47f5\x2d9d5d\x2d54c845af80ec.swap
124ms systemd-hostnamed.service
117ms proc-sys-fs-binfmt_misc.mount
113ms systemd-tmpfiles-setup-dev.service
113ms systemd-bootctl.socket
93ms systemd-remount-fs.service
86ms systemd-update-utmp.service
56ms systemd-user-sessions.service
32ms sys-kernel-config.mount
32ms sys-fs-fuse-connections.mount
9ms systemd-ask-password.socket
4ms systemd-sysext.socket
2ms systemd-factory-reset.socket
2ms systemd-coredump.socket
1ms systemd-creds.socket
801us avahi-daemon.socket
734us dbus.socket
135us systemd-journald-dev-log.socket
109us systemd-machined.socket
90us systemd-journald.socket
77us systemd-importd.socket
66us systemd-logind-varlink.socket
63us systemd-resolved-monitor.socket
62us systemd-networkd-varlink.socket
57us systemd-udevd-control.socket
53us systemd-udevd-varlink.socket
53us nscd.socket
49us systemd-hostnamed.socket
43us systemd-udevd-kernel.socket
41us systemd-resolved-varlink.socket
30us systemd-rfkill.socket
29us systemd-networkd.socket
13.796s mandriva-everytime.service
13.673s network-up.service
13.645s plymouth-quit-wait.service
9.483s dev-sda5.device
8.411s shorewall.service
7.481s upower.service
6.778s network.service
4.824s udisks2.service
4.144s iio-sensor-proxy.service
3.768s systemd-fsck@dev-disk-by\x2duuid-76133e0b\x2d3c2c\x2d48d3\x2db365\x2d73060bd1449d.service
3.709s polkit.service
3.670s avahi-daemon.service
3.612s dbus.service
3.248s mga-bg-res.service
2.953s systemd-resolved.service
2.914s rtkit-daemon.service
2.902s switcheroo-control.service
2.831s ModemManager.service
2.675s media-windows.mount
2.669s systemd-vconsole-setup.service
2.323s systemd-tmpfiles-setup-dev-early.service
2.283s power-profiles-daemon.service
2.199s systemd-fsck-root.service
2.096s systemd-udev-trigger.service
2.016s systemd-networkd.service
1.972s systemd-networkd-persistent-storage.service
1.874s user@0.service
1.804s systemd-udevd.service
1.779s dkms-autorebuild.service
1.504s home.mount
1.349s systemd-tmpfiles-setup.service
1.184s systemd-logind.service
1.171s accounts-daemon.service
1.129s systemd-journald.service
1.084s systemd-backlight@backlight:acpi_video0.service
1.079s modprobe@fuse.service
1.075s systemd-modules-load.service
1.039s systemd-udev-load-credentials.service
1.008s systemd-rfkill.service
993ms nscd.service
906ms modprobe@dm_mod.service
902ms lightdm.service
845ms mdmonitor-takeover.service
844ms acpid.service
816ms cpupower.service
806ms dracut-shutdown.service
796ms gpm.service
627ms plymouth-start.service
615ms user-runtime-dir@0.service
591ms user@500.service
559ms modprobe@loop.service
553ms systemd-binfmt.service
419ms modprobe@configfs.service
394ms tmp.mount
361ms systemd-random-seed.service
314ms dev-hugepages.mount
313ms dev-mqueue.mount
313ms plymouth-read-write.service
312ms sys-kernel-debug.mount
311ms sys-kernel-tracing.mount
279ms systemd-timesyncd.service
277ms kmod-static-nodes.service
196ms systemd-sysctl.service
149ms user-runtime-dir@500.service
147ms dev-disk-by\x2duuid-9fe3a5b1\x2d3734\x2d47f5\x2d9d5d\x2d54c845af80ec.swap
124ms systemd-hostnamed.service
117ms proc-sys-fs-binfmt_misc.mount
113ms systemd-tmpfiles-setup-dev.service
113ms systemd-bootctl.socket
93ms systemd-remount-fs.service
86ms systemd-update-utmp.service
56ms systemd-user-sessions.service
32ms sys-kernel-config.mount
32ms sys-fs-fuse-connections.mount
9ms systemd-ask-password.socket
4ms systemd-sysext.socket
2ms systemd-factory-reset.socket
2ms systemd-coredump.socket
1ms systemd-creds.socket
801us avahi-daemon.socket
734us dbus.socket
135us systemd-journald-dev-log.socket
109us systemd-machined.socket
90us systemd-journald.socket
77us systemd-importd.socket
66us systemd-logind-varlink.socket
63us systemd-resolved-monitor.socket
62us systemd-networkd-varlink.socket
57us systemd-udevd-control.socket
53us systemd-udevd-varlink.socket
53us nscd.socket
49us systemd-hostnamed.socket
43us systemd-udevd-kernel.socket
41us systemd-resolved-varlink.socket
30us systemd-rfkill.socket
29us systemd-networkd.socket
@Nico80, tu parlais des services "network", comment est-ce que je peux vérifier qu'il n'y a pas d'anciennes connexions en trop?
Yuusha Membre non connecté
-
- Voir le profil du membre Yuusha
- Inscrit le : 04/07/2017
- Groupes :
-
Modérateur
-
Administrateur
-
Forgeron
Ton disque est-il un SSD ou un HDD ?
prune bleue Membre non connecté
-
- Voir le profil du membre prune bleue
- Inscrit le : 28/12/2008
- Groupes :
prune bleue Membre non connecté
-
- Voir le profil du membre prune bleue
- Inscrit le : 28/12/2008
- Groupes :
Il me semble que les cartes Nvidia anciennes sont compliquées à gérer?
Répondre
Vous n'êtes pas autorisé à écrire dans cette catégorie