Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Démarrage trop lent.

Mhady

Bonjour j'ai un HP notebook
Core i5 7th Gen, 8Go RAM, 2To HDD
Ubuntu 20.04.1 Gnome 3.
Son démarrage est trop lent(2-2.3 min)
Après quelques heures d'usage il se plante aussi.
Alors il a fait juste 1an d'usage.
Je sais pas si le problème vient du système ou de la machine.
SVP besoin d'aide. C'est pas facile de coder avec une machine pareille.
Merci.

geole

Bonjour
On ne peut pas parler de lenteur lorsque ubuntu 20.04.1 démarre en deux minutes à partir d'un disque dur.
Peux-tu donner ces retours

systemd-analyze time

systemd-analyze blame | head -25

systemd-analyze critical-chain

journalctl -b --no-pager -p err

Mhady

Merci d'avoir repondu voici le retour des commandes.

systemd-analyze time:

systemd-analyze time
Startup finished in 8.068s (firmware) + 3.692s (loader) + 22.374s (kernel) + 2min 30.589s (userspace) = 3min 4.725s 
graphical.target reached after 2min 30.434s in userspace.

systemd-analyze blame | head -25:

1min 9.208s plymouth-quit-wait.service                                                               
 1min 383ms mysql.service                                                                            
    54.869s systemd-fsck@dev-disk-by\x2duuid-fe764620\x2d93b3\x2d4cb5\x2d81b4\x2d7ca357799a98.service
    38.842s virtualbox.service                                                                       
    18.302s apport-autoreport.service                                                                
    15.756s dev-sda1.device                                                                          
    15.272s NetworkManager-wait-online.service                                                       
    10.180s networkd-dispatcher.service                                                              
    10.053s apache2.service                                                                          
     8.705s dev-loop17.device                                                                        
     8.656s dev-loop18.device                                                                        
     8.624s dev-loop6.device                                                                         
     8.239s dev-loop24.device                                                                        
     8.207s dev-loop23.device                                                                        
     8.196s dev-loop25.device                                                                        
     8.155s dev-loop28.device                                                                        
     8.142s dev-loop31.device                                                                        
     8.137s dev-loop22.device                                                                        
     8.114s dev-loop29.device                                                                        
     8.067s dev-loop32.device                                                                        
     8.059s dev-loop30.device                                                                        
     7.539s dev-loop16.device                                                                        
     7.420s dev-loop8.device                                                                         
     7.348s ModemManager.service                                                                     
     7.324s accounts-daemon.service

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 @2min 30.434s
└─multi-user.target @2min 30.434s
  └─snapd.seeded.service @2min 25.529s +1.073s
    └─snapd.service @2min 25.881s +695ms
      └─basic.target @1min 16.123s
        └─sockets.target @1min 16.123s
          └─snapd.socket @1min 16.118s +3ms
            └─sysinit.target @1min 15.996s
              └─local-fs.target @1min 15.995s
                └─run-snapd-ns-canonical\x2dlivepatch.mnt.mount @1min 31.019s
                  └─run-snapd-ns.mount @1min 27.482s
                    └─local-fs-pre.target @5.682s
                      └─systemd-tmpfiles-setup-dev.service @5.176s +506ms
                        └─systemd-sysusers.service @4.785s +387ms
                          └─systemd-remount-fs.service @4.671s +73ms
                            └─systemd-journald.socket @4.419s
                              └─system.slice @4.409s
                                └─-.slice @4.409s

journalctl -b --no-pager -p err:

