Very slow system startup and shutdown

Hi, Endeavor has been very slow starting up and shutting down the system for a few days. It remains stationary for a few minutes when closing and also when starting up. How do I show you the system startup and shutdown screen, is there a log that can help understand the problem? Thank you

Look here to troubleshoot your slow system yourself, and here on “how to view log-files, and post them here”… :v:

I think these are the logs, sorry if I’m wrong but I’m not an expert. If there are problems and you tell me the specific log you need I will do my best to get them to you. Thanks for now!

To boot as fast as per your systemd-analyze blame is not long at all, imo. Sure, your system is not the latest, but it seems very much ok to run Linux.

Can you post an URL to this?

journalctl -b -0 | grep fail | eos-sendlog

It seems to me that your hard-drive might be getting old, or even be damaged:

apr 13 17:39:21 eduardolp3-endeavour kernel: sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error - auto reallocate failed

More info on such matters.

Maybe I explained myself badly. I’m not complaining about the boot/shutdown speed of the system. There is something that stops the system from closing, when I choose to restart for example, all the processes that the system is closing are printed on the screen, at a certain point everything stops and there is about 2 minutes left to close a process. I would like to be able to print the whole system closing form, how do I do it? System startup/shutdown times are normally very fast but now there is something holding back these operations.

The SSD disk is about a year old, how can I see if it is really damaged?

Please post the output of this:
lsblk -f

And this:
cat /etc/fstab

…and mark the pasted output from your terminal and format it as code, using the symbol </> in your post-editor.


[eduardolp3@eduardolp3-endeavour ~]$ lsblk -f
NAME   FSTYPE FSVER LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
├─sda1 vfat   FAT32             8415-4124                                           
├─sda3 ntfs                     FA3A68C23A687D8F                                    
├─sda4 ntfs                     5C4A12DA4A12B12E                                    
├─sda5 vfat   FAT32             5FCA-4D6E                             510,7M     0% /boot/efi
├─sda6 swap   1                 e9fe1e37-91cc-4933-8ab7-2dba61c68e4f                [SWAP]
├─sda7 ext4   1.0               1aa8d530-b0d6-450a-b51f-6130ad7b7619  115,1G    27% /
└─sda9 ntfs         DELLSUPPORT 30BAFF28BAFEE8EC                                    
[eduardolp3@eduardolp3-endeavour ~]$ 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>
UUID=5FCA-4D6E                            /boot/efi      vfat    defaults,noatime 0 2
UUID=1aa8d530-b0d6-450a-b51f-6130ad7b7619 /              ext4    defaults,noatime 0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
[eduardolp3@eduardolp3-endeavour ~]$

As a quick and dirty fix, what I did was go to


and then uncomment the following line


replacing 90s with 5s.

This is not ideal, but honestly I don’t see what difference it makes if the Watchdog stops after 5 seconds of timing out than after 90 seconds.

What is Watchdog?

A running process that can (sometimes) render the shut-down taking long (90 seconds).

1 Like

Thanks, what about the health of the SSD?

I think the file-system on it (/dev/sda7) is checked on every boot, as per viewing your fstab. So the error in your boot-log may be a one-timer. - To be exactly sure, you’d have to do the
journalctl -b -0 | grep fail
a couple times over to see if it happens again, or not.

In case it happens more often, the drive may be failing. A last resort then would be to re-format it. Or send it back to the vendor.

Ok, grazie!

De nada. :v:

So, as I have been there, I believe your issue is with shutting down mainly.
If you do a cold boot (from power off), it boots normally?
Anyway, please have a look at Restarting -> stop job for user running!
I do not know yet what causes this very long time to shut down.
I hope this helps!
Please let me know if this was of any help.


1 Like

Thank you all for your patience. I transcribe the message it gave me when I restarted the system, the startup no longer has problems. I fixed the problem following theillywriter’s instructions.

[64.408868] watchdog: watchdog0: watchdog did not stop!
[74.437945] system-shutdown[1]: Waiting for preocess: 331 (brltty)
[1712.567217] watchdog: watchdog0: watchdog did not stop!

Using the forum’s search function ( :mag: at top right), there are several topics about brltty among which the following with a solution:

You could also disable watchdog if you wish:

You may find several topics about this as well on the forum

1 Like