I have a way longer boot time in my lenovo laptop, around 4 minutes, than in my HP desktop. Id like to link the journal_pager.svg here. Is it possible?
Just give us the text input/output from systemd-analyze, systemd-analyze blame & systemd-analyze critical-chain. We like text much better than images. 
Inptu/output from inxi -baz would be good too. Text can be quoted in replies.
Output of systemd-analyze blame is verbose but messy. Users may try:
erlangen:~ # journalctl -b -u init.scope -g Reached -o short-monotonic
[ 3.438558] erlangen systemd[1]: Reached target System Initialization.
[ 3.439373] erlangen systemd[1]: Reached target Path Units.
[ 3.439390] erlangen systemd[1]: Reached target Basic System.
[ 3.500343] erlangen systemd[1]: Reached target Initrd Root Device.
[ 4.174593] erlangen systemd[1]: Reached target Preparation for Remote File Systems.
[ 4.174606] erlangen systemd[1]: Reached target Remote File Systems.
[ 4.247842] erlangen systemd[1]: Reached target Initrd Root File System.
[ 4.254198] erlangen systemd[1]: Reached target Initrd File Systems.
[ 4.254210] erlangen systemd[1]: Reached target Initrd Default Target.
[ 4.305425] erlangen systemd[1]: Reached target Switch Root.
[ 4.812151] erlangen systemd[1]: Reached target Preparation for Local File Systems.
[ 5.519291] erlangen systemd[1]: Reached target Sound Card.
[ 5.855568] erlangen systemd[1]: Reached target Local File Systems.
[ 5.905279] erlangen systemd[1]: Reached target System Initialization.
[ 5.906260] erlangen systemd[1]: Reached target Path Units.
[ 5.907807] erlangen systemd[1]: Reached target Socket Units.
[ 5.907828] erlangen systemd[1]: Reached target Basic System.
[ 5.949478] erlangen systemd[1]: Reached target Network.
[ 5.949501] erlangen systemd[1]: Reached target Network is Online.
[ 6.007937] erlangen systemd[1]: Reached target System Time Synchronized.
[ 6.009074] erlangen systemd[1]: Reached target Timer Units.
[ 6.270317] erlangen systemd[1]: Reached target Login Prompts.
...
erlangen:~ #
sysmtemd-analyze :
Startup finished in 5.924s (firmware) + 4.091s (loader) + 948ms (kernel) + 14.158s (initrd) + 12.126s (userspace) = 37.249s
graphical.target reached after 12.126s in userspace.
systemd-analyze blame :
14.072s dev-ttyS11.device
14.072s sys-devices-platform-serial8250-tty-ttyS11.device
14.070s dev-ttyS0.device
14.070s sys-devices-platform-serial8250-tty-ttyS0.device
14.070s sys-devices-platform-serial8250-tty-ttyS10.device
14.070s dev-ttyS10.device
14.070s sys-devices-platform-serial8250-tty-ttyS24.device
14.070s dev-ttyS24.device
14.069s dev-ttyS12.device
14.069s sys-devices-platform-serial8250-tty-ttyS12.device
14.069s dev-ttyS20.device
14.069s dev-ttyS22.device
14.069s sys-devices-platform-serial8250-tty-ttyS22.device
14.069s sys-devices-platform-serial8250-tty-ttyS20.device
14.068s dev-ttyS13.device
14.068s sys-devices-platform-serial8250-tty-ttyS13.device
14.068s dev-ttyS23.device
14.068s sys-devices-platform-serial8250-tty-ttyS23.device
14.067s dev-ttyS30.device
14.067s sys-devices-platform-serial8250-tty-ttyS30.device
14.067s dev-ttyS1.device
14.067s sys-devices-platform-serial8250-tty-ttyS1.device
14.066s sys-devices-platform-serial8250-tty-ttyS27.device
14.066s dev-ttyS27.device
14.066s dev-ttyS15.device
14.066s sys-devices-platform-serial8250-tty-ttyS15.device
14.066s dev-ttyS3.device
14.066s sys-devices-platform-serial8250-tty-ttyS3.device
14.066s dev-ttyS26.device
14.066s sys-devices-platform-serial8250-tty-ttyS26.device
14.066s sys-devices-platform-serial8250-tty-ttyS17.device
14.066s dev-ttyS17.device
14.065s sys-devices-platform-serial8250-tty-ttyS31.device
14.065s dev-ttyS31.device
14.065s dev-ttyS14.device
14.065s sys-devices-platform-serial8250-tty-ttyS14.device
14.063s dev-ttyS5.device
14.063s sys-devices-platform-serial8250-tty-ttyS5.device
14.063s sys-devices-platform-serial8250-tty-ttyS6.device
14.063s dev-ttyS6.device
14.062s sys-devices-platform-serial8250-tty-ttyS4.device
14.062s dev-ttyS4.device
14.061s dev-ttyS7.device
14.061s sys-devices-platform-serial8250-tty-ttyS7.device
14.060s sys-devices-platform-serial8250-tty-ttyS25.device
14.060s dev-ttyS25.device
14.059s sys-devices-platform-serial8250-tty-ttyS8.device
14.059s dev-ttyS8.device
14.058s sys-devices-platform-serial8250-tty-ttyS9.device
14.058s dev-ttyS9.device
14.055s dev-ttyS29.device
14.055s sys-devices-platform-serial8250-tty-ttyS29.device
14.054s dev-ttyS21.device
14.054s sys-devices-platform-serial8250-tty-ttyS21.device
14.053s sys-devices-platform-serial8250-tty-ttyS28.device
14.053s dev-ttyS28.device
14.053s sys-devices-platform-serial8250-tty-ttyS16.device
14.053s dev-ttyS16.device
14.048s dev-ttyS2.device
14.048s sys-devices-platform-serial8250-tty-ttyS2.device
14.047s sys-devices-platform-serial8250-tty-ttyS18.device
14.047s dev-ttyS18.device
14.044s sys-devices-platform-serial8250-tty-ttyS19.device
14.044s dev-ttyS19.device
11.437s dracut-initqueue.service
7.258s NetworkManager-wait-online.service
3.650s sys-devices-pci0000:00-0000:00:1d.2-0000:3d:00.0-nvme-nvme0-nvme0n1.device
3.650s dev-nvme0n1.device
3.650s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKKF256G8L_BTHH82340MYH256B.device
3.650s dev-disk-by\x2did-nvme\x2deui.5cd2e42a81a1a60b.device
3.650s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1.device
3.650s dev-disk-by\x2ddiskseq-1.device
3.630s dev-disk-by\x2duuid-b663e40f\x2d22e6\x2d44e3\x2da458\x2d3461e1735f98.device
3.630s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKKF256G8L_BTHH82340MYH256B\x2dpart5.device
3.630s dev-disk-by\x2dpartuuid-65418dca\x2d7a08\x2d438a\x2db2c1\x2dbe94e2b3d937.device
3.630s dev-disk-by\x2did-nvme\x2deui.5cd2e42a81a1a60b\x2dpart5.device
3.630s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart5.device
3.630s dev-nvme0n1p5.device
3.630s sys-devices-pci0000:00-0000:00:1d.2-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p5.device
3.620s dev-disk-by\x2dpartuuid-3c3b3af3\x2d8eaa\x2d4670\x2d9997\x2dfe3669b1bca8.device
3.620s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart2.device
3.620s sys-devices-pci0000:00-0000:00:1d.2-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
3.620s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKKF256G8L_BTHH82340MYH256B\x2dpart2.device
3.620s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
3.620s dev-disk-by\x2did-nvme\x2deui.5cd2e42a81a1a60b\x2dpart2.device
3.620s dev-nvme0n1p2.device
3.610s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart6.device
3.610s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKKF256G8L_BTHH82340MYH256B\x2dpart6.device
3.610s dev-disk-by\x2dpartuuid-0926b1e6\x2dd703\x2d4db7\x2d8b1f\x2d9e606fbf9950.device
3.610s dev-disk-by\x2did-nvme\x2deui.5cd2e42a81a1a60b\x2dpart6.device
3.610s dev-nvme0n1p6.device
3.610s sys-devices-pci0000:00-0000:00:1d.2-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p6.device
3.609s dev-disk-by\x2duuid-407a1606\x2d741d\x2d480e\x2dba10\x2d0799d6ab96f4.device
3.608s dev-disk-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
3.608s dev-disk-by\x2did-nvme\x2deui.5cd2e42a81a1a60b\x2dpart1.device
3.608s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart1.device
3.608s dev-nvme0n1p1.device
3.608s sys-devices-pci0000:00-0000:00:1d.2-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
3.608s dev-disk-by\x2dpartuuid-a0eedea0\x2df5e4\x2d498c\x2d942e\x2d10f3679285d3.device
3.607s dev-disk-by\x2duuid-0615\x2dCB8F.device
3.607s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKKF256G8L_BTHH82340MYH256B\x2dpart1.device
3.598s dev-disk-by\x2duuid-0E7474B97474A55D.device
3.598s dev-nvme0n1p4.device
3.598s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKKF256G8L_BTHH82340MYH256B\x2dpart4.device
3.598s dev-disk-by\x2did-nvme\x2deui.5cd2e42a81a1a60b\x2dpart4.device
3.598s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart4.device
3.598s sys-devices-pci0000:00-0000:00:1d.2-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p4.device
3.598s dev-disk-by\x2dpartuuid-14af3117\x2d8015\x2d4dad\x2d9a53\x2dc4d78bd96824.device
3.590s dev-disk-by\x2dpartuuid-435ebeb4\x2d07f8\x2d4bfd\x2da449\x2d02db126a10cc.device
3.590s dev-disk-by\x2duuid-64C2189EC2187690.device
3.590s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
3.590s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKKF256G8L_BTHH82340MYH256B\x2dpart3.device
3.590s sys-devices-pci0000:00-0000:00:1d.2-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
3.590s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart3.device
3.590s dev-disk-by\x2did-nvme\x2deui.5cd2e42a81a1a60b\x2dpart3.device
3.590s dev-nvme0n1p3.device
3.303s sys-devices-pci0000:00-0000:00:02.0-drm-card1-card1\x2deDP\x2d1-intel_backlight.device
1.843s postfix.service
1.171s plymouth-switch-root.service
1.019s vboxdrv.service
894ms initrd-switch-root.service
847ms display-manager.service
839ms firewalld.service
545ms apparmor.service
536ms user@1000.service
489ms bolt.service
428ms ModemManager.service
413ms dracut-pre-udev.service
378ms libvirtd.service
352ms kbdsettings.service
321ms systemd-journal-flush.service
273ms boot-efi.mount
271ms sshd.service
267ms avahi-daemon.service
265ms plymouth-quit-wait.service
257ms upower.service
256ms augenrules.service
254ms auditd.service
249ms bluetooth.service
231ms smartd.service
217ms cups.service
199ms mcelog.service
195ms polkit.service
195ms systemd-logind.service
192ms chronyd.service
176ms wpa_supplicant.service
141ms issue-generator.service
135ms systemd-udev-trigger.service
133ms dracut-shutdown.service
131ms nscd.service
124ms iscsi.service
123ms systemd-machined.service
106ms dbus.service
100ms rtkit-daemon.service
93ms sound-extra.service
90ms systemd-fsck-root.service
78ms udisks2.service
74ms NetworkManager.service
71ms systemd-tmpfiles-setup.service
69ms lvm2-monitor.service
67ms systemd-vconsole-setup.service
66ms plymouth-start.service
62ms systemd-update-utmp.service
62ms systemd-udevd.service
59ms systemd-fsck@dev-disk-by\x2duuid-0615\x2dCB8F.service
54ms dracut-cmdline.service
49ms dev-hugepages.mount
48ms initrd-parse-etc.service
46ms sys-kernel-debug.mount
46ms dev-mqueue.mount
43ms user-runtime-dir@1000.service
43ms sys-kernel-tracing.mount
42ms systemd-backlight@leds:tpacpi::kbd_backlight.service
39ms kmod-static-nodes.service
35ms initrd-cleanup.service
30ms \x2esnapshots.mount
30ms modprobe@fuse.service
30ms modprobe@configfs.service
30ms systemd-journald.service
29ms systemd-backlight@backlight:intel_backlight.service
29ms systemd-random-seed.service
28ms boot-grub2-i386\x2dpc.mount
27ms boot-grub2-x86_64\x2defi.mount
27ms modprobe@drm.service
26ms home.mount
25ms opt.mount
24ms dev-disk-by\x2duuid-407a1606\x2d741d\x2d480e\x2dba10\x2d0799d6ab96f4.swap
24ms root.mount
23ms srv.mount
22ms usr-local.mount
22ms systemd-user-sessions.service
20ms var.mount
19ms systemd-remount-fs.service
19ms vboxautostart-service.service
18ms tmp.mount
15ms systemd-modules-load.service
15ms plymouth-read-write.service
14ms systemd-tmpfiles-setup-dev.service
11ms alsa-restore.service
10ms systemd-sysctl.service
10ms kernel-sysctl.service
6ms initrd-udevadm-cleanup-db.service
5ms sys-kernel-config.mount
3ms sys-fs-fuse-connections.mount
systemd-analyze critical-chain :
mekazawa@localhost:~> 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 @\12.126s
└─display-manager.service @\11.277s +847ms
└─systemd-user-sessions.service @11.246s +22ms
└─remote-fs.target @\11.204s
└─iscsi.service @\11.077s +124ms
└─network-online.target @\11.049s
└─NetworkManager-wait-online.service @\3.788s +7.258s
└─NetworkManager.service @\3.681s +74ms
└─network-pre.target @\3.677s
└─wpa_supplicant.service @\4.328s +176ms
└─dbus.service @\2.508s +106ms
└─basic.target @\2.499s
└─sockets.target @\2.499s
└─virtlogd.socket @\2.499s
└─sysinit.target @\2.492s
└─systemd-update-utmp.service @\2.430s +62ms
└─auditd.service @\2.159s +254ms
└─systemd-tmpfiles-setup.service @\2.086s +71ms
└─systemd-journal-flush.service @\1.763s +321ms
└─var.mount @\1.734s +20ms
└─dev-nvme0n1p5.device @\584542y 2w 2d 20h 1min 46.837s +3.630s
inxi -baz :
System:
Kernel: 6.1.3-1-default arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.3-1-default
root=UUID=b663e40f-22e6-44e3-a458-3461e1735f98 splash=silent
mitigations=auto quiet security=apparmor
Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.7 wm: kwin_x11 vt: 7 dm: SDDM
Distro: openSUSE Tumbleweed 20230108
Machine:
Type: Laptop System: LENOVO product: 20L6S8LU1R v: ThinkPad T480
serial: Chassis: type: 10 serial:
Mobo: LENOVO model: 20L6S8LU1R v: SDK0J40697 WIN
serial: UEFI: LENOVO v: N24ET71W (1.46 )
date: 09/29/2022
Battery:
ID-1: BAT0 charge: 0 Wh condition: N/A volts: N/A model: N/A type: Unknown
serial: N/A status: not charging cycles: -1
ID-2: BAT1 charge: 37.1 Wh (58.1%) condition: 63.9/71.3 Wh (89.6%)
volts: 11.3 min: 10.8 model: SANYO 01AV427 type: Li-ion serial:
status: discharging cycles: 200
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial:
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: dual core Intel Core i5-7300U [MT MCP] arch: Amber/Kaby Lake
note: check speed (MHz): avg: 1649 min/max: 400/3500
Graphics:
Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916
class-ID: 0300
Device-2: IMC Networks Integrated Camera type: USB driver: uvcvideo
bus-ID: 1-8:4 chip-ID: 13d3:56a6 class-ID: 0e02 serial:
Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa
alternate: intel dri: iris gpu: i915 resolution: 1920x1080~60Hz
API: OpenGL v: 4.6 Mesa 22.3.2 renderer: Mesa Intel HD Graphics 620 (KBL
GT2) direct render: Yes
Network:
Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d7 class-ID: 0200
Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:24fd
class-ID: 0280
Drives:
Local Storage: total: 238.47 GiB used: 43.85 GiB (18.4%)
Info:
Processes: 239 Uptime: 0h 15m wakeups: 1772 Memory: 7.52 GiB
used: 2.91 GiB (38.7%) Init: systemd v: 252 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 alt: 12 Packages: pm: rpm pkgs: N/A
note: see --rpm tools: yast,zypper pm: flatpak pkgs: 13 Shell: Bash
v: 5.2.15 running-in: konsole inxi: 3.3.23
@mrmazda @karlmistelberger hope that helps. thanks.
This is the only thing that looks wrong, and it looks gigantically wrong. It means 584,542 years, 2 weeks, 2 days… Please post output with input from cat /etc/fstab and sudo parted -l. This time, include your pastes in a single reply, and within [pre] tags, like the following:
[pre]your pastes
go here[/pre]
which retains whatever formatting was part of the command output, and looks like this when submitted:
your pastes
go here
[pre] UUID=b663e40f-22e6-44e3-a458-3461e1735f98 / btrfs defaults 0 0
UUID=b663e40f-22e6-44e3-a458-3461e1735f98 /var btrfs subvol=/@/var 0 0
UUID=b663e40f-22e6-44e3-a458-3461e1735f98 /usr/local btrfs subvol=/@/usr/local 0 0
UUID=b663e40f-22e6-44e3-a458-3461e1735f98 /srv btrfs subvol=/@/srv 0 0
UUID=b663e40f-22e6-44e3-a458-3461e1735f98 /root btrfs subvol=/@/root 0 0
UUID=b663e40f-22e6-44e3-a458-3461e1735f98 /opt btrfs subvol=/@/opt 0 0
UUID=b663e40f-22e6-44e3-a458-3461e1735f98 /home btrfs subvol=/@/home 0 0
UUID=b663e40f-22e6-44e3-a458-3461e1735f98 /boot/grub2/x86_64-efi btrfs subvol=/@/boot/grub2/x86_64-efi 0 0
UUID=b663e40f-22e6-44e3-a458-3461e1735f98 /boot/grub2/i386-pc btrfs subvol=/@/boot/grub2/i386-pc 0 0
UUID=0615-CB8F /boot/efi vfat utf8 0 2
UUID=b663e40f-22e6-44e3-a458-3461e1735f98 /.snapshots btrfs subvol=/@/.snapshots 0 0
UUID=407a1606-741d-480e-ba10-0799d6ab96f4 swap swap defaults 0 0
[/pre]
[pre] Model: INTEL SSDPEKKF256G8L (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 106MB 105MB fat32 EFI system partition boot, esp
2 106MB 123MB 16.8MB Microsoft reserved partition msftres
3 123MB 117GB 117GB ntfs Basic data partition msftdata
5 117GB 253GB 136GB btrfs
6 253GB 256GB 2147MB linux-swap(v1) swap
4 256GB 256GB 532MB ntfs hidden, diag
[/pre]
You showed no evidence supporting your claim of a four minutes wait. I won’t read through the lengthy mess posted above. Again show output of :
journalctl -b -u init.scope -g Reached -o short-monotonic
1 Like
I still see no direct evidence to suggest abnormally long boot time is occurring. From when to when are you measuring the four minutes? Does it take that long to reach the login manager? Are you using auto-login, and just not able to use your Plasma desktop until after that long?
Please do as karlmistelberger suggested.
Also please explain why iscsi is appearing in systemd-analyze output. It’s never appeared on any of my PCs or laptops, and I’ve never tried to enable or use it. Are you using iscsi for anything? It’s an internet protocol, which sort of suggests you may be using the cloud for data storage or other automatic web connection responsible for startup delay.
If you edit /etc/sysconfig/network/config and change the entry WAIT_FOR_INTERFACES="30" to WAIT_FOR_INTERFACES="1"and NM_ONLINE_TIMEOUT="30" to NM_ONLINE_TIMEOUT="0"should reduce this delay.
edit: fixed file path.
@malcolmlewis I didnt notice any difference, I couldnt find the path you gave, I think you meant /etc/sysconfig/network/config.
@kapedward I editied the link 
I see here;
systemd-analyze blame | grep Network
38ms NetworkManager.service
6ms NetworkManager-wait-online.service
Change to NM_ONLINE_TIMEOUT=“1” and WAIT_FOR_INTERFACES=“0”.
Alright, I was away, my bad for the delay. youre right the was probably not that long but still considerable. The time got reduced by an update I belive like 2 weeks ago.
I find 20 seconds still long (I use SSD), on my desktop is around 10 seconds. Any clues how to reduce it more? Thanks
[ 1.675107] localhost systemd[1]: Reached target System Initialization.
[ 1.703379] localhost systemd[1]: Reached target Path Units.
[ 1.703417] localhost systemd[1]: Reached target Basic System.
[ 12.056914] localhost systemd[1]: Reached target Initrd Root Device.
[ 12.892741] localhost systemd[1]: Reached target Preparation for Remote File Systems.
[ 12.892793] localhost systemd[1]: Reached target Remote File Systems.
[ 13.052226] localhost systemd[1]: Reached target Initrd Root File System.
[ 13.153606] localhost systemd[1]: Reached target Initrd File Systems.
[ 13.153781] localhost systemd[1]: Reached target Initrd Default Target.
[ 13.277525] localhost systemd[1]: Reached target Switch Root.
[ 15.566547] localhost systemd[1]: Reached target Preparation for Local File Systems.
[ 15.790816] localhost systemd[1]: Reached target Swaps.
[ 16.899929] localhost systemd[1]: Reached target Local File Systems.
[ 17.249222] localhost systemd[1]: Reached target System Initialization.
[ 17.258217] localhost systemd[1]: Reached target Path Units.
[ 17.262979] localhost systemd[1]: Reached target Socket Units.
[ 17.263134] localhost systemd[1]: Reached target Basic System.
[ 17.411626] localhost systemd[1]: Reached target Host and Network Name Lookups.
[ 17.411835] localhost systemd[1]: Reached target User and Group Name Lookups.
[ 17.789869] localhost systemd[1]: Reached target Bluetooth Support.
[ 17.853029] localhost systemd[1]: Reached target Sound Card.
[ 18.132338] localhost systemd[1]: Reached target Preparation for Network.
[ 18.192861] localhost systemd[1]: Reached target Network.
[ 18.216631] localhost.localdomain systemd[1]: Reached target Network is Online.
[ 18.289641] localhost.localdomain systemd[1]: Reached target Remote File Systems.
[ 18.521776] localhost.localdomain systemd[1]: Reached target System Time Synchronized.
[ 18.536833] localhost.localdomain systemd[1]: Reached target Timer Units.
[ 18.828159] localhost.localdomain systemd[1]: Reached target Login Prompts.
[ 19.970908] localhost.localdomain systemd[1]: Reached target Multi-User System.
[ 19.971168] localhost.localdomain systemd[1]: Reached target Graphical Interface.
@kapedward need to see the output from;
systemd-analyze
systemd-analyze critical-chain
systemd-analyze:
Startup finished in 5.858s (firmware) + 2.881s (loader) + 739ms (kernel) + 14.120s (initrd) + 5.110s (userspace) = 28.710s
graphical.target reached after 5.110s in userspace.
systemd-analyze critical-chain
graphical.target @5.110s
└─multi-user.target @5.110s
└─cron.service @5.109s
└─postfix.service @3.714s +1.367s
└─time-sync.target @3.661s
└─chronyd.service @3.337s +323ms
└─network.target @3.331s
└─NetworkManager.service @3.293s +36ms
└─network-pre.target @3.271s
└─wpa_supplicant.service @3.974s +99ms
└─dbus.service @2.409s +100ms
└─basic.target @2.402s
└─sockets.target @2.402s
└─virtlogd.socket @2.402s
└─sysinit.target @2.388s
└─systemd-update-utmp.service @2.344s +42ms
└─auditd.service @2.217s +100ms
└─systemd-tmpfiles-setup.service @2.114s +62ms
└─local-fs.target @2.039s
└─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @2.148s
└─local-fs-pre.target @705ms
└─systemd-tmpfiles-setup-dev.service @688ms +17ms
└─kmod-static-nodes.service @621ms +59ms
└─systemd-journald.socket
└─system.slice
└─-.slice
What about:
erlangen:~ # systemctl list-dependencies initrd-root-device.target
initrd-root-device.target
○ ├─remote-cryptsetup.target
○ └─remote-veritysetup.target
erlangen:~ #
systemctl list-dependencies initrd-root-device.target :
initrd-root-device.target
○ ├─remote-cryptsetup.target
○ └─remote-veritysetup.target
Exactly the same as your
You may want to check details of journal between target Basic System (1.703417) and target Initrd Root Device (12.056914). This is huge delay compared to erlangen’s 3.435604 and 3.495185.
erlangen:~ # journalctl -b -u init.scope -g Reached -o short-monotonic
[ 3.434797] erlangen systemd[1]: Reached target System Initialization.
[ 3.435588] erlangen systemd[1]: Reached target Path Units.
[ 3.435604] erlangen systemd[1]: Reached target Basic System.
[ 3.495185] erlangen systemd[1]: Reached target Initrd Root Device.
...
erlangen:~ #