Advertising

Author Topic: Slow boot...(SOLVED)  (Read 362 times)

Offline tenfoot

  • Jr. Member
  • **
  • Posts: 73
Slow boot...(SOLVED)
« on: August 03, 2018, 11:02:36 pm »
[Using Sparky v5.3 Mate. Details of my desktop are: 

For some reason unknown to me my computer is much slower in booting and I cannot determine why, as I have not installed any programs recently which could affect this.

Searching the net, I found that systemd has some analytical commands.  So I have used them and post the results below.

Code: [Select]
zed@zed-pc:~$ sudo -s
[sudo] password for zed:
root@zed-pc:/home/zed# systemd-analyze time
Startup finished in 35.448s (kernel) + 14.049s (userspace) = 49.497s
graphical.target reached after 14.038s in userspace
root@zed-pc:/home/zed# systemd-analyze --no-pager blame
         12.404s NetworkManager-wait-online.service
          2.785s postgresql@10-main.service
          1.425s upower.service
           804ms udisks2.service
           430ms dev-sda3.device
           363ms exim4.service
           311ms loadcpufreq.service
           274ms ModemManager.service
           265ms systemd-journald.service
           207ms accounts-daemon.service
           176ms systemd-logind.service
           166ms acpi-support.service
           164ms wpa_supplicant.service
           161ms NetworkManager.service
           159ms rtkit-daemon.service
           154ms keyboard-setup.service
           142ms lm-sensors.service
           140ms systemd-modules-load.service
           138ms systemd-timesyncd.service
           136ms rsyslog.service
           130ms alsa-restore.service
           129ms console-kit-daemon.service
           128ms systemd-fsck@dev-disk-by\x2duuid-70783429\x2dbd9d\x2d467f\x2dad32\x2d682fd3768c93.service
           126ms avahi-daemon.service
           113ms lightdm.service
            83ms systemd-udev-trigger.service
            82ms teamviewerd.service
            80ms apparmor.service
            79ms systemd-journal-flush.service
            78ms user@1000.service
            67ms networking.service
            55ms packagekit.service
            54ms ntp.service
            53ms polkit.service
            42ms systemd-udevd.service
            41ms colord.service
            38ms console-kit-log-system-start.service
            35ms media-zed-Data.mount
            35ms pppd-dns.service
            29ms rpcbind.service
            28ms run-rpc_pipefs.mount
            27ms ifplugd.service
            27ms systemd-sysctl.service
            26ms cpufrequtils.service
            23ms hddtemp.service
            22ms systemd-tmpfiles-setup-dev.service
            21ms sys-kernel-debug.mount
            21ms ifupdown-wait-online.service
            21ms ufw.service
            20ms dev-hugepages.mount
            19ms kmod-static-nodes.service
            19ms systemd-tmpfiles-setup.service
            18ms systemd-remount-fs.service
            17ms systemd-sysusers.service
            17ms dev-mqueue.mount
            17ms systemd-update-utmp.service
            15ms plymouth-start.service
            12ms plymouth-read-write.service
            11ms systemd-random-seed.service
            11ms plymouth-quit-wait.service
             9ms systemd-user-sessions.service
             8ms systemd-update-utmp-runlevel.service
             7ms minissdpd.service
             7ms postgresql.service
             7ms console-setup.service
             6ms rc-local.service
             5ms sys-fs-fuse-connections.mount
             3ms nfs-config.service
             3ms tmp.mount
root@zed-pc:/home/zed# systemd-analyze plot > plot.svg
root@zed-pc:/home/zed# journalctl --no-pager -b -p3
-- Logs begin at Sat 2018-08-04 08:16:39 NZST, end at Sat 2018-08-04 08:25:12 NZST. --
Aug 04 08:16:39 zed-pc kernel: sd 6:0:0:0: [sdc] No Caching mode page found
Aug 04 08:16:39 zed-pc kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Aug 04 08:16:39 zed-pc systemd-udevd[489]: Invalid rule /etc/udev/rules.d/60-brother-libsane-type1.rules:17: unknown key 'SYSFS{idVendor}'
Aug 04 08:16:41 zed-pc ntpd[872]: error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2)
Aug 04 08:16:42 zed-pc ntpd[872]: error resolving pool 1.debian.pool.ntp.org: Name or service not known (-2)
Aug 04 08:16:43 zed-pc ntpd[872]: error resolving pool 2.debian.pool.ntp.org: Name or service not known (-2)
Aug 04 08:16:44 zed-pc ntpd[872]: error resolving pool 3.debian.pool.ntp.org: Name or service not known (-2)
Aug 04 08:16:45 zed-pc colord-sane[962]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Aug 04 08:16:45 zed-pc ntpd[872]: bind(23) AF_INET6 fe80::2bd3:86f7:151e:29f8%2#123 flags 0x11 failed: Cannot assign requested address
Aug 04 08:16:45 zed-pc ntpd[872]: unable to create socket on eth0 (4) for fe80::2bd3:86f7:151e:29f8%2#123
Aug 04 08:16:45 zed-pc hp[1122]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Aug 04 08:16:45 zed-pc /hpfax[1116]: [1116]: error: Failed to create /var/spool/cups/tmp/.hplip
Aug 04 08:16:45 zed-pc /hpfax[1116]: io/hpmud/pp.c 627: unable to read device-id ret=-1
root@zed-pc:/home/zed# systemctl --no-pager --state=failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
root@zed-pc:/home/zed# lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINT,UUID
NAME     SIZE TYPE FSTYPE MOUNTPOINT         UUID
sda    223.6G disk                           
├─sda1  49.3G part ext4                      c21e2a06-9a04-4f91-9ecb-7a8a26977038
├─sda2   1.5G part swap                      0dc73dea-b3e1-48b8-8291-8155df8bf954
└─sda3 147.8G part ext4   /                  931b93ca-b127-4d40-8673-ee06a6fe9b42
sdb    465.8G disk                           
└─sdb1 465.8G part ext4   /media/zed/Data    70783429-bd9d-467f-ad32-682fd3768c93
sdc    931.5G disk                           
└─sdc1 931.5G part ntfs   /media/zed/USB-HDD 6092D5E95F8A15E5
sr0     1024M rom                           
sr1     1024M rom                           
root@zed-pc:/home/zed# systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @14.038s
└─multi-user.target @14.038s
  └─exim4.service @13.674s +363ms
    └─network-online.target @13.668s
      └─NetworkManager-wait-online.service @1.263s +12.404s
        └─NetworkManager.service @1.100s +161ms
          └─dbus.service @1.092s
            └─basic.target @1.081s
              └─sockets.target @1.081s
                └─avahi-daemon.socket @1.081s
                  └─sysinit.target @1.076s
                    └─systemd-timesyncd.service @936ms +138ms
                      └─systemd-tmpfiles-setup.service @912ms +19ms
                        └─local-fs.target @902ms
                          └─run-user-1000.mount @2.284s
                            └─local-fs-pre.target @339ms
                              └─keyboard-setup.service @183ms +154ms
                                └─systemd-journald.socket @179ms
                                  └─-.mount @176ms
                                    └─system.slice @176ms
                                      └─-.slice @176ms

