3 min boot-time

[gorgonzolase]

Hi,

I noticed boot-times get longer and longer.
Now it's > 3 minutes.

Startup finished in 7.983s (kernel) + 3min 533ms (userspace) = 3min 8.517s

Code: Select all

xxx@YYY ~ $ 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 @1min 37.133s
└─multi-user.target @1min 37.133s
  └─apache2.service @1min 36.023s +1.109s
    └─network-online.target @1min 36.020s
      └─NetworkManager-wait-online.service @1min 30.484s +5.535s
        └─NetworkManager.service @1min 30.305s +174ms
          └─dbus.service @1min 30.292s
            └─basic.target @1min 30.291s
              └─sockets.target @1min 30.291s
                └─snapd.socket @1min 30.287s +2ms
                  └─sysinit.target @1min 30.282s
                    └─brltty.service @992ms
                      └─systemd-journald.socket @114ms
                        └─-.slice @97ms

does the following point to problems with swap-partition?

Code: Select all

xxx@HAL ~ $ journalctl --no-pager -b -p3
-- Logs begin at So 2018-06-17 05:17:31 CEST, end at So 2018-06-17 06:08:48 CEST. --
Jun 17 05:17:31 HAL kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)
Jun 17 05:17:32 HAL ntpdate[953]: name server cannot be used: Temporary failure in name resolution (-3)
Jun 17 05:19:01 HAL systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-25a75445\x2d707c\x2d4edf\x2dbdb5\x2da1bcac16f582.device.
Jun 17 05:19:01 HAL bluetoothd[1102]: Failed to obtain handles for "Service Changed" characteristic
Jun 17 05:19:01 HAL bluetoothd[1102]: Not enough free handles to register service
Jun 17 05:19:01 HAL bluetoothd[1102]: Error adding Link Loss service
Jun 17 05:19:01 HAL bluetoothd[1102]: Not enough free handles to register service
Jun 17 05:19:01 HAL bluetoothd[1102]: Not enough free handles to register service
Jun 17 05:19:01 HAL bluetoothd[1102]: Not enough free handles to register service
Jun 17 05:19:01 HAL bluetoothd[1102]: Current Time Service could not be registered
Jun 17 05:19:01 HAL bluetoothd[1102]: gatt-time-server: Input/output error (5)
Jun 17 05:19:01 HAL bluetoothd[1102]: Not enough free handles to register service
Jun 17 05:19:01 HAL bluetoothd[1102]: Not enough free handles to register service
Jun 17 05:19:01 HAL bluetoothd[1102]: Sap driver initialization failed.
Jun 17 05:19:01 HAL bluetoothd[1102]: sap-server: Operation not permitted (1)
Jun 17 05:19:02 HAL NetworkManager[1036]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Jun 17 05:19:02 HAL lightdm[1276]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 17 05:19:02 HAL lightdm[1276]: PAM adding faulty module: pam_kwallet.so
Jun 17 05:19:02 HAL lightdm[1276]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 17 05:19:02 HAL lightdm[1276]: PAM adding faulty module: pam_kwallet5.so
Jun 17 05:19:02 HAL wpa_supplicant[1272]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Jun 17 05:19:02 HAL wpa_supplicant[1272]: dbus: Failed to construct signal
Jun 17 05:19:02 HAL wpa_supplicant[1272]: Could not read interface p2p-dev-wlp2s0 flags: No such device
Jun 17 05:19:03 HAL lightdm[1361]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 17 05:19:03 HAL lightdm[1361]: PAM adding faulty module: pam_kwallet.so
Jun 17 05:19:03 HAL lightdm[1361]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 17 05:19:03 HAL lightdm[1361]: PAM adding faulty module: pam_kwallet5.so
Jun 17 05:19:08 HAL ntpd[1425]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Jun 17 05:19:09 HAL ntpd[1425]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Jun 17 05:19:10 HAL ntpd[1425]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Jun 17 05:19:11 HAL ntpd[1425]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Jun 17 05:19:12 HAL ntpd[1425]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
Jun 17 05:19:31 HAL kernel: hid-generic 0005:04E8:A006.0003: unknown main item tag 0x0
Jun 17 05:19:38 HAL pulseaudio[1838]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
Jun 17 05:19:38 HAL pulseaudio[1897]: [pulseaudio] pid.c: Daemon already running.
Jun 17 05:19:52 HAL ntpdate[2302]: the NTP socket is in use, exiting
Jun 17 05:19:53 HAL ntpd[1425]: bind(24) AF_INET6 fe80::a75b:d3fd:4f30:6b70%3#123 flags 0x11 failed: Cannot assign requested address
Jun 17 05:19:53 HAL ntpd[1425]: unable to create socket on wlp2s0 (5) for fe80::a75b:d3fd:4f30:6b70%3#123
Jun 17 05:20:32 HAL systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-25a75445\x2d707c\x2d4edf\x2dbdb5\x2da1bcac16f582.device.
Jun 17 05:25:32 HAL systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-25a75445\x2d707c\x2d4edf\x2dbdb5\x2da1bcac16f582.device.

