Horribly long boot on LL4 on SSD

[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