Arranque de sistema muy lento

Hola a todos
Recientemente instalé Manjaro con entorno de escritorio GNOME en una DELL 6420 i5 con 8 Gb de RAM.

El arranque del sistema es muy lento, ya he investigado algunos problemas similares en el foro y en Google pero no he logrado agilizar el arranque.

Les agradezco su apoyo para revisar la configuración actual y los servicios habilitados para sugerir como mejorar el arranque. No sé si esta configuración afecta que la apertura de las aplicaciones también sea muy lenta.

A continuación lo que tengo:


 ██████████████████  ████████     jorge@jorge-dell
 ██████████████████  ████████     OS: Manjaro 18.1.0 Juhraya
 ██████████████████  ████████     Kernel: x86_64 Linux 5.2.11-1-MANJARO
 ██████████████████  ████████     Uptime: 6h 58m
 ████████            ████████     Packages: 1169
 ████████  ████████  ████████     Shell: bash
 ████████  ████████  ████████     Resolution: 1600x900
 ████████  ████████  ████████     DE: GNOME 3.32.2
 ████████  ████████  ████████     WM: Mutter
 ████████  ████████  ████████     WM Theme: Matcha-light-sea
 ████████  ████████  ████████     GTK Theme: Matcha-light-sea [GTK2/3]
 ████████  ████████  ████████     Icon Theme: Faenza-Green
 ████████  ████████  ████████     Font: Noto Sans 10
 ████████  ████████  ████████     Disk: 88G / 183G (51%)
                                  CPU: Intel Core i5-2520M @ 4x 3.2GHz [63.0°C]
                                  GPU: Mesa DRI Intel(R) Sandybridge Mobile 
                                  RAM: 3646MiB / 7854MiB

[jorge@jorge-dell ~]$ systemd-analyze
Startup finished in 6.385s (kernel) + 1min 1.870s (userspace) = 1min 8.255s 
graphical.target reached after 36.910s in userspace


[jorge@jorge-dell ~]$ systemd-analyze blame
         26.653s accounts-daemon.service
         26.165s org.cups.cupsd.service
         24.860s polkit.service
         16.591s systemd-journal-flush.service
         12.572s lvm2-monitor.service
         11.140s dev-sda3.device
         10.551s colord.service
          9.144s upower.service
          6.391s cpupower.service
          6.384s systemd-logind.service
          5.941s NetworkManager.service
          3.360s tlp.service
          3.158s ufw.service
          3.157s systemd-udevd.service
          2.035s systemd-timesyncd.service
          1.973s systemd-tmpfiles-setup-dev.service
          1.938s systemd-rfkill.service
          1.914s user@120.service
          1.880s wpa_supplicant.service
          1.541s udisks2.service
          1.403s systemd-backlight@leds:dell::kbd_backlight.service
          1.038s systemd-modules-load.service
           966ms systemd-journald.service
           928ms gdm.service
           874ms systemd-tmpfiles-setup.service
           825ms systemd-random-seed.service
           823ms haveged.service
           693ms systemd-sysctl.service
           628ms tmp.mount
           625ms dev-hugepages.mount
           621ms dev-mqueue.mount
           621ms linux-module-cleanup.service
           620ms kmod-static-nodes.service
           593ms systemd-udev-trigger.service
           510ms systemd-backlight@backlight:acpi_video0.service
           490ms systemd-backlight@backlight:intel_backlight.service
           485ms systemd-update-utmp.service
           395ms systemd-remount-fs.service
           353ms systemd-tmpfiles-clean.service
           148ms sys-kernel-debug.mount
            61ms user@1000.service
            41ms user-runtime-dir@120.service
            30ms systemd-user-sessions.service
            10ms user-runtime-dir@1000.service
             5ms sys-kernel-config.mount
             3ms rtkit-daemon.service
             3ms sys-fs-fuse-connections.mount
lines 1-47


