[Résolu] LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

French Forum

Moderator: Laurent85

User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

[Résolu] LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

Bonjour,

Je ne parviens pas a corriger ce problème au démarrage.

Suite a une mise a jour de LM20 vers LM20.1 le temps de démarrage de mon PC est supérieur a 3 minute.
le retour de la commande suivante: "systemd-analyze critical-chain", me donne ce résultat, comment corriger ce problème?

networkd-dispatcher.service @3min 5.195s +13.152s
apparmor.service @1min 33.763s +1.531s

Code: Select all

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 @3min 18.349s
└─multi-user.target @3min 18.349s
  └─networkd-dispatcher.service @3min 5.195s +13.152s
    └─basic.target @3min 5.017s
      └─sockets.target @3min 5.017s
        └─uuidd.socket @3min 5.016s
          └─sysinit.target @3min 4.782s
            └─apparmor.service @1min 33.763s +1.531s
              └─systemd-journald.socket @3.619s
                └─-.mount @3.607s
                  └─system.slice @3.607s
                    └─-.slice @3.607s

Code: Select all

systemd-analyze
Startup finished in 20.190s (kernel) + 3min 18.376s (userspace) = 3min 38.567s 
graphical.target reached after 3min 18.349s in userspace
Last edited by pbm on Thu Jan 21, 2021 11:22 am, edited 1 time in total.
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

J'ajoute le résultat de la commande: "systemd-analyze blame"

Code: Select all

systemd-analyze blame
13.152s networkd-dispatcher.service                                            >
 9.954s udisks2.service                                                        >
 8.839s accounts-daemon.service                                                >
 6.988s NetworkManager.service                                                 >
 6.645s ubuntu-system-adjustments.service                                      >
 6.131s polkit.service                                                         >
 5.485s dev-mapper-vgmint\x2droot.device                                       >
 5.289s lightdm.service                                                        >
 5.247s plymouth-quit-wait.service                                             >
 4.930s avahi-daemon.service                                                   >
 4.679s thermald.service                                                       >
 4.663s systemd-logind.service                                                 >
 4.662s wpa_supplicant.service                                                 >
 4.481s gpu-manager.service                                                    >
 3.843s ModemManager.service                                                   >
 3.528s grub-common.service                                                    >
 3.315s networking.service                                                     >
 3.299s hddtemp.service                                                        >
 2.989s rsyslog.service                                                        >
 2.804s systemd-journal-flush.service                                          >
 2.566s upower.service                                                         >
 2.069s grub-initrd-fallback.service                                           >
 1.790s user@1000.service                                                      >
 1.536s systemd-udevd.service                                                  >
 1.531s apparmor.service                                                       >
 1.466s colord.service                                                         >
 1.138s e2scrub_reap.service                                                   >
 1.111s systemd-backlight@backlight:acpi_video0.service                        >
  856ms systemd-modules-load.service                                           >
  827ms ntp.service                                                            >
  816ms atd.service                                                            >
  807ms systemd-tmpfiles-setup.service                                         >
  777ms systemd-sysusers.service                                               >
  767ms ecbd.service                                                           >
  735ms keyboard-setup.service                                                 >
  707ms systemd-tmpfiles-setup-dev.service                                     >
  698ms systemd-resolved.service                                               >
Last edited by Laurent85 on Sun Jan 17, 2021 5:52 am, edited 1 time in total.
Reason: Removed duplicates
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
maqc
Level 1
Level 1
Posts: 30
Joined: Thu Dec 31, 2020 12:02 pm
Location: Québec

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by maqc »

Est-ce que la commande dmesg affiche des erreurs juste après le démarrage? As-tu fais un changement dans tes disques durs ou tes partitions?
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

Je n'ai pas fais de changement sur mes partitions dernièrement, j'ai fais une install de "win" et "playonlinux" et une mise a jour lm20 vers lm20.1
pour les install, j'ai tenté de déinstaller "win et "playonlinux" ca n'a rien changer.

la réponse à la commande "dmesg" me retourne le ca:
une erreur

Code: Select all

[   11.927478] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

Je viens de redémarrer et relancer une commande "dmesg", et il n'y à plus d’erreur par contre démarrage très long.
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

3ème redémarrage + la commande "dmesg"
cette fois de nouveau une erreur !!!

Code: Select all

