[Roy]

Hello

I've installed a couple of week ago a fresh LL4 OS on my SSD
Everything was find and boots and startup was super fast
But now the system's load very slow.. it takes for it something like 02:20 minutes from pressing enter in GRUB until the first desktop sight
I tried running systemd-analyze blame as suggested on old post here to see what takes so long.. but the output wasn't satisfying

Code:

        11.905s vboxadd.service         11.693s plymouth-quit-wait.service           3.188s NetworkManager-wait-online.service           1.612s ufw.service           579ms motd-news.service           367ms systemd-timesyncd.service           356ms systemd-logind.service           348ms systemd-resolved.service           275ms udisks2.service           273ms NetworkManager.service           270ms dev-sdb2.device           228ms upower.service           178ms networkd-dispatcher.service           127ms systemd-journal-flush.service           122ms [email protected]           115ms apparmor.service           111ms lightdm.service           111ms grub-common.service           103ms ModemManager.service           102ms systemd-fsck@dev-disk-by\x2duuid-df866604\x2d929e\x2d4590\x2d897b\x2d697584521899.s             97ms systemd-udev-trigger.service             96ms nmbd.service             85ms smbd.service             85ms apport.service             77ms avahi-daemon.service             76ms accounts-daemon.service             75ms home.mount             72ms zram-config.service             71ms lm-sensors.service             69ms systemd-journald.service             68ms keyboard-setup.service             67ms thermald.service             66ms console-kit-log-system-start.service             62ms pppd-dns.service             61ms ubiquity.service             57ms rsyslog.service             56ms teamviewerd.service             47ms lvm2-monitor.service             41ms snap-core-4917.mount             40ms wpa_supplicant.service             37ms polkit.service             35ms gpu-manager.service             32ms alsa-restore.service             30ms systemd-udevd.service             29ms dev-zram3.device             26ms networking.service             24ms dev-zram1.device             22ms dev-zram2.device             22ms systemd-modules-load.service             22ms systemd-tmpfiles-setup.service             21ms dev-zram0.device             20ms dev-zram4.device             18ms systemd-tmpfiles-setup-dev.service             18ms dev-loop0.device             18ms binfmt-support.service             17ms plymouth-start.service             17ms dev-zram5.device             16ms plymouth-read-write.service             15ms dev-zram6.device             12ms resolvconf.service             11ms proc-sys-fs-binfmt_misc.mount             11ms hddtemp.service             10ms dev-zram7.device             9ms dev-hugepages.mount             8ms resolvconf-pull-resolved.service             7ms systemd-sysctl.service             7ms systemd-remount-fs.service             6ms ureadahead-stop.service             6ms dns-clean.service             6ms kmod-static-nodes.service             5ms blk-availability.service             4ms systemd-update-utmp.service             4ms systemd-random-seed.service             4ms rtkit-daemon.service             3ms systemd-user-sessions.service             3ms systemd-update-utmp-runlevel.service             3ms dev-mqueue.mount             3ms sys-fs-fuse-connections.mount             2ms console-setup.service             2ms sys-kernel-debug.mount             2ms sys-kernel-config.mount             1ms nvidia-persistenced.service             1ms setvtrgb.service             1ms openvpn.service

Also.. what is that vboxadd.service? I remember deleting virtual box as I don't really need it right now
I also tried to reformat my swap partition as it was suggested in some post
I did move my home partition to another hard drive
Can someone help? the internet isn't helpful that much this time...  :-\

[trinidad]

Read the release notes here:

https://mityer.khdlhfjijfrupr.tk/forums/relea...-released/

Use the code to properly deal with vbox additions.

Code: sudo apt purge virtualbox*
sudo systemctl stop vboxadd.service
sudo systemctl stop vboxadd-service.service
sudo systemctl disable vboxadd.service
sudo systemctl disable vboxadd-service.service


TC

[tomg54]

Hello.  Same problem here.  The removal of vb via Jerry's post helped, but still over a minute to boot.  I just tried installing kernel 4.4.0. out of curiosity.  Now boot time is about 20 seconds, as it was with lite 3.8. 

[Roy]

Well the code to properly deal with the vbox additions only cut down 9 seconds I think I'll try different kernel versions..
I have currently installed 4.15.0
I can try 16 or 17 or downgrade.. what do you recommend?

[Roy]

I am currently on 4.17.0 after trying 4.16.0 and 4.4.0
Boot time still the same.. or even longer with 4.4.0

I have noticed something suspicious
There's a timeout waiting for two devices and after that I saw a "job" that takes 1:30 minutes and I really don't know what it is




The output of systemctl status apparmor.service is:

Code:

apparmor.service - AppArmor initialization   Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled)   Active: failed (Result: exit-code) since Sun 2018-07-08 23:22:32 IDT; 11min ago     Docs: man:apparmor(7)           http://wiki.apparmor.net/   Process: 785 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 785 (code=exited, status=123) Jul 08 23:22:30 roy-linuxlite4 apparmor[785]: AppArmor parser error for /etc/apparmor.d/usr.lib.snap Jul 08 23:22:30 roy-linuxlite4 apparmor[785]: Skipping profile in /etc/apparmor.d/disable: usr.sbin. Jul 08 23:22:32 roy-linuxlite4 apparmor[785]: AppArmor parser error for /etc/apparmor.d/snap.core.49 Jul 08 23:22:32 roy-linuxlite4 apparmor[785]: Skipping profile in /etc/apparmor.d/disable: usr.bin.f Jul 08 23:22:32 roy-linuxlite4 apparmor[785]: AppArmor parser error for /etc/apparmor.d/usr.lib.snap Jul 08 23:22:32 roy-linuxlite4 apparmor[785]: Skipping profile in /etc/apparmor.d/disable: usr.sbin. Jul 08 23:22:32 roy-linuxlite4 apparmor[785]:    ...fail! Jul 08 23:22:32 roy-linuxlite4 systemd[1]: apparmor.service: Main process exited, code=exited, statu Jul 08 23:22:32 roy-linuxlite4 systemd[1]: apparmor.service: Failed with result 'exit-code'. Jul 08 23:22:32 roy-linuxlite4 systemd[1]: Failed to start AppArmor initialization.