-- Logs begin at Sun 2020-11-29 00:09:51 GMT, end at Thu 2021-01-14 17:39:11 GMT. --
janv. 14 13:02:26 mhady-PC kernel: Initramfs unpacking failed: Decoding failed
janv. 14 13:02:26 mhady-PC systemd[256]: /usr/lib/systemd/system-generators/netplan failed with exit status 1.
janv. 14 13:02:37 mhady-PC systemd[1]: Timed out waiting for device /dev/disk/by-uuid/5DE3-128F.
janv. 14 13:02:37 mhady-PC systemd[1]: Timed out waiting for device /dev/disk/by-uuid/c1901225-1961-497a-8af0-7cc7fa6990be.
janv. 14 13:02:37 mhady-PC systemd[1]: Timed out waiting for device /dev/disk/by-uuid/fe764620-93b3-4cb5-81b4-7ca357799a98.
janv. 14 13:02:37 mhady-PC systemd[1]: Timed out waiting for device /dev/disk/by-uuid/04b85c84-f004-4a33-b6bd-95c12a53a990.
janv. 14 13:02:47 mhady-PC systemd[1]: Timed out waiting for device /dev/disk/by-uuid/c1901225-1961-497a-8af0-7cc7fa6990be.
janv. 14 13:03:43 mhady-PC systemd[1]: Failed to start VirtualBox Web Service.
janv. 14 13:03:47 mhady-PC named[1055]: /etc/bind/named.conf.default-zones:39: missing ';' before '}'
janv. 14 13:03:47 mhady-PC named[1055]: loading configuration: failure
janv. 14 13:03:47 mhady-PC named[1055]: exiting (due to fatal error)
janv. 14 13:03:48 mhady-PC systemd[1]: Failed to start Dispatcher daemon for systemd-networkd.
janv. 14 13:03:51 mhady-PC bluetoothd[964]: Loading LTKs timed out for hci0
janv. 14 13:03:53 mhady-PC systemd[1]: Failed to start The Apache HTTP Server.
janv. 14 13:03:55 mhady-PC wpa_supplicant[1003]: bgscan simple: Failed to enable signal strength monitoring
janv. 14 13:04:00 mhady-PC systemd[1]: Failed to start Disk Manager.
janv. 14 13:04:29 mhady-PC systemd[1]: Failed to start Disk Manager.
janv. 14 13:04:37 mhady-PC systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
janv. 14 13:04:47 mhady-PC systemd[1]: Failed to start Snap Daemon.
janv. 14 13:05:48 mhady-PC gdm-password][2046]: gkr-pam: unable to locate daemon control file
janv. 14 13:06:44 mhady-PC systemd[1]: Failed to start Firmware update daemon.
janv. 14 13:24:04 mhady-PC wpa_supplicant[1003]: bgscan simple: Failed to enable signal strength monitoring
janv. 14 13:27:00 mhady-PC wpa_supplicant[1003]: bgscan simple: Failed to enable signal strength monitoring
janv. 14 14:09:12 mhady-PC wpa_supplicant[1003]: bgscan simple: Failed to enable signal strength monitoring

geole

anv. 14 13:02:37 mhady-PC systemd[1]: Timed out waiting for device /dev/disk/by-uuid/5DE3-128F.
janv. 14 13:02:37 mhady-PC systemd[1]: Timed out waiting for device /dev/disk/by-uuid/c1901225-1961-497a-8af0-7cc7fa6990be.
janv. 14 13:02:37 mhady-PC systemd[1]: Timed out waiting for device /dev/disk/by-uuid/fe764620-93b3-4cb5-81b4-7ca357799a98.
janv. 14 13:02:37 mhady-PC systemd[1]: Timed out waiting for device /dev/disk/by-uuid/04b85c84-f004-4a33-b6bd-95c12a53a990.
janv. 14 13:02:47 mhady-PC systemd[1]: Timed out waiting for device /dev/disk/by-uuid/c1901225-1961-497a-8af0-7cc7fa6990be.

peux-tu donner ces retours

sudo blkid
cat /etc/fstab

Tu devrais regarder le contenu de ce fichier /etc/bind/named.conf.default-zones

Mhady

mhady@mhady-PC:~$ sudo blkid
[sudo] Mot de passe de mhady : 
/dev/sda3: UUID="04b85c84-f004-4a33-b6bd-95c12a53a990" TYPE="swap" PARTUUID="83c93109-8659-416c-9747-0d7905e9afa3"
/dev/sda1: UUID="2cc0b168-d2df-4fa0-9292-8eb2b0e6f29e" TYPE="ext4" PARTUUID="aaf55ce3-f0ec-4aa3-a62c-0ab327096aad"
/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/sda2: UUID="fe764620-93b3-4cb5-81b4-7ca357799a98" TYPE="ext4" PARTUUID="fdc42a0e-9d72-43d6-bf75-616e03857df1"
/dev/sda4: UUID="5DE3-128F" TYPE="vfat" PARTUUID="28667344-1656-4536-907e-5916b76f4d50"
/dev/sda5: LABEL="Exchange" UUID="ae4b1daa-dd70-4664-b45c-0d33d466defc" TYPE="ext4" PARTUUID="28f716be-c40f-48a9-8f7c-f5b24fc6a07a"
/dev/sda6: UUID="592934e5-f71b-4b1f-b1a7-3acbd9b1ff3e" TYPE="ext4" PARTUUID="9fb8fc19-bb2e-4861-a462-4a5630058f2b"
/dev/sda7: UUID="51b20c23-1401-48b0-88f8-7460ed926572" TYPE="ext4" PARTUUID="8f13bdb0-23aa-48ed-91dd-2af024fec12c"
/dev/sda8: UUID="c6120f6b-ea31-47c8-bf47-7c1d58846961" TYPE="swap" PARTUUID="9bee3e0b-4051-4e96-b09f-13286c53a6a8"
/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"
/dev/loop20: TYPE="squashfs"
/dev/loop21: TYPE="squashfs"
/dev/loop22: TYPE="squashfs"
/dev/loop23: TYPE="squashfs"
/dev/loop24: TYPE="squashfs"
/dev/loop25: TYPE="squashfs"
/dev/loop26: TYPE="squashfs"
/dev/loop27: TYPE="squashfs"
/dev/loop28: TYPE="squashfs"
/dev/loop29: TYPE="squashfs"
/dev/loop30: TYPE="squashfs"
/dev/loop31: TYPE="squashfs"
/dev/loop32: TYPE="squashfs"

