Painfully slow boot. my fixes don't fix

  1. Hardware:
  • Laptop: HP EliteBook 8460p
  • Network Card: Intel 82579LM (Intel PRO/1000)
  • Boot Mode: MBR/Legacy
  • Drives: Triple-boot (Internal: Windows, Zorin; External: Parrot OS, encrypted LUKS SSD). Parrot OS's GRUB manages the boot process.
  1. Symptom:
  • A consistent 90-second hang at the Zorin splash screen before the login screen appears. The boot process is slow regardless of which OS was last used.
  1. Diagnostic Output:
  • systemd-analyze critical-chain :
graphical.target @1min 36.308s
└─multi-user.target @1min 36.308s
  └─plymouth-quit-wait.service @1min 33.472s +2.822s
    └─systemd-user-sessions.service @1min 33.435s +21ms
      └─network.target @1min 33.418s
        └─NetworkManager.service @1min 31.412s +2.005s

4.This shows the hang is at network.target .*

  • dmesg | grep -i e1000e (after boot):
[    1.676126] e1000e: Intel(R) PRO/1000 Network Driver
...
[  999.901709] e1000e: EEE TX LPI TIMER: 00000011
[ 1001.863914] e1000e 0000:00:19.0 enp0s25: NIC Link is Down

5.This shows the e1000e driver loaded, but the "EEE TX LPI TIMER" message is a known indicator of the 90-second hang on this chip.*
6. Troubleshooting Attempted:

  • Added e1000e.disable_msi=1 and e1000e.EEE=0 to Parrot OS's GRUB config.
  • Created a systemd service in Zorin to run ethtool -K enp0s25 tso off gso off gro off at boot.
  • None of these attempts resolved the 90-second splash screen hang.

Hello and welcome,
disable Fast Startup in Windows power management
After show me the output of

systemd-analyze
systemd-analyze blame

and

cat /etc/default/grub

