Monday, May 6, 2024
 Popular · Latest · Hot · Upcoming
1
rated 0 times [  1] [ 0]  / answers: 1 / hits: 840  / 2 Years ago, tue, september 27, 2022, 12:22:30

I have Ubuntu 20.04 (triple boot w Windows 10/kali 2020.4) on a Lenovo machine.
Here is my Hardware Information:



  • RAM - 8GB

  • Disk Type - SSD

  • Disk Space - 50 GB

  • Architecture - amd64

  • Processor - Intel(core i7) 10th generation


My windows boots up in 4-5 seconds while ubuntu has been taking 8-10 mins for a month or so, I don't know how to debug.


I ran dmesg and got the following log



  1. snippet 1:


[    2.556631] audit: type=1400 audit(1616666280.585:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=651 comm="apparmor_parser"
[ 92.015617] kauditd_printk_skb: 37 callbacks suppressed


  1. snippet 2:


[  127.766206] audit: type=1400 audit(1616646605.387:69): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.snap-store.snap-store" pid=3756 comm="apparmor_parser"
[ 473.393428] kauditd_printk_skb: 19 callbacks suppressed

What is the meaning of



kauditd_printk_skb: 37 callbacks suppressed



systemd-analyse output:


Startup finished in 2.426s (firmware) + 7.991s (loader) + 1.468s (kernel) + 1min 51.594s (userspace) = 2min 3.480s 
graphical.target reached after 1min 51.577s in userspace

systemd-analyze blame output :


21.031s plymouth-quit-wait.service                                                               
4.388s NetworkManager-wait-online.service
3.804s fwupd.service
1.730s snapd.service
1.488s fstrim.service
693ms snap-snapd-11107.mount
683ms snap-code-58.mount
619ms snap-core18-1944.mount
586ms snap-gtkx2dcommonx2dthemes-1514.mount
423ms snap-core18-1988.mount
403ms snap-code-59.mount
363ms dev-nvme0n1p7.device
347ms systemd-logind.service
334ms snap-core-10859.mount
283ms dev-loop0.device
239ms snap-gtkx2dcommonx2dthemes-1506.mount
237ms snap-snapx2dstore-498.mount
213ms snap-canonicalx2dlivepatch-95.mount
213ms dev-loop2.device
204ms snap-gnomex2d3x2d34x2d1804-60.mount
203ms snap-gnomex2d3x2d34x2d1804-66.mount
200ms snap-snapx2dstore-518.mount
193ms tuned.service
192ms dev-loop3.device
181ms dev-loop8.device
175ms systemd-resolved.service
165ms dev-loop4.device
165ms networkd-dispatcher.service
151ms systemd-timesyncd.service
148ms udisks2.service
138ms dev-loop11.device
127ms dev-loop5.device
120ms systemd-rfkill.service
117ms accounts-daemon.service
111ms systemd-fsck@dev-disk-byx2duuid-05cdca1fx2d6222x2d4ec0x2d8675x2d862db39f842a.service
104ms upower.service
101ms apparmor.service
96ms [email protected]
88ms dev-loop9.device
88ms dev-loop7.device
87ms dev-loop12.device
79ms systemd-journal-flush.service
77ms dev-loop13.device
72ms dev-loop6.device
69ms systemd-journald.service
66ms polkit.service
66ms bluetooth.service
65ms systemd-udev-trigger.service
65ms avahi-daemon.service
61ms NetworkManager.service
60ms switcheroo-control.service
58ms systemd-udevd.service
52ms snap-core-10908.mount
51ms keyboard-setup.service

systemd-analyze critical-chain output :


graphical.target @1min 51.577s
└─multi-user.target @1min 51.577s
└─snapd.seeded.service @1min 35.340s +21ms
└─basic.target @1min 30.453s
└─sockets.target @1min 30.452s
└─snapd.socket @1min 30.451s +651us
└─sysinit.target @1min 30.439s
└─systemd-timesyncd.service @1.091s +151ms
└─systemd-tmpfiles-setup.service @1.067s +21ms
└─local-fs.target @1.063s
└─run-snapd-ns-snapx2dstore.mnt.mount @1min 35.053s
└─run-snapd-ns.mount @1min 34.150s
└─local-fs-pre.target @351ms
└─keyboard-setup.service @300ms +51ms
└─systemd-journald.socket @296ms
└─system.slice @294ms
└─-.slice @294ms

cat /etc/fstab output:


# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p7 during installation
UUID=e1e7a401-980c-44c4-9567-cf04951b42a2 / ext4 errors=remount-ro 0 1
# /boot was on /dev/nvme0n1p8 during installation
UUID=05cdca1f-6222-4ec0-8675-862db39f842a /boot ext4 defaults 0 2
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=C0A5-904E /boot/efi vfat umask=0077 0 1
# swap was on /dev/nvme0n1p9 during installation
UUID=56534486-e9b5-4a7b-b03d-71f87ad9d8df none swap sw 0 0

I'm quite new, how can I fix this boot delay?


More From » boot

 Answers
1

Turns out somehow the UUID of my swap partition which is /dev/nvme0n1p9 here, got changed. I installed gparted to check the UUID of my swap partition (/dev/nvme0n1p9), changed it in the /etc/fstab and now the booting process works fine and takes about 5-6 seconds.
Check this Slow boot - "a start job is running for dev-disk-by..." solution for more info in this.


[#1785] Thursday, September 29, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
bblerest

Total Points: 240
Total Questions: 119
Total Answers: 113

Location: Wallis and Futuna
Member since Mon, May 18, 2020
4 Years ago
bblerest questions
Sun, Apr 16, 23, 13:50, 1 Year ago
Fri, Nov 4, 22, 06:21, 2 Years ago
Tue, Dec 14, 21, 09:20, 2 Years ago
;