Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[Solved] Significant boot time due to presumed multiple issues

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
JianZen
Posts: 3
Joined: 2022-11-25 16:50

[Solved] Significant boot time due to presumed multiple issues

#1 Post by JianZen »

About a week ago my Debian installation has increased from about a ~10s boot to >2 minutes. Have attempted the normal diagnoses to see issues but I'm a bit lost. I think there are potentially multiple parts to it but my searching hasn't yielded many positive results.

Code: Select all

        _,met$$$$$gg.           tommy@Dragon-r7
      ,g$$$$$$$$$$$$$$$P.        OS: Debian 11 bullseye
    ,g$$P""       """Y$$.".      Kernel: x86_64 Linux 5.19.0-0.deb11.2-amd64
   ,$$P'              `$$$.      Uptime: 12m
  ',$$P       ,ggs.     `$$b:    Packages: 2208
  `d$$'     ,$P"'   .    $$$     Shell: bash 5.1.4
   $$P      d$'     ,    $$P     Resolution: 4480x1440
   $$:      $$.   -    ,d$$'     DE: Cinnamon 4.8.6
   $$\;      Y$b._   _,d$P'      WM: Muffin
   Y$$.    `.`"Y$$$$P"'          WM Theme: Blue-Submarine (BlackMATE)
   `$$b      "-.__               GTK Theme: Blue-Submarine [GTK2/3]
    `Y$$                         Icon Theme: mate
     `Y$$.                       Font: Sans 9
       `$$b.                     Disk: 436G / 786G (59%)
         `Y$$b.                  CPU: AMD Ryzen 7 5800H with Radeon Graphics @ 16x 3.2GHz
            `"Y$b._              GPU: NVIDIA GeForce RTX 3060 Laptop GPU
                `""""            RAM: 4532MiB / 15856MiB
systemd-analyze

Code: Select all

Startup finished in 5.944s (firmware) + 2.873s (loader) + 32.991s (kernel) + 1min 31.525s (userspace) = 2min 13.334s 
graphical.target reached after 1min 31.520s in userspace
systemd-analyze blame

Code: Select all

21.398s upower.service
 2.830s fwupd.service
 1.316s nvidia-persistenced.service
  311ms systemd-modules-load.service
  206ms dev-nvme0n1p4.device
  159ms systemd-udev-trigger.service
  147ms lm-sensors.service
  136ms systemd-logind.service
  134ms udisks2.service
  116ms apparmor.service
  102ms lightdm.service
  101ms plymouth-quit-wait.service
   75ms systemd-rfkill.service
   74ms accounts-daemon.service
   58ms user@1000.service
   56ms polkit.service
   56ms avahi-daemon.service
   54ms bluetooth.service
   53ms NetworkManager.service
   50ms systemd-timesyncd.service
   50ms boot-efi.mount
   48ms systemd-udevd.service
   47ms wpa_supplicant.service
   47ms systemd-journald.service
   45ms systemd-journal-flush.service
   41ms systemd-tmpfiles-setup.service
   41ms keyboard-setup.service
   38ms systemd-fsck@dev-disk-by\x2duuid-5FD5\x2d9BD4.service
   38ms ModemManager.service
   35ms console-setup.service
   35ms plymouth-read-write.service
   33ms rsyslog.service
   27ms e2scrub_reap.service
   25ms systemd-backlight@backlight:acpi_video0.service
   23ms networking.service
   21ms cups.service
   20ms packagekit.service
   20ms ssh.service
   19ms systemd-fsck@dev-disk-by\x2duuid-375f4eac\x2dda6d\x2d4d87\x2da17a\x2daed548fe7961.service
   16ms plymouth-start.service
   12ms systemd-fsck@dev-disk-by\x2duuid-6bee998f\x2db10b\x2d4d1e\x2d951a\x2da86b6d1b8b59.service
   11ms hddtemp.service
   10ms alsa-restore.service
   10ms colord.service
    8ms systemd-sysctl.service
    7ms modprobe@fuse.service
    7ms systemd-tmpfiles-setup-dev.service
    7ms systemd-sysusers.service
    6ms dev-hugepages.mount
    6ms dev-mqueue.mount
    6ms SLibrary.mount
    6ms sys-kernel-debug.mount
    6ms systemd-update-utmp.service
    5ms sys-kernel-tracing.mount
    5ms systemd-random-seed.service
    5ms kmod-static-nodes.service
    4ms modprobe@configfs.service
    4ms systemd-remount-fs.service
    3ms user-runtime-dir@1000.service
    3ms systemd-update-utmp-runlevel.service
    3ms ifupdown-pre.service
    3ms systemd-user-sessions.service
    3ms home.mount
    2ms rtkit-daemon.service
    1ms sys-fs-fuse-connections.mount
    1ms modprobe@drm.service
  957us sys-kernel-config.mount
Video of my boot up after selecting Debian in grub:
https://drive.google.com/file/d/1583T0m ... p=sharing

Many thanks for any help!
Last edited by JianZen on 2022-11-28 14:18, edited 1 time in total.

User avatar
sunrat
Administrator
Administrator
Posts: 6382
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 115 times
Been thanked: 456 times

Re: [Software] Significant boot time due to presumed multiple issues

#2 Post by sunrat »

It's almost impossible to make out anything on that video. dmesg, logs in /var/log/ or journalctl would be better.
Try

Code: Select all

journalctl -b -p3
"-b" will show current boot, "-b -1" will show previous boot. Use "-p4" instead of "-p3" to show warnings as well as errors.

From the blurry video, I can see "Start job is running..." and guess it is attempting to mount a device which is not available. Check the UUID against any entries in /etc/fstab.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

