#1 Le 22/02/2021, à 05:02
- Mario2020C
[RÉSOLU] Démarrage très lent après une réinstallation d'image sur SSD
Bonjour à tous.
J'ai changé mon disque dur SSD et j'ai réinstallé l'image de mes partitions Dual-boot Win10, partition Datas et Ubuntu 20.04.
Tout a bien redémarré à la différence que Linux prend plus de 2 minutes pour démarrer.
J'ai lu les docs mais je ne trouve pas la solution puisque je ne m'y connais pas assez en commandes Linux.
J'en déduis que je n'ai plus de swap depuis la réinstallation de mon image (est-ce nécessaire avec un SSD de 800G et 8g de RAM?)
Mon processeur:
mario@mario-HP-EliteBook-Folio-9480m:~$ lscpu
Architecture : x86_64
Mode(s) opératoire(s) des processeurs : 32-bit, 64-bit
Boutisme : Little Endian
Address sizes: 39 bits physical, 48 bits virtual
Processeur(s) : 4
Liste de processeur(s) en ligne : 0-3
Thread(s) par cœur : 2
Cœur(s) par socket : 2
Socket(s) : 1
Nœud(s) NUMA : 1
Identifiant constructeur : GenuineIntel
Famille de processeur : 6
Modèle : 69
Nom de modèle : Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
Révision : 1
Vitesse du processeur en MHz : 1534.613
Vitesse maximale du processeur en MHz : 3300,0000
Vitesse minimale du processeur en MHz : 800,0000
BogoMIPS : 5387.45
Cache L1d : 64 KiB
Cache L1i : 64 KiB
Cache L2 : 512 KiB
Cache L3 : 4 MiB
Nœud NUMA 0 de processeur(s) : 0-3
Vulnerability Itlb multihit: KVM: Mitigation: VMX unsupported
Vulnerability L1tf: Mitigation; PTE Inversion
Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown: Mitigation; PTI
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling
Vulnerability Srbds: Mitigation; Microcode
Vulnerability Tsx async abort: Not affected
Drapaux : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse
2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology no
nstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm
pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fau
lt epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsave
opt dtherm ida arat pln pts md_clear flush_l1dInformations système:
mario@mario-HP-EliteBook-Folio-9480m:~$ 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/sda6 during installation
UUID=aceb1bd9-3ec7-4250-99b1-aac3489226c9 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
#UUID=405C-EBF7 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
UUID=405C-EBF7 /boot/efi vfat defaults 0 1Aussi:
mario@mario-HP-EliteBook-Folio-9480m:~$ sudo blkid
[sudo] Mot de passe de mario :
/dev/sda5: UUID="aceb1bd9-3ec7-4250-99b1-aac3489226c9" TYPE="ext4" PARTUUID="0eef610f-c7fe-4f04-94b7-5333672839ed"
/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="DF28-495A" TYPE="vfat" PARTUUID="ed27ea9a-480d-4ced-b9a4-acfbd8eebf2b"
/dev/sda3: UUID="01416B718C76436D" TYPE="ntfs" PARTUUID="a37ae10a-811a-4b32-befe-9660fc4b09a1"
/dev/sda4: LABEL="DATAS hp" UUID="32DE0495DE04540F" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="2dbcdb15-5c50-46e6-b78b-0da7115f62bb"
/dev/sda6: UUID="8D59276DDFFE16DF" TYPE="ntfs" PARTUUID="7adbafef-81db-41c2-8e03-3018280fe848"
/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/sda1: PARTUUID="323ffb0e-1b91-423f-8812-f0c43cc6ce76"Puis, j'ai créé un fichier graphique boot.svg pour voir visuellement où c'est plus lent.
sudo systemd-analyze plot > boot.svg
J'ai continué par faire un Boot-Info qui donne:
boot-info-4ppa125 [20210221_2141]
============================== Boot Info Summary ===============================
=> No boot loader is installed in the MBR of /dev/sda.
sda1: __________________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
sda2: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 8/2012: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootmgfw.efi
/efi/Boot/bootx64.efi /efi/Boot/fbx64.efi
/efi/Boot/grubx64.efi /efi/Boot/mmx64.efi
/efi/Boot/UBbootx64.efi /efi/ubuntu/grubx64.efi
/efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi
/efi/ubuntu/grub.cfg /efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/bootmgr.efi
/efi/Microsoft/Boot/memtest.efi
sda3: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 8 or 10
Boot files: /bootmgr /Windows/System32/winload.exe
sda4: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda5: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 20.04.2 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub
sda6: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
================================ 2 OS detected =================================
OS#1: L'OS actuellement utilisé - Ubuntu 20.04.2 LTS CurrentSession on sda5
OS#2: Windows 8 or 10 on sda3
============================ Architecture/Host Info ============================
CPU architecture: 64-bit
BOOT_IMAGE of the installed session in use:
/boot/vmlinuz-5.8.0-43-generic root=UUID=aceb1bd9-3ec7-4250-99b1-aac3489226c9 ro quiet splash vt.handoff=7
===================================== UEFI =====================================
BIOS is EFI-compatible, and is setup in EFI-mode for this installed-session.
SecureBoot disabled.
efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000
Boot0000* Notebook Hard Drive BBS(HD,,0x0).......................................................................
Boot0001* USB Hard Drive 1 - USB Flash Memory BBS(HD,,0x900).......................................................................
Boot0002* USB Hard Drive 2 - Generic External BBS(HD,,0x900).......................................................................
Boot0003* Notebook Ethernet BBS(128,,0x0)........................E..............................................
Boot0004* ubuntu HD(1,GPT,5d3ad37e-afc0-46d5-8957-a8511208b235,0x800,0x32000)/File(\EFI\ubuntu\shimx64.efi)
Boot0005* Windows Boot Manager HD(2,GPT,ed27ea9a-480d-4ced-b9a4-acfbd8eebf2b,0x40800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0007* ubuntu (cloned) HD(2,GPT,ed27ea9a-480d-4ced-b9a4-acfbd8eebf2b,0x40800,0x32000)/File(\EFI\ubuntu\shimx64.efi)
78415fb8fb9b909f8029858113f1335f sda2/Boot/bkpbootx64.efi
e69be5ddc7c4165e0f3e5ee05d267ec2 sda2/Boot/bootmgfw.efi
3c080490d0eb8fdb738f298c3e44b3e0 sda2/Boot/bootx64.efi
2895d47544fd587b26c7e29be1295c27 sda2/Boot/fbx64.efi
8ed07d5ee4e5e1534bcf64037b7589ff sda2/Boot/grubx64.efi
dc3c47be2f78a78e5e57d097ae6c5c84 sda2/Boot/mmx64.efi
78415fb8fb9b909f8029858113f1335f sda2/Boot/UBbootx64.efi
637fa7fabc8a2f70312edf2f15e275ff sda2/ubuntu/grubx64.efi
dc3c47be2f78a78e5e57d097ae6c5c84 sda2/ubuntu/mmx64.efi
78415fb8fb9b909f8029858113f1335f sda2/ubuntu/shimx64.efi
3c080490d0eb8fdb738f298c3e44b3e0 sda2/Microsoft/Boot/bootmgfw.efi
da7c9088c9d0bff4ac469abdfc8f540e sda2/Microsoft/Boot/bootmgr.efi
============================= Drive/Partition Info =============================
Disks info: ____________________________________________________________________
sda : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, has-os, 34 sectors * 512 bytes
Partitions info (1/3): _________________________________________________________
sda5 : is-os, 64, apt-get, signed grub-pc grub-efi , grub2, grub-install, grubenv-ok, update-grub, farbios
sda2 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda3 : is-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda4 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda6 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
Partitions info (2/3): _________________________________________________________
sda5 : isnotESP, fstab-has-bad-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda2 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda3 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, bootmgr, notwinboot
sda4 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda6 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot
Partitions info (3/3): _________________________________________________________
sda5 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda
sda2 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda3 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda4 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda6 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
fdisk -l (filtered): ___________________________________________________________
Disk sda: 588.74 GiB, 632131200000 bytes, 1234631250 sectors
Disk identifier: 7A8B9E19-9504-4603-8BC7-C5B338D6094E
Start End Sectors Size Type
sda1 34 262177 262144 128M Microsoft reserved
sda2 264192 468991 204800 100M EFI System
sda3 468992 293281791 292812800 139.6G Microsoft basic data
sda4 293281792 1026736127 733454336 349.8G Microsoft basic data
sda5 1026736128 1233586175 206850048 98.6G Linux filesystem
sda6 1233586176 1234630655 1044480 510M Windows recovery environment
parted -lm (filtered): _________________________________________________________
sda:632GB:scsi:512:4096:gpt:ATA INTEL SSDSC2BB80:;
1:17.4kB:134MB:134MB:::msftres;
2:135MB:240MB:105MB:fat32::boot, esp;
3:240MB:150GB:150GB:ntfs::msftdata;
4:150GB:526GB:376GB:ntfs:Basic data partition:msftdata;
5:526GB:632GB:106GB:ext4::;
6:632GB:632GB:535MB:ntfs::diag;
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 323ffb0e-1b91-423f-8812-f0c43cc6ce76
├─sda2 vfat DF28-495A ed27ea9a-480d-4ced-b9a4-acfbd8eebf2b
├─sda3 ntfs 01416B718C76436D a37ae10a-811a-4b32-befe-9660fc4b09a1
├─sda4 ntfs 32DE0495DE04540F 2dbcdb15-5c50-46e6-b78b-0da7115f62bb DATAS hp Basic data partition
├─sda5 ext4 aceb1bd9-3ec7-4250-99b1-aac3489226c9 0eef610f-c7fe-4f04-94b7-5333672839ed
└─sda6 ntfs 8D59276DDFFE16DF 7adbafef-81db-41c2-8e03-3018280fe848
df (filtered): _________________________________________________________________
Avail Use% Mounted on
sda2 60.6M 39% /mnt/boot-sav/sda2
sda3 61.2G 56% /mnt/boot-sav/sda3
sda4 283.4G 19% /mnt/boot-sav/sda4
sda5 66G 27% /
sda6 85.9M 83% /mnt/boot-sav/sda6
Mount options: __________________________________________________________________
sda2 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sda3 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda4 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda5 rw,relatime,errors=remount-ro
sda6 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
===================== sda2/efi/ubuntu/grub.cfg (filtered) ======================
search.fs_uuid aceb1bd9-3ec7-4250-99b1-aac3489226c9 root hd0,gpt5
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
====================== sda5/boot/grub/grub.cfg (filtered) ======================
Ubuntu aceb1bd9-3ec7-4250-99b1-aac3489226c9
Ubuntu, avec Linux 5.8.0-43-generic aceb1bd9-3ec7-4250-99b1-aac3489226c9
Ubuntu, avec Linux 5.8.0-41-generic aceb1bd9-3ec7-4250-99b1-aac3489226c9
Windows Boot Manager (sur sda1) osprober-efi-405C-EBF7
### END /etc/grub.d/30_os-prober ###
UEFI Firmware Settings uefi-firmware
### END /etc/grub.d/30_uefi-firmware ###
========================== sda5/etc/fstab (filtered) ===========================
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda6 during installation
UUID=aceb1bd9-3ec7-4250-99b1-aac3489226c9 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
/swapfile none swap sw 0 0
UUID=405C-EBF7 /boot/efi vfat defaults 0 1
======================= sda5/etc/default/grub (filtered) =======================
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
==================== sda5: Location of files loaded by Grub ====================
GiB - GB File Fragment(s)
526,572212219 = 565,402607616 boot/grub/grub.cfg 2
499,040298462 = 535,840440320 boot/vmlinuz 1
514,423110962 = 552,357609472 boot/vmlinuz-5.8.0-41-generic 1
499,040298462 = 535,840440320 boot/vmlinuz-5.8.0-43-generic 1
514,423110962 = 552,357609472 boot/vmlinuz.old 1
499,310844421 = 536,130936832 boot/initrd.img 2
508,837535858 = 546,360143872 boot/initrd.img-5.8.0-41-generic 3
499,310844421 = 536,130936832 boot/initrd.img-5.8.0-43-generic 2
508,837535858 = 546,360143872 boot/initrd.img.old 3
===================== sda5: ls -l /etc/grub.d/ (filtered) ======================
-rwxr-xr-x 1 root root 17622 nov 12 18:15 10_linux
-rwxr-xr-x 1 root root 42359 nov 12 18:15 10_linux_zfs
-rwxr-xr-x 1 root root 12894 jui 30 2020 20_linux_xen
-rwxr-xr-x 1 root root 12059 jui 30 2020 30_os-prober
-rwxr-xr-x 1 root root 1424 jui 30 2020 30_uefi-firmware
-rwxr-xr-x 1 root root 214 jui 30 2020 40_custom
-rwxr-xr-x 1 root root 216 jui 30 2020 41_custom
Suggested repair: ______________________________________________________________
The default repair of the Boot-Repair utility would reinstall the grub-efi-amd64-signed of
sda5,
using the following options: sda2/boot/efi,
Additional repair would be performed: unhide-bootmenu-10s win-legacy-basic-fix use-standard-efi-file restore-efi-backups
Final advice in case of suggested repair: ______________________________________
Please do not forget to make your UEFI firmware boot on the L'OS actuellement utilisé - Ubuntu 20.04.2 LTS CurrentSession entry (sda2/efi/****/shim****.efi (**** will be updated in the final message) file) !
If your computer reboots directly into Windows, try to change the boot order in your UEFI firmware.
If your UEFI firmware does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI\****\shim****.efi (**** will be updated in the final message)Ensuite j'ai tapé la commande: systemd-analyze
mario@mario-HP-EliteBook-Folio-9480m:~$ systemd-analyze
Startup finished in 13.848s (firmware) + 1.656s (loader) + 5.474s (kernel) + 1min 41.211s (userspace) = 2min 2.190s
graphical.target reached after 1min 41.185s in userspaceEnsuite la commande systemd-analyze critical-chain
mario@mario-HP-EliteBook-Folio-9480m:~$ 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 @1min 41.185s
└─multi-user.target @1min 41.185s
└─smbd.service @1min 41.039s +145ms
└─nmbd.service @1min 40.941s +96ms
└─network-online.target @1min 40.937s
└─NetworkManager-wait-online.service @1min 31.532s +9.404s
└─NetworkManager.service @1min 31.331s +198ms
└─dbus.service @1min 31.326s
└─basic.target @1min 31.313s
└─sockets.target @1min 31.313s
└─snapd.socket @1min 31.312s +939us
└─sysinit.target @1min 31.308s
└─snapd.apparmor.service @1min 31.160s +147ms
└─apparmor.service @1min 31.003s +155ms
└─systemd-journald.socket @754ms
└─-.mount @751ms
└─system.slice @751ms
└─-.slice @751mssystemd-analyze; systemd-analyze blame --no-pager; systemd-analyze --user; systemd-analyze blame --user --no-pager;systemctl --failed;
mario@mario-HP-EliteBook-Folio-9480m:~$ systemd-analyze; systemd-analyze blame --no-pager; systemd-analyze --user; systemd-analyze blame --user --no-pager;systemctl --failed;
Startup finished in 13.848s (firmware) + 1.656s (loader) + 5.474s (kernel) + 1min 41.211s (userspace) = 2min 2.190s
graphical.target reached after 1min 41.185s in userspace
45.640s apt-daily-upgrade.service
38.660s apt-daily.service
9.404s NetworkManager-wait-online.service
4.138s plymouth-quit-wait.service
2.592s fwupd-refresh.service
1.375s dev-sda5.device
889ms systemd-backlight@backlight:intel_backlight.service
854ms man-db.service
781ms snapd.service
766ms dev-loop1.device
740ms dev-loop3.device
731ms logrotate.service
728ms dev-loop2.device
697ms snap-gnome\x2d3\x2d34\x2d1804-66.mount
682ms snap-snapd-10707.mount
681ms dev-loop0.device
680ms dev-loop5.device
675ms dev-loop6.device
629ms dev-loop4.device
617ms dev-loop8.device
612ms dev-loop9.device
605ms dev-loop7.device
545ms dev-loop11.device
538ms dev-loop10.device
519ms networkd-dispatcher.service
504ms dev-loop12.device
479ms snap-kde\x2dframeworks\x2d5\x2dqt\x2d5\x2d14\x2dcore18-4.mount
477ms dev-loop13.device
453ms snap-gtk\x2dcommon\x2dthemes-1514.mount
437ms snap-gtk\x2dcommon\x2dthemes-1506.mount
423ms udisks2.service
398ms snap-core18-1944.mount
388ms systemd-logind.service
368ms accounts-daemon.service
333ms snap-simplescreenrecorder\x2dbrlin-69.mount
329ms systemd-resolved.service
320ms snap-snapd-11036.mount
308ms snap-core-10823.mount
292ms upower.service
277ms dev-loop14.device
258ms dev-loop15.device
245ms snap-ksudoku-50.mount
245ms systemd-journald.service
229ms systemd-udev-trigger.service
229ms snap-core18-1988.mount
226ms snap-core-10583.mount
222ms systemd-timesyncd.service
212ms polkit.service
208ms snap-snap\x2dstore-518.mount
198ms NetworkManager.service
198ms avahi-daemon.service
198ms ModemManager.service
191ms bluetooth.service
185ms user@1000.service
175ms iio-sensor-proxy.service
161ms systemd-udevd.service
156ms switcheroo-control.service
155ms apparmor.service
149ms systemd-rfkill.service
147ms snapd.apparmor.service
145ms smbd.service
140ms rtkit-daemon.service
138ms thermald.service
137ms apport.service
133ms wpa_supplicant.service
125ms snap-snap\x2dstore-467.mount
121ms grub-common.service
118ms e2scrub_reap.service
112ms gpu-manager.service
111ms snap-canonical\x2dlivepatch-95.mount
107ms gdm.service
106ms alsa-restore.service
103ms systemd-modules-load.service
102ms snap-gnome\x2d3\x2d34\x2d1804-60.mount
96ms nmbd.service
95ms grub-initrd-fallback.service
92ms keyboard-setup.service
76ms rsyslog.service
76ms systemd-random-seed.service
75ms systemd-sysusers.service
73ms systemd-journal-flush.service
71ms e2scrub_all.service
69ms systemd-sysctl.service
67ms snapd.seeded.service
65ms systemd-user-sessions.service
62ms colord.service
60ms systemd-tmpfiles-setup.service
58ms systemd-tmpfiles-setup-dev.service
52ms systemd-remount-fs.service
46ms pppd-dns.service
36ms user-runtime-dir@1000.service
34ms swapfile.swap
33ms systemd-update-utmp.service
23ms modprobe@drm.service
23ms systemd-update-utmp-runlevel.service
23ms plymouth-start.service
22ms systemd-tmpfiles-clean.service
17ms openvpn.service
16ms dev-hugepages.mount
15ms kerneloops.service
15ms dev-mqueue.mount
14ms sys-kernel-debug.mount
13ms sys-kernel-tracing.mount
13ms proc-sys-fs-binfmt_misc.mount
12ms plymouth-read-write.service
10ms kmod-static-nodes.service
9ms console-setup.service
6ms ufw.service
5ms sys-fs-fuse-connections.mount
4ms sys-kernel-config.mount
3ms setvtrgb.service
2ms motd-news.service
939us snapd.socket
Startup finished in 684ms (userspace)
default.target reached after 684ms in userspace
1.858s gnome-shell-x11.service
709ms gsd-xsettings.service
520ms gsd-rfkill.service
489ms update-notifier-crash.service
477ms tracker-miner-fs.service
381ms gsd-power.service
302ms gsd-media-keys.service
297ms gsd-datetime.service
296ms gsd-color.service
277ms pulseaudio.service
257ms tracker-extract.service
250ms gsd-housekeeping.service
245ms gsd-wwan.service
237ms gsd-keyboard.service
210ms gsd-smartcard.service
197ms gsd-print-notifications.service
188ms gsd-screensaver-proxy.service
185ms gsd-wacom.service
185ms gsd-sharing.service
184ms gsd-usb-protection.service
175ms gsd-sound.service
171ms evolution-source-registry.service
159ms evolution-calendar-factory.service
156ms gnome-terminal-server.service
115ms gsd-a11y-settings.service
106ms gnome-session-manager@ubuntu.service
91ms gvfs-goa-volume-monitor.service
75ms gnome-session-signal-init.service
67ms evolution-addressbook-factory.service
64ms gvfs-udisks2-volume-monitor.service
50ms xdg-document-portal.service
20ms dbus.socket
17ms gnome-keyring.service
13ms gvfs-gphoto2-volume-monitor.service
12ms gvfs-mtp-volume-monitor.service
11ms gvfs-daemon.service
11ms gvfs-afc-volume-monitor.service
10ms gvfs-metadata.service
9ms gnome-session-monitor.service
7ms xdg-permission-store.service
5ms at-spi-dbus-bus.service
5ms gnome-keyring-ssh.service
4ms session-migration.service
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.Puis la commande
mario@mario-HP-EliteBook-Folio-9480m:~$ sudo blkid
/dev/sda5: UUID="aceb1bd9-3ec7-4250-99b1-aac3489226c9" TYPE="ext4" PARTUUID="0eef610f-c7fe-4f04-94b7-5333672839ed"
/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="DF28-495A" TYPE="vfat" PARTUUID="ed27ea9a-480d-4ced-b9a4-acfbd8eebf2b"
/dev/sda3: UUID="01416B718C76436D" TYPE="ntfs" PARTUUID="a37ae10a-811a-4b32-befe-9660fc4b09a1"
/dev/sda4: LABEL="DATAS hp" UUID="32DE0495DE04540F" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="2dbcdb15-5c50-46e6-b78b-0da7115f62bb"
/dev/sda6: UUID="8D59276DDFFE16DF" TYPE="ntfs" PARTUUID="7adbafef-81db-41c2-8e03-3018280fe848"
/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/sda1: PARTUUID="323ffb0e-1b91-423f-8812-f0c43cc6ce76"Et la commande
mario@mario-HP-EliteBook-Folio-9480m:~$ 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/sda6 during installation
UUID=aceb1bd9-3ec7-4250-99b1-aac3489226c9 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
#UUID=405C-EBF7 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
UUID=405C-EBF7 /boot/efi vfat defaults 0 1Je crois pouvoir faire un update du Grub pour effacer les références à la swap par:
mario@mario-HP-EliteBook-Folio-9480m:~$ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Création du fichier de configuration GRUB…
Image Linux trouvée : /boot/vmlinuz-5.8.0-43-generic
Image mémoire initiale trouvée : /boot/initrd.img-5.8.0-43-generic
Image Linux trouvée : /boot/vmlinuz-5.8.0-41-generic
Image mémoire initiale trouvée : /boot/initrd.img-5.8.0-41-generic
Windows Boot Manager trouvé sur /dev/sda2@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings
faitJe crois avoir fait le tour des infos de mon système mais à part la dernière commande pour updater le Grub, je ne sais pas par où commencer.
Merci
Dernière modification par Mario2020C (Le 23/02/2021, à 17:04)
Hors ligne
#2 Le 22/02/2021, à 07:37
- malbo
Re : [RÉSOLU] Démarrage très lent après une réinstallation d'image sur SSD
Bonjour,
Dans ton fichier fstab, on peut voir cette ligne :
UUID=405C-EBF7 /boot/efi vfat defaults 0 1or dans la liste des identifiants de partitions, on ne trouve pas 405C-EBF7 :
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 323ffb0e-1b91-423f-8812-f0c43cc6ce76
├─sda2 vfat DF28-495A ed27ea9a-480d-4ced-b9a4-acfbd8eebf2b
├─sda3 ntfs 01416B718C76436D a37ae10a-811a-4b32-befe-9660fc4b09a1
├─sda4 ntfs 32DE0495DE04540F 2dbcdb15-5c50-46e6-b78b-0da7115f62bb DATAS hp Basic data partition
├─sda5 ext4 aceb1bd9-3ec7-4250-99b1-aac3489226c9 0eef610f-c7fe-4f04-94b7-5333672839ed
└─sda6 ntfs 8D59276DDFFE16DF 7adbafef-81db-41c2-8e03-3018280fe848 Il va falloir dans un premier temps que tu commentes la ligne du fstab, c'est à dire qu'elle devienne :
# UUID=405C-EBF7 /boot/efi vfat defaults 0 1Le caractère # en tête de la ligne, ça permet que la ligne soit considérée comme un commentaire et qu'elle ne soit pas prise en compte au démarrage de l'ordi.
Dernière modification par malbo (Le 22/02/2021, à 08:23)
Hors ligne
#3 Le 22/02/2021, à 18:43
- Mario2020C
Re : [RÉSOLU] Démarrage très lent après une réinstallation d'image sur SSD
Merci malbo pour ta réponse.
J'ai modifié le fichier fstab tel que demandé par la commande $ sudo gedit /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/sda6 during installation
UUID=aceb1bd9-3ec7-4250-99b1-aac3489226c9 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
#UUID=405C-EBF7 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
#UUID=405C-EBF7 /boot/efi vfat defaults 0 1Puis, la commande:
mario@mario-HP-EliteBook-Folio-9480m:~$ systemd-analyze
Startup finished in 11.442s (firmware) + 1.659s (loader) + 5.389s (kernel) + 12.694s (userspace) = 31.184s
graphical.target reached after 12.669s in userspace31 secondes au lieu de 2 minutes c'est toute une différence. Merci beaucoup.
Est-ce possible de le peaufiner de 12 secondes de moins pour éliminer le temps de recherche de la carte graphique?
Hors ligne
#4 Le 22/02/2021, à 19:11
- lucmars
Re : [RÉSOLU] Démarrage très lent après une réinstallation d'image sur SSD
A mon avis c'est ça ou le mode console !
Gaulois Matter !
Hors ligne
#5 Le 23/02/2021, à 05:59
- malbo
Re : [RÉSOLU] Démarrage très lent après une réinstallation d'image sur SSD
Bonjour,
La réparation que je t'ai conseillée (et qui a fonctionné) est une réparation provisoire. Elle a permis de mettre en évidence la ligne qui posait problème mais il convient de faire la réparation complète, c'est de modifier le fstab afin de remplacer la ligne :
#UUID=405C-EBF7 /boot/efi vfat defaults 0 1par la ligne suivante (caractère # enlevé et UUID corrigé) :
UUID=DF28-495A /boot/efi vfat defaults 0 1Cette modif étant faite, il faut que le temps de démarrage reste ce qu'il est actuellement (environ 31 secondes) sinon c'est que la modif de la ligne est incorrecte.
EDIT : tu passeras la commande suivante pour vérifier que la partition EFI est bien montée :
mount | grep sdaDans le résultat, tu dois trouver une ligne qui mentionne le montage de /dev/sda2 dans /boot/efi
Dernière modification par malbo (Le 23/02/2021, à 06:39)
Hors ligne
#6 Le 23/02/2021, à 17:02
- Mario2020C
Re : [RÉSOLU] Démarrage très lent après une réinstallation d'image sur SSD
Merci
J'ai récupéré une seconde quand même... Ce n'est pas rien.
Voici mes résultats:
mario@mario-HP-EliteBook-Folio-9480m:~$ 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/sda6 during installation
UUID=aceb1bd9-3ec7-4250-99b1-aac3489226c9 / ext4 errors=remount-ro 0 1
/swapfile none swap sw 0 0
UUID=DF28-495A /boot/efi vfat defaults 0 1Ce qui donne après redémarrage:
mario@mario-HP-EliteBook-Folio-9480m:~$ systemd-analyze
Startup finished in 13.520s (firmware) + 1.657s (loader) + 5.571s (kernel) + 9.737s (userspace) = 30.486s
graphical.target reached after 9.721s in userspace
mario@mario-HP-EliteBook-Folio-9480m:~$ Et finalement:
mario@mario-HP-EliteBook-Folio-9480m:~$ mount | grep sda
/dev/sda5 on / type ext4 (rw,relatime,errors=remount-ro)
/dev/sda2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)Un gros merci encore. Vous êtes des pros.
Hors ligne