[DEBIAN]Iniciar demorando

1. [DEBIAN]Iniciar demorando

Jonathan Barros Franco
jona1

(usa Debian)

Enviado em 06/09/2018 - 00:47h

Pessoal, é o seguinte, a um tempo atrás eu usava o Debian ( e ainda uso), ele demorava em torno de 30 segs pra ligar, até que resolvi instalar o KALI LINUX pra acompanhar um curso Hacking, Pentest e etc, e de 30 segs passou para quase 2min de demora pra iniciar.

No comeco ao escolhar a particao debian, fica um Travessao no canto da tela piscando, geralmente isso nem aparecia, alem de estar gastando mais bateria que o normal

HELP?


  


2. Re: [DEBIAN]Iniciar demorando

Clodoaldo Santos
clodoaldops

(usa Linux Mint)

Enviado em 06/09/2018 - 07:31h

-vc tem debian e kali em dual-boot ?



3. Re: [DEBIAN]Iniciar demorando

Lenon Ricardo
lenonr

(usa Debian)

Enviado em 07/09/2018 - 01:40h

Swap... já verificou ela?


4. [DEBIAN]Iniciar demorando

Jonathan Barros Franco
jona1

(usa Debian)

Enviado em 08/09/2018 - 10:18h

Já verifiquei a swap, sim, ela estava desativada, ja ativei normalmente pelo bash com a UID , mas continua demorando no carregamento.

SIm, dual boot kali e debian


5. Re: [DEBIAN]Iniciar demorando

Clodoaldo Santos
clodoaldops

(usa Linux Mint)

Enviado em 08/09/2018 - 10:25h

Debian ou Kali está gerenciando o GRUB?
Aqui Boot em menos de 30 segundos só no SSD. Pois no HD demorar o dobro do tempo.



6. Re: [DEBIAN]Iniciar demorando

Ryuk Shinigami
Ryuk

(usa Nenhuma)

Enviado em 08/09/2018 - 11:10h

Mostre a saída dos comandos abaixo:

systemd-analyze time 

systemd-analyze blame 

journalctl -x | egrep -i 'fail|erro' 



7. Re: [DEBIAN]Iniciar demorando

Jonathan Barros Franco
jona1

(usa Debian)

Enviado em 08/09/2018 - 13:28h

Ryuk escreveu:

Mostre a saída dos comandos abaixo:

systemd-analyze time 

systemd-analyze blame 

journalctl -x | egrep -i 'fail|erro' 


systemd-analyze time
[/b]Startup finished in 36.526s (kernel) + 50.462s (userspace) = 1min 26.988s



systemd-analyze blame
23.895s postgresql@10-main.service
16.455s openvas-manager.service
14.640s NetworkManager-wait-online.service
13.706s winbind.service
13.684s dev-sda3.device
12.869s ModemManager.service
9.003s dev-loop3.device
8.926s dev-loop0.device
8.883s dev-loop1.device
8.852s dev-loop2.device
8.624s speech-dispatcher.service
8.042s lm-sensors.service
8.032s xdm.service
8.008s thermald.service
8.003s systemd-logind.service
7.857s avahi-daemon.service
7.645s sysstat.service
7.643s pppd-dns.service
7.642s alsa-restore.service
7.625s rsyslog.service
7.620s bluetooth.service
7.618s rtkit-daemon.service
5.519s redis-server.service
5.509s redis-server@openvas.service
4.092s NetworkManager.service
3.086s accounts-daemon.service
2.926s networking.service
2.777s systemd-udevd.service
2.086s polkit.service
1.947s binfmt-support.service
1.652s lightdm.service
1.451s systemd-modules-load.service
1.425s systemd-tmpfiles-setup-dev.service
1.370s keyboard-setup.service
1.320s snap-core-5328.mount
1.306s snap-pycharm\x2dcommunity-83.mount
1.278s snap-pycharm\x2dcommunity-79.mount
1.238s exim4.service
1.195s snap-anbox\x2dinstaller-24.mount
1.015s openvas-scanner.service
978ms wpa_supplicant.service
962ms tlp.service
954ms systemd-tmpfiles-setup.service
889ms systemd-journald.service
866ms resolvconf.service
782ms proc-sys-fs-binfmt_misc.mount
747ms systemd-timesyncd.service
608ms systemd-udev-trigger.service
457ms colord.service
443ms systemd-update-utmp.service
423ms kmod-static-nodes.service
405ms systemd-random-seed.service
366ms snapd.autoimport.service
347ms systemd-user-sessions.service
347ms udisks2.service
317ms sys-kernel-debug.mount
316ms dev-hugepages.mount
284ms dev-mqueue.mount
277ms systemd-journal-flush.service
229ms systemd-remount-fs.service
223ms systemd-backlight@backlight:intel_backlight.service
211ms upower.service
197ms console-setup.service
163ms hddtemp.service
163ms systemd-sysctl.service
135ms minissdpd.service
131ms postgresql.service
63ms user@1000.service
60ms dev-disk-by\x2duuid-cdf5a0b2\x2d6d9a\x2d4fd2\x2db0fb\x2d10af8f1
36ms snapd.refresh.service
8ms systemd-update-utmp-runlevel.service
5ms sys-fs-fuse-connections.mount
654us snapd.socket