JianZen
Posts: 3
Joined: 2022-11-25 16:50

Re: [Software] Significant boot time due to presumed multiple issues

#3 Post by JianZen »

Apologies for posting the poor quality video.
journalctl -b -p3

Code: Select all

-- Journal begins at Thu 2022-11-03 15:59:38 GMT, ends at Sat 2022-11-26 12:55:48 GMT. --
Nov 26 12:52:27 Dragon-r7 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20220331/dswload2-162)
Nov 26 12:52:27 Dragon-r7 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
Nov 26 12:52:27 Dragon-r7 kernel: integrity: Problem loading X.509 certificate -65
Nov 26 12:52:27 Dragon-r7 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20220331/psargs-3>
Nov 26 12:52:27 Dragon-r7 kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Nov 26 12:52:27 Dragon-r7 kernel: hid (null): invalid report_size 2056
Nov 26 12:52:27 Dragon-r7 kernel: hid-generic 0003:05AC:0500.0002: invalid report_size 2056
Nov 26 12:52:27 Dragon-r7 kernel: hid-generic 0003:05AC:0500.0002: item 0 4 1 7 parsing failed
Nov 26 12:52:27 Dragon-r7 kernel: hid (null): invalid report_size 32768
Nov 26 12:52:27 Dragon-r7 kernel: hid-generic 0003:05AC:0500.0003: invalid report_size 32768
Nov 26 12:52:27 Dragon-r7 kernel: hid-generic 0003:05AC:0500.0003: item 0 4 1 7 parsing failed
Nov 26 12:52:27 Dragon-r7 kernel: hid (null): invalid report_size 2056
Nov 26 12:52:27 Dragon-r7 kernel: hid-generic 0003:05AC:0500.0004: invalid report_size 2056
Nov 26 12:52:27 Dragon-r7 kernel: hid-generic 0003:05AC:0500.0004: item 0 4 1 7 parsing failed
Nov 26 12:52:27 Dragon-r7 kernel: 
Nov 26 12:52:39 Dragon-r7 kernel: Bluetooth: hci0: Execution of wmt command timed out
Nov 26 12:52:39 Dragon-r7 kernel: Bluetooth: hci0: Failed to send wmt patch dwnld (-110)
Nov 26 12:52:39 Dragon-r7 kernel: Bluetooth: hci0: Failed to set up firmware (-110)
Nov 26 12:53:57 Dragon-r7 systemd[1]: Timed out waiting for device /dev/disk/by-uuid/ccef30d0-1d24-491d-950a-cfbaf5fefe7f.
Nov 26 12:54:02 Dragon-r7 pipewire[1134]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.fre>
Nov 26 12:54:12 Dragon-r7 lightdm[1184]: gkr-pam: unable to locate daemon control file
Nov 26 12:54:12 Dragon-r7 pulseaudio[1135]: Error opening PCM device hdmi:0: No such file or directory
Nov 26 12:54:12 Dragon-r7 pulseaudio[1135]: Error opening PCM device front:1: No such file or directory
Nov 26 12:54:12 Dragon-r7 pulseaudio[1135]: Error opening PCM device front:1: No such file or directory
Nov 26 12:54:12 Dragon-r7 pipewire[1205]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.fre>
Nov 26 12:54:14 Dragon-r7 wpa_supplicant[959]: bgscan simple: Failed to enable signal strength monitoring
Nov 26 12:54:50 Dragon-r7 wpa_supplicant[959]: nl80211: kernel reports: key not allowed
Nov 26 12:54:51 Dragon-r7 wpa_supplicant[959]: bgscan simple: Failed to enable signal strength monitoring
Nov 26 12:54:59 Dragon-r7 kernel: hid (null): invalid report_size 2056
Nov 26 12:54:59 Dragon-r7 kernel: hid-generic 0003:05AC:0500.000A: invalid report_size 2056
Nov 26 12:54:59 Dragon-r7 kernel: hid-generic 0003:05AC:0500.000A: item 0 4 1 7 parsing failed
Nov 26 12:54:59 Dragon-r7 kernel: hid (null): invalid report_size 32768
Nov 26 12:54:59 Dragon-r7 kernel: hid-generic 0003:05AC:0500.000B: invalid report_size 32768
Nov 26 12:54:59 Dragon-r7 kernel: hid-generic 0003:05AC:0500.000B: item 0 4 1 7 parsing failed
Nov 26 12:54:59 Dragon-r7 kernel: hid (null): invalid report_size 2056
Nov 26 12:54:59 Dragon-r7 kernel: hid-generic 0003:05AC:0500.000C: invalid report_size 2056
Nov 26 12:54:59 Dragon-r7 kernel: hid-generic 0003:05AC:0500.000C: item 0 4 1 7 parsing failed
I had a look at /etc/fstab for the drive in question that was hanging on its start job and it's by Swap partition - I've tried to turn it both on and off and the results are the same. Should I delete it / reformat it?

p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: [Software] Significant boot time due to presumed multiple issues

#4 Post by p.H »

Update the swap UUID in /etc/fstab and /etc/initramfs-tools/conf.d/resume to match the UUID given by blkid.
Run

Code: Select all

update-initramfs -u

JianZen
Posts: 3
Joined: 2022-11-25 16:50

Re: [Software] Significant boot time due to presumed multiple issues

#5 Post by JianZen »

Updating the UUID in both /etc/fstab and /etc/initramfs-tools/conf.d/resume and running update-initramfs -u did fix it, thank you so much!

p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: [Software] Significant boot time due to presumed multiple issues

#6 Post by p.H »

Thanks for the feedback. Can you please edit the original post subject and mark the topic solved ?

Post Reply