SDA disparu
boot sur sdb mais plus de sda
Système et matériels / Installation et configuration
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
Reprise du message précédent
Bonjour,systemd-analyze blame
Caché :
[guy-jean@Asus-R-900V ~]$ systemd-analyze blame
27.866s network-up.service
1.186s network.service
964ms systemd-binfmt.service
824ms mandriva-everytime.service
716ms shorewall6.service
643ms dkms-autorebuild.service
626ms nfs-server.service
371ms systemd-udev-settle.service
369ms upower.service
362ms dev-sdb9.device
319ms packagekit.service
313ms systemd-udev-trigger.service
285ms udisks2.service
276ms user@1001.service
257ms resolvconf.service
186ms cups.service
178ms proc-fs-nfsd.mount
143ms mga-bg-res.service
132ms accounts-daemon.service
106ms polkit.service
94ms systemd-journal-flush.service
89ms bluetooth.service
89ms avahi-daemon.service
84ms lvm2-monitor.service
82ms power-profiles-daemon.service
81ms systemd-udevd.service
80ms dbus.service
77ms systemd-logind.service
64ms systemd-journald.service
61ms partimaged.service
55ms rtkit-daemon.service
53ms acpid.service
50ms systemd-vconsole-setup.service
47ms systemd-tmpfiles-setup.service
46ms gpm.service
46ms dracut-shutdown.service
43ms plymouth-quit-wait.service
42ms plymouth-start.service
40ms plymouth-quit.service
39ms systemd-fsck-root.service
37ms nfs-mountd.service
36ms colord.service
36ms systemd-remount-fs.service
27.866s network-up.service
1.186s network.service
964ms systemd-binfmt.service
824ms mandriva-everytime.service
716ms shorewall6.service
643ms dkms-autorebuild.service
626ms nfs-server.service
371ms systemd-udev-settle.service
369ms upower.service
362ms dev-sdb9.device
319ms packagekit.service
313ms systemd-udev-trigger.service
285ms udisks2.service
276ms user@1001.service
257ms resolvconf.service
186ms cups.service
178ms proc-fs-nfsd.mount
143ms mga-bg-res.service
132ms accounts-daemon.service
106ms polkit.service
94ms systemd-journal-flush.service
89ms bluetooth.service
89ms avahi-daemon.service
84ms lvm2-monitor.service
82ms power-profiles-daemon.service
81ms systemd-udevd.service
80ms dbus.service
77ms systemd-logind.service
64ms systemd-journald.service
61ms partimaged.service
55ms rtkit-daemon.service
53ms acpid.service
50ms systemd-vconsole-setup.service
47ms systemd-tmpfiles-setup.service
46ms gpm.service
46ms dracut-shutdown.service
43ms plymouth-quit-wait.service
42ms plymouth-start.service
40ms plymouth-quit.service
39ms systemd-fsck-root.service
37ms nfs-mountd.service
36ms colord.service
36ms systemd-remount-fs.service
35ms dmraid-activation.service
34ms systemd-tmpfiles-setup-dev.service
29ms mdmonitor.service
29ms systemd-fsck@dev-disk-by\x2duuid-b2d53723\x2d48bf\x2d4327\x2d8b35\x2dd12010d0e9df.service
29ms systemd-rfkill.service
28ms gssproxy.service
28ms msec.service
lines 1-50/93 47%
27.866s network-up.service
1.186s network.service
964ms systemd-binfmt.service
824ms mandriva-everytime.service
716ms shorewall6.service
643ms dkms-autorebuild.service
626ms nfs-server.service
371ms systemd-udev-settle.service
369ms upower.service
362ms dev-sdb9.device
319ms packagekit.service
313ms systemd-udev-trigger.service
285ms udisks2.service
276ms user@1001.service
257ms resolvconf.service
186ms cups.service
178ms proc-fs-nfsd.mount
143ms mga-bg-res.service
132ms accounts-daemon.service
106ms polkit.service
94ms systemd-journal-flush.service
89ms bluetooth.service
89ms avahi-daemon.service
84ms lvm2-monitor.service
82ms power-profiles-daemon.service
81ms systemd-udevd.service
80ms dbus.service
77ms systemd-logind.service
64ms systemd-journald.service
61ms partimaged.service
55ms rtkit-daemon.service
53ms acpid.service
50ms systemd-vconsole-setup.service
47ms systemd-tmpfiles-setup.service
46ms gpm.service
46ms dracut-shutdown.service
43ms plymouth-quit-wait.service
42ms plymouth-start.service
40ms plymouth-quit.service
39ms systemd-fsck-root.service
37ms nfs-mountd.service
36ms colord.service
36ms systemd-remount-fs.service
27.866s network-up.service
1.186s network.service
964ms systemd-binfmt.service
824ms mandriva-everytime.service
716ms shorewall6.service
643ms dkms-autorebuild.service
626ms nfs-server.service
371ms systemd-udev-settle.service
369ms upower.service
362ms dev-sdb9.device
319ms packagekit.service
313ms systemd-udev-trigger.service
285ms udisks2.service
276ms user@1001.service
257ms resolvconf.service
186ms cups.service
178ms proc-fs-nfsd.mount
143ms mga-bg-res.service
132ms accounts-daemon.service
106ms polkit.service
94ms systemd-journal-flush.service
89ms bluetooth.service
89ms avahi-daemon.service
84ms lvm2-monitor.service
82ms power-profiles-daemon.service
81ms systemd-udevd.service
80ms dbus.service
77ms systemd-logind.service
64ms systemd-journald.service
61ms partimaged.service
55ms rtkit-daemon.service
53ms acpid.service
50ms systemd-vconsole-setup.service
47ms systemd-tmpfiles-setup.service
46ms gpm.service
46ms dracut-shutdown.service
43ms plymouth-quit-wait.service
42ms plymouth-start.service
40ms plymouth-quit.service
39ms systemd-fsck-root.service
37ms nfs-mountd.service
36ms colord.service
36ms systemd-remount-fs.service
35ms dmraid-activation.service
34ms systemd-tmpfiles-setup-dev.service
29ms mdmonitor.service
29ms systemd-fsck@dev-disk-by\x2duuid-b2d53723\x2d48bf\x2d4327\x2d8b35\x2dd12010d0e9df.service
29ms systemd-rfkill.service
28ms gssproxy.service
28ms msec.service
lines 1-50/93 47%
le fstab je l'ai contrôlé et rien de l'ancien
Merci
Édité par GPE GPE Le 13/01/2026 à 10h50
Papoteur Membre non connecté
-
- Voir le profil du membre Papoteur
- Inscrit le : 03/10/2011
- Groupes :
-
Modérateur
-
Équipe Mageia
-
Administrateur
-
Forgeron
Le plus long est le démarrage du réseau.
Il y a pu avoir un démarrage long avec une compilation par dkms, mais pas sur le dernier démarrage.
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
suite à ton message je me suis penché sur les connexions et je me suis aperçu que l’Ethernet ne fonctionner plus, j'ai donc dans le MCC supprimer la connexion mais c'est toujours aussi long.
comment dire au système de ne pas rechercher une autre connexion? et bloquer sur wifi
Merci
Papoteur Membre non connecté
-
- Voir le profil du membre Papoteur
- Inscrit le : 03/10/2011
- Groupes :
-
Modérateur
-
Équipe Mageia
-
Administrateur
-
Forgeron
Il faut connaître le pilote de la carte et le blacklister dans un fichier de configuration à ajouter je ne sais plus où.
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
Papoteur :Tu es vraiment sûr de vouloir déactiver la carte réseau ? Je n'aime pas ça, le jour où on en a besoin, va retrouver la manip à faire.
Il faut connaître le pilote de la carte et le blacklister dans un fichier de configuration à ajouter je ne sais plus où.
Oui juste bloquer l’Ethernet qui ne marche plus, je suppose que c'est ça qui rallonge le temps d'allumage!
à moins que ce soit autre chose!
j'ai désactiver quelque services qui me servait pas, c'est un peu mieux
systemd-analyze blame
Caché :
[guy-jean@Asus-R-900V ~]$ systemd-analyze blame
1.358s network.service
919ms systemd-binfmt.service
832ms mandriva-everytime.service
646ms dkms-autorebuild.service
518ms dev-sdb9.device
385ms systemd-udev-trigger.service
370ms systemd-udev-settle.service
364ms nfs-server.service
345ms upower.service
314ms user@1001.service
295ms udisks2.service
182ms proc-fs-nfsd.mount
165ms accounts-daemon.service
155ms packagekit.service
149ms cups.service
139ms mga-bg-res.service
102ms lvm2-monitor.service
98ms polkit.service
91ms resolvconf.service
90ms systemd-journal-flush.service
81ms systemd-journald.service
79ms systemd-udevd.service
79ms power-profiles-daemon.service
72ms systemd-vconsole-setup.service
70ms systemd-logind.service
60ms bluetooth.service
58ms systemd-remount-fs.service
53ms dmraid-activation.service
52ms avahi-daemon.service
50ms partimaged.service
48ms systemd-fsck@dev-disk-by\x2duuid-bf4a3f4b\x2d3f25\x2d47a0\x2d929d\x2da2258b96de6c.service
45ms systemd-tmpfiles-setup.service
43ms dbus.service
41ms systemd-fsck@dev-disk-by\x2duuid-74f4ed01\x2d37fc\x2d4869\x2d81ca\x2d13c43c0ae7d9.service
40ms systemd-tmpfiles-clean.service
39ms plymouth-start.service
39ms systemd-fsck@dev-disk-by\x2duuid-b2d53723\x2d48bf\x2d4327\x2d8b35\x2dd12010d0e9df.service
38ms rtkit-daemon.service
37ms plymouth-quit-wait.service
36ms systemd-fsck@dev-disk-by\x2duuid-e43f1875\x2d593a\x2d4d24\x2d9c09\x2d843d8e18b6be.service
36ms systemd-fsck@dev-disk-by\x2duuid-0a94859a\x2d52ca\x2d4fdb\x2d96b2\x2d80bda81f5647.service
36ms plymouth-quit.service
33ms nfs-mountd.service
32ms systemd-tmpfiles-setup-dev.service
30ms acpid.service
28ms rpc-statd.service
27ms systemd-fsck-root.service
26ms gssproxy.service
24ms systemd-modules-load.service
24ms rpcbind.service
23ms boot-EFI.mount
23ms colord.service
23ms systemd-fsck@dev-disk-by\x2duuid-023218fe\x2def0a\x2d49a9\x2db634\x2dad6d0c4cc425.service
22ms dracut-shutdown.service
22ms nfs-idmapd.service
21ms gpm.service
21ms systemd-backlight@backlight:intel_backlight.service
21ms home-guy\x2djean-Box.mount
21ms msec.service
21ms dev-disk-by\x2duuid-2ad553c1\x2de663\x2d4113\x2da363\x2d5db239446c1f.swap
20ms modprobe@fuse.service
20ms dev-hugepages.mount
19ms dev-mqueue.mount
19ms modprobe@configfs.service
18ms sys-kernel-debug.mount
17ms sys-kernel-tracing.mount
17ms kmod-static-nodes.service
14ms nfsdcld.service
14ms user-runtime-dir@1001.service
14ms systemd-rfkill.service
14ms stockage.mount
14ms Home.mount
12ms tmp.mount
12ms systemd-random-seed.service
12ms plymouth-read-write.service
11ms home-test-1.mount
11ms systemd-sysctl.service
11ms home.mount
9ms systemd-update-utmp.service
8ms home-guy\x20jean-Diag.mount
7ms proc-sys-fs-binfmt_misc.mount
7ms systemd-update-utmp-runlevel.service
6ms var-lib-nfs-rpc_pipefs.mount
5ms systemd-user-sessions.service
4ms modprobe@drm.service
3ms rpc-statd-notify.service
3ms sys-kernel-config.mount
2ms modprobe@dm_mod.service
2ms modprobe@loop.service
2ms sys-fs-fuse-connections.mount
lines 41-90/90 (END)
1.358s network.service
919ms systemd-binfmt.service
832ms mandriva-everytime.service
646ms dkms-autorebuild.service
518ms dev-sdb9.device
385ms systemd-udev-trigger.service
370ms systemd-udev-settle.service
364ms nfs-server.service
345ms upower.service
314ms user@1001.service
295ms udisks2.service
182ms proc-fs-nfsd.mount
165ms accounts-daemon.service
155ms packagekit.service
149ms cups.service
139ms mga-bg-res.service
102ms lvm2-monitor.service
98ms polkit.service
91ms resolvconf.service
90ms systemd-journal-flush.service
81ms systemd-journald.service
79ms systemd-udevd.service
79ms power-profiles-daemon.service
72ms systemd-vconsole-setup.service
70ms systemd-logind.service
60ms bluetooth.service
58ms systemd-remount-fs.service
53ms dmraid-activation.service
52ms avahi-daemon.service
50ms partimaged.service
48ms systemd-fsck@dev-disk-by\x2duuid-bf4a3f4b\x2d3f25\x2d47a0\x2d929d\x2da2258b96de6c.service
45ms systemd-tmpfiles-setup.service
43ms dbus.service
41ms systemd-fsck@dev-disk-by\x2duuid-74f4ed01\x2d37fc\x2d4869\x2d81ca\x2d13c43c0ae7d9.service
40ms systemd-tmpfiles-clean.service
39ms plymouth-start.service
39ms systemd-fsck@dev-disk-by\x2duuid-b2d53723\x2d48bf\x2d4327\x2d8b35\x2dd12010d0e9df.service
38ms rtkit-daemon.service
37ms plymouth-quit-wait.service
36ms systemd-fsck@dev-disk-by\x2duuid-e43f1875\x2d593a\x2d4d24\x2d9c09\x2d843d8e18b6be.service
36ms systemd-fsck@dev-disk-by\x2duuid-0a94859a\x2d52ca\x2d4fdb\x2d96b2\x2d80bda81f5647.service
36ms plymouth-quit.service
33ms nfs-mountd.service
32ms systemd-tmpfiles-setup-dev.service
30ms acpid.service
28ms rpc-statd.service
27ms systemd-fsck-root.service
26ms gssproxy.service
24ms systemd-modules-load.service
24ms rpcbind.service
23ms boot-EFI.mount
23ms colord.service
23ms systemd-fsck@dev-disk-by\x2duuid-023218fe\x2def0a\x2d49a9\x2db634\x2dad6d0c4cc425.service
22ms dracut-shutdown.service
22ms nfs-idmapd.service
21ms gpm.service
21ms systemd-backlight@backlight:intel_backlight.service
21ms home-guy\x2djean-Box.mount
21ms msec.service
21ms dev-disk-by\x2duuid-2ad553c1\x2de663\x2d4113\x2da363\x2d5db239446c1f.swap
20ms modprobe@fuse.service
20ms dev-hugepages.mount
19ms dev-mqueue.mount
19ms modprobe@configfs.service
18ms sys-kernel-debug.mount
17ms sys-kernel-tracing.mount
17ms kmod-static-nodes.service
14ms nfsdcld.service
14ms user-runtime-dir@1001.service
14ms systemd-rfkill.service
14ms stockage.mount
14ms Home.mount
12ms tmp.mount
12ms systemd-random-seed.service
12ms plymouth-read-write.service
11ms home-test-1.mount
11ms systemd-sysctl.service
11ms home.mount
9ms systemd-update-utmp.service
8ms home-guy\x20jean-Diag.mount
7ms proc-sys-fs-binfmt_misc.mount
7ms systemd-update-utmp-runlevel.service
6ms var-lib-nfs-rpc_pipefs.mount
5ms systemd-user-sessions.service
4ms modprobe@drm.service
3ms rpc-statd-notify.service
3ms sys-kernel-config.mount
2ms modprobe@dm_mod.service
2ms modprobe@loop.service
2ms sys-fs-fuse-connections.mount
lines 41-90/90 (END)
Répondre
Vous n'êtes pas autorisé à écrire dans cette catégorie