Which I don't really understand........

I have two devices to power up my Linux system which is SSD (/dev/sdb) and HDD
SSD consist of two partitions one for SWAP in the beginning of the drive weights ~30GB and the rest 200GB is for root
The other HDD splitted in half consist of HOME partition (/dev/sdd1) and another ext4 non-relevant old home partition (/dev/sdd2) that will be gone soon...

I think the "job" is cycling between SWAP and ROOT partition doing something to them or just checking them..
And what is that "apparmor" thing fail to parse things? a bug maybe?

I am still new to the linux system so help will be much appreciated

[Roy]

Alright I fixed that "start job" annoying issue
Because there was already an old system before I switched to LL4 (the time I was dual boot with LL3.8 and Win10) and then deleting the old one after everything was okay in LL4 the /etc/fstab file was corrupted
I have noticed my swap partition wasn't on on every boot so I dug again but this time I searched for "start job waiting for device.." and ended up reading this answer edit the file makes it point to the right devices (it still pointed to old swap) save and reboot
Now boot time is ~40 seconds! At F-ing Last..!

Maybe someone should write a tutorial how to properly remove old system from a dual boot  :

Thank you all for supporting me I still need to fix apparmor issue.. or at least wait for a fix
Thanks again

[trinidad]

What is the result for: ls /etc/apparmor.d/

TC

[Roy]

The content of it is:

Code:

total 152 3408572 drwxr-xr-x 4 root root  4096 Apr 21 08:14 abstractions 3408573 drwxr-xr-x 2 root root  4096 Jul  8 23:22 cache 3408574 drwxr-xr-x 2 root root  4096 Apr 30  2016 disable 3408575 drwxr-xr-x 2 root root  4096 Apr  5  2016 force-complain 3408578 -rw-r--r-- 1 root root  802 Feb 13 05:33 lightdm-guest-session 3408576 drwxr-xr-x 2 root root  4096 Jul  5 19:07 local 3408579 -rw-r--r-- 1 root root  3194 Mar 27 00:00 sbin.dhclient 3417547 -rw-r--r-- 1 root root 21845 Jul  5 19:09 snap.core.4917.usr.lib.snapd.snap-confine 3408577 drwxr-xr-x 5 root root  4096 Apr 21 08:14 tunables 3408580 -rw-r--r-- 1 root root  5995 Mar  8  2016 usr.bin.evince 3408581 -rw-r--r-- 1 root root  8467 Nov 30  2017 usr.bin.firefox 3408582 -rw-r--r-- 1 root root  2857 Apr  7 14:14 usr.bin.man 3408583 -rw-r--r-- 1 root root  1519 Mar  5 15:25 usr.lib.libreoffice.program.oosplash 3408584 -rw-r--r-- 1 root root  1330 Mar  5 15:25 usr.lib.libreoffice.program.senddoc 3408585 -rw-r--r-- 1 root root  6618 Mar  5 15:25 usr.lib.libreoffice.program.soffice.bin 3408586 -rw-r--r-- 1 root root  1284 Mar  5 15:25 usr.lib.libreoffice.program.xpdfimport 3409595 -rw-r--r-- 1 root root 21143 May 16 11:20 usr.lib.snapd.snap-confine.real 3408587 -rw-r--r-- 1 root root  540 Feb 26 09:52 usr.sbin.cups-browsed 3408588 -rw-r--r-- 1 root root  5518 Feb 10 12:14 usr.sbin.cupsd 3408589 -rw-r--r-- 1 root root  643 Jan 17 02:39 usr.sbin.ippusbxd 3408590 -rw-r--r-- 1 root root  2425 Feb 14 10:23 usr.sbin.ntpd 3408591 -rw-r--r-- 1 root root  1550 Apr 24 16:15 usr.sbin.rsyslogd 3408592 -rw-r--r-- 1 root root  1353 Mar 26 23:28 usr.sbin.tcpdump

[trinidad]

Run your system on the kernel it came with, and only go forward with repairs for your problem on that kernel. Second problem shouldn't even be there in LL 4.0 so I'm assuming you changed kernels at some point, maybe back and forth.   

first problem
https://bugs.launchpad.net/snapd/+bug/1739485

second problem
https://bugs.launchpad.net/ubuntu/+sourc...ug/1734038

TC 

[tomg54]

I did not change the kernel.  Installed on ssd 3x.  Followed purge VB instructions per release announcements.  Plus 2 minute boot, after VB purge, just under.2 minutes.  I just installled xubuntu 18.04 on same spare ssd, 4.15.0-23-generic.  Boot in 12 seconds.  Reversion to that kernel in Lite broke my wi-fi, but, it booted fast.
[size=78%].  [/size]