[solved] Mint takes too long to startup (red dots appearing)

[JBento]

When I first installed Mint, everything was fine, but when starting up the Linux Mint logo would show up with some white dots that would change to green. They would suddenly become red (I may be wrong, but usually red is not good) and it would take forever for the OS to finally start up. I tried formatting and installing again using a new downloaded ISO (since the old one could be corrupted or something), but still have the same problem.

Is that normal or is something I can fix?

[karlchen]

Hello, JBento.

Welcome to the Linux Mint forum.

With respect to issue of long startup times, it would be very helpful to have a few more details on your system in order to be able to give helpful advice.

Therefore I would like to ask you to provide to us, please, ...

• an inxi -Fxz report. This will give us a concise overview on your system hardware and on your system configuration.
  Please, open a terminal window. Make the terminal window full screen. Execute the commandline

  Code: Select all

  inxi -Fxz

  precisely as it has been typed here. Mark the complete text output which inxi will display with your mouse. Press <Ctrl><Shift>C in order to copy the marked text into the clibpboard. Paste it into your next reply.
  .
• the output of the commandline systemd-analyze It will reveal how much time your system takes to load the kernel and how much time it takes to load the graphical desktop environment, plus the overall system startup time.
  Execute the commandline

  Code: Select all

  systemd-analyze

  Mark the complete text output which systemd-analyze will display with your mouse. Press <Ctrl><Shift>C in order to copy the marked text into the clibpboard. Paste it into your next reply.
  .
• the output of the commandline systemd-analyze blame It will reveal how much time systemd spends on loading every single service and may help identify services which waste too much time (for whichever reason).
  Execute the commandline

  Code: Select all

  systemd-analyze blame

  Mark the complete text output which systemd-analyze will display with your mouse. Press <Ctrl><Shift>C in order to copy the marked text into the clibpboard. Paste it into your next reply.

Best regards,
Karl

[JBento]

Thank you and sorry for the long time to reply. Here it is:

an inxi -Fxz report

Code: Select all

inxi -Fxz
System:    Host: Ugly Kernel: 4.15.0-20-generic x86_64 bits: 64 compiler: gcc v: 7.3.0 Desktop: Cinnamon 4.0.8 
           Distro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic 
Machine:   Type: Desktop Mobo: Gigabyte model: GA-78LMT-S2 serial: <filter> BIOS: Award v: F5 date: 10/19/2012 
CPU:       Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 42187 
           Speed: 1405 MHz min/max: 1400/3500 MHz Core speeds (MHz): 1: 1402 2: 1405 3: 1405 4: 1406 5: 1403 6: 1406 
Graphics:  Device-1: NVIDIA GK106 [GeForce GTX 660] driver: nvidia v: 390.77 bus ID: 01:00.0 
           Display: x11 server: X.Org 1.19.6 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa 
           resolution: 1920x1080~60Hz, 1440x900~60Hz 
           OpenGL: renderer: GeForce GTX 660/PCIe/SSE2 v: 4.6.0 NVIDIA 390.77 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] SBx00 Azalia vendor: Gigabyte driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 
           Device-2: NVIDIA GK106 HDMI Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           Device-3: Philips (or NXP) Webcam SPC530NC type: USB driver: snd-usb-audio,uvcvideo bus ID: 2-5:3 
           Sound Server: ALSA v: k4.15.0-20-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: 2.3LK-NAPI 
           port: de00 bus ID: 02:00.0 
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.66 TiB used: 24.06 GiB (1.4%) 
           ID-1: /dev/sda vendor: Western Digital model: WD5000AVDS-63U7B1 size: 465.76 GiB 
           ID-2: /dev/sdb vendor: Western Digital model: WD3200AAJS-00YZCA0 size: 298.09 GiB 
           ID-3: /dev/sdc vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB 
Partition: ID-1: / size: 91.17 GiB used: 12.03 GiB (13.2%) fs: ext4 dev: /dev/sda1 
Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A gpu: nvidia temp: 41 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
Info:      Processes: 204 Uptime: 54m Memory: 7.79 GiB used: 1.12 GiB (14.4%) Init: systemd runlevel: 5 Compilers: gcc: 7.3.0 
           Shell: bash v: 4.4.19 inxi: 3.0.27 

the output of the commandline systemd-analyze

Code: Select all

systemd-analyze
Startup finished in 38.866s (kernel) + 3min 2.856s (userspace) = 3min 41.722s
graphical.target reached after 1min 37.140s in userspace

