A start job that makes startup after boot take 1.5 minute

Hello all,
I have this issue on the KDE version of EOS where my boot time is a literal 3 - 5 minutes because a stop and a start job. I have managed to block watchdog (it is what is causing the stop job) using modprobe.d, but the start job can’t be stopped, as it is not related to watchdog. It is a process that mentions /dev/disk/by-uuid/. I do have 3 drives in my machine. One NVME SSD that has the root and boot partitions on it and is running btrfs. A second sata ssd that has the /home partition (ext4), and a third one that I use for games and steam (ext4). I made the last one mount automatically by adding it to fstab and all that jargon. I’m not sure how to stop this from stopping the system from starting for 2 minutes every time I restart, or is it even ok to stop that job since it looks like it is mounting drives?:confused: . It is very frustrating, and I would love your help to solve it. Thank you for any help.


Operating System: EndeavourOS
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.5.9-arch2-1 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: A520I AC
System Version: -CF

Can we see the contents of /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=ba0dea00-f5fc-49c0-a067-fc988d5c4295 /boot          ext4    defaults,noatime 0 2
UUID=B178-A406                            /boot/efi      vfat    defaults,noatime 0 2
UUID=8666b0ee-2e9c-4f0e-bb7c-70e9dbf6867b /              btrfs   subvol=/@,defaults,noatime,compress=zstd 0 0
UUID=8666b0ee-2e9c-4f0e-bb7c-70e9dbf6867b /var/cache     btrfs   subvol=/@cache,defaults,noatime,compress=zstd 0 0
UUID=8666b0ee-2e9c-4f0e-bb7c-70e9dbf6867b /var/log       btrfs   subvol=/@log,defaults,noatime,compress=zstd 0 0
UUID=e482995c-a000-4681-b0f6-21c1a7631fd8 /home          ext4    defaults,noatime 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
# Games drive
UUID=1bdaf90c-50b0-4bc2-8364-6bf9ae6e8807	/Drives/Games	ext4	defaults	0	0

Now, compare the UUIDs there to the UUID that is having the slow start and determine which one it is.

There isn’t one uuid that shows up on the start job, it is several that keep recycling. It is as if the system is going through the drives one by one to make sure they start/mount

What does this show?

systemd-analyze critical-chain

How about:

journalctl -x -b | grep /dev/disk

sudo blkid


systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @3.803s
└─multi-user.target @3.803s
  └─cups.service @3.745s +57ms
    └─network.target @3.744s
      └─wpa_supplicant.service @3.736s +7ms
        └─dbus.service @3.208s +41ms
          └─basic.target @3.206s
            └─sockets.target @3.206s
              └─virtlogd.socket @3.206s
                └─sysinit.target @3.203s
                  └─systemd-timesyncd.service @3.173s +29ms
                    └─systemd-tmpfiles-setup.service @2.934s +199ms
                      └─local-fs.target @2.866s
                        └─boot-efi.mount @2.509s +354ms
                          └─boot.mount @1.693s +5ms
                            └─systemd-fsck@dev-disk-by\x2duuid-ba0dea00\x2df5fc\x2d49c0\x2da067\x2dfc988d5c4295.service @1>
                              └─dev-disk-by\x2duuid-ba0dea00\x2df5fc\x2d49c0\x2da067\x2dfc988d5c4295.device @584542y 2w 2d>
lines 1-20/20 (END)

journalctl -x -b | grep /dev/disk gives this:

