Boot Time takes very long (userspace)

Support
1

Hello Dear Manjaro Community,

I found a post regarding to my problem, but it is closed and I cant answer to it, so I have to open a new one. The old one is here:

The problem is, that my userspace takes a long time and probably looks to boot a partition in the wrong place. There is no link on a guide how to fix it thoug and I coudnt find the folder mentioned (/etc/fstab/)

Here is the output of systemd-analyze

Startup finished in 5.567s (firmware) + 5.410s (loader) + 2.683s (kernel) + 1min 39.797s (userspace) = 1min 53.458s 
graphical.target reached after 1min 31.576s in userspace.

Out put systemd-analyze blame

8.067s NetworkManager-wait-online.service
1.422s systemd-random-seed.service
 862ms NetworkManager.service
 857ms apparmor.service
 773ms dev-nvme0n1p2.device
 360ms snapd.service
 331ms systemd-udev-trigger.service
 306ms systemd-tmpfiles-setup.service
 302ms snapd.apparmor.service
 203ms pkgfile-update.service
 200ms systemd-journald.service
 191ms user@1000.service
 187ms systemd-journal-flush.service
 169ms systemd-rfkill.service
 160ms upower.service
 113ms polkit.service
 112ms systemd-logind.service
 109ms boot-efi.mount
 107ms lvm2-monitor.service
 101ms systemd-udevd.service
  98ms systemd-vconsole-setup.service
  94ms systemd-tmpfiles-setup-dev-early.service
  91ms bluetooth.service
  87ms accounts-daemon.service
  77ms systemd-tmpfiles-clean.service
  77ms logrotate.service
  75ms ModemManager.service
  70ms systemd-hostnamed.service
  60ms udisks2.service
  58ms systemd-fsck@dev-disk-by\x2duuid-4809\x2dBF21.service
  55ms systemd-tmpfiles-setup-dev.service
  50ms dbus-broker.service
  47ms dev-hugepages.mount
  46ms dev-mqueue.mount
  46ms modprobe@fuse.service
  44ms sys-kernel-debug.mount
  43ms ufw.service
  42ms sys-kernel-tracing.mount
  38ms systemd-modules-load.service
  37ms kmod-static-nodes.service
  35ms systemd-binfmt.service
  33ms systemd-udev-load-credentials.service
  32ms maia-console@tty1.service
  32ms add-autologin-group.service
  31ms modprobe@configfs.service
  29ms sys-kernel-config.mount
  29ms avahi-daemon.service
  27ms systemd-remount-fs.service
  27ms lightdm.service
  26ms cups.service
  26ms alsa-restore.service
  26ms modprobe@drm.service
  25ms systemd-backlight@backlight:amdgpu_bl0.service
  23ms rtkit-daemon.service
  21ms systemd-sysctl.service
  20ms sys-fs-fuse-connections.mount
  20ms wpa_supplicant.service
  17ms proc-sys-fs-binfmt_misc.mount
  16ms tmp.mount
  14ms user-runtime-dir@1000.service
  11ms systemd-update-utmp.service
  10ms systemd-user-sessions.service
   8ms snapd.socket
   7ms modprobe@loop.service
   7ms modprobe@dm_mod.service

lsblk output:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1     259:0    0 238,5G  0 disk 
├─nvme0n1p1 259:1    0   300M  0 part /boot/efi
└─nvme0n1p2 259:2    0 238,2G  0 part /

Thanks in advance for your help! :slight_smile:

2

/etc/fstab is not a folder, it is a file named “fstab”, located in the /etc folder

You could simply press ESC during boot to see all the messages that are normally being hidden behind the plymouth boot splash.
That might give you some clue.

Then there are other ways to see what is going on:
journalctl -b 0 (if memory serves right)
scroll using the up and down arrows

then there is a few other ways to analyze what is happening when during the boot process.
(link goes to the Arch wiki)

My boot time is about the same as yours - but I don’t have nvme solid state “drives”, but a real spinning disk.

3

I’d remove quiet and splash from the GRUB cmdline. That will give you a chance to see where it hangs, with any luck, without having to hit ESC at the right time. It might even help if it’s actually Plymouth holding things up?

sudo nano /etc/default/grub
5

Relevant Output of journalctl -b 0

Jul 16 08:12:51 systemd[1]: systemd-rfkill.service: Deactivated successfully.
Jul 16 08:14:14 systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start timed out.
Jul 16 08:14:14 systemd[1]: Timed out waiting for device /dev/tpmrm0.
Jul 16 08:14:14 systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start failed with result 'timeout'.
Jul 16 08:14:14 systemd[1]: Reached target Trusted Platform Module.

THERE is the 1 minute waiting time according to the timestamp (from line 1 to line 2)

6

Easily fixed:

1 Like
7

looks like the TPM is the source of your troble.
I don’t have a computer with such a thing myself but I’d likely disable it if I did.

Can’t tell you more about it due to lack of experience - I know I read it could be disabled by supplying a kernel command line parameter to Grub.

Then again, the thing has a purpose and you may not want to simply disable it …

8

Thank you SO MUCH, that was the solution :smile: :smile: :smile:

1 Like
9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.