Thank you very much. I appreciate this help.
Much respect to you.
stats:
systemd-analyze blame
Startup finished in 4.845s (kernel) + 1min 36.259s (userspace) = 1min 41.104s
graphical.target reached after 1min 36.211s in userspace.
2.868s plymouth-quit-wait.service
2.476s fwupd.service
1.926s NetworkManager.service
1.536s snapd.seeded.service
1.308s dev-sdb5.device
953ms snapd.service
785ms systemd-backlight@backlight:intel_backlight.service
624ms networkd-dispatcher.service
545ms accounts-daemon.service
527ms udisks2.service
515ms gnome-remote-desktop.service
498ms iio-sensor-proxy.service
482ms power-profiles-daemon.service
452ms polkit.service
430ms gpu-manager.service
427ms e2scrub_reap.service
372ms user@1000.service
360ms avahi-daemon.service
331ms ufw.service
322ms bluetooth.service
316ms grub-common.service
303ms apparmor.service
300ms lm-sensors.service
279ms upower.service
278ms systemd-udev-trigger.service
270ms dev-loop7.device
266ms dev-loop6.device
lines 1-27...skipping...
2.868s plymouth-quit-wait.service
2.476s fwupd.service
1.926s NetworkManager.service
1.536s snapd.seeded.service
1.308s dev-sdb5.device
953ms snapd.service
785ms systemd-backlight@backlight:intel_backlight.service
624ms networkd-dispatcher.service
545ms accounts-daemon.service
527ms udisks2.service
515ms gnome-remote-desktop.service
498ms iio-sensor-proxy.service
482ms power-profiles-daemon.service
452ms polkit.service
430ms gpu-manager.service
427ms e2scrub_reap.service
372ms user@1000.service
360ms avahi-daemon.service
331ms ufw.service
322ms bluetooth.service
316ms grub-common.service
303ms apparmor.service
300ms lm-sensors.service
279ms upower.service
278ms systemd-udev-trigger.service
270ms dev-loop7.device
266ms dev-loop6.device
261ms dev-loop5.device
253ms dev-loop4.device
251ms systemd-resolved.service
241ms systemd-journald.service
239ms dev-loop3.device
232ms update-notifier-download.service
227ms switcheroo-control.service
223ms dev-loop2.device
222ms disable-tso.service
215ms dev-loop1.device
213ms dev-loop10.device
212ms ModemManager.service
206ms dev-loop9.device
204ms systemd-modules-load.service
203ms thermald.service
202ms systemd-logind.service
199ms dbus.service
195ms dev-loop8.device
182ms dev-loop0.device
171ms systemd-journal-flush.service
161ms systemd-udevd.service
156ms keyboard-setup.service
141ms sysstat.service
136ms systemd-timesyncd.service
136ms alsa-restore.service
129ms systemd-oomd.service
117ms grub-initrd-fallback.service
110ms wpa_supplicant.service
84ms snapd.apparmor.service
82ms gdm.service
80ms packagekit.service
78ms snap-bare-5.mount
75ms snap-core18-2999.mount
72ms snap-core20-2866.mount
70ms dev-hugepages.mount
69ms systemd-rfkill.service
69ms dev-mqueue.mount
67ms sys-kernel-debug.mount
66ms snap-core24-1643.mount
65ms sys-kernel-tracing.mount
65ms kerneloops.service
61ms snap-gnome\x2d3\x2d28\x2d1804-198.mount
58ms snap-gnome\x2d46\x2d2404-153.mount
57ms disable-offload.service
56ms colord.service
54ms snap-gtk\x2dcommon\x2dthemes-1535.mount
53ms systemd-tmpfiles-setup-dev-early.service
53ms modprobe@configfs.service
51ms kmod-static-nodes.service
50ms systemd-binfmt.service
50ms snap-mesa\x2d2404-1165.mount
49ms systemd-tmpfiles-setup.service
48ms systemd-random-seed.service
46ms modprobe@drm.service
46ms systemd-remount-fs.service
46ms dev-disk-by\x2duuid-3df9dfde\x2db902\x2d4230\x2d95c7\x2d79dc017d7e87.swap
45ms snap-snapd-26865.mount
42ms plymouth-start.service
39ms snap-terminal\x2dfun-6.mount
38ms systemd-update-utmp-runlevel.service
37ms modprobe@fuse.service
34ms snap-whatsapp\x2ddesktop\x2dlinux-1.mount
33ms systemd-update-utmp.service
31ms systemd-sysctl.service
28ms sys-fs-fuse-connections.mount
27ms setvtrgb.service
27ms sys-kernel-config.mount
23ms proc-sys-fs-binfmt_misc.mount
20ms plymouth-read-write.service
20ms openvpn.service
20ms swapfile.swap
19ms rtkit-daemon.service
18ms user-runtime-dir@1000.service
18ms systemd-user-sessions.service
17ms console-setup.service
15ms systemd-tmpfiles-setup-dev.service
11ms modprobe@efi_pstore.service
8ms snapd.socket
8ms modprobe@loop.service
7ms modprobe@dm_mod.service
lines 45-107/107 (END)

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=1 e1000e.disable_msi=1"
GRUB_CMDLINE_LINUX=""

If your computer has multiple operating systems installed, then you

probably want to run os-prober. However, if your computer is a host

for guest OSes installed via LVM or raw disk devices, running

os-prober can cause damage to those guest OSes as it mounts

filesystems to look for things.

#GRUB_DISABLE_OS_PROBER=false

Uncomment to enable BadRAM filtering, modify to suit your needs

This works with Linux (no patch required) and with any kernel that obtains

the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)

#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

Uncomment to disable graphical terminal

#GRUB_TERMINAL=console

The resolution used on graphical terminal

note that you can use only modes which your graphic card supports via VBE