Mhady

mhady@mhady-PC:~$ 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>
# / was on /dev/sda1 during installation
UUID=2cc0b168-d2df-4fa0-9292-8eb2b0e6f29e /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda4 during installation
#UUID=5DE3-128F  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/sda2 during installation
UUID=fe764620-93b3-4cb5-81b4-7ca357799a98 /home           ext4    defaults        0       2
# swap was on /dev/sda3 during installation
UUID=c1901225-1961-497a-8af0-7cc7fa6990be none            swap    sw              0       0
UUID=5DE3-128F  /boot/efi       vfat    defaults      0       1
/dev/disk/by-uuid/04b85c84-f004-4a33-b6bd-95c12a53a990 none swap sw 0 0

geole

Je ne sais pas expliquer ces time-out. Le disque serait-il en mauvais état? Tu vas installer l'outil smartmontools https://doc.ubuntu-fr.org/smartmontools avec cette commande

sudo apt-get install --no-install-recommends smartmontools

et donner ce retour

sudo smartclt   -s on - a /dev/sda

Mhady

mhady@mhady-PC:~$ sudo smartctl -s on -a /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.8.0-36-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Mobile HDD
Device Model:     ST2000LM007-1R8174
Serial Number:    ZDZ4GVM8
LU WWN Device Id: 5 000c50 0b310ab43
Firmware Version: RDM4
User Capacity:    2000398934016 bytes [2,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Jan 14 18:48:31 2021 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x51) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 331) minutes.
SCT capabilities: 	       (0x303d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   080   064   006    Pre-fail  Always       -       106360428
  3 Spin_Up_Time            0x0023   099   098   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   098   098   000    Old_age   Always       -       2517
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   084   060   045    Pre-fail  Always       -       248388044
  9 Power_On_Hours          0x0032   095   095   000    Old_age   Always       -       4532 (27 34 0)
 10 Spin_Retry_Count        0x0033   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       -       2442
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       1
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   059   045   040    Old_age   Always       -       41 (Min/Max 34/42)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       600
192 Power-Off_Retract_Count 0x0022   100   100   000    Old_age   Always       -       77
193 Load_Cycle_Count        0x0032   086   086   000    Old_age   Always       -       28334
194 Temperature_Celsius     0x0022   041   055   000    Old_age   Always       -       41 (0 21 0 0 0)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       3
254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

marcodel

salut

fstab a écrit UUID=c1901225-1961-497a-8af0-7cc7fa6990be none swap sw 0 0
/dev/disk/by-uuid/04b85c84-f004-4a33-b6bd-95c12a53a990 none swap sw 0 0

Mhady

Oui j'ai pas compris.
Et pourtant quand je lance Monitor System je vois bel et bien mon swap(7Gb).
Mais je vois la RAM qui est chargée et le swap juste vide(à 0%, la ram 52% cache 2.8G)

marcodel a écritsalut
fstab a écrit UUID=c1901225-1961-497a-8af0-7cc7fa6990be none swap sw 0 0
/dev/disk/by-uuid/04b85c84-f004-4a33-b6bd-95c12a53a990 none swap sw 0 0
a+

sudo fdisk -l:

Périphérique      Début        Fin   Secteurs Taille Type
/dev/sda1          2048  999999487  999997440 476,9G Système de fichiers Linux
/dev/sda2     999999488 3037929471 2037929984 971,8G Système de fichiers Linux
/dev/sda3    3037929472 3053953023   16023552   7,7G Partition d'échange Linux
/dev/sda4    3053953024 3054051327      98304    48M Système EFI

marcodel

dans fstab le swap est declare 2 fois
si tu compares les uuid avec celles de blkid , tu verras qu' une n'est pas bonne
a+

Mhady

Je vois peut etre c'est parce que j'ai Kali aussi installé (dual boot) d'où le second swap (pour la partition de Kali-linux).

geole

Il y a bien deux partitions de swap dans le fstab qui correspondent â deux partitions formatées en swap d'après la commande blkid. De plus, il y aussi attente pour le home et la partition de boot EFI.
Cela fait beaucoup.

Mhady

Oui comme j'ai indiqué ici. ça pourrait être la raison non?

Mhady a écritJe vois peut être c'est parce que j'ai Kali aussi installé (dual boot) d'où le second swap (pour la partition de Kali-linux).

marcodel

cette uuid c1901225-1961-497a-8af0-7cc7fa6990be n'est pas trouve par blkid
donc elle est fausse

Mhady

Ok Alors du coup je peux supprimer cette partition swap sans problème?

marcodel

c'est cette ligne qu'il faut supprimer dans le fstab

    UUID=c1901225-1961-497a-8af0-7cc7fa6990be none            swap    sw              0       0

geole

Bonjour
Bien vu pour cette ligne mais va rester certainement les deux autres cas