the output of the commandline systemd-analyze blame

Code: Select all

~$ systemd-analyze blame
         12.143s dev-sda1.device
          9.769s systemd-journal-flush.service
          9.761s lvm2-monitor.service
          9.274s systemd-sysctl.service
          8.823s systemd-udevd.service
          8.716s apt-daily.service
          3.019s udisks2.service
          2.851s NetworkManager.service
          2.664s networkd-dispatcher.service
          2.435s systemd-tmpfiles-setup.service
          2.291s ubuntu-system-adjustments.service
          2.200s apparmor.service
          1.886s ModemManager.service
          1.783s thermald.service
          1.602s gpu-manager.service
          1.374s accounts-daemon.service
          1.197s avahi-daemon.service
          1.170s lm-sensors.service
          1.025s systemd-modules-load.service
           993ms keyboard-setup.service
           976ms polkit.service
           891ms systemd-tmpfiles-setup-dev.service
           707ms grub-common.service
           705ms rsyslog.service
           670ms networking.service
           670ms setvtrgb.service
           644ms apt-daily-upgrade.service
           604ms apport.service
           590ms colord.service
           546ms kmod-static-nodes.service
           536ms kerneloops.service
           434ms systemd-logind.service
           427ms dns-clean.service
           421ms lightdm.service
           419ms plymouth-quit-wait.service
           394ms wpa_supplicant.service
           374ms systemd-journald.service
           330ms systemd-random-seed.service
           254ms systemd-timesyncd.service
           235ms systemd-resolved.service
           224ms dev-mqueue.mount
           222ms dev-hugepages.mount
           220ms sys-kernel-debug.mount
           215ms upower.service
           195ms blk-availability.service
           194ms ufw.service
           127ms systemd-remount-fs.service
           116ms console-setup.service
            97ms systemd-udev-trigger.service
            96ms speech-dispatcher.service
            90ms hddtemp.service
            74ms user@1000.service
            74ms systemd-update-utmp.service
            72ms alsa-restore.service
            68ms pppd-dns.service
            63ms nvidia-persistenced.service
            52ms systemd-tmpfiles-clean.service
            13ms plymouth-start.service
            11ms plymouth-read-write.service
             9ms ureadahead-stop.service
             4ms rtkit-daemon.service
             4ms systemd-update-utmp-runlevel.service
             4ms systemd-user-sessions.service
             2ms sys-fs-fuse-connections.mount
             2ms sys-kernel-config.mount
             1ms openvpn.service

[karlchen]

Hello, JBento.

The inxi report looks all right to me. At least, I do not spot any obvious source of extreme slowness at startup time in the inxi report.

Yet, the result of systemd-analyze

Code: Select all

Startup finished in 38.866s (kernel) + 3min 2.856s (userspace) = 3min 41.722s
graphical.target reached after 1min 37.140s in userspace

looks really disconcerting.
Both timespans, kernel loading time of 38.866s and userspace loading time of 3 min 2.856s, are much much longer than on my slow old Zotac mini-desktop from 2009, which is slowed down by its lame Atom CPU's.

About the kernel loading time:
The question is whether this is the normal kernel loading time as systemd-analyze will report it after every reboot.
On the mentioned Zotac I see CPU load times of about 35 seconds on every 20th reboot, because on every 20th reboot, the system will run an fsck on its root filesystem /. In all other cases the kernel load time will be below 10s.
So you might run systemd-analyze after the 3 or 4 next reboots, in order to determine whether your kernel loading time is around 39s everytime or whether this is an extreme value.

About the userspace loading time:
3min 2.856s is really extremely long.
And to be honest, the timespans, which systemd-analyze blame reports, do not account for more than 3 minutes.

This means it will be necessary to investigate the system logs, generated during the current and the past few system sessions. The term session here denotes the complete timespan between reboot and shutdown.

The (detailled) system logs of each session can be inspected by executing the following terminal commands:

• journalct -b displays the current session
• journalctl -b -1 displays the previous session
• journalctl -b -2 displays the session before the previous session
• journalctl -b -X displays the X-last session, where -X is a negative number like -1, -2, -3 etc

journalctl will display each entry with there exact timestamps
What I would be looking for would be significant gaps between such timestamps. And of course error messages.

Best regards,
Karl

[trytip]