[jorge@jorge-dell ~]$ systemd-analyze blame
         26.653s accounts-daemon.service
         26.165s org.cups.cupsd.service
         24.860s polkit.service
         16.591s systemd-journal-flush.service
         12.572s lvm2-monitor.service
         11.140s dev-sda3.device
         10.551s colord.service
          9.144s upower.service
          6.391s cpupower.service
          6.384s systemd-logind.service
          5.941s NetworkManager.service
          3.360s tlp.service
          3.158s ufw.service
          3.157s systemd-udevd.service
          2.035s systemd-timesyncd.service
          1.973s systemd-tmpfiles-setup-dev.service
          1.938s systemd-rfkill.service
          1.914s user@120.service
          1.880s wpa_supplicant.service
          1.541s udisks2.service
          1.403s systemd-backlight@leds:dell::kbd_backlight.service
          1.038s systemd-modules-load.service
           966ms systemd-journald.service
           928ms gdm.service
           874ms systemd-tmpfiles-setup.service
           825ms systemd-random-seed.service
           823ms haveged.service
           693ms systemd-sysctl.service
           628ms tmp.mount
           625ms dev-hugepages.mount
           621ms dev-mqueue.mount
           621ms linux-module-cleanup.service
           620ms kmod-static-nodes.service
           593ms systemd-udev-trigger.service
           510ms systemd-backlight@backlight:acpi_video0.service
           490ms systemd-backlight@backlight:intel_backlight.service
           485ms systemd-update-utmp.service
           395ms systemd-remount-fs.service
           353ms systemd-tmpfiles-clean.service
           148ms sys-kernel-debug.mount
            61ms user@1000.service
            41ms user-runtime-dir@120.service
            30ms systemd-user-sessions.service
            10ms user-runtime-dir@1000.service
             5ms sys-kernel-config.mount
             3ms rtkit-daemon.service
             3ms sys-fs-fuse-connections.mount

[3]+  Detenido                systemd-analyze blame
[jorge@jorge-dell ~]$ mhwd-kernel -li
Currently running: 5.2.11-1-MANJARO (linux52)
The following kernels are installed in your system:
   * linux419
   * linux52

[jorge@jorge-dell ~]$ systemctl list-unit-files --type=service | grep enabled
autovt@.service                             enabled        
bluetooth.service                           enabled        
cpupower.service                            enabled        
cronie.service                              enabled        
dbus-org.bluez.service                      enabled        
dbus-org.freedesktop.NetworkManager.service enabled        
dbus-org.freedesktop.nm-dispatcher.service  enabled        
dbus-org.freedesktop.timesync1.service      enabled        
display-manager.service                     enabled        
gdm.service                                 enabled        
getty@.service                              enabled        
haveged.service                             enabled        
irqbalance.service                          enabled        
linux-module-cleanup.service                enabled        
NetworkManager-dispatcher.service           enabled        
NetworkManager-wait-online.service          enabled        
NetworkManager.service                      enabled        
org.cups.cupsd.service                      enabled        
preload.service                             enabled        
systemd-fsck-root.service                   enabled-runtime
systemd-remount-fs.service                  enabled-runtime
systemd-timesyncd.service                   enabled        
tlp-sleep.service                           enabled        
tlp.service                                 enabled        
ufw.service                                 enabled        
upower.service                              enabled        

  GNU nano 4.4                                    /etc/default/grub                                                 
GRUB_DEFAULT=saved
GRUB_TIMEOUT=1
GRUB_TIMEOUT_STYLE=menu
GRUB_DISTRIBUTOR='Manjaro'
GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=3ee17d2f-a234-4ea8-b41b-62e7d12bae02 libahci.ignore_sss=1 "
GRUB_CMDLINE_LINUX=""

# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true

# Preload both GPT and MBR modules so that they are not missed
#GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"

Desde ya muchas gracias.
Saludos

esto es muy alto, ¿has comprobado la información de SMART en tu disco?

¿puedes volver

sudo journalctl -b0 -p4 

Eso es mucho tiempo también. Asumo que no tienes disco sólido. Lo que hace ese servicio mover cualquier log que haya en /run/log/journal hacia /var/log/journal para ello debe montar los respectivos systemas de archivos y escribir.
Quizá tienes muchos archivos de logs y eso hace lento este proceso.
Tienes 2 opciones:
a) Deshabilitar el servicio. Puede que no tengas logs para cuando necesites debuggear un problema. Pero ante tal caso lo puedes volver a habilitar.
b) Limpiar el registro de logs. Para ello te recomiento investigar el comando journalctl --vacuum y también la configuración de journal en /etc/systemd/journald.conf

Puedes deshabilitar este servicio si no tienes impresoras. Pero desconozco por qué tarda tanto en arrancar.

Este es el resultado:


