Recentemente, eu inicializei meu laptop Windows 10 com o Ubuntu 17.10 No entanto, ele está inicializando muito lento na minha opinião, cerca de 1-2 minutos. Eu chequei criptografar minha pasta de início na instalação do Ubuntu, eu sei que isso pode causar o problema, mas isso deve ser corrigido, removendo o UID um arquivo de adição / swap, mas infelizmente não resolveu o meu problema
Conteúdo do meu crypttab:
cryptswap1 /swapfile /dev/urandom swap,offset=1024,cipher=aes-xts-plain64
$ systemd-analyze blame
17.293s plymouth-quit-wait.service
15.724s NetworkManager-wait-online.service
14.905s mysql.service
12.692s snapd.service
9.346s dev-sda4.device
9.194s winbind.service
8.144s [email protected]
7.689s gpu-manager.service
6.093s ModemManager.service
5.312s apache2.service
4.490s accounts-daemon.service
4.387s apport.service
4.377s udisks2.service
4.372s grub-common.service
3.909s NetworkManager.service
2.675s speech-dispatcher.service
2.609s systemd-logind.service
2.520s colord.service
2.227s apparmor.service
2.174s networking.service
2.020s avahi-daemon.service
2.004s bluetooth.service
1.974s alsa-restore.service
1.972s pppd-dns.service
1.972s rsyslog.service
1.959s fwupd.service
1.869s thermald.service
1.646s packagekit.service
1.612s polkit.service
1.218s keyboard-setup.service
1.164s dev-loop1.device
1.036s wpa_supplicant.service
1.024s systemd-modules-load.service
1.015s console-setup.service
997ms dns-clean.service
843ms dev-loop0.device
781ms systemd-resolved.service
746ms gdm.service
728ms qemu-kvm.service
646ms systemd-udevd.service
613ms systemd-timesyncd.service
597ms systemd-rfkill.service
546ms systemd-tmpfiles-setup-dev.service
545ms systemd-update-utmp.service
520ms kerneloops.service
516ms ufw.service
479ms dev-mqueue.mount
467ms systemd-backlight@backlight:intel_backlight.service
447ms dev-hugepages.mount
421ms systemd-tmpfiles-setup.service
417ms sys-kernel-debug.mount
332ms systemd-journald.service
312ms systemd-udev-trigger.service
276ms systemd-journal-flush.service
255ms dev-mapper-cryptswap1.swap
233ms upower.service
220ms systemd-fsck@dev-disk-by\x2duuid-04DB\x2dF406.service
218ms snap-intellij\x2didea\x2dultimate-9.mount
213ms systemd-user-sessions.service
186ms systemd-sysctl.service
142ms snap-core-3440.mount
127ms [email protected]
122ms kmod-static-nodes.service
97ms systemd-random-seed.service
49ms [email protected]
43ms rtkit-daemon.service
36ms plymouth-read-write.service
32ms systemd-remount-fs.service
32ms setvtrgb.service
25ms boot-efi.mount
12ms plymouth-start.service
8ms systemd-update-utmp-runlevel.service
1ms nvidia-persistenced.service
1ms sys-kernel-config.mount
1ms sys-fs-fuse-connections.mount
1ms snapd.socket
$ systemd-analyze crítico-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @36.720s
└─multi-user.target @36.719s
└─kerneloops.service @34.948s +520ms
└─network-online.target @34.938s
└─NetworkManager-wait-online.service @19.209s +15.724s
└─NetworkManager.service @15.285s +3.909s
└─dbus.service @13.420s
└─basic.target @13.263s
└─sockets.target @13.263s
└─snapd.socket @13.262s +1ms
└─sysinit.target @13.214s
└─apparmor.service @10.977s +2.227s
└─local-fs.target @10.938s
└─boot-efi.mount @10.913s +25ms
└─systemd-fsck@dev-disk-by\x2duuid-04DB\x2dF406.service @10.660s +220ms
└─dev-disk-by\x2duuid-04DB\x2dF406.device @10.660s
$ systemd-analyze
Startup finished in 3.396s (firmware) + 4.131s (loader) + 9.062s (kernel) + 36.755s (userspace) = 53.346s
Alguém sabe o que posso fazer para acelerar o processo de inicialização