Demora de boot

removido
(usa Nenhuma)

Enviado em 31/03/2020 - 15:10h

O boot do manjaro demora mais de um minuto enquanto que com o windows iniciava em 20 segundos, o que pode ser? (instalação limpa no modo UEFI, secure boot desativado, fast boot desativado)?.
rodando systemd-analyze blame ele dá isso:

13.058s linux-module-cleanup.service >
11.969s lvm2-monitor.service >
10.310s dev-sda2.device >
7.386s systemd-modules-load.service >
7.371s polkit.service >
6.788s systemd-journal-flush.service >
6.159s apparmor.service >
5.626s NetworkManager.service >
4.826s org.cups.cupsd.service >
4.202s systemd-sysusers.service >
4.007s systemd-logind.service >
3.467s bluetooth.service >
3.172s ModemManager.service >
2.994s ldconfig.service >
2.849s systemd-tmpfiles-setup-dev.service >
1.942s udisks2.service >
1.426s snapd.apparmor.service >
1.421s tlp.service >
1.406s systemd-fsck@dev-disk-by\x2duuid-6B77\x2d31D3.service >
1.314s systemd-udevd.service >
1.185s upower.service >
1.030s gdm.service >
953ms systemd-random-seed.service >
lines 1-23...skipping...
13.058s linux-module-cleanup.service
11.969s lvm2-monitor.service
10.310s dev-sda2.device
7.386s systemd-modules-load.service
7.371s polkit.service
6.788s systemd-journal-flush.service
6.159s apparmor.service
5.626s NetworkManager.service
4.826s org.cups.cupsd.service
4.202s systemd-sysusers.service
4.007s systemd-logind.service
3.467s bluetooth.service
3.172s ModemManager.service
2.994s ldconfig.service
2.849s systemd-tmpfiles-setup-dev.service
1.942s udisks2.service
1.426s snapd.apparmor.service
1.421s tlp.service
1.406s systemd-fsck@dev-disk-by\x2duuid-6B77\x2d31D3.service
1.314s systemd-udevd.service
1.185s upower.service
1.030s gdm.service
953ms systemd-random-seed.service
939ms colord.service
912ms systemd-journal-catalog-update.service
781ms systemd-tmpfiles-setup.service
741ms systemd-backlight@backlight:intel_backlight.service
736ms accounts-daemon.service
685ms systemd-udev-trigger.service
668ms dev-disk-by\x2duuid-dbe11ecd\x2d4d20\x2d4999\x2dabe8\x2de6bfcfa55ef9.swap
660ms systemd-journald.service
620ms snapd.service
540ms systemd-timesyncd.service
404ms wpa_supplicant.service
278ms ufw.service
262ms user@1000.service
238ms boot-efi.mount
231ms systemd-update-utmp.service
224ms dev-hugepages.mount
223ms systemd-sysctl.service
223ms dev-mqueue.mount
222ms sys-kernel-debug.mount
221ms kmod-static-nodes.service
194ms systemd-remount-fs.service
137ms systemd-update-done.service
119ms systemd-tmpfiles-clean.service
73ms systemd-user-sessions.service
47ms var-lib-snapd-snap-teams\x2dfor\x2dlinux-79.mount
46ms rtkit-daemon.service
36ms var-lib-snapd-snap-snapd-6953.mount
35ms user-runtime-dir@1000.service
30ms var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-116.mount
27ms dev-loop0.device
26ms var-lib-snapd-snap-skype-118.mount
25ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1474.mount
22ms var-lib-snapd-snap-core-8935.mount
19ms var-lib-snapd-snap-core18-1705.mount
lines 1-57
13.058s linux-module-cleanup.service
11.969s lvm2-monitor.service
10.310s dev-sda2.device
7.386s systemd-modules-load.service
7.371s polkit.service
6.788s systemd-journal-flush.service
6.159s apparmor.service
5.626s NetworkManager.service
4.826s org.cups.cupsd.service
4.202s systemd-sysusers.service
4.007s systemd-logind.service
3.467s bluetooth.service
3.172s ModemManager.service
2.994s ldconfig.service
2.849s systemd-tmpfiles-setup-dev.service
13.058s linux-module-cleanup.service
11.969s lvm2-monitor.service
10.310s dev-sda2.device
7.386s systemd-modules-load.service
7.371s polkit.service
6.788s systemd-journal-flush.service
6.159s apparmor.service
5.626s NetworkManager.service
4.826s org.cups.cupsd.service
4.202s systemd-sysusers.service
4.007s systemd-logind.service
3.467s bluetooth.service
3.172s ModemManager.service
2.994s ldconfig.service
2.849s systemd-tmpfiles-setup-dev.service
2.849s systemd-tmpfiles-setup-dev.service
4.202s systemd-sysusers.service
4.007s systemd-logind.service
3.467s bluetooth.service
3.172s ModemManager.service
2.994s ldconfig.service
2.849s systemd-tmpfiles-setup-dev.service
13.058s linux-module-cleanup.service
11.969s lvm2-monitor.service
10.310s dev-sda2.device
7.386s systemd-modules-load.service
7.371s polkit.service
6.788s systemd-journal-flush.service
6.159s apparmor.service
5.626s NetworkManager.service
4.826s org.cups.cupsd.service
4.202s systemd-sysusers.service
4.007s systemd-logind.service
3.467s bluetooth.service
3.172s ModemManager.service
2.994s ldconfig.service
2.849s systemd-tmpfiles-setup-dev.service
1.942s udisks2.service
1.426s snapd.apparmor.service
1.421s tlp.service
1.406s systemd-fsck@dev-disk-by\x2duuid-6B77\x2d31D3.service
1.314s systemd-udevd.service
1.185s upower.service
1.030s gdm.service
953ms systemd-random-seed.service
939ms colord.service
912ms systemd-journal-catalog-update.service
781ms systemd-tmpfiles-setup.service
741ms systemd-backlight@backlight:intel_backlight.service
736ms accounts-daemon.service
685ms systemd-udev-trigger.service
668ms dev-disk-by\x2duuid-dbe11ecd\x2d4d20\x2d4999\x2dabe8\x2de6bfcfa55ef9.swap
660ms systemd-journald.service
620ms snapd.service
540ms systemd-timesyncd.service
404ms wpa_supplicant.service
278ms ufw.service
262ms user@1000.service
238ms boot-efi.mount
231ms systemd-update-utmp.service
224ms dev-hugepages.mount
223ms systemd-sysctl.service
223ms dev-mqueue.mount
222ms sys-kernel-debug.mount
221ms kmod-static-nodes.service
194ms systemd-remount-fs.service
137ms systemd-update-done.service
119ms systemd-tmpfiles-clean.service
73ms systemd-user-sessions.service
47ms var-lib-snapd-snap-teams\x2dfor\x2dlinux-79.mount
46ms rtkit-daemon.service
36ms var-lib-snapd-snap-snapd-6953.mount
35ms user-runtime-dir@1000.service
30ms var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-116.mount
27ms dev-loop0.device
26ms var-lib-snapd-snap-skype-118.mount
25ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1474.mount
22ms var-lib-snapd-snap-core-8935.mount
19ms var-lib-snapd-snap-core18-1705.mount
19ms tmp.mount
19ms dev-loop4.device
19ms pamac-daemon.service
16ms dev-loop5.device
15ms systemd-rfkill.service
14ms modprobe@drm.service
14ms dev-loop3.device
12ms dev-loop6.device
11ms dev-loop1.device
9ms sys-fs-fuse-connections.mount
7ms dev-loop2.device
2ms snapd.socket
2ms sys-kernel-config.mount