[jorge@jorge-dell ~]$ sudo journalctl -b0 -p4
[sudo] password for jorge: 
-- Logs begin at Wed 2019-09-04 12:40:52 CST, end at Thu 2019-09-19 19:24:54 CST. --
sep 19 05:30:21 jorge-dell kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/d>
sep 19 05:30:21 jorge-dell kernel:   #3
sep 19 05:30:21 jorge-dell kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
sep 19 05:30:21 jorge-dell kernel: i8042: Warning: Keylock active
sep 19 05:30:21 jorge-dell kernel: usb 2-1.8: config 0 descriptor??
sep 19 05:30:44 jorge-dell kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts wit>
sep 19 05:30:44 jorge-dell kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts wit>
sep 19 05:30:44 jorge-dell kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts wit>
sep 19 05:30:44 jorge-dell kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts wit>
sep 19 05:30:44 jorge-dell kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
sep 19 05:30:44 jorge-dell kernel: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
sep 19 05:30:44 jorge-dell kernel: dell-smbios A80593CE-A997-11DA-B012-B622A1EF5492: WMI SMBIOS userspace interface>
sep 19 05:30:45 jorge-dell kernel: iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
sep 19 05:30:45 jorge-dell kernel: kauditd_printk_skb: 19 callbacks suppressed
sep 19 05:30:31 jorge-dell systemd-udevd[385]: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.
sep 19 05:30:31 jorge-dell systemd-vconsole-setup[410]: KD_FONT_OP_GET failed while trying to get the font metadata>
sep 19 05:30:31 jorge-dell systemd-vconsole-setup[410]: Fonts will not be copied to remaining consoles
sep 19 05:30:33 jorge-dell systemd-udevd[372]: Config file /usr/lib/systemd/network/99-default.link applies to devi>
sep 19 05:30:34 jorge-dell systemd-udevd[404]: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
sep 19 05:30:48 jorge-dell kernel: kauditd_printk_skb: 4 callbacks suppressed
sep 19 05:30:53 jorge-dell NetworkManager[645]: <warn>  [1568892653.1678] device (eno1): connectivity: "/proc/sys/n>
sep 19 05:30:53 jorge-dell NetworkManager[645]: <warn>  [1568892653.9451] device (wlp2s0): connectivity: "/proc/sys>
sep 19 05:31:14 jorge-dell colord[786]: failed to get session [pid 666]: No hay datos disponibles
sep 19 05:31:16 jorge-dell systemd-udevd[2638]: Process '/usr/bin/crda' failed with exit code 255.
sep 19 05:31:20 jorge-dell /usr/lib/gdm-x-session[2677]: (--) Log file renamed from "/var/lib/gdm/.local/share/xorg>
sep 19 05:31:20 jorge-dell /usr/lib/gdm-x-session[2677]: (WW) Failed to open protocol names file lib/xorg/protocol.>
sep 19 05:31:20 jorge-dell /usr/lib/gdm-x-session[2677]: X.Org X Server 1.20.5
sep 19 05:31:20 jorge-dell /usr/lib/gdm-x-session[2677]: X Protocol Version 11, Revision 0
lines 1-29