journalctl -x | egrep -i 'fail|erro'

set 08 11:23:52 Hades kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
set 08 11:23:52 Hades kernel: EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
set 08 11:23:59 Hades systemd-udevd[446]: Process '/usr/sbin/tlp auto' failed with exit code 4.
set 08 11:24:02 Hades systemd-udevd[451]: Process '/sbin/crda' failed with exit code 249.
set 08 11:24:07 Hades kernel: usb 2-1.4: device descriptor read/64, error -110
set 08 11:24:14 Hades thermald[869]: sysfs write failed /sys/devices/virtual/powercap/intel-rapl/intel-rapl:0/enabled
set 08 11:24:17 Hades kernel: usb 2-1.4: device not accepting address 4, error -32
set 08 11:24:18 Hades bluetoothd[891]: Failed to obtain handles for "Service Changed" characteristic
set 08 11:24:18 Hades bluetoothd[891]: Sap driver initialization failed.
set 08 11:24:24 Hades snapd[923]: stateengine.go:102: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapcraft.io on [::1]:53: read udp [::1]:53644->[::1]:53: read: connection refused
set 08 11:24:37 Hades postgresql@10-main[921]: The PostgreSQL server failed to start. Please check the log output:
set 08 11:24:39 Hades kernel: acpi_call: Cannot get handle: Error: AE_NOT_FOUND
set 08 11:24:39 Hades kernel: acpi_call: Cannot get handle: Error: AE_NOT_FOUND
set 08 13:12:03 Hades bluetoothd[891]: Failed to obtain handles for "Service Changed" characteristic
set 08 13:12:03 Hades bluetoothd[891]: Sap driver initialization failed.
set 08 13:12:30 Hades x-session-manager[2110]: WARNING: t+11,61506s: Failed to start app: Unable to start application: Failed to execute child process “/home/hades/Área” (No such file or directory)
set 08 13:17:09 Hades gvfsd-network[2558]: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Não há suporte à operação pelo backend
set 08 13:17:09 Hades gvfsd-network[2556]: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Não há suporte à operação pelo backend
set 08 13:18:27 Hades kernel: EXT4-fs error (device sda6): htree_dirblock_to_tree:962: inode #1706109: comm pool: Directory block failed checksum
set 08 13:18:46 Hades kernel: EXT4-fs error (device sda6): htree_dirblock_to_tree:962: inode #3937063: comm pool: Directory block failed checksum
set 08 13:19:00 Hades kernel: EXT4-fs error (device sda6): htree_dirblock_to_tree:962: inode #3414084: comm pool: Directory block failed checksum
set 08 13:19:05 Hades kernel: EXT4-fs error (device sda6): htree_dirblock_to_tree:962: inode #3676968: comm pool: Directory block failed checksum



8. Re: [DEBIAN]Iniciar demorando

Ryuk Shinigami
Ryuk

(usa Nenhuma)

Enviado em 08/09/2018 - 21:03h

Cara, tem vários serviços aí falhando na inicialização.
Veja o que realmente não precisa e desabilite-os.






Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts