O Ubuntu 17.04 leva 3 minutos do GRUB para a tela de login

1

Estou executando o Ubuntu Budgie 17.04 em um HP Envy 13 com 8 GB de RAM, um SSD e um núcleo I5, portanto, espero que o Ubuntu seja inicializado rapidamente. Estou com a inicialização dupla no Windows 10 e desativei a inicialização rápida nas configurações do Windows. Inicialização segura está ativada. Eu vi algumas "correções", como inicialização terrivelmente lenta no Ubuntu 17.04 mas não vai me deixar salvar o arquivo editado nem tenho certeza quanto do arquivo para editar para tentar isso.

Veja a saída de systemd-analyze :

jake@jake-HP-ENVY-13:~$ systemd-analyze
Startup finished in 3.046s (firmware) + 2.865s (loader) + 1.564s (kernel) + 3min 482ms (userspace) = 3min 7.958s

jake@jake-HP-ENVY-13:~$ systemd-analyze blame
          5.022s nmbd.service
          1.904s fwupd.service
          1.454s apparmor.service
          1.414s plymouth-read-write.service
           560ms dev-nvme0n1p5.device
           368ms NetworkManager-wait-online.service
           335ms systemd-resolved.service
           193ms [email protected]
           126ms lightdm.service
           124ms plymouth-quit-wait.service
           102ms systemd-udev-trigger.service
            98ms systemd-timesyncd.service
            95ms networking.service
            86ms keyboard-setup.service
            86ms ModemManager.service
            83ms smbd.service
            80ms snapd.service
            77ms upower.service
            74ms tlp.service
            68ms accounts-daemon.service
            68ms apport.service
            66ms NetworkManager.service
            57ms speech-dispatcher.service
            55ms irqbalance.service
            53ms gpu-manager.service
            53ms grub-common.service
            53ms systemd-tmpfiles-clean.service
            50ms systemd-logind.service
            48ms systemd-journald.service
            47ms thermald.service
            46ms bluetooth.service
            41ms avahi-daemon.service
            33ms alsa-restore.service
            32ms systemd-udevd.service
            31ms udisks2.service
            26ms snap-repair.service
            26ms pppd-dns.service
            25ms colord.service
            25ms systemd-fsck@dev-disk-by\x2duuid-FA26\x2d239C.service
            24ms packagekit.service
            23ms systemd-modules-load.service
            23ms plymouth-start.service
            20ms [email protected]
            20ms systemd-tmpfiles-setup-dev.service
            18ms geoclue.service
            17ms polkit.service
            14ms ureadahead-stop.service
            14ms rsyslog.service
            12ms setvtrgb.service
            10ms resolvconf.service
          5.022s nmbd.service
          1.904s fwupd.service
          1.454s apparmor.service
          1.414s plymouth-read-write.service
           560ms dev-nvme0n1p5.device
           368ms NetworkManager-wait-online.service
           335ms systemd-resolved.service
           193ms [email protected]
           126ms lightdm.service
           124ms plymouth-quit-wait.service
           102ms systemd-udev-trigger.service
            98ms systemd-timesyncd.service
            95ms networking.service
            86ms keyboard-setup.service
            86ms ModemManager.service
            83ms smbd.service
            80ms snapd.service
            77ms upower.service
            74ms tlp.service
            68ms accounts-daemon.service
            68ms apport.service
            66ms NetworkManager.service
            57ms speech-dispatcher.service
            55ms irqbalance.service
            53ms gpu-manager.service
            53ms grub-common.service
            53ms systemd-tmpfiles-clean.service
            50ms systemd-logind.service
            48ms systemd-journald.service
            47ms thermald.service
            46ms bluetooth.service
            41ms avahi-daemon.service
            33ms alsa-restore.service
            32ms systemd-udevd.service
            31ms udisks2.service
            26ms snap-repair.service
            26ms pppd-dns.service
            25ms colord.service
            25ms systemd-fsck@dev-disk-by\x2duuid-FA26\x2d239C.service
            24ms packagekit.service
            23ms systemd-modules-load.service
            23ms plymouth-start.service
            20ms [email protected]
            20ms systemd-tmpfiles-setup-dev.service
            18ms geoclue.service
            17ms polkit.service
            14ms ureadahead-stop.service
            14ms rsyslog.service
            12ms setvtrgb.service
            10ms resolvconf.service
            10ms wpa_supplicant.service
             9ms sys-kernel-debug.mount
             8ms systemd-remount-fs.service
             8ms dev-mqueue.mount
             7ms dev-hugepages.mount
             7ms snapd.autoimport.service
             6ms systemd-tmpfiles-setup.service
             5ms systemd-journal-flush.service
             5ms ufw.service
             5ms boot-efi.mount
             4ms systemd-user-sessions.service
             4ms systemd-sysctl.service
             4ms systemd-update-utmp-runlevel.service
             4ms kmod-static-nodes.service
             3ms systemd-update-utmp.service
             3ms rtkit-daemon.service
             3ms systemd-random-seed.service
             2ms console-setup.service
             2ms systemd-backlight@backlight:intel_backlight.service
             2ms sys-fs-fuse-connections.mount
             1ms swapfile.swap
           927us postfix.service
           385us snapd.socket