En un blog recomiendan cambiar el tiempo de almacenamiento (se cambió de persistent a auto y el tamaño de los archivos.

$ sudo nano /etc/systemd/journald.conf
GNU nano 4.4              /etc/systemd/journald.conf                          
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See journald.conf(5) for details.

[Journal]
**Storage=auto**
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=10000
#SystemMaxUse=
#SystemKeepFree=
**SystemMaxFileSize=1G**
**SystemMaxFiles=5**
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=

Prácticamente no tuvo ningún efecto

[jorge@jorge-dell ~]$ systemd-analyze
Startup finished in 6.529s (kernel) + 1min 5.660s (userspace) = 1min 12.189s 
graphical.target reached after 33.806s in userspace
[jorge@jorge-dell ~]$ systemd-analyze blame
         29.459s polkit.service
         15.216s systemd-journal-flush.service
         12.101s lvm2-monitor.service
         10.896s dev-sda3.device
          6.794s upower.service
          5.151s systemd-logind.service
          5.104s cpupower.service
          4.666s NetworkManager.service
          3.953s accounts-daemon.service
          3.557s systemd-udevd.service
          2.848s ufw.service
          2.805s tlp.service
          2.368s systemd-timesyncd.service
          2.350s gdm.service
          2.147s udisks2.service
          1.954s systemd-tmpfiles-setup-dev.service
          1.947s systemd-modules-load.service
          1.859s systemd-rfkill.service
          1.345s wpa_supplicant.service
          1.152s systemd-backlight@leds:dell::kbd_backlight.service
          1.149s systemd-random-seed.service
           961ms systemd-tmpfiles-setup.service
           740ms haveged.service

No se si será consecuencia del mismo problema, después de ingresar a mi usuario se tarda hasta 30 seg en abrir una aplicación.

¿puedes volver

inxi -Fxxxza 

es hora de cambiar los discos duros, ¿verdad?
un disco SSD hará el truco

Puede ser interesante echar un vistazo al tema de la entropía.

Haz una búsqueda por "haveged" en el foro y/o la arch wiki.

Amigo recomiendo que busques correr alguno programa para medir la integridad del disco, veo seguido estos síntomas son normalmente producto del disco que funciona mal, cumplió su siclo!

Sí, quisiera cambiar el disco SSD y la máquina completa... :slight_smile:
Por ahora es lo que tengo, si me ayudan a sacarle el jugo hasta lo que dé se los agradezco.


[jorge@jorge-dell ~]$ inxi -Fxxxza
System:    Host: jorge-dell Kernel: 5.2.11-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.1.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.2-x86_64 root=UUID=3ee17d2f-a234-4ea8-b41b-62e7d12bae02 rw quiet 
           resume=UUID=3ee17d2f-a234-4ea8-b41b-62e7d12bae02 
           Desktop: Gnome 3.32.2 wm: gnome-shell dm: GDM 3.32.0 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Dell product: Latitude E6420 v: 01 serial: <filter> Chassis: type: 9 serial: <filter> 
           Mobo: Dell model: 0P6K8J v: A00 serial: <filter> BIOS: Dell v: A16 date: 01/01/2013 
Battery:   ID-1: BAT0 charge: 15.6 Wh condition: 41.6/62.2 Wh (67%) volts: 12.3/11.1 model: SMP DELL MKD6223 type: Li-ion 
           serial: <filter> status: Charging 
CPU:       Topology: Dual Core model: Intel Core i5-2520M bits: 64 type: MT MCP arch: Sandy Bridge family: 6 model-id: 2A (42) 
           stepping: 7 microcode: 2F L2 cache: 3072 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19967 
           Speed: 2264 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 2691 2: 2993 3: 2740 4: 1703 
           Vulnerabilities: Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Dell driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0126 
           Display: x11 server: X.Org 1.20.5 driver: i915 compositor: gnome-shell resolution: 1600x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.1.5 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:1c20 
           Sound Server: ALSA v: k5.2.11-1-MANJARO 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e v: 3.2.6-k port: 4080 bus ID: 00:19.0 
           chip ID: 8086:1502 
           IF: eno1 state: down mac: <filter> 
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel port: 4040 bus ID: 02:00.0 
           chip ID: 8086:0082 
           IF: wlp2s0 state: up mac: <filter> 
Drives:    Local Storage: total: 232.89 GiB used: 87.21 GiB (37.4%) 
           ID-1: /dev/sda vendor: Western Digital model: WD2500BPVT-75JJ5T0 size: 232.89 GiB block size: physical: 4096 B 
           logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 1A03 scheme: MBR 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: 4060 bus ID: 00:1f.2 
           chip ID: 8086.282a rev: 04 
Partition: ID-1: / raw size: 183.00 GiB size: 179.12 GiB (97.88%) used: 87.21 GiB (48.7%) fs: ext4 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 55.0 C mobo: 32.0 C sodimm: 39.0 C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 248 Uptime: 1h 15m Memory: 7.67 GiB used: 2.46 GiB (32.1%) Init: systemd v: 242 Compilers: gcc: 9.1.0 
           Shell: bash v: 5.0.9 running in: gnome-terminal inxi: 3.0.36 

Si, gracias. Ya lo he visto e instalé el servicio haveged pero no tuvo ningún efecto positivo.

image

Gracias por la sugerencia. Haré algunas mediciones y te comento.

modificación a realizar en las biografías

¿puedes poner tu disco duro en AHCI (y no en modo Raid)?

1 Like

Estos son los resultados del test usando Discos de GNOME

Agradezco tus comentarios.

es necesario cambiar el disco opta por una SSD ( 250Go or 500Go SSD AHCI ),
porque está empezando a cometer muchos errores de lectura,
cad ya sea pb en la escritura, o problema real de lectura y riesgo de corrupción

Ya cambié el disco duro a modo AHCI

Si disminuyó un poco el tiempo de arranque.

[jorge@jorge-dell ~]$ systemd-analyze
Startup finished in 6.537s (kernel) + 53.404s (userspace) = 59.942s 
graphical.target reached after 27.699s in userspace
[jorge@jorge-dell ~]$ systemd-analyze blame
         25.808s accounts-daemon.service
         24.848s polkit.service
         13.051s lvm2-monitor.service
         12.138s dev-sda3.device
          6.465s upower.service
          6.103s systemd-udevd.service
          5.102s cpupower.service
          5.101s systemd-logind.service
          5.068s NetworkManager.service
          4.272s systemd-sysctl.service
          2.204s systemd-rfkill.service
          2.198s udisks2.service

Pero como anotabas antes, el disco duro está dañado y será mejor reemplazarlo.

Gracias a todos por su ayuda.
Saludos

Forum kindly sponsored by