LINUX LITE 7.2 FINAL RELEASED - SEE RELEASE ANNOUNCEMENTS SECTION FOR DETAILS


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Slow boot time with new SSD
#1
Hey Jerry,
I took your advice and bought a new SSD.  I even bumped up RAM to a whopping 3GB.  :Smile
However boot time is still sloooooooooooooow!

Here's the current analysis:

systemd-analyze blame
    1min 11.601s plymouth-quit-wait.service
        40.464s vboxadd.service
        31.669s lightdm.service
          5.029s NetworkManager-wait-online.service
          3.071s dev-sda1.device
          1.036s networkd-dispatcher.service
          875ms ufw.service
          756ms motd-news.service
          739ms lm-sensors.service
          714ms networking.service
          567ms upower.service
          546ms udisks2.service
          540ms apparmor.service
          525ms NetworkManager.service
          507ms systemd-rfkill.service
          487ms apport.service
          469ms grub-common.service
          442ms systemd-udev-trigger.service
          415ms keyboard-setup.service
          373ms pppd-dns.service
          371ms ModemManager.service
          367ms thermald.service
          355ms accounts-daemon.service
          354ms ubiquity.service
          332ms systemd-udevd.service
          330ms gpu-manager.service
          308ms systemd-journald.service
          290ms swapfile.swap
          279ms rsyslog.service
          269ms systemd-journal-flush.service
          222ms wpa_supplicant.service
          210ms avahi-daemon.service
          178ms systemd-resolved.service
          178ms systemd-modules-load.service
          164ms systemd-timesyncd.service
          145ms systemd-logind.service
          129ms lvm2-monitor.service
          120ms smbd.service
          109ms packagekit.service
          100ms [email protected]
          100ms systemd-sysctl.service
            93ms nmbd.service
            90ms polkit.service
            70ms blk-availability.service
            67ms dev-mqueue.mount
            65ms systemd-tmpfiles-setup.service
            64ms dev-hugepages.mount
            59ms systemd-remount-fs.service
            55ms kmod-static-nodes.service
            53ms sys-kernel-debug.mount
            40ms hddtemp.service
            39ms systemd-tmpfiles-setup-dev.service
            38ms plymouth-start.service
            37ms dns-clean.service
            35ms systemd-random-seed.service
            34ms iio-sensor-proxy.service
            32ms resolvconf.service
            31ms console-kit-daemon.service
            30ms systemd-user-sessions.service
            27ms console-setup.service
            27ms sys-kernel-config.mount
            27ms systemd-update-utmp.service
            27ms systemd-tmpfiles-clean.service
            26ms resolvconf-pull-resolved.service
            25ms sys-fs-fuse-connections.mount
            21ms bluetooth.service
            19ms openvpn.service
            16ms plymouth-read-write.service
            14ms console-kit-log-system-start.service
            13ms ureadahead-stop.service
            13ms systemd-backlight@backlight:acpi_video0.serv
            8ms systemd-backlight@backlight:intel_backlight.
            8ms systemd-update-utmp-runlevel.service
            7ms rtkit-daemon.service
            7ms setvtrgb.service
lines 60-75/75 (END)
            27ms console-setup.service
            27ms sys-kernel-config.mount
            27ms systemd-update-utmp.service
            27ms systemd-tmpfiles-clean.service
            26ms resolvconf-pull-resolved.service
            25ms sys-fs-fuse-connections.mount
            21ms bluetooth.service
            19ms openvpn.service
            16ms plymouth-read-write.service
            14ms console-kit-log-system-start.service
            13ms ureadahead-stop.service
            13ms systemd-backlight@backlight:acpi_video0.serv
            8ms systemd-backlight@backlight:intel_backlight.
            8ms systemd-update-utmp-runlevel.service
            7ms rtkit-daemon.service

systemd-analyze critical-chain
The time after the unit is active or started is printed after
The time the unit takes to start is printed after the "+" cha
The time after the unit is active or started is printed after
The time the unit takes to start is printed after the "+" cha

graphical.target @1min 13.708s
└─lightdm.service @42.038s +31.669s
  └─systemd-user-sessions.service @2.034s +30ms
    └─network.target @2.028s
      └─NetworkManager.service @1.502s +525ms
        └─dbus.service @1.392s
          └─basic.target @1.258s
            └─paths.target @1.258s
              └─resolvconf-pull-resolved.path @1.250s
                └─sysinit.target @1.234s
                  └─systemd-backlight@backlight:intel_backlig
                    └─system-systemd\x2dbacklight.slice @2.32

Any suggestions?
Reply
#2
bermudalite

Check your kernel version. Can be done easily going Menu->System->System Info->Operating System.
If it is Linux 4.15.0-24 generic you maybe having the same problem as me. 

If it is as mentioned above after the boot splash screen with whirling thing, move your mouse around and see what happens.
Reply
#3
I moved this to it's own thread as your SSD is new. Will you be running VirtualBox?
Reply
#4
Thx Charvie...I'll check that out.
Jerry...no, vbox will not be used on this machine.
Reply
#5
Charvie, my kernel is 4.15.0-23 generic.
What should it be?
Reply
#6
That kernel is NOT the one causing trouble.  The -24 is causing slow boot-ups.  So your trouble is something else.  Sorry I couldn't help but it was worth a try.

If you are not going to use vbox, try following Jerry's instructions he gave at the bottom of the Linux Lite 4.0 Final Release Announcement message (Performance TipsSmile.  Worked well for me when I installed LL 4.0. 

https://www.linuxliteos.com/forums/relea...-released/

Reply
#7
(07-06-2018, 01:51 AM)charvie link Wrote: If you are not going to use vbox, try following Jerry's instructions he gave at the bottom of the Linux Lite 4.0 Final Release Announcement message (Performance TipsSmile.  Worked well for me when I installed LL 4.0. 
https://www.linuxliteos.com/forums/relea...-released/

Definitely try what charvie suggested above.
It speeded up boot very significantly from around 40 seconds to 13 seconds on the i7 laptop in setup (1), listed in signature below.
64bit OS (32-bit on Samsung[i] netbook) installed in [i]Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)  
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work
Reply
#8
That worked!
5 minute boot down to 30 seconds!!!

Thanks!
Reply
#9
(07-06-2018, 01:41 PM)bermudalite link Wrote: That worked!
5 minute boot down to 30 seconds!!!

Thanks!

Glad it worked - remember to "thank" charvie for mentioning it ...
64bit OS (32-bit on Samsung[i] netbook) installed in [i]Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)  
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work
Reply
#10
Absolutely...thx Charvie! 
My laptop now has a new lease on life.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)