Slow boot Endeavour i3 "Starting Version 249.5-3-arch"

Hey,

Super happy so far, learnt a lot from the installation guide and this forum.
One thing I can’t seem to resolve… Endeavour boots really slowly for me.
I get stuck on “Starting Version 249.5-3-arch” for 60 seconds give or take a few seconds.

It’s almost like it’s searching for something, gives up after 1 minute, and then just boots as it should.
Once I’m in it’s all great, no problems.
Anyone have any ideas on how I could troubleshoot?

  1. Remove quiet from GRUB’s boot line to see boot messages;
  2. Check the output of journalctl to see what’s happening during the boot process;
  3. Look at systemd-analyze blame and systemd-analyze critical-chain to see if there’s a specific service which seems to be taking a long time to start.
3 Likes

I think I shaved off 30s of boot time by masking man-db.

Thank you for your reply, your commands got me to the arch wiki.
After having run systemd-analyze I’ve found that I got 1 min 10 sec on Kernel for a total boot time of 1 min 30 sec.

Anyone else had this be the case?
If the solution is to install a custom kernel that plays nice then I think I’ll just live with it and hope that a future update magically solves my problem.

Perhaps if you would post the output of these commands, it might give someone on the forum some clue about what is going on with your system.

Also, did you try this

?

Hey,

By removing “quiet loglevel=3 nowatchdog” I was able to make some improvement:

systemd-analyze
Startup finished in 11.367s (firmware) + 5.544s (loader) + 38.807s (kernel) + 2.011s (userspace) = 57.731s

Nothing stood out to me with these commands, here they are:

systemd-analyze blame
1.370s tlp.service
1.228s systemd-random-seed.service
 226ms systemd-journal-flush.service
 181ms dev-sdb2.device
 109ms boot-efi.mount
  92ms lvm2-monitor.service
  88ms accounts-daemon.service
  78ms polkit.service
  73ms data.mount
  71ms user@1000.service
  63ms systemd-udevd.service
  51ms NetworkManager.service
  47ms systemd-udev-trigger.service
  38ms avahi-daemon.service
  36ms systemd-journald.service
  34ms systemd-timesyncd.service
  32ms systemd-logind.service
  31ms systemd-tmpfiles-setup.service
  30ms systemd-fsck@dev-disk-by\x2duuid-823D\x2d31AA.service
  14ms systemd-tmpfiles-setup-dev.service
  12ms modprobe@drm.service
  10ms systemd-modules-load.service
  10ms lightdm.service
  10ms systemd-binfmt.service
   9ms bluetooth.service
   7ms dev-hugepages.mount
   7ms dev-mqueue.mount
   7ms sys-kernel-debug.mount
   6ms sys-kernel-tracing.mount
   6ms kmod-static-nodes.service
   6ms user-runtime-dir@1000.service
   6ms modprobe@fuse.service
   6ms alsa-restore.service
   5ms modprobe@configfs.service
   4ms systemd-update-utmp.service
   4ms sys-fs-fuse-connections.mount
   4ms systemd-remount-fs.service
   3ms systemd-sysctl.service
   3ms systemd-rfkill.service
   3ms NetworkManager-dispatcher.service
   2ms systemd-user-sessions.service
   2ms rtkit-daemon.service
   1ms sys-kernel-config.mount
   1ms proc-sys-fs-binfmt_misc.mount
   1ms tmp.mount
systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @651ms
└─lightdm.service @640ms +10ms
  └─systemd-user-sessions.service @637ms +2ms
    └─nss-user-lookup.target @651ms
1 Like

Those outputs seem quite normal. Could you also post the output of
inxi -Fxxxz
to give the forum a general idea of your system?
Also, are you using a HDD or SDD?

Hey,

OS is on SSD.

inxi -Fxxxz
System:    Kernel: 5.14.16-arch1-1 x86_64 bits: 64 compiler: gcc v: 11.1.0 Desktop: i3 4.20.1 info: i3bar vt: 7
           dm: LightDM 1.30.0 Distro: EndeavourOS base: Arch Linux
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-F GAMING v: Rev 1.xx serial: <filter> UEFI: American Megatrends
           v: 4602 date: 08/17/2021
Battery:   ID-1: hidpp_battery_0 charge: N/A condition: N/A volts: 3.9 min: N/A model: Logitech G Pro Wireless Gaming Mouse
           type: N/A serial: <filter> status: Discharging
CPU:       Info: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 rev: 0 cache: L2: 4 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 115247
           Speed: 2199 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2199 2: 2053 3: 2057 4: 2050 5: 2056
           6: 2093 7: 2053 8: 3597 9: 2057 10: 2057 11: 2196 12: 2199 13: 2154 14: 3588 15: 3603 16: 2057
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
           vendor: Sapphire Limited driver: amdgpu v: kernel bus-ID: 0b:00.0 chip-ID: 1002:731f class-ID: 0300
           Display: x11 server: X.Org 1.21.1.1 driver: loaded: amdgpu resolution: 1: 2560x1440 2: 2560x1440~144Hz s-dpi: 218
           OpenGL: renderer: AMD Radeon RX 5700 XT (NAVI10 DRM 3.42.0 5.14.16-arch1-1 LLVM 12.0.1) v: 4.6 Mesa 21.2.4
           direct render: Yes
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus-ID: 0b:00.1
           chip-ID: 1002:ab38 class-ID: 0403
           Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
           bus-ID: 0d:00.4 chip-ID: 1022:1487 class-ID: 0403
           Device-3: Generalplus USB Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-2:2
           chip-ID: 1b3f:2008 class-ID: 0300
           Device-4: GYROCOM C&C Fiio E10 type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-5:3 chip-ID: 1852:7022
           class-ID: 0102
           Sound Server-1: ALSA v: k5.14.16-arch1-1 running: yes
           Sound Server-2: JACK v: 1.9.19 running: no
           Sound Server-3: PulseAudio v: 15.0 running: yes
           Sound Server-4: PipeWire v: 0.3.39 running: no
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: e000 bus-ID: 04:00.0
           chip-ID: 8086:1539 class-ID: 0200
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth: Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-1:2 chip-ID: 0b05:17cb
           class-ID: fe01 serial: <filter>
           Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:    Local Storage: total: 2.06 TiB used: 212.67 GiB (10.1%)
           ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW010T8 size: 953.87 GiB speed: 31.6 Gb/s lanes: 4 type: SSD
           serial: <filter> rev: 002C temp: 38.9 C scheme: GPT
           ID-2: /dev/sda vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB speed: 3.0 Gb/s type: HDD rpm: 7200
           serial: <filter> rev: A39C scheme: GPT
           ID-3: /dev/sdb vendor: Kingston model: SV300S37A240G size: 223.57 GiB speed: 6.0 Gb/s type: SSD serial: <filter>
           rev: BBF0 scheme: GPT
