Tea Glorious Tea!
My laptop is taking a LONG time (~10 minutes) to boot. Here are two line from syslog during boot showing an 8 minute gap between them:
This is on an Ubuntu 20.04 LTS laptop.Code:Sep 19 12:38:44 Relic systemd[1]: Starting Daemon for power management... Sep 19 12:46:53 Relic systemd-timesyncd[584]: Initial synchronization to time ser
It has to be Xubuntu.
Please run command systemd-analyze blame and show us the output.
Please use Code-Tags for terminal output. See my signature below for a How-to
Code-tags --- Boot-Repair --- Grub2 wiki & Grub2 Basics --- RootSudo --- Wireless-Info --- SolvedThreads --- System-Info-Script
A Carafe of Ubuntu
Also this please:
Code:timedatectl status
And this:
Code:journalctl --unit=systemd-timesyncd.service
Last edited by 1fallen2; 2 Weeks Ago at 07:21 PM.
"When you practice gratefulness, there is a sense of respect toward others." >>Dalai Lama
Super Master Roaster
Also:
What brand/model system?
What video card/chip?
Have you updated UEFI firmware to latest available.
And if SSD, its firmware to latest available.
UEFI boot install & repair info - Regularly Updated :
https://ubuntuforums.org/showthread.php?t=2147295
Please use Thread Tools above first post to change to [Solved] when/if answered completely.
Tea Glorious Tea!
$ systemd-analyze blame
I didn't get any emails (odd) so I thought there were no responses.Code:1min 12.586s sendmail.service 56.409s mysql.service 38.887s dev-loop12.device 32.116s snapd.seeded.service 29.955s udisks2.service 28.331s snapd.service 22.163s networkd-dispatcher.service 18.118s dev-sda6.device 16.449s systemd-journal-flush.service 14.441s accounts-daemon.service 14.155s ModemManager.service 13.895s apache2.service 12.438s NetworkManager-wait-online.service 9.315s polkit.service 8.755s NetworkManager.service 8.733s avahi-daemon.service 8.137s dev-loop10.device 8.061s dev-loop7.device 8.024s switcheroo-control.service 7.995s dev-loop5.device 7.947s thermald.service 7.938s systemd-logind.service 7.938s wpa_supplicant.service 7.847s dev-loop9.device 7.688s dev-loop8.device 7.627s dev-loop0.device 7.414s dev-loop4.device 7.286s dev-loop3.device 7.180s dev-loop11.device 6.462s dev-loop6.device 6.384s dev-loop1.device 4.207s dev-loop2.device 3.956s fwupd.service 3.911s apparmor.service 3.726s gpu-manager.service 3.701s rsyslog.service 3.557s lightdm.service 3.545s plymouth-quit-wait.service 3.462s colord.service 3.271s ssh.service 3.086s apport.service 2.955s autofs.service 2.807s e2scrub_reap.service 2.614s systemd-udevd.service 2.399s systemd-tmpfiles-clean.service 1.856s nfs-server.service 1.761s systemd-resolved.service 1.636s grub-common.service 1.529s phpsessionclean.service 1.175s upower.service 1.172s snapd.apparmor.service 1.042s networking.service 1.022s mythtv-backend.service 1.022s nfs-mountd.service 956ms systemd-tmpfiles-setup.service 943ms systemd-modules-load.service 935ms grub-initrd-fallback.service 843ms rpcbind.service 708ms systemd-tmpfiles-setup-dev.service 708ms systemd-rfkill.service 699ms snap-bare-5.mount 695ms systemd-random-seed.service 674ms proc-fs-nfsd.mount 638ms snap-core18-1705.mount 611ms snap-core18-2829.mount 605ms systemd-sysctl.service 587ms systemd-sysusers.service 579ms home.mount 561ms systemd-journald.service 556ms swapfile.swap 538ms keyboard-setup.service 530ms dns-clean.service 519ms snap-core22-1612.mount 515ms lm-sensors.service 493ms host.mount 474ms systemd-udev-trigger.service 447ms snap-gnome\x2d3\x2d34\x2d1804-24.mount 434ms rpc-statd.service 410ms snap-gnome\x2d3\x2d34\x2d1804-93.mount 398ms nfs-idmapd.service 375ms user@1000.service 333ms snap-gnome\x2d42\x2d2204-176.mount 324ms ifupdown-pre.service 320ms systemd-timesyncd.service 318ms boot-efi.mount 286ms openvpn.service 272ms systemd-remount-fs.service 269ms snap-gtk\x2dcommon\x2dthemes-1506.mount 266ms systemd-backlight@backlight:acpi_video0.service 254ms alsa-restore.service 253ms plymouth-start.service 251ms snap-gtk\x2dcommon\x2dthemes-1535.mount 250ms modprobe@efi_pstore.service 243ms dev-hugepages.mount 241ms dev-mqueue.mount 237ms run-rpc_pipefs.mount 235ms modprobe@drm.service 234ms sys-kernel-debug.mount 232ms sys-kernel-tracing.mount 230ms hddtemp.service 229ms rpc-statd-notify.service 193ms kmod-static-nodes.service 190ms snap-snap\x2dstore-1216.mount 187ms rtkit-daemon.service 177ms modprobe@pstore_blk.service 175ms modprobe@pstore_zone.service 173ms modprobe@ramoops.service 168ms snap-snapd-21759.mount 164ms pppd-dns.service 164ms setvtrgb.service 154ms kerneloops.service 148ms snap-snap\x2dstore-433.mount 144ms console-setup.service 139ms ufw.service 130ms systemd-fsck@dev-disk-by\x2duuid-35D4\x2d3631.service 117ms nfs-blkmap.service 105ms proc-sys-fs-binfmt_misc.mount 105ms systemd-update-utmp.service 98ms plymouth-read-write.service 83ms systemd-user-sessions.service 66ms modprobe@chromeos_pstore.service 30ms user-runtime-dir@1000.service 22ms systemd-update-utmp-runlevel.service 14ms sys-fs-fuse-connections.mount 9ms sys-kernel-config.mount 5ms nfs-config.service 3ms snapd.socket
Here's the syslog gap from today:
Code:Sep 24 06:08:39 Relic snapd[769]: backends.go:58: AppArmor status: apparmor is enabled and all features are available Sep 24 06:15:02 Relic systemd-timesyncd[653]: Initial synchronization to time server 185.125.190.58:123 (ntp.ubuntu.com).
Staff Emeritus
I'm surprised by how many services are running.
If I run the same command on a standard Ubuntu 22.04 laptop, I don't get even half the amount of services you are showing.
Could you please show us also the output for these commands:
Code:systemd-analyze critical-chainCode:lsblk -e 7 -o name,size,type,fstype,mountpoint
Tea Glorious Tea!
Code:root@Relic:~# timedatectl status Local time: Tue 2024-09-24 10:45:44 EDT Universal time: Tue 2024-09-24 14:45:44 UTC RTC time: Tue 2024-09-24 14:45:44 Time zone: America/New_York (EDT, -0400) System clock synchronized: yes NTP service: active RTC in local TZ: noCode:root@Relic:~# 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 @2min 1.037s └─multi-user.target @2min 1.037s └─sendmail.service @48.449s +1min 12.586s └─network-online.target @48.047s └─NetworkManager-wait-online.service @35.608s +12.438s └─NetworkManager.service @26.848s +8.755s └─dbus.service @26.842s └─basic.target @26.727s └─sockets.target @26.727s └─snapd.socket @26.722s +3ms └─sysinit.target @26.539s └─snapd.apparmor.service @25.366s +1.172s └─apparmor.service @21.447s +3.911s └─local-fs.target @21.443s └─run-user-1000-doc.mount @1min 55.755s └─run-user-1000.mount @1min 45.337s └─local-fs-pre.target @3.320s └─systemd-tmpfiles-setup-dev.service @2.611s +7> └─systemd-sysusers.service @2.021s +587ms └─systemd-remount-fs.service @1.679s +272ms └─systemd-journald.socket @1.442s └─-.mount @1.427s └─system.slice @1.427s └─-.slice @1.427s lCode:root@Relic:~# lsblk -e 7 -o name,size,type,fstype,mountpoint NAME SIZE TYPE FSTYPE MOUNTPOINT sda 298.1G disk ├─sda1 199M part ntfs ├─sda2 267.2G part ntfs /host ├─sda3 14G part ext4 ├─sda4 1K part ├─sda5 512M part vfat /boot/efi └─sda6 16.2G part ext4 / sr0 1024M rom
Tea Glorious Tea!
Code:root@Relic:~# journalctl --unit=systemd-timesyncd.service^C root@Relic:~# timedatectl status Local time: Tue 2024-09-24 11:13:05 EDT Universal time: Tue 2024-09-24 15:13:05 UTC RTC time: Tue 2024-09-24 15:13:05 Time zone: America/New_York (EDT, -0400) System clock synchronized: yes NTP service: active RTC in local TZ: noCode:root@Relic:~# journalctl --unit=systemd-timesyncd.service -- Reboot -- Sep 23 05:54:55 Relic systemd[1]: Starting Network Time Synchronization... Sep 23 05:54:55 Relic systemd[1]: Started Network Time Synchronization. Sep 23 06:00:22 Relic systemd-timesyncd[603]: Initial synchronization to time s> Sep 23 07:19:53 Relic systemd-timesyncd[603]: Initial synchronization to time s> Sep 23 10:44:24 Relic systemd-timesyncd[603]: Initial synchronization to time s> Sep 23 18:49:55 Relic systemd[1]: Stopping Network Time Synchronization... Sep 23 18:49:56 Relic systemd[1]: systemd-timesyncd.service: Succeeded. Sep 23 18:49:56 Relic systemd[1]: Stopped Network Time Synchronization. -- Reboot -- Sep 24 06:08:09 Relic systemd[1]: Starting Network Time Synchronization... Sep 24 06:08:09 Relic systemd[1]: Started Network Time Synchronization. Sep 24 06:15:02 Relic systemd-timesyncd[653]: Initial synchronization to time s>
Last edited by bilkay; 2 Weeks Ago at 04:20 PM.
Tea Glorious Tea!
HP G62Originally Posted by oldfred
I have no idea.
I don't know how do do that.
Super Master Roaster
If you can boot or boot live installer.
Some hardware info:
inxi -bz
Compare to vendors support site and info on how to update your system, varies by vendor.
sudo dmidecode -s bios-version
udisksctl status
UEFI boot install & repair info - Regularly Updated :
https://ubuntuforums.org/showthread.php?t=2147295
Please use Thread Tools above first post to change to [Solved] when/if answered completely.
Adv Reply
Bookmarks