lines 51-73/73 (END)

O que posso tentar acelerar? Eu sou um novato, então ELI5 por favor.

    
por Jake 15.09.2017 / 12:25

2 respostas

0

O problema pode ser que o Ubuntu esteja esperando que a partição swap apareça. Dê uma olhada nisso:

Ubuntu Desktop 17.04 64-bit com casa criptografada, inicialização lenta

Para editar os arquivos, use

sudo gedit /etc/crypttab

e

sudo gedit /etc/fstab

O uso do sudo fornece os privilégios elevados necessários para editar esses arquivos.

Espero que ajude.

    
por scriptdwarf 21.09.2017 / 02:43
0

Aqui estão os números da minha máquina e ela inicializa como um foguete com 17.04 Ubuntu Mate, SSD e I7 kaby lake. Você pode compará-los com os seus para grandes diferenças.

A primeira coisa que gostaria de fazer é ter certeza e exibir o processo de inicialização seguindo estas instruções:

% bl0ck_qu0te%

Veja onde estão os atrasos ao inicializar.

A minha leva 13 segundos para chegar a "inicialização no modo inseguro" e mais 14 segundos para pedir minha senha.

sudo systemd-analyze blame
      8.840s NetworkManager-wait-online.service
      4.030s fwupd.service
       550ms systemd-resolved.service
       512ms dev-sda3.device
       372ms click-system-hooks.service
       340ms winbind.service
       338ms vboxdrv.service
       279ms home-john-Libraries.mount
       239ms gpu-manager.service
       237ms systemd-timesyncd.service
       231ms swapfile.swap
       225ms [email protected]
       207ms tlp.service
       192ms snapd.service
       188ms accounts-daemon.service
       157ms ModemManager.service
       117ms irqbalance.service
       114ms apport.service
       111ms thermald.service
        95ms systemd-fsck@dev-disk-by\x2duuid-5649\x2dD6F4.service
        89ms grub-common.service
        88ms pppd-dns.service
        87ms keyboard-setup.service
        84ms alsa-restore.service
        84ms lm-sensors.service
        77ms NetworkManager.service
        72ms networking.service
        68ms extra.mount
        66ms upower.service
        57ms teamviewerd.service
        56ms apparmor.service
        56ms avahi-daemon.service
        49ms swapspace.service
        47ms repowerd.service
        41ms systemd-udev-trigger.service
        41ms systemd-udevd.service
        41ms speech-dispatcher.service
        40ms systemd-logind.service
        36ms udisks2.service
        35ms bluetooth.service
        33ms colord.service
        33ms systemd-tmpfiles-setup-dev.service
        32ms smbd.service
        29ms lightdm.service
        26ms polkit.service
        25ms systemd-sysctl.service
        22ms dev-mqueue.mount
        21ms sys-kernel-debug.mount
        21ms systemd-journald.service
        21ms systemd-modules-load.service
        19ms rsyslog.service
        19ms ufw.service
        18ms plymouth-read-write.service
        17ms kmod-static-nodes.service
        16ms binfmt-support.service
        15ms nmbd.service
        14ms systemd-update-utmp.service
        13ms ureadahead-stop.service
         9ms systemd-journal-flush.service
         7ms boot-efi.mount
         7ms systemd-tmpfiles-setup.service
         6ms dev-hugepages.mount
         5ms resolvconf.service
         5ms dns-clean.service
         4ms systemd-user-sessions.service
         4ms systemd-update-utmp-runlevel.service
         4ms snapd.autoimport.service
         3ms snapd.socket
         3ms proc-sys-fs-binfmt_misc.mount
         3ms openvpn.service
         3ms vboxweb-service.service
         3ms vboxautostart-service.service
         3ms vboxballoonctrl-service.service
         3ms setvtrgb.service
         2ms sys-fs-fuse-connections.mount
         2ms systemd-remount-fs.service
         2ms systemd-random-seed.service
         2ms rtkit-daemon.service
         1ms systemd-backlight@backlight:acpi_video0.service
         1ms console-setup.service
         1ms rc-local.service
       872us plymouth-quit-wait.service
    
por jpezz 21.09.2017 / 03:05