your white dots instead of the mint logo are the cause of nvidia driver being loaded at boot. if you go back to the nouveau driver your mint logo will return. it's a well known issue with nvidia since before log ago. to me the red dots look dark orange but maybe it's from some theme i'm using

if you want to try to fix it:
sudo xed /etc/default/grub
find the line #GRUB_GFXMODE=640x480 and BELOW it add

Code: Select all

GRUB_GFXPAYLOAD_LINUX="1024x768"

then run sudo update-grub

test it and post if the mint logo is returned

[karlchen]

<moderator on>
Split off whois1230's post and turned it into a dedicated new thread: Mint 18.3 takes too long to startup. - Do not hijack another user's thread, please.
<moderator off>

[karlchen]

Hello, JBento.

Continuing the idea, explained in my previous on-topic post above, of using journalctl to find out what may be going on and what may be going wrong during the more than 3 minutes, which your system spends to load the userspace environment, I would now simply suggest to you how to make your systemlog entries available here for inspection, please:

How to provide your journalctl output to us for inspection:

Please, proceed like this in order in order to post the current systemlog entries to us for inspection:

• Open a terminal window.
• Execute the following commandline, please:

  Code: Select all

  journalctl --no-pager -b 0 > journalctl_jbento.txt

  This command will write the whole current system log to the file journalctl_jbento.txt. The file will be located in your $HOME directory (very likely /home/jbento).
• Now gzip the file journalctl_jbento.txt by executing the commandline:

  Code: Select all

  gzip journalctl_jbento.txt

  The resulting .gz file will be named journalctl_jbento.txt.gz.
• Attach this file to your next reply, please.

If we are lucky the systemlog will put us on the right track. Hopefully.

Best regards,
Karl

[JBento]

your white dots instead of the mint logo are the cause of nvidia driver being loaded at boot. if you go back to the nouveau driver your mint logo will return. it's a well known issue with nvidia since before log ago. to me the red dots look dark orange but maybe it's from some theme i'm using

if you want to try to fix it:
sudo xed /etc/default/grub
find the line #GRUB_GFXMODE=640x480 and BELOW it add

Code: Select all

GRUB_GFXPAYLOAD_LINUX="1024x768"

then run sudo update-grub

test it and post if the mint logo is returned

I was using Nouveau, but it would crash de video from time to time (the display would become a bunch of squares, forcing me to restart the computer).

Hello, JBento.

Continuing the idea, explained in my previous on-topic post above, of using journalctl to find out what may be going on and what may be going wrong during the more than 3 minutes, which your system spends to load the userspace environment, I would now simply suggest to you how to make your systemlog entries available here for inspection, please:

How to provide your journalctl output to us for inspection:

Please, proceed like this in order in order to post the current systemlog entries to us for inspection:

• Open a terminal window.
• Execute the following commandline, please:

  Code: Select all

  journalctl --no-pager -b 0 > journalctl_jbento.txt

  This command will write the whole current system log to the file journalctl_jbento.txt. The file will be located in your $HOME directory (very likely /home/jbento).
• Now gzip the file journalctl_jbento.txt by executing the commandline:

  Code: Select all

  gzip journalctl_jbento.txt

  The resulting .gz file will be named journalctl_jbento.txt.gz.
• Attach this file to your next reply, please.

If we are lucky the systemlog will put us on the right track. Hopefully.

Best regards,
Karl

I did it. I can't understand what's written, but checking it out I found a point, around 9:41, where there's a 2 minutes gap (one line it's loaded at 9:41, the next is already 9:43). Anyway, here is the file, I hope you guys can help.

[karlchen]

Hello, JBento.

Below is what struck me in the journalctl output:

journalctl lines 994 - 1007

Code: Select all

Feb 26 06:41:49 Ugly systemd[1]: Reached target Host and Network Name Lookups.
Feb 26 06:43:05 Ugly systemd[1]: dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device: Job dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device/start timed out.
Feb 26 06:43:05 Ugly systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device.
Feb 26 06:43:05 Ugly systemd[1]: Dependency failed for Cryptography Setup for cryptswap1.
Feb 26 06:43:05 Ugly systemd[1]: Dependency failed for Local Encrypted Volumes.
Feb 26 06:43:05 Ugly systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'.
Feb 26 06:43:05 Ugly systemd[1]: Dependency failed for dev-mapper-cryptswap1.device.
Feb 26 06:43:05 Ugly systemd[1]: Dependency failed for /dev/mapper/cryptswap1.
Feb 26 06:43:05 Ugly systemd[1]: Dependency failed for Swap.
Feb 26 06:43:05 Ugly systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
Feb 26 06:43:05 Ugly systemd[1]: dev-mapper-cryptswap1.swap: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
Feb 26 06:43:05 Ugly systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'.
Feb 26 06:43:05 Ugly systemd[1]: systemd-cryptsetup@cryptswap1.service: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
Feb 26 06:43:05 Ugly systemd[1]: dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device: Job dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device/start failed with result 'timeout'.

Gap between 06:41:49 and 06:43:05: 1min 16s

journalctl lines 1542 - 1545

Code: Select all

Feb 26 09:44:36 Ugly systemd[1]: Startup finished in 38.869s (kernel) + 3min 2.630s (userspace) = 3min 41.500s.
Feb 26 09:44:36 Ugly systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'.
Feb 26 09:44:36 Ugly systemd[1]: systemd-cryptsetup@cryptswap1.service: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
Feb 26 09:44:36 Ugly systemd[1]: dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device: Job dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device/start failed with result 'timeout'.

1min 16s seem to be accounted for by swap device encryption and in particular by issues with the encrypted swap device.
Yet, this alone does not sum up to 3min 2.630s.
Something must be going on and the stopwatch must have started before journalctl started logging. Or I misunderstand something.


Below are 4 more blocks of complaints about unresolvable issues to load an encrypted swap device.

journalctl lines 1560 - 1568:

Code: Select all

Feb 26 09:46:30 Ugly systemd[1]: dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device: Job dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device/start timed out.
Feb 26 09:46:30 Ugly systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device.
Feb 26 09:46:30 Ugly systemd[1]: Dependency failed for Cryptography Setup for cryptswap1.
Feb 26 09:46:30 Ugly systemd[1]: Dependency failed for dev-mapper-cryptswap1.device.
Feb 26 09:46:30 Ugly systemd[1]: Dependency failed for /dev/mapper/cryptswap1.
Feb 26 09:46:30 Ugly systemd[1]: dev-mapper-cryptswap1.swap: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
Feb 26 09:46:30 Ugly systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'.
Feb 26 09:46:30 Ugly systemd[1]: systemd-cryptsetup@cryptswap1.service: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
Feb 26 09:46:30 Ugly systemd[1]: dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device: Job dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device/start failed with result 'timeout'.

journalctl lines 1590 - 1598:

Code: Select all

Feb 26 09:49:37 Ugly systemd[1]: dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device: Job dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device/start timed out.
Feb 26 09:49:37 Ugly systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device.
Feb 26 09:49:37 Ugly systemd[1]: Dependency failed for Cryptography Setup for cryptswap1.
Feb 26 09:49:37 Ugly systemd[1]: Dependency failed for dev-mapper-cryptswap1.device.
Feb 26 09:49:37 Ugly systemd[1]: Dependency failed for /dev/mapper/cryptswap1.
Feb 26 09:49:37 Ugly systemd[1]: dev-mapper-cryptswap1.swap: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
Feb 26 09:49:37 Ugly systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'.
Feb 26 09:49:37 Ugly systemd[1]: systemd-cryptsetup@cryptswap1.service: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
Feb 26 09:49:37 Ugly systemd[1]: dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device: Job dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device/start failed with result 'timeout'.

journalctl lines 1603 - 1611:

Code: Select all

Feb 26 09:52:10 Ugly systemd[1]: dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device: Job dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device/start timed out.
Feb 26 09:52:10 Ugly systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device.
Feb 26 09:52:10 Ugly systemd[1]: Dependency failed for Cryptography Setup for cryptswap1.
Feb 26 09:52:10 Ugly systemd[1]: Dependency failed for dev-mapper-cryptswap1.device.
Feb 26 09:52:10 Ugly systemd[1]: Dependency failed for /dev/mapper/cryptswap1.
Feb 26 09:52:10 Ugly systemd[1]: dev-mapper-cryptswap1.swap: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
Feb 26 09:52:10 Ugly systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'.
Feb 26 09:52:10 Ugly systemd[1]: systemd-cryptsetup@cryptswap1.service: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
Feb 26 09:52:10 Ugly systemd[1]: dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device: Job dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device/start failed with result 'timeout'.

journalctl 1646 - 1654:

Code: Select all

Feb 26 10:00:30 Ugly systemd[1]: dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device: Job dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device/start timed out.
Feb 26 10:00:30 Ugly systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device.
Feb 26 10:00:30 Ugly systemd[1]: Dependency failed for Cryptography Setup for cryptswap1.
Feb 26 10:00:30 Ugly systemd[1]: Dependency failed for dev-mapper-cryptswap1.device.
Feb 26 10:00:30 Ugly systemd[1]: Dependency failed for /dev/mapper/cryptswap1.
Feb 26 10:00:30 Ugly systemd[1]: dev-mapper-cryptswap1.swap: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
Feb 26 10:00:30 Ugly systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'.
Feb 26 10:00:30 Ugly systemd[1]: systemd-cryptsetup@cryptswap1.service: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
Feb 26 10:00:30 Ugly systemd[1]: dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device: Job dev-disk-by\x2duuid-b21dcddf\x2dd42f\x2d4507\x2d915a\x2d0ac9ffe95790.device/start failed with result 'timeout'.

Somehow I assume that this encrypted swap device, which cannot be started, is the reason why the system spends 3 min. loading userspace.
Yet, I do not use encryption on my systems. So I may have reached the point where my knowledge ends at the moment.

Hm. In the inxi report above, I do not spot any encrypted swap device. In fact, I do not spot any encrypted device at all.
So maybe the solution is as simple as switching off cryptswap in systemd completely.

--
Came across this (German, sorry) thread: systemd-cryptsetup@cryptswap1.service dauert wieder lange trotz Anpassungen
(systemd-cryptsetup@cryptswap1.service takes a long time inspite of modifications).
Suggests we should inspect the files:
+ /etc/fstab
+ /etc/crypttab
+ /etc/initramfs-tools/conf.d/resume
+ the output of "sudo lsblk -f"

So, JBento,
please, execute each of the following 4 terminal commands and post each command and its output.

• cat /etc/fstab
• cat /etc/crypttab
• cat /etc/initramfs-tools/conf.d/resume
• sudo lsblk -f

Karl

[JBento]

So, JBento,
please, execute each of the following 4 terminal commands and post each command and its output.

• cat /etc/fstab
• cat /etc/crypttab
• cat /etc/initramfs-tools/conf.d/resume
• sudo lsblk -f

Karl

Here they are, in the order you asked them. When I installed Mint I selected the option to encrypt the disk, however in the time before I did not encrypted the disk and the problem was still there. Thank you for the help.

Code: Select all

bento@Ugly:~$ cat /etc/fstab
# /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/sdb1 during installation
UUID=7a127700-bdf4-413f-968d-ef2a733653d8 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sdc5 during installation
#UUID=b21dcddf-d42f-4507-915a-0ac9ffe95790 none            swap    sw              0       0
/dev/mapper/cryptswap1 none swap sw 0 0

Code: Select all

bento@Ugly:~$ cat /etc/crypttab
cryptswap1 UUID=b21dcddf-d42f-4507-915a-0ac9ffe95790 /dev/urandom swap,offset=1024,cipher=aes-xts-plain64

Code: Select all

bento@Ugly:~$ cat /etc/initramfs-tools/conf.d/resume
RESUME=UUID=8ff1259c-a590-4c65-965c-f9ef6853b865

Code: Select all

bento@Ugly:~$ sudo lsblk -f
[sudo] password for bento:            
NAME   FSTYPE LABEL           UUID                                 MOUNTPOINT
sda                                                                
├─sda1 ntfs   System Reserved 4E8411008410EC69                     
├─sda2 ntfs   Sistema         70CCCE96CCCE564E                     
└─sda3 ntfs   Arquivos        8EE6FF5EE6FF454D                     
sdb                                                                
└─sdb1 ext4                   7a127700-bdf4-413f-968d-ef2a733653d8 /
sdc                                                                
├─sdc1 ext4                   61ab7797-97ca-4134-b57a-f9eec815c7de 
├─sdc2                                                             
└─sdc5 swap                   2bca6c23-d057-47a2-a7ce-f58fe552d53d 
sr0                                                     

[karlchen]

Hello, JBento.

In a parallel thread, where the same issue occurred which you had reported, but on Mint 18.3, I had analyzed what I think needs fixing in order to slve the issue. I will not repeat what had been explained there, but only point to my post in that other thread here, Re: Mint 18.3 takes too long to startup, for reference.

