Slow boot/fstrim

Tyskr · 2020-02-18 20:22:58

Hey guys,

so being quite new to Arch still, I recognized that my boot-time is quite long, even with an SSD.

systemd-analyze

Startup finished in 6.679s (firmware) + 2.875s (loader) + 3.741s (kernel) + 14.387s (userspace) = 27.683s 
graphical.target reached after 14.387s in userspace

I'm using gnome and plan on continue doing so until I get a hang of the basics of Arch. My research told me that having a tiling window manager like i3 oder bspwm can seed up my boot process, because it is not graphical like gnome. But I don't even know if that's true or not.

systemd-analyze critical-chain

graphical.target @14.387s
└─gdm.service @13.203s +1.182s
  └─systemd-user-sessions.service @13.151s +50ms
    └─network.target @13.148s
      └─NetworkManager.service @10.376s +2.770s
        └─dbus.service @10.375s
          └─basic.target @10.374s
            └─sockets.target @10.374s
              └─dbus.socket @10.374s
                └─sysinit.target @10.374s
                  └─systemd-update-done.service @10.368s +5ms
                    └─ldconfig.service @9.606s +761ms
                      └─local-fs.target @9.605s
                        └─boot.mount @9.540s +64ms
                          └─systemd-fsck@dev-disk-by\x2duuid-1499\x2d9AD8.service @9.093s +4>
                            └─local-fs-pre.target @9.092s
                              └─lvm2-monitor.service @7.117s +1.966s
                                └─lvm2-lvmetad.service @7.487s
                                  └─systemd-journald.socket @7.103s
                                    └─-.mount @7.011s
                                      └─system.slice @7.011s
                                        └─-.slice @7.011s

I've read the Improving Arch Boot process article, but it didn't really help.

I did

# systemctl enable upower

and

$ dmesg | grep SSS

gives me no output.

I'm currently planing on looking into hooking mkinitcpio's

fsck

(kernel line options) and silent boot. Not sure if it will help, but I'm giving it a try.

There is maybe one thing you can help me with:

I want to disable the red Lenovo logo on startup. I'm using GRUB and the wiki says that this bootloader 'typically' blanks the logo, but it doesn't. How do I manually make it disappear?

Thanks for any help, I can not reply today, but I'll get back here asap.

You guys have been of great help so far on my arch journey!
English is not my first english, sorry.

Cheers,

Tyskr

cirrus · 2020-02-19 00:34:02

The 'red lenovo' splash screen is shown before system even gets to the 'grub bootloader' stage, have a look in your BIOS for something like, disable splash screen. Sorry i have no suggestions for speeding up your boot time.

loqs · 2020-02-19 01:03:54

Tyskr wrote:

My research told me that having a tiling window manager like i3 oder bspwm can seed up my boot process, because it is not graphical like gnome.

All WMs are graphical they differ in how they display content.

Tyskr wrote:

I did

# systemctl enable upower

Did it make any difference?

Tyskr wrote:

$ dmesg | grep SSS
gives me no output.

wiki wrote:

If it wasn't used during boot, there will be no output.

Tyskr wrote:

I'm currently planing on looking into hooking mkinitcpio's
fsck
(kernel line options) and silent boot. Not sure if it will help, but I'm giving it a try.

Why? Looking at the critical chain fsck is adding a few milliseconds. Seven seconds are use before linux starts, thee seconds used by NetworkManager, two by LVM, one by GDM, most of one by dconfig and that accounts for almost all of the boot time.

You mentioned fstim in the title not in the post body.

Tyskr · 2020-02-19 07:07:59

loqs wrote:

You mentioned fstim in the title not in the post body.

whoops, my bad. Trying to enable the service gives me:

sudo systemctl enable fstrim.service

The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

loqs wrote:

Why? Looking at the critical chain fsck is adding a few milliseconds. Seven seconds are use before linux starts, thee seconds used by NetworkManager, two by LVM, one by GDM, most of one by dconfig and that accounts for almost all of the boot time.

Can I disable something here to save some time?

loqs wrote:

Did it make any difference?

Barely, maybe 1 or 2 seconds.

V1del · 2020-02-19 09:40:08

Enabling fstrim is going to be detrimental to boot time if the fstrim.timer (which is the part you are supposed to enable) decides to shoot directly when booting (can be worked around with an override to add a BootDelaySec=). One question is why is NM taking so long (how many network interfaces do you have?), I'd guess you are using WLAN/something that requires early boot entropy in which case you'd want to check if lscpu | grep rdrand gives you output, if it does add random.trust_cpu=on to your kernel parameters, otherwise install and enable haveged in order to get enough entropy up during early boot.

Last edited by V1del (2020-02-19 09:43:18)

Tyskr · 2020-02-20 14:53:23

V1del wrote:

Enabling fstrim is going to be detrimental to boot time if the fstrim.timer (which is the part you are supposed to enable) decides to shoot directly when booting (can be worked around with an override to add a BootDelaySec=). One question is why is NM taking so long (how many network interfaces do you have?), I'd guess you are using WLAN/something that requires early boot entropy in which case you'd want to check if lscpu | grep rdrand gives you output, if it does add random.trust_cpu=on to your kernel parameters, otherwise install and enable haveged in order to get enough entropy up during early boot.

Yes, WLAN.

lscpu | grep rdrand

34:Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d

'rdrand' is in there.

Last edited by Tyskr (2020-02-20 14:55:15)

V1del · 2020-02-20 14:58:43

Add

random.trust_cpu=on

to your kernel parameters. That should shave a bit off of userspace time across the board. Though the be honest I wouldn't define 27 secs as slow in any case, you are not that likely to get "much" faster.

Tyskr · 2020-02-20 15:10:00

V1del wrote:

Add
random.trust_cpu=on
to your kernel parameters. That should shave a bit off of userspace time across the board. Though the be honest I wouldn't define 27 secs as slow in any case, you are not that likely to get "much" faster.

Alright, thank you. I know that there are slower boots and this is more of a luxury problem, but I want to learn and I think this helps me in the end.

Last edited by Tyskr (2020-02-20 15:48:25)

Vizitor · 2020-02-20 21:00:02

Tyskr wrote:

Can I disable something here to save some time?

If You don't use LVM, You can spare 2 secs at booting.
Link

Arch Linux

#1 2020-02-18 20:22:58

Slow boot/fstrim

#2 2020-02-19 00:34:02

Re: Slow boot/fstrim

#3 2020-02-19 01:03:54

Re: Slow boot/fstrim

#4 2020-02-19 07:07:59

Re: Slow boot/fstrim

#5 2020-02-19 09:40:08

Re: Slow boot/fstrim

#6 2020-02-20 14:53:23

Re: Slow boot/fstrim

#7 2020-02-20 14:58:43

Re: Slow boot/fstrim

#8 2020-02-20 15:10:00

Re: Slow boot/fstrim

#9 2020-02-20 21:00:02

Re: Slow boot/fstrim

Board footer