Partition: ID-1: / size: 218.51 GiB used: 114.37 GiB (52.3%) fs: ext4 dev: /dev/sdb2
           ID-2: /boot/efi size: 511 MiB used: 296 KiB (0.1%) fs: vfat dev: /dev/sdb1
Swap:      Alert: No swap data was found.
Sensors:   System Temperatures: cpu: 40.5 C mobo: N/A gpu: amdgpu temp: 56.0 C mem: 58.0 C
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:      Processes: 316 Uptime: 21m wakeups: 2 Memory: 15.55 GiB used: 2 GiB (12.8%) Init: systemd v: 249 Compilers:
           gcc: 11.1.0 Packages: pacman: 1040 Shell: Bash v: 5.1.8 running-in: alacritty inxi: 3.3.07
1 Like

this is not run on every boot only if it needs to update the man database… it should not be masked…
https://savannah.nongnu.org/projects/man-db

Frankly I cannot see anything off in the output you have posted so far motivating the rather long kernel load time. I am not sure if this would help but you can experiment and see if installing other kernels like LTS or ZEN will make some difference:

sudo pacman -Syu linux-lts linux-lts-headers

and/or

sudo pacman -Syu linux-zen linux-zen-headers

You could then choose the one or the other from the Grub boot menu and compare their

systemd-analyze.

1 Like

it also not only systemd that can slow down the boot process, there is a lot other stuff going to start and load on boot, if you would give a complete boot journal it could give a hint on issues:

journalctl -b -0 | eos-sendlog
1 Like

This is slightly strange. Are you booting the fallback initramfs, or did you customise /etc/mkinitcpio.conf ?

As Joe said, the other thing to check is the journal - something is causing the kernel to take a long time to load.

1 Like

Hey, absolutely.

Here you go:
https://clbin.com/mUZrH

In regards to my kernel boot time and how proud I was of reaching 40s… It’s jumping up and down. Every other boot is either 1min10s or 40s.

@jonathon I’ve seen the fallback initramfs thing on startup in grub(?) but no, I just go with the top option.
I have not customized:

/etc/mkinitcpio.conf

You’ll need to provide a log a boot when the issue happens - according to the timestamps, it took one second from loading the kernel to reaching a graphical target.

Or, are you using full disk encryption?

Interesting… It did occur on that one, it always does…
Here’s another one (38.793s (kernel)) from systemd-analyze:
https://clbin.com/ipEw4

I noticed something strange, the clock starts on 22:03:23 and then at the end goes to 21:03:56, local time currently being 21. Also my BIOS clock has been acting real strange lately, keeps going back 1h behind local time. Maybe not relevant but there you go.

In regards to encryption. I don’t actually know, sorry.
I used the Erase option in the Calamares installer, not sure if that means I got full encryption or not.

After looking at: https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/
I can determine that no, I do not have full disk encryption.

Thanks for the suggestion. Wasn’t so hard to install additional kernels it seems :smiley:
I tried both LTS and ZEN and it’s same as stock kernel. 1min10sec ±1s.

systemd-analyze
Startup finished in 11.344s (firmware) + 4.257s (loader) + 1min 8.953s (kernel) + 1.852s (userspace) = 1min 26.407s
graphical.target reached after 686ms in userspace

I added ^ as an example, this was Zen.

1 Like

dmesg shows the following, perhaps a clue?

[    6.861876] input: Logitech G Pro  as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-6/1-6:1.2/0003:046D:C539.0008/0003:046D:4079.0009/input/input18
[    6.861962] logitech-hidpp-device 0003:046D:4079.0009: input,hidraw8: USB HID v1.11 Keyboard [Logitech G Pro ] on usb-0000:02:00.0-6/input2:1
[   35.162262] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   35.964901] ata5.00: configured for UDMA/100
[   67.418262] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   68.221056] ata5.00: configured for UDMA/100
[   69.213022] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[   69.323360] systemd[1]: systemd 249.6-3-arch running in system mode (+PAM +AUDIT -SELINUX -APPARMOR -IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified)
[   69.335196] systemd[1]: Detected architecture x86-64.

My fstab looks like this:

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=823D-31AA                            /boot/efi      vfat    umask=0077 0 2
UUID=c35c9a18-5bdf-47bc-b445-66f90ddd6cf6 /              ext4    defaults,noatime 0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
UUID=b4f17a82-f403-4057-b0b4-12764cefa85f /data    auto nosuid,nodev,nofail,x-gvfs-show 0 0
UUID=80b8dc2e-f21a-4156-8741-276ac7573fb8 /data2   auto nosuid,nodev,nofail,x-gvfs-show 0 0

Which disk device is this?

:thinking: