LinuxQuestions.org - [SOLVED] Mint 19.3 (Cinnamon): Boot time!

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - Mint 19.3 (Cinnamon): Boot time! (https://www.linuxquestions.org/questions/linux-software-2/mint-19-3-cinnamon-boot-time-4175671517/)

Mint 19.3 (Cinnamon): Boot time!

Guys, I have a Samsung Series 3 Notebook, model NP300E5a-A05US and I recently upgraded from Mint 18.3 (Cinnamon) to Mint 19.3 (Cinnamon). Once booted, my laptop seems to run fine; in fact, I love the enhancements made since my previous installation of Mint 18.3 (Cinnamon).

My issue is boot time (see logs below):

Code:

$ systemd-analyze time

Startup finished in 7.310s (kernel) + 1min 57.249s (userspace) = 2min 4.560s

graphical.target reached after 46.787s in userspace



systemd-analyze blame

        15.692s dev-sda1.device

        14.689s systemd-journal-flush.service

          9.664s accounts-daemon.service

          8.985s NetworkManager.service

          8.812s ModemManager.service

          8.622s configure-printer@usb-002-003.service

          6.974s apparmor.service

          6.896s udisks2.service

          6.720s grub-common.service

          6.544s ufw.service

          6.192s systemd-udevd.service

          4.879s lvm2-monitor.service

          4.517s networkd-dispatcher.service

          3.922s thermald.service

          3.846s speech-dispatcher.service

          3.749s lm-sensors.service

          3.739s gpu-manager.service

          3.633s networking.service

          3.422s wpa_supplicant.service

          2.778s systemd-tmpfiles-setup-dev.service

          2.650s polkit.service

          2.353s dns-clean.service

          2.135s ubuntu-system-adjustments.service

lines 1-23...skipping...

        15.692s dev-sda1.device

        14.689s systemd-journal-flush.service

          9.664s accounts-daemon.service

          8.985s NetworkManager.service

          8.812s ModemManager.service

          8.622s configure-printer@usb-002-003.service

          6.974s apparmor.service

          6.896s udisks2.service

          6.720s grub-common.service

          6.544s ufw.service

          6.192s systemd-udevd.service

          4.879s lvm2-monitor.service

          4.517s networkd-dispatcher.service

          3.922s thermald.service

          3.846s speech-dispatcher.service

          3.749s lm-sensors.service

          3.739s gpu-manager.service

          3.633s networking.service

          3.422s wpa_supplicant.service

          2.778s systemd-tmpfiles-setup-dev.service

          2.650s polkit.service

          2.353s dns-clean.service

          2.135s ubuntu-system-adjustments.service

          2.098s colord.service

          2.066s systemd-tmpfiles-setup.service

          1.793s systemd-rfkill.service

          1.586s systemd-sysctl.service

          1.424s keyboard-setup.service

          1.417s lightdm.service

          1.413s plymouth-quit-wait.service

          1.299s rsyslog.service

          1.277s plymouth-read-write.service

          1.255s systemd-update-utmp.service

          1.247s systemd-modules-load.service

          1.133s avahi-daemon.service

          897ms systemd-backlight@backlight:acpi_video0.service

          873ms alsa-restore.service

          810ms systemd-logind.service

          706ms upower.service

lines 1-39

It seems that my Mint 18.3 installation booted much faster than my new Mint 19.3 installation, so my question is:

Is 2+ minutes boot time typical for my setup, or can I do better?

Thanks in advance, guys.

Get rid of the boot eye-candy (temporarily) and watch the messages. No doubt waiting for device (90 sec timeout), and I'll have a small wager it's a UUID mismatch on swap.

Quote:

Originally Posted by syg00 (Post 6101853)

Get rid of the boot eye-candy (temporarily) and watch the messages. No doubt waiting for device (90 sec timeout), and I'll have a small wager it's a UUID mismatch on swap.

How do I do it, syg00? I'm not a techy. :banghead:

Quote:

Originally Posted by FenderGuy (Post 6101868)

How do I do it...

Lots of Google hits describe it, but maybe syg00 made what to do a bit sketchy. Goto https://en.opensuse.org/SDB:Nomodese...tion_Obstacles and read the upper blue paragraph about how to edit in the Grub menu. Don't use nomodeset though. Instead, use that method to test with the list of three items near the end of the page, starting with plymouth.

Unneeded services to disable, among several others, probably include:

lvm2-monitor (if you don't use LVM)
ModemManager (if you are a broadband user)
speech-dispatcher (if you're not blind)

Please paste here commands with output from the following:

Code:

sudo parted -l

sudo cat /etc/fstab

sudo blkid

sudo journalctl -b | grep ailed

Quote:

Originally Posted by mrmazda (Post 6101949)

Unneeded services to disable, among several others, probably include:

lvm2-monitor (if you don't use LVM)
ModemManager (if you are a broadband user)
speech-dispatcher (if you're not blind)

Please paste here commands with output from the following:

Code:

sudo parted -l

sudo cat /etc/fstab

sudo blkid

sudo journalctl -b | grep ailed

Here ya go, mrmazda.

~$ sudo parted -l

Code:

[sudo] password for ray:        

Model: ATA ST500LM012 HN-M5 (scsi)

Disk /dev/sda: 500GB

Sector size (logical/physical): 512B/4096B

Partition Table: msdos

Disk Flags: 



Number  Start  End    Size  Type    File system  Flags

 1      1049kB  500GB  500GB  primary  ext4        boot

~$ sudo cat /etc/fstab

Code:

# /etc/fstab: static file system information.

#

# Use 'blkid' to print the universally unique identifier for a

# device; this may be used with UUID= as a more robust way to name devices

# that works even if disks are added and removed. See fstab(5).

#

# <file system> <mount point>  <type>  <options>      <dump>  <pass>

# / was on /dev/sda1 during installation

UUID=04dd8594-1c70-4f0f-b767-126f3d8c160b /              ext4    errors=remount-ro 0      1

/swapfile                                none            swap    sw              0      0

~$ sudo blkid

Code:

/dev/sda1: UUID="04dd8594-1c70-4f0f-b767-126f3d8c160b" TYPE="ext4" PARTUUID="0419b197-01"

~$ sudo journalctl -b | grep ailed

Code:

Mar 18 15:12:44 Samsung kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

Mar 18 15:13:08 Samsung udisksd[840]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory

Mar 18 15:13:08 Samsung udisksd[840]: Failed to load the 'mdraid' libblockdev plugin

Mar 18 15:13:09 Samsung thermald[827]: sysfs write failed /sys/devices/virtual/powercap/intel-rapl/intel-rapl:0/enabled

Mar 18 15:13:19 Samsung colord[923]: failed to get session [pid 844]: No data available

Mar 18 15:13:23 Samsung wpa_supplicant[843]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed

Mar 18 15:13:23 Samsung wpa_supplicant[843]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none

Mar 18 15:13:23 Samsung wpa_supplicant[843]: dbus: Failed to construct signal

Mar 18 15:13:23 Samsung wpa_supplicant[843]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed

Mar 18 15:13:23 Samsung /hpfax[1013]: [1013]: error: Failed to create /var/spool/cups/tmp/.hplip

Mar 18 15:14:15 Samsung pulseaudio[2037]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Mar 18 15:14:15 Samsung dbus-daemon[796]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

Mar 18 15:18:09 Samsung colord[923]: failed to get session [pid 3404]: No data available

Mar 18 15:25:39 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed

Mar 18 15:27:08 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed

Mar 18 15:27:20 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed

Mar 18 15:29:12 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed

Mar 18 15:29:22 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed

Mar 18 15:29:55 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed

Whenever you are asked to provide command output, please use the code icon [#] found above the reply input window. https://forums.opensuse.org/showthre...und-Your-Paste provides an explanation how this is done.

You have a quite uncommon configuration that may well play a part in the problem. Most machines use multiple partitions, usually at least two, often more, but you only have one. Thus Mint is using a swap file instead of a partition, and all user data is on the same partition as the operating system. I wouldn't expect this to play a part, but that's not to say it couldn't. I don't have much experience with Mint, and none at all with your partitioning.

Among the failed messages there is only one I recognize as having significant likelihood of material or primary contribution to the delay: mdraid. Why there would be any reference to mdraid on a laptop with only one disk and one partition on that disk I cannot imagine. It may well have a connection to the dev-sda1.device time, but I don't know how to find out. It's possible a perusal of the messages before and after that journal message could provide a clue. Here's a quick way to scan just that portion of the journal:

Code:

sudo journalctl -b | grep -B8 -A24 dev-sda1.device

The journal can readily be scanned in its entirety. It automatically employs the less command, so that you can scroll and use pgup/pgdn keys to navigate through it.

Code:

sudo journalctl -b -e

will open it at the end point. Leave off the -e and it will start at the beginning. If you'd like to share the journal for an entire boot, redirect output to a file then upload it. This should do both in one step:

Code:

sudo journalctl -b | pastebinit

It will provide a URL for you to paste here. If a command not found results:

Code:

sudo apt install pastebinit

You should do the same thing with blame:

Code:

sudo systemd-analyze blame | pastebinit

Quote:

Originally Posted by mrmazda (Post 6102007)

You have a quite uncommon configuration that may well play a part in the problem. Most machines use multiple partitions, usually at least two, often more, but you only have one. Thus Mint is using a swap file instead of a partition, and all user data is on the same partition as the operating system. I wouldn't expect this to play a part, but that's not to say it couldn't. I don't have much experience with Mint, and none at all with your partitioning.

mrmazda, I think that I partitioned the HDD on the laptop before I installed Mint 19.3. If I reinstalled Mint 19.3 from the CD, would there be an option to install Mint with partitions?

OK, you need to get to a boot menu - if it's dual boot, you already see it. If not, on reboot, right after POST (you may see a message from the PC maker), immediately hit the <Esc> key. Should get the boot menu - if not, keep repeating (faster) till it does.

The first entry should be your Mint option - if not use the cursor keys to highlight it. Hit <Enter>, and cursor down to the linux line, and delete the quiet splash options. Then hit <Ctrl>-x to continue the boot (don't hit <Enter>).

This is a one-off change just for that boot.

Quote:

Originally Posted by FenderGuy (Post 6102022)

I think that I partitioned the HDD on the laptop before I installed Mint 19.3. If I reinstalled Mint 19.3 from the CD, would there be an option to install Mint with partitions?

I'm not sure any Linux installer fails to at least off it as an option, but let's not be quite so hasty to think reinstallation necessary, unless it's just something you feel like doing.

syg00 describes in another manner what I suggested in the first part of comment #4. What he describes enables a way to observe the boot process which could unveil clues to the problem not yet spotted in journal or elsewhere.

In the boot menu, I changed the boot option from BIOS to UEFI; the change decreased my boot time from +2 minutes to +/- 30 seconds!

Thanks, guys.