what else you want to know?

[catweazel]

└─NetworkManager-wait-online.service @1min 30.484s +5.535s

systemctl disable NetworkManager-wait-online.service

[Flemur]

└─NetworkManager-wait-online.service @1min 30.484s +5.535s

Yeah, disable that.

does the following point to problems with swap-partition?

It might be swap - this line appears 3 times:
Jun 17 05:20:32 HAL systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-25a75445\x2d707c\x2d4edf\x2dbdb5\x2da1bcac16f582.device.

By default "it" waits 90 seconds if it can't mount a partition - two times that = 3 minutes; or "wait-online" service + one partition failure = 3 minutes.

what else you want to know?

Yes: why is there evil? No MS jokes, please.

You might do these commands to check that the UUID(s) match:

Code: Select all

sudo blkid

see that those UUIDs match the ones in

Code: Select all

cat /etc/fstab | grep -v ^#

(fstab w/o the comments...)

[gorgonzolase]

thx for help so far!

disabled NetworkManager-wait-online.service

sudo blkid gives:

Code: Select all

/dev/sda1: UUID="b1735ee1-4d8d-44cb-a525-00437d86842f" TYPE="ext4" PARTUUID="93ff0331-01"
/dev/sda5: UUID="559c910b-933b-41c7-a088-8d6297e4adfc" TYPE="swap" PARTUUID="93ff0331-05"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/mapper/cryptswap2: UUID="32efb771-d980-4cfa-b58e-6cf30e7c99e3" TYPE="swap"

cat /etc/fstab | grep -v ^# gives:

Code: Select all

UUID=b1735ee1-4d8d-44cb-a525-00437d86842f /               ext4    errors=remount-ro 0       1
/dev/mapper/cryptswap1 none swap sw 0 0
/dev/mapper/cryptswap2 none swap sw 0 0

maybe this problem is connected to:
had two SSD disks in there (tripple boot)
removed the SSD with dual boot (Mint + Win 7)
new M.2 SSD with Mint didn't boot because bootloader on other SSD
reinstalled grub and was somehow confused during this with grub logic

anyway I feel this timed out uuid-25a75445\x2d707c\x2d4edf\x2dbdb5\x2da1bcac16f582.device might be the other (not connected) SSD!?!?
right?

shall I just connect other SSD and test?
might have to change BIOS bootorder

Since this might be related, I want to do this:
occasionally connect other (dual boot) SSD with some magnetic switch (SATA cable always connected, but power switched on/off with a magnet externally from the case).
When switched on, there should again be the trippleboot-system.

In case this is confusing how do I just resolve the current timeout?

[Flemur]

cat /etc/fstab | grep -v ^# gives:

Code: Select all

UUID=b1735ee1-4d8d-44cb-a525-00437d86842f /               ext4    errors=remount-ro 0       1
/dev/mapper/cryptswap1 none swap sw 0 0
/dev/mapper/cryptswap2 none swap sw 0 0

anyway I feel this timed out uuid-25a75445\x2d707c\x2d4edf\x2dbdb5\x2da1bcac16f582.device might be the other (not connected) SSD!?!?
right?
shall I just connect other SSD and test?

Sure - see if it's the right UUID; but why is it trying to mount that partition?

I'm also wondering if perhaps you're booting from the wrong grub ? IOW, you updated the one that's not used for booting, and it's looking for a missing disk...? (Here Mint thinks it controls booting and updates the grub files for kernels, etc, but Ubuntu controls booting, so when I update grub in Mint it doesn't have any effect)

might have to change BIOS bootorder

When switched on, there should again be the trippleboot-system.
In case this is confusing how do I just resolve the current timeout?

Dunno, sorry.

[gorgonzolase]

I'm also wondering if perhaps you're booting from the wrong grub ? IOW, you updated the one that's not used for booting, and it's looking for a missing disk...? (Here Mint thinks it controls booting and updates the grub files for kernels, etc, but Ubuntu controls booting, so when I update grub in Mint it doesn't have any effect)

that is very well possible.
I wanted to have grub on both disks, because one is used only occasionally.

Is it true, that grub has to be on the disk, that contains the windows partition?
Alas this disk can't be the first bootoption in BIOS, because it's only occasionally connected.