journalctl -x -b | grep /dev/disk
Nov 01 15:25:56 kalzi-EOS systemd[1]: Starting File System Check on /dev/disk/by-uuid/8666b0ee-2e9c-4f0e-bb7c-70e9dbf6867b...
Nov 01 15:25:56 kalzi-EOS systemd[1]: Finished File System Check on /dev/disk/by-uuid/8666b0ee-2e9c-4f0e-bb7c-70e9dbf6867b.
Nov 01 15:25:58 kalzi-EOS systemd[1]: Starting File System Check on /dev/disk/by-uuid/B178-A406...
Nov 01 15:25:58 kalzi-EOS systemd[1]: Starting File System Check on /dev/disk/by-uuid/ba0dea00-f5fc-49c0-a067-fc988d5c4295...
Nov 01 15:25:58 kalzi-EOS systemd[1]: Starting File System Check on /dev/disk/by-uuid/e482995c-a000-4681-b0f6-21c1a7631fd8...
Nov 01 15:25:58 kalzi-EOS systemd[1]: Finished File System Check on /dev/disk/by-uuid/ba0dea00-f5fc-49c0-a067-fc988d5c4295.
Nov 01 15:25:58 kalzi-EOS systemd[1]: Finished File System Check on /dev/disk/by-uuid/B178-A406.
Nov 01 15:25:58 kalzi-EOS systemd[1]: Finished File System Check on /dev/disk/by-uuid/e482995c-a000-4681-b0f6-21c1a7631fd8.
[kalzi@kalzi-EOS ~]$

sudo blkid gives this:

/dev/nvme0n1p3: UUID="274fa7e8-dd19-4dc6-8d46-d42cbfae90b4" TYPE="swap" PARTUUID="9573f066-ef49-4fed-b814-8224ba06282d"
/dev/nvme0n1p1: UUID="ba0dea00-f5fc-49c0-a067-fc988d5c4295" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e5ed9e69-af04-41f8-9eb2
/dev/nvme0n1p4: LABEL="@" UUID="8666b0ee-2e9c-4f0e-bb7c-70e9dbf6867b" UUID_SUB="e0fc96a9-094d-4c1b-a0c3-3c9b17f3b30a" BLOCK
_SIZE="4096" TYPE="btrfs" PARTUUID="b09c224e-ac92-4e8e-a392-7cf93235e4ff"
/dev/nvme0n1p2: UUID="B178-A406" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="a2c4d1a0-1c96-433c-aa65-cafe0568755a"
/dev/sdb: LABEL="Games" UUID="1bdaf90c-50b0-4bc2-8364-6bf9ae6e8807" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sda1: UUID="e482995c-a000-4681-b0f6-21c1a7631fd8" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9f34a9e3-050e-bc42-97a2-8c97
1 Like

I have this exact problem and I use KDE Plasma as well. Another user on a different thread concluded it was my device. I ended up RMA’ing the device with warranty and it still happens lol.

It is definitely not your device. I have always had extra drives, and never had this issue until recently. Something has certainly changed that I can’t find.

I feel it started occurring about one month ago. It was fine before that. Hopefully we can help the developers pinpoint the problem so they can push a fix.

I’m willing to test the crap out of it to fix it. I think it is a KDE thing, though. I don’t remember it ever happening on gnome. Not sure about that, just anecdotal.

It must be a KDE issue. I tested a few other distros with other DE’s on this same device and the issue did not persist. So yeah, I agree.

Tried solution from here? https://www.reddit.com/r/archlinux/comments/10bpx6o/painfully_slow_startup_kdeplssma/

CC @Kundalini

It appears his solution is xorg drivers? I have an Intel GPU, and it sounds like he does too. Hmm, but why all of a sudden and not over a month ago? Nothing changed other than updating the system.


The fix from the link you provided seems to be installing xf86-video-intel, but I have all AMD, is this still a viable solution?

I’m afraid to even install the xorg drivers despite having Intel ARC GPU. I am going to wait until it happens again, so I can post logs and be sure. My system took way too long to set up to where it is now to screw it up.

So, I bit the bullet and installed that xf86-video-intel driver, even though I have all AMD. It seems to have fixed the issue so far. Now, I have another problem, my wireless keyboard and mouse take about 1.5 minutes to respond on SDDM after a reboot, now I have to sit there for 1.5 minutes until they respond, so I can log into my PC :joy:

You’re certainly braver than I am :joy:

I hope it’s not a false flag for you because sometimes it appears to be “fixed” but it just randomly occurs again. That’s been my experience, at least