Extremely long boot time

[die.boer]

and these

systemctl show grub-common.service -p After -p Before -p Wants -p Requires

systemctl list-dependencies --reverse grub-common.service

systemd-analyze critical-chain grub-common.service

all are read only

[Snowhog]

That's the result I get running that command on my Linux desktop PC. The final number for mine is (914).

But I can't run the command on the laptop as shown in post #12 above.

[die.boer]

can you do post #16 ?

[Snowhog]

systemctl show grub-common.service -p After -p Before -p Wants -p Requires
Requires=system.slice sysinit.target
Wants=
Before=multi-user.target shutdown.target graphical.target
After=sysinit.target basic.target system.slice all.target systemd-journald.socket


systemctl list-dependencies --reverse grub-common.service
grub-common.service
● ├─graphical.target
○ ├─hibernate.target
○ ├─hybrid-sleep.target
● ├─multi-user.target
● │ └─graphical.target
○ ├─sleep.target
○ │ ├─systemd-hibernate.service
○ │ ├─systemd-hybrid-sleep.service
○ │ ├─systemd-suspend-then-hibernate.service
○ │ └─systemd-suspend.service
○ ├─suspend-then-hibernate.target
○ └─suspend.target


systemd-analyze critical-chain grub-common.service
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.

grub-common.service +1min 35.408s
└─basic.target @30.938s
└─sockets.target @30.938s
└─snapd.socket @30.924s +13ms
└─sysinit.target @30.870s
└─snapd.apparmor.service @29.529s +1.338s
└─apparmor.service @26.874s +2.651s
└─local-fs.target @26.867s
└─run-snapd-ns-canonical\x2dlivepatch.mnt.mount @48.817s
└─run-snapd-ns.mount @45.733s
└─local-fs-pre.target @8.897s
└─systemd-tmpfiles-setup-dev.service @8.838s +55ms
└─systemd-tmpfiles-setup-dev-early.service @6.252s +2.562s
└─kmod-static-nodes.service @5.528s +222ms
└─systemd-journald.socket @5.450s +195us
└─-.mount @5.355s
└─-.slice @5.355s