Is any member able to suggest to me what I could do to improve the speed of boot, please?
« Last Edit: August 07, 2018, 11:23:08 pm by tenfoot »
Dogs laugh, but they laugh with their tails.

Offline tenfoot

  • Jr. Member
  • **
  • Posts: 73
Re: Slow boot...
« Reply #1 on: August 06, 2018, 02:35:29 am »
Further to the systemd Analysis tests.

I have done some more investigating and find that I have the following linux-headers in Synaptic.

Installed:
linux-headers-4.15.17-1  Common header files for Linux 4.15.0-3
linux-headers-4.16.5-1  Common header files for Linux 4.16.0-1
linux-headers-4.16.16-2  Common header files for Linux 4.16.0-2
linux-headers-4.15.17-1  Common header files for Linux 4.15.0-3-amd64
linux-headers-4.16.5-1  Common header files for Linux 4.16.0-1-amd64
linux-headers-4.16.16-2  Common header files for Linux 4.16.0-2-amd64

Upon Boot of Sparky Linux using the Advanced option I have two choices. 

(a) the default kernel 4.17.0-1 or (b) kernel 4.16.0-2

Choosing (b) leads to a much decreased boot time.

However, what is strange is that searching Synaptic for linux-headers 4.17.0-1 reveals that none of them are installed.

Some questions.

(a) What must I do to automatically boot into kernel 4.16.0-2 (the one where boot time is greatly reduced)?

(b) Why is the Advanced option on boot showing 4.17.0-1?

(c) Is it safe to removed the kernel-headers which are not -amd64 or would I need these if I installed other distributions under VirtualBox?
Dogs laugh, but they laugh with their tails.

Offline pavroo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1905
    • SparkyLinux
Re: Slow boot...
« Reply #2 on: August 06, 2018, 01:56:13 pm »
c) If you din's have such kernels installed, you can uninstall all the headers.
b) the advanced kernel option lets you run the system with minimal set of services, in a case of problems with normal boot.
a) edit (as root) /etc/default/grub
and change the option:
Code: [Select]
GRUB_DEFAULT=0The "0" choose the first line from the grub list, so...
The second line is 1, the third is 2, etc.
Count lines at grub list, paste the right number to the default/grub file, then
Code: [Select]
sudo update-grubMake sure if you install another kernel, the list will be changed, but grub will choose still the same number.
Nothing is easy as it looks.
Danielle Steel

Offline tenfoot

  • Jr. Member
  • **
  • Posts: 73
Re: Slow boot...
« Reply #3 on: August 07, 2018, 11:21:59 pm »
Thank you for your reply and suggestion.  I did as you suggested but it didn't improve things very much.  So, I decided to take the extreme step of doing a complete re-installation of Sparky v5.3 Mate.

As I had copious notes of how I'd configured my Desktop and the additional programs I had installed, it was not hard to recreate things as they had been, as in addition to my notes, I had backed up all the hidden files I needed to ensure I didn't lose important configuration files.  I didn't need to back-up anything else from Home, as all data I create is saved to a separate Data drive.

The installation was successful and the computer now boots in 17.406s. and I have marked the subject as Solved.

However, there are two problems. which I describe in a separate post under Hardware.

Dogs laugh, but they laugh with their tails.