leoCCB
(usa Slackware)

Enviado em 01/04/2020 - 20:55h

vc consegue acompanhar os processos em real time na hora do boot? Aqui eu clico na seta pra cima ou então shift+seta pra cima. Tenta ver aí, eu não sei como faz na sua distro. Mas o meu tava demorando pra caramba, e acompanhando os processos em real time vi que era a swap que estava com o endereço errado.

leoCCB
(usa Slackware)

Enviado em 01/04/2020 - 21:00h

pra saber se é a swap, vai até a pasta /etc

$cd /etc
e verifica o arquivo fstab, que é onde estão os endereços das partições

$cat fstab
Aí vc roda

$sudo blkid

e compara a saída deste ultimo com o primeiro. Se os endereços de alguma partição estiver errada, vc edita o fstab com o endereço correto.

Pebis
(usa Debian)

Enviado em 01/04/2020 - 21:03h

Acho que a questão principal é que o Windows não desliga, ele hiberna, por isso fica mais rápida a inicialização.

RogerDez
(usa Outra)

Enviado em 01/04/2020 - 21:46h

muitos serviços aí estão rodando em duplicata, triplicata..

o que é isso? o que vc fez?

mr_peartnoy
(usa Arch Linux)

Enviado em 02/04/2020 - 14:51h

Ja tentou criar o pendrive bootavel no Etcher?