Next I would like to give you the steps, which will hopefully reduce the system startup time substantially.

1. Open a terminal window, please.
   .
2. Try to disable the systemd service, which tries to find and enable an encrypted swap device, which does not exist.
   Execute the following commandline, please:

   Code: Select all

   sudo systemctl disable systemd-cryptsetup@cryptswap1.service

   In the terminal window, mark the commandline and all the text output, which it will display with your mouse.
   Press <ctrl><shift>C in order to copy the marked text into the clipboard.
   Paste it into your next reply, please.
   .
3. Edit the file /etc/fstab with root permissions. This can be done by executing

   Code: Select all

   xed admin:///etc/fstab

   In the editor xed change the last 3 lines of the file /etc/fstab to read:

   Code: Select all

   # swap was on /dev/sdc5 during installation
   UUID=2bca6c23-d057-47a2-a7ce-f58fe552d53d  none            swap    sw              0       0
   # /dev/mapper/cryptswap1 none swap sw 0 0

   Save. Exit editor xed.
   
   Execute the commandline:

   Code: Select all

   cat /etc/fstab

   Mark the complete output, which will be displayed with your mouse.
   Press <ctrl><shift>C in order to copy the marked text into the clipboard.
   Paste it into your next reply, please.
   .
4. Remove the file /etc/crypttab. This should be done by renaming it with root permission. So its content is kept for later references if need be.
   Command to be executed:

   Code: Select all

   sudo mv /etc/crypttab /etc/crypttab.backup

5. Edit the file /etc/initramfs-tools/conf.d/resume with root permissions. This can be done by executing

   Code: Select all

   xed admin:///etc/initramfs-tools/conf.d/resume

   In xed change the only line in the file /etc/initramfs-tools/conf.d/resume to read:

   Code: Select all

   RESUME=UUID=2bca6c23-d057-47a2-a7ce-f58fe552d53d

   Save. Exit xed.
   .
6. In order to enable the changed resume file, the initrd.img-4.15.0-20-generic has to be rebuilt now. This can be done by executing the following command:

   Code: Select all

   sudo update-initramfs -u

   In the terminal window, mark the commandline and all the text output, which it will display with your mouse.
   Press <ctrl><shift>C in order to copy the marked text into the clipboard.
   Paste it into your next reply, please.
   .
7. Once the command above has terminated successfully, please, reboot the system.
   .
8. After the system has come up again, please, check the startup time using systemd-analyze again and post the screen output here, please.

Hope it will all work out as desired.

Best regards,
Kar

[JBento]

Hey, the first step (disable systemd-cryptsetup) did not return anything on the terminal. After entering my password, it simply jumped to a new line on terminal. But I did the other steps:

Code: Select all

bento@Ugly:~$ cat /etc/fstab
# /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/sdb1 during installation
UUID=7a127700-bdf4-413f-968d-ef2a733653d8 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sdc5 during installation
UUID=2bca6c23-d057-47a2-a7ce-f58fe552d53d  none            swap    sw              0       0
# /dev/mapper/cryptswap1 none swap sw 0 0

In order to enable the changed resume file, the initrd.img-4.15.0-20-generic has to be rebuilt now. This can be done by executing the following command:

Code: Select all

sudo update-initramfs -u

In the terminal window, mark the commandline and all the text output, which it will display with your mouse.
Press <ctrl><shift>C in order to copy the marked text into the clipboard.
Paste it into your next reply, please.

Code: Select all

bento@Ugly:~$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic

After the system has come up again, please, check the startup time using systemd-analyze again and post the screen output here, please

Code: Select all

bento@Ugly:~$ systemd-analyze
Startup finished in 6.456s (kernel) + 21.628s (userspace) = 28.085s
graphical.target reached after 21.622s in userspace

Thank you, man, you did it! It loaded pretty fast now, thank you so much.

[karlchen]

Hello, JBento.

You're welcome. I am really happy to learn that the problem, which you had reported, has been resolved.

Best regards,
Karl
--
P.S.:
You seem to be worried why the very first command, sudo systemctl disable systemd-cryptsetup@cryptswap1.service, did not display any message and returned silently.
Quite a few terminal commands on Linux will do their work silently and display no feedback message, if they succeed.
In case the command sudo systemctl disable systemd-cryptsetup@cryptswap1.service had encountered any problem, it would have displayed a warning or an error message telling you so.
It finished silently, it succeeded.
A bit irritating this behaviour, I admit.