you can see them in real GRUB with the command `vbeinfo'

#GRUB_GFXMODE=640x480

Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux

#GRUB_DISABLE_LINUX_UUID=true

Uncomment to disable generation of recovery mode menu entries

#GRUB_DISABLE_RECOVERY="true"

Uncomment to get a beep at grub start

#GRUB_INIT_TUNE="480 440 1"

GRUB_THEME=/usr/share/grub/themes/zorin/theme.txt
GRUB_DISABLE_MEMTEST=true

IN your Zorin Grub you need to add the same you did with Parrot, actually you have

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=1 e1000e.disable_msi=1"

change it to

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=1 e1000e.EEE=0"
sudo update-grub
sudo reboot

Thank you for coaching me through this.
I performed the edit, updated, then rebooted to a boot error screen that told me to type "journalctl -bx" in the terminal. (10000+ lines to read :woozy_face: )
But I digress;
Once I did get back in, the boot was pretty much the same.
I'm stumped.

current situation:

~$ systemd-analyze
systemd-analyze blame
Startup finished in 4.920s (kernel) + 1min 36.430s (userspace) = 1min 41.350s
graphical.target reached after 1min 36.384s in userspace.
2.816s plymouth-quit-wait.service
2.398s fwupd.service
2.059s NetworkManager.service
1.576s snapd.seeded.service
1.205s dev-sdb5.device
965ms snapd.service
671ms networkd-dispatcher.service
587ms accounts-daemon.service
557ms udisks2.service
554ms gnome-remote-desktop.service
547ms iio-sensor-proxy.service
499ms power-profiles-daemon.service
489ms polkit.service
441ms gpu-manager.service
439ms e2scrub_reap.service
357ms user@1000.service
335ms grub-common.service
315ms apparmor.service
307ms ufw.service
296ms systemd-logind.service
281ms systemd-udev-trigger.service
267ms avahi-daemon.service
266ms lm-sensors.service
lines 1-23...skipping...
2.816s plymouth-quit-wait.service
2.398s fwupd.service
2.059s NetworkManager.service
1.576s snapd.seeded.service
1.205s dev-sdb5.device
965ms snapd.service
671ms networkd-dispatcher.service
587ms accounts-daemon.service
557ms udisks2.service
554ms gnome-remote-desktop.service
547ms iio-sensor-proxy.service
499ms power-profiles-daemon.service
489ms polkit.service
441ms gpu-manager.service
439ms e2scrub_reap.service
357ms user@1000.service
335ms grub-common.service
315ms apparmor.service
307ms ufw.service
296ms systemd-logind.service
281ms systemd-udev-trigger.service
267ms avahi-daemon.service
266ms lm-sensors.service
266ms systemd-resolved.service
264ms upower.service
260ms thermald.service
251ms bluetooth.service
246ms systemd-modules-load.service
218ms dev-loop7.device
216ms dev-loop9.device
215ms dev-loop6.device
212ms dev-loop2.device
208ms dev-loop4.device
203ms dev-loop8.device
199ms ModemManager.service
198ms dev-loop5.device
196ms update-notifier-download.service
195ms disable-tso.service
190ms dev-loop3.device
186ms dbus.service
180ms dev-loop1.device
167ms dev-loop10.device
160ms systemd-timesyncd.service
157ms alsa-restore.service
155ms systemd-journald.service
146ms dev-loop0.device
146ms systemd-journal-flush.service
141ms keyboard-setup.service
131ms systemd-udevd.service
131ms systemd-oomd.service
129ms switcheroo-control.service
110ms grub-initrd-fallback.service
99ms snap-core18-2999.mount
97ms snap-bare-5.mount
95ms snap-core20-2866.mount
91ms snap-core24-1643.mount
91ms sysstat.service
87ms snap-gnome\x2d3\x2d28\x2d1804-198.mount
85ms wpa_supplicant.service
83ms snap-gnome\x2d46\x2d2404-153.mount
lines 1-60

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=1 e1000e.EEE=0"
GRUB_CMDLINE_LINUX=""
#GRUB_DISABLE_OS_PROBER=false

#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

#GRUB_TERMINAL=console

#GRUB_GFXMODE=640x480

#GRUB_DISABLE_LINUX_UUID=true

#GRUB_DISABLE_RECOVERY="true"

Uncomment to get a beep at grub start

#GRUB_INIT_TUNE="480 440 1"

GRUB_THEME=/usr/share/grub/themes/zorin/theme.txt
GRUB_DISABLE_MEMTEST=true

Give me the output of

systemctl status NetworkManager-wait-online.service

$ systemctl status NetworkManager-wait-online.service
○ NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; disabled; preset: enabled)
Active: inactive (dead)
Docs: man:NetworkManager-wait-online.service(8)

try this and reboot after

sudo systemctl disable NetworkManager-wait-online.service
sudo systemctl mask NetworkManager-wait-online.service

This seems to be the Reason why it took so long. @Nourpon: Do You know what flaas in specific under ''userspace''?

Also: Maybe that Parrot OS is encrypted and on an external Driver could be a Factor, too.

Here is the problem

Back in. At last.
This happened:
"Emergency mode. After logging in, type "journal -xb" to view......"

Every 2nd boot is a fail. My Zorin boot situation has been jacked since jump.
I was forced to use grub2win for a bit. Until I learned my (painful lesson).

ParrotOS allows grub to connect, at least. (Chainloaded. bypassing Zorin's grub).

But I am not knowledgeable enough to see what is right in front of me.
You know?

Ok.
you just confirmed my conclusion. Something was staring right at me.
But I am unable to properly analyze the data.

is it the NIC Link being down?
Noob student getting owned. You know?

give me the output of

systemd-analyze blame | head -25
systemctl --failed
systemctl list-units --type=mount --type=swap
journalctl -b | grep -iE "timed out|timeout|dependency failed|job .*running"

and also that

cat /etc/fstab 
cat /etc/crypttab

I was wrong the problem is elsewhere, maybe a bad entry in fstab...

systemctl --failed
systemctl list-units --type=mount --type=swap
journalctl -b | grep -iE "timed out|timeout|dependency failed|job .*running"
2.841s plymouth-quit-wait.service
2.368s fwupd.service
2.065s NetworkManager.service
1.560s snapd.seeded.service
1.158s dev-sdb5.device
986ms snapd.service
847ms systemd-backlight@backlight:intel_backlight.service
613ms networkd-dispatcher.service
575ms gpu-manager.service
575ms accounts-daemon.service
537ms udisks2.service
533ms gnome-remote-desktop.service
515ms iio-sensor-proxy.service
471ms power-profiles-daemon.service
451ms e2scrub_reap.service
446ms polkit.service
364ms grub-common.service
359ms user@1000.service
345ms avahi-daemon.service
324ms bluetooth.service
316ms ufw.service
296ms apparmor.service
291ms systemd-udev-trigger.service
291ms update-notifier-download.service
281ms upower.service
UNIT LOAD ACTIVE SUB DESCRIPTION

0 loaded units listed.
UNIT LOAD ACTIVE SUB DESCRIPTION
-.mount loaded active mounted Root Mount
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
proc-sys-fs-binfmt_misc.mount loaded active mounted Arbitrary Executable File Formats File System
run-user-1000-doc.mount loaded active mounted /run/user/1000/doc
run-user-1000-gvfs.mount loaded active mounted /run/user/1000/gvfs
run-user-1000.mount loaded active mounted /run/user/1000
snap-bare-5.mount loaded active mounted Mount unit for bare, revision 5
snap-core18-2999.mount loaded active mounted Mount unit for core18, revision 2999
snap-core20-2866.mount loaded active mounted Mount unit for core20, revision 2866
snap-core24-1643.mount loaded active mounted Mount unit for core24, revision 1643
snap-gnome\x2d3\x2d28\x2d1804-198.mount loaded active mounted Mount unit for gnome-3-28-1804, revision 198
snap-gnome\x2d46\x2d2404-153.mount loaded active mounted Mount unit for gnome-46-2404, revision 153
snap-gtk\x2dcommon\x2dthemes-1535.mount loaded active mounted Mount unit for gtk-common-themes, revision 1535
snap-mesa\x2d2404-1165.mount loaded active mounted Mount unit for mesa-2404, revision 1165
snap-snapd-26865.mount loaded active mounted Mount unit for snapd, revision 26865
snap-terminal\x2dfun-6.mount loaded active mounted Mount unit for terminal-fun, revision 6
snap-whatsapp\x2ddesktop\x2dlinux-1.mount loaded active mounted Mount unit for whatsapp-desktop-linux, revision 1
sys-fs-fuse-connections.mount loaded active mounted FUSE Control File System
sys-kernel-config.mount loaded active mounted Kernel Configuration File System
sys-kernel-debug.mount loaded active mounted Kernel Debug File System
sys-kernel-tracing.mount loaded active mounted Kernel Trace File System
dev-disk-by\x2duuid-3df9dfde\x2db902\x2d4230\x2d95c7\x2d79dc017d7e87.swap loaded active active /dev/disk/by-uuid/3df9dfde-b902-4230-95c7-79dc017d7e87
swapfile.swap loaded active active /swapfile

Legend: LOAD → Reflects whether the unit definition was properly loaded.
ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
SUB → The low-level unit activation state, values depend on unit type.

24 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
jun 02 19:15:39 Inez-HP-EliteBook-8460p systemd[1]: dev-disk-by\x2duuid-B5B8\x2dAD78.device: Job dev-disk-by\x2duuid-B5B8\x2dAD78.device/start timed out.
jun 02 19:15:39 Inez-HP-EliteBook-8460p systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-B5B8\x2dAD78.device - /dev/disk/by-uuid/B5B8-AD78.
jun 02 19:15:39 Inez-HP-EliteBook-8460p systemd[1]: Dependency failed for systemd-fsck@dev-disk-by\x2duuid-B5B8\x2dAD78.service - File System Check on /dev/disk/by-uuid/B5B8-AD78.
jun 02 19:15:39 Inez-HP-EliteBook-8460p systemd[1]: Dependency failed for boot-efi.mount - /boot/efi.
jun 02 19:15:39 Inez-HP-EliteBook-8460p systemd[1]: Dependency failed for local-fs.target - Local File Systems.
jun 02 19:15:39 Inez-HP-EliteBook-8460p systemd[1]: dev-disk-by\x2duuid-B5B8\x2dAD78.device: Job dev-disk-by\x2duuid-B5B8\x2dAD78.device/start failed with result 'timeout'.
jun 02 19:15:41 Inez-HP-EliteBook-8460p snapd[1116]: daemon.go:370: adjusting startup timeout by 1m25s (pessimistic estimate of 30s plus 5s per snap)
jun 02 19:15:46 Inez-HP-EliteBook-8460p NetworkManager[1169]: [1780420546.2463] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
jun 02 19:16:23 Inez-HP-EliteBook-8460p fwupd[2820]: ERROR:tcti:src/tss2-tcti/tcti-device.c:502:Tss2_Tcti_Device_Init() timeout waiting for response from fd 14
jun 02 19:37:41 Inez-HP-EliteBook-8460p update-notifier.desktop[5391]: WARNING:root:timeout reached, exiting

$ cat /etc/fstab
cat /etc/crypttab

/etc/fstab: static file system information.

Use 'blkid' to print the universally unique identifier for a

device; this may be used with UUID= as a more robust way to name devices

that works even if disks are added and removed. See fstab(5).

/ was on /dev/sda6 during installation

UUID=6d267e20-d203-49ec-8546-3b6e3368c6cc / ext4 errors=remount-ro 0 1

/boot/efi was on /dev/sda1 during installation

UUID=B5B8-AD78 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
UUID=3df9dfde-b902-4230-95c7-79dc017d7e87 none swap sw 0 0

now this please

sudo blkid | grep -iE "B5B8-AD78|vfat"
lsblk -f

sudo blkid | grep -iE "B5B8-AD78|vfat"
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /snap/bare/5
loop1 squashfs 4.0 0 100% /snap/core20/2866
loop2 squashfs 4.0 0 100% /snap/core18/2999
loop3 squashfs 4.0 0 100% /snap/core24/1643
loop4 squashfs 4.0 0 100% /snap/gnome-3-28-1804/198
loop5 squashfs 4.0 0 100% /snap/gnome-46-2404/153
loop6 squashfs 4.0 0 100% /snap/gtk-common-themes/1535
loop7 squashfs 4.0 0 100% /snap/mesa-2404/1165
loop8 squashfs 4.0 0 100% /snap/snapd/26865
loop9 squashfs 4.0 0 100% /snap/terminal-fun/6
loop10 squashfs 4.0 0 100% /snap/whatsapp-desktop-linux/1
sda
├─sda1 ntfs 1456E08356E06748
├─sda2 ntfs 01DCCE863BEF24A0
├─sda3 ntfs 5CD289D8D289B6B4
└─sda4 ntfs 01DCCDE7512CEB30
sdb
├─sdb1
├─sdb5 ext4 1.0 6d267e20-d203-49ec-8546-3b6e3368c6cc 134,4G 34% /
└─sdb6 swap 1 3df9dfde-b902-4230-95c7-79dc017d7e87 [SWAP]
sdc
└─sdc1 crypto_LUKS 1 d53918e5-bc8f-4b61-9c00-2a1467ed55dc

Do that

sudo sed -i 's|^UUID=B5B8-AD78|#&|' /etc/fstab
sudo systemctl daemon-reload
sudo reboot
2 Likes

Bingo!
That did it.
24 seconds.
Just about 70% quicker. I reckon.
Safe.

Thank you for taking time out of your day to assist me.
To you both.
Cheers

1 Like