[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

Pendant le redémarrage il semble que le temps d'attente soit divisé sur 2 problème:
Le premier temps d'attente est ici:

Code: Select all

/dev/sdb: open failed: No medium found
Volume group "vgmint" not found
Cannot process volume group vgmint
/dev/sdb: open failed: No medium found
Volume group "vgmint" not found
Cannot process volume group vgmint
/dev/mapper/vgmint-root: clean, 1771461/30384128 files, 3725832/12152216 blocks
/dev/sdb: open failed: No medium found
Volume group "vgmint" not found
Cannot process volume group vgmint
/dev/sdb: open failed: No medium found
Volume group "vgmint" not found
Cannot process volume group vgmint
/dev/mapper/vgmint-root: clean, 1771461/30384128 files, 3725832/12152216 blocks
/dev/sdb: open failed: No medium found
Volume group "vgmint" not found
Cannot process volume group vgmint
/dev/sdb: open failed: No medium found
Volume group "vgmint" not found
Cannot process volume group vgmint
/dev/mapper/vgmint-root: clean, 1771461/30384128 files, 3725832/12152216 blocks
/dev/sdb: open failed: No medium found
Volume group "vgmint" not found
Cannot process volume group vgmint
/dev/sdb: open failed: No medium found
Volume group "vgmint" not found
Cannot process volume group vgmint
/dev/mapper/vgmint-root: clean, 1771461/30384128 files, 3725832/12152216 blocks
/dev/sdb: open failed: No medium found
Volume group "vgmint" not found
Cannot process volume group vgmint
/dev/sdb: open failed: No medium found
Volume group "vgmint" not found
Cannot process volume group vgmint
/dev/mapper/vgmint-root: clean, 1771461/30384128 files, 3725832/12152216 blocks
[ TIME ] Timed out waiting for device /dev/disk/by-uuid/6898f8be-c300-4df8-ba17-a4f0d202c154
[DEPEND] Dependency failed for Cryptography Setup for sdb5_crypt.
[DEPEND] Dependency failed for Local Encrypted Volumes.
[ TIME ] Timed out waiting for device /dev/disk/by-uuid/bb4ed0bc-b9ae-4db4-a64a-e70a1d65e9e2.
[DEPEND] Dependency failed for /Boot.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Clean up any left by 0dns-up.
resolvconf.service
finard.service
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
maqc
Level 1
Level 1
Posts: 30
Joined: Thu Dec 31, 2020 12:02 pm
Location: Québec

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by maqc »

Je ne suis pas un expert, mais se peut-il que ton système ait de la misère à trouver la partition swap?
Quel est le résultat complet de sudo cat /var/log/boot.log ou journalctl -b?
Et aussi de lsblk -f?
Laurent85
Level 16
Level 16
Posts: 6984
Joined: Tue May 26, 2015 10:11 am

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by Laurent85 »

Bonjour,
Quel est le retour de :

Code: Select all

blkid
cat /etc/fstab
Image
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

Bonjour,

Pour le retour "

Code: Select all

sudo cat /var/log/boot.log
[/b]"

Code: Select all

        
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started LSB: Record successful boot for GRUB.
         Stopping CUPS Scheduler...
[  OK  ] Stopped CUPS Scheduler.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Finished Detect the availa… deal with any system changes.
[  OK  ] Started Login Service.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Make remote CUPS printers available locally.
[  OK  ] Started WPA supplicant.
[  OK  ] Started Thermal Daemon Service.
[  OK  ] Started Network Manager.
[  OK  ] Reached target Network.
         Starting Manage, Install and Generate Color Profiles...
         Starting Network Time Service...
         Starting OpenVPN service...
         Starting Permit User Sessions...
[  OK  ] Finished OpenVPN service.
[  OK  ] Finished Permit User Sessions.
         Starting Light Display Manager...
         Starting Hold until boot process finishes up...
[  OK  ] Started Authorization Manager.
         Starting Modem Manager...
         Starting Hostname Service...
[  OK  ] Started Network Time Service.
[  OK  ] Finished Ubuntu system adjustments.
[  OK  ] Started Hostname Service.
[  OK  ] Finished Rotate log files.
[  OK  ] Started Manage, Install and Generate Color Profiles.
[  OK  ] Started Modem Manager.
[  OK  ] Started Accounts Service.
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started Dispatcher daemon for systemd-networkd.
------------ Thu Jan 21 13:37:52 CET 2021 ------------
  /dev/sdb: open failed: No medium found
  Volume group "vgmint" not found
  Cannot process volume group vgmint
  /dev/sdb: open failed: No medium found
  Volume group "vgmint" not found
  Cannot process volume group vgmint
/dev/mapper/vgmint-root: clean, 1814963/30384128 files, 38675833/121522176 blocks
[ TIME ] Timed out waiting for device /dev/disk/by-uuid/6090f8be-c300-4df8-ba17-a4f0d202c154.
[DEPEND] Dependency failed for Cryptography Setup for sdb5_crypt.
[DEPEND] Dependency failed for Local Encrypted Volumes.
[ TIME ] Timed out waiting for device /dev/disk/by-uuid/bb4ed0bc-b9ae-4db4-a64a-e70a1d65e9e2.
[DEPEND] Dependency failed for /Boot.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Clean up any mess left by 0dns-up.
[  OK  ] Stopped target Block Device Preparation for /dev/mapper/sdb5_crypt.
[  OK  ] Finished Tell Plymouth To Write Out Runtime Data.
[  OK  ] Finished Set console font and keymap.
         Mounting Arbitrary Executable File Formats File System...
[  OK  ] Mounted Arbitrary Executable File Formats File System.
[  OK  ] Finished Enable support for additional executable binary formats.
         Starting Show Plymouth Boot Screen...
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Finished Create Volatile Files and Directories.
         Starting Network Name Resolution...
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Finished Update UTMP about System Boot/Shutdown.
[  OK  ] Finished Load AppArmor profiles.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
[   ***] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[     *] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[*     ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[     *] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[*     ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[     *] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[*     ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[     *] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[*     ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[     *] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[*     ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[     *] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[*     ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[     *] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[*     ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[     *] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[*     ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[     *] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[*     ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[     *] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[*     ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[     *] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[  *** ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[*     ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[     *] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[    **] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[   ***] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[  *** ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[*     ] (1 of 2) A start job is running for /dev/disk/by-uuid/6090f8be-c300-4df[**    ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[***   ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/bb4ed0bc-b9ae-4db[ TIME ] Timed out waiting for device /dev/disk/by-uuid/6090f8be-c300-4df8-ba17-a4f0d202c154.
[DEPEND] Dependency failed for Cryptography Setup for sdb5_crypt.
[DEPEND] Dependency failed for Local Encrypted Volumes.
[ TIME ] Timed out waiting for device /dev/disk/by-uuid/bb4ed0bc-b9ae-4db4-a64a-e70a1d65e9e2.
[DEPEND] Dependency failed for /Boot.
[DEPEND] Dependency failed for Local File Systems.
[  OK  ] Reached target Block Device Preparation for /dev/mapper/sdb5_crypt.
         Starting Raise network interfaces...
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Stopped target Block Device Preparation for /dev/mapper/sdb5_crypt.
------------ Thu Jan 21 13:39:23 CET 2021 ------------
[  OK  ] Finished Tell Plymouth To Write Out Runtime Data.
[  OK  ] Reached target System Initialization.
[  OK  ] Started ACPI Events Check.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Started resolvconf-pull-resolved.path.
[  OK  ] Started Trigger anacron every hour.
[  OK  ] Started Daily apt download activities.
[  OK  ] Started Daily apt upgrade and clean activities.
[  OK  ] Started Periodic ext4 Online Metadata Check for All Filesystems.
[  OK  ] Started Discard unused blocks once a week.
[  OK  ] Started Refresh fwupd metadata regularly.
[  OK  ] Started Daily rotation of log files.
[  OK  ] Started Daily man-db regeneration.
[  OK  ] Started Message of the Day.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Timers.
[  OK  ] Listening on ACPID Listen Socket.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on CUPS Scheduler.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Listening on UUID daemon activation socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Accounts Service...
[  OK  ] Started ACPI event daemon.
         Starting Save/Restore Sound Card State...
[  OK  ] Started Run anacron jobs.
         Starting Deferred execution scheduler...
         Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Started Regular background program processing daemon.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Started D-Bus System Message Bus.
         Starting Network Manager...
[  OK  ] Started Save initial kernel messages after boot.
         Starting Remove Stale Online ext4 Metadata Check Snapshots...
         Starting LSB: EPSON Custom Backend Daemon...
         Starting Detect the available GPUs and deal with any system changes...
         Starting LSB: Record successful boot for GRUB...
         Starting GRUB failed boot detection...
         Starting LSB: disk temperature monitoring daemon...
[  OK  ] Started irqbalance daemon.
         Starting Tool to automatically collect and submit kernel crash signatures...
         Starting Initialize hardware monitoring sensors...
[  OK  ] Started mintsystem.service.
         Starting Dispatcher daemon for systemd-networkd...
[  OK  ] Started ntp-systemd-netif.service.
[  OK  ] Started Set the CPU Frequency Scaling governor.
         Starting Authorization Manager...
         Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
         Starting resolvconf-pull-resolved.service...
         Starting System Logging Service...
         Starting Login Service...
         Starting Thermal Daemon Service...
         Starting Ubuntu system adjustments...
         Starting Disk Manager...
         Starting WPA supplicant...
[  OK  ] Started Deferred execution scheduler.
[  OK  ] Started LSB: EPSON Custom Backend Daemon.
[  OK  ] Finished Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
[  OK  ] Finished Save/Restore Sound Card State.
[  OK  ] Reached target Sound Card.
[  OK  ] Finished Initialize hardware monitoring sensors.
[  OK  ] Finished Remove Stale Online ext4 Metadata Check Snapshots.
[  OK  ] Started Tool to automatically collect and submit kernel crash signatures.
[  OK  ] Finished GRUB failed boot detection.
[  OK  ] Finished resolvconf-pull-resolved.service.
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started LSB: Record successful boot for GRUB.
[  OK  ] Finished Raise network interfaces.
[  OK  ] Started System Logging Service.
[  OK  ] Finished Detect the available GPUs and deal with any system changes.
[  OK  ] Started Login Service.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Make remote CUPS printers available locally.
[  OK  ] Started Thermal Daemon Service.
[  OK  ] Started WPA supplicant.
         Starting Manage, Install and Generate Color Profiles...
[  OK  ] Finished Ubuntu system adjustments.
[  OK  ] Started Authorization Manager.
         Starting Modem Manager...
[  OK  ] Started Network Manager.
[  OK  ] Reached target Network.
         Starting Network Time Service...
         Starting OpenVPN service...
         Starting Permit User Sessions...
[  OK  ] Finished OpenVPN service.
[  OK  ] Started Network Time Service.
[  OK  ] Finished Permit User Sessions.
         Starting Light Display Manager...
         Starting Hold until boot process finishes up...
[  OK  ] Started Manage, Install and Generate Color Profiles.
         Starting Hostname Service...
[  OK  ] Started Accounts Service.
[  OK  ] Started Hostname Service.
[  OK  ] Started Modem Manager.
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Disk Manager.
[  OK  ] Started Network Manager Script Dispatcher Service.
et

Code: Select all

lsblk -f

Code: Select all

NAME FSTYPE LABEL UUID                                   FSAVAIL FSUSE% MOUNTPOINT
sda                                                                     
├─sda1
│    vfat         AF61-F85C                                 511M     0% /boot/efi
├─sda2
│                                                                       
├─sda5
│    ext4         c1854e96-4e58-4a44-a026-4399a96c3d09    149,3M    72% /boot
└─sda6
     crypto       5579a076-86e7-4f64-8859-c1d9814717ee                  
  └─sda6_crypt
     LVM2_m       s87oQY-kGNU-L59L-rcVJ-aZEG-iFJK-bDJML2                
    ├─vgmint-root
    │  ext4         fe6f9625-2541-4ef0-8d54-07a90bbd2d78    292,5G    31% /run/times
    └─vgmint-swap_1
       swap         d738de1e-1b35-459a-a4c5-50b684b0cbca                  [SWAP]
sr0                               
Last edited by pbm on Thu Jan 21, 2021 9:49 am, edited 1 time in total.
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

Bonjour,

Pour le retour de :

Code: Select all

blkid
cat /etc/fstab
[/b]

Code: Select all

/dev/mapper/sda6_crypt: UUID="s87oQY-kGNU-L59L-rcVJ-aZEG-iFJK-bDJML2" TYPE="LVM2_member"
/dev/sda1: UUID="AF61-F85C" TYPE="vfat" PARTUUID="fff5a75b-01"
/dev/sda5: UUID="c1854e96-4e58-4a44-a026-4399a96c3d09" TYPE="ext4" PARTUUID="fff5a75b-05"
/dev/sda6: UUID="5579a076-86e7-4f64-8859-c1d9814717ee" TYPE="crypto_LUKS" PARTUUID="fff5a75b-06"
/dev/mapper/vgmint-root: UUID="fe6f9625-2541-4ef0-8d54-07a90bbd2d78" TYPE="ext4"
/dev/mapper/vgmint-swap_1: UUID="d738de1e-1b35-459a-a4c5-50b684b0cbca" TYPE="swap"
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
Laurent85
Level 16
Level 16
Posts: 6984
Joined: Tue May 26, 2015 10:11 am

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by Laurent85 »

Il manque le retour de :

Code: Select all

cat /etc/fstab
Image
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

Oups

Code: Select all

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>
/dev/mapper/vgmint-root /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda5 during installation
UUID=c1854e96-4e58-4a44-a026-4399a96c3d09 /boot           ext4    defaults        0       2
# /boot/efi was on /dev/sda1 during installation
UUID=AF61-F85C  /boot/efi       vfat    umask=0077      0       1
/dev/mapper/vgmint-swap_1 none            swap    sw              0       0
UUID=bb4ed0bc-b9ae-4db4-a64a-e70a1d65e9e2 /Boot ext4 defaults 0 0
/dev/disk/by-id/usb-Generic-_Multi-Card_20090516388200000-0:0 /mnt/usb-Generic-_Multi-Card_20090516388200000-0:0 auto nosuid,nodev,nofail,noauto,x-gvfs-show 0 0
Je ne sais pas si il y a un rapport, j'ai remplacer mon DD en utilisant OEMIE sur PC.
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
Laurent85
Level 16
Level 16
Posts: 6984
Joined: Tue May 26, 2015 10:11 am

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by Laurent85 »

pbm wrote:
Thu Jan 21, 2021 10:16 am
Je ne sais pas si il y a un rapport, j'ai remplacer mon DD en utilisant OEMIE sur PC.
Déjà fstab n'est as correct. Edite le fichier et supprime cette ligne :
pbm wrote:
Thu Jan 21, 2021 10:16 am

Code: Select all

...
UUID=bb4ed0bc-b9ae-4db4-a64a-e70a1d65e9e2 /Boot ext4 defaults 0 0
...
Donne aussi le retour de :

Code: Select all

sudo cat /etc/crypttab
Image
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

Merci Laurent,

le retour pour la commande

Code: Select all

cat /etc/crypttab

Code: Select all

sda6_crypt UUID=5579a076-86e7-4f64-8859-c1d9814717ee none luks,discard
sdb5_crypt UUID=6090f8be-c300-4df8-ba17-a4f0d202c154 none luks,discard
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

comment éditer le fichier et supprime une ligne quant je l'ouvre il est en lecture seul..
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
Laurent85
Level 16
Level 16
Posts: 6984
Joined: Tue May 26, 2015 10:11 am

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by Laurent85 »

Supprime aussi la ligne :
pbm wrote:
Thu Jan 21, 2021 10:30 am

Code: Select all

...
sdb5_crypt UUID=6090f8be-c300-4df8-ba17-a4f0d202c154 none luks,discard
Mets à jour l'initramfs :

Code: Select all

sudo update-initramfs -u
Ça devrait être bon après, redémarre.
Image
Laurent85
Level 16
Level 16
Posts: 6984
Joined: Tue May 26, 2015 10:11 am

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by Laurent85 »

pbm wrote:
Thu Jan 21, 2021 10:36 am
comment éditer le fichier et supprime une ligne quant je l'ouvre il est en lecture seul..
Utilise :

Code: Select all

xed admin:/etc/fstab
Image
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

OK Merci je viens de supprimer la ligne

Code: Select all

UUID=bb4ed0bc-b9ae-4db4-a64a-e70a1d65e9e2 /Boot ext4 defaults 0 0
Dans le fichier fstab

l'autre ligne a supprimer se trouve dans quelle fichier ?

Code: Select all

sdb5_crypt UUID=6090f8be-c300-4df8-ba17-a4f0d202c154 
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
User avatar
pbm
Level 1
Level 1
Posts: 14
Joined: Fri Jan 15, 2021 6:36 am
Location: france

Re: LM20.1 Démarrage trés lent > 3mn (networkd-dispatcher.service)

Post by pbm »

Ok je viens de supprimer la second ligne dans le fichier cryptab

Code: Select all

/etc/crypttab

le retour de la commande

Code: Select all

sudo update-initramfs -u
me donne :

Code: Select all

sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-64-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgmint-swap_1)
I: Set the RESUME variable to override this.
est-ce normal ?
Version Linux Mint 20.1 Ulyssa 64-bit | Noyau Linux 5.4.0-62-generic x86_64 | MATE 1.24.0
Toshiba Satellite-C660 | Pentium(R) Dual-Core CPU T4500 @ 2.30GHz × 2
Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
Post Reply

Return to “Français (French)”