Very slow boot - something hanging at boot w/ long timeout

General system Newbie
1

Unfortunately, whatever it is flashes by really fast before I can see what it is. All I can see is that whatever it is is something that throws an error and apparently has a really long timeout. Here is my bootlog: https://clbin.com/mBakx

Thanks for any help you can give.

2

Can we see the output of:

systemd-analyze
systemd-analyze critical-chain
systemctl list-units --failed
3

systemd-analyze
Startup finished in 12.270s (kernel) + 1min 30.862s (userspace) = 1min 43.133s
graphical.target reached after 1min 30.590s in userspace

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 @1min 30.590s
└─lightdm.service @1min 30.567s +21ms
└─systemd-user-sessions.service @1min 30.563s +3ms
└─nss-user-lookup.target @1min 30.592s

systemctl list-units --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.

4

Also:

 systemd-analyze blame
5

systemd-analyze blame
650ms mnt-68E2A87AE2A84DDE.mount
428ms dev-sda5.device
290ms tlp.service
249ms cups.service
194ms accounts-daemon.service
177ms udisks2.service
146ms polkit.service
119ms systemd-journal-flush.service
111ms ldconfig.service
105ms user@1000.service
90ms upower.service
89ms systemd-udevd.service
79ms systemd-rfkill.service
62ms systemd-udev-trigger.service
59ms lvm2-monitor.service
53ms colord.service
48ms NetworkManager.service
45ms systemd-journald.service
41ms systemd-tmpfiles-setup.service
36ms systemd-tmpfiles-setup-dev.service
31ms avahi-daemon.service
29ms systemd-logind.service
28ms dbus.service
28ms systemd-timesyncd.service
25ms systemd-tmpfiles-clean.service
25ms systemd-sysusers.service
23ms systemd-fsck@dev-disk-by\x2duuid-d99157f7\x2d4be7\x2d461e\x2d97c2\x2d9315e7eef116.service
21ms lightdm.service
17ms systemd-modules-load.service

6

How about cat /etc/fstab

This is likely the issue:

Apr 06 14:32:58 Desktop systemd[1]: dev-disk-by\x2duuid-13ce1f6e\x2dda1c\x2d419d\x2d8a48\x2dc4f8e7d13ebd.device: Job dev-disk-by\x2duuid-13ce1f6e\x2dda1c\x2d419d\x2d8a48\x2dc4f8e7d13ebd.device/start timed out.
Apr 06 14:32:58 Desktop systemd[1]: Timed out waiting for device /dev/disk/by-uuid/13ce1f6e-da1c-419d-8a48-c4f8e7d13ebd.
Apr 06 14:32:58 Desktop systemd[1]: Dependency failed for /dev/disk/by-uuid/13ce1f6e-da1c-419d-8a48-c4f8e7d13ebd.
7

Yeah, that seems right.

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).

UUID=987f0e17-f8f3-4007-985d-9d801070a0dc / ext4 defaults,noatime 0 1
UUID=13ce1f6e-da1c-419d-8a48-c4f8e7d13ebd swap swap defaults,noatime 0 0
UUID=d99157f7-4be7-461e-97c2-9315e7eef116 /home ext4 defaults,noatime 0 2
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
/dev/disk/by-uuid/68E2A87AE2A84DDE /mnt/68E2A87AE2A84DDE auto nosuid,nodev,nofail,x-gvfs-show 0 0

8

That is an odd mount. I guess some tool created that for you?

Can you share this last thing?

lsblk -o name,size,fstype,mountpoint,uuid
9

lsblk -o name,size,fstype,mountpoint,uuid
NAME SIZE FSTYPE MOUNTPOINT UUID
sda 111.8G
├─sda1 81.6G ntfs 3E02B9BA02B9780B
├─sda2 1K
├─sda5 19.2G ext4 / 987f0e17-f8f3-4007-985d-9d801070a0dc
├─sda6 10G ext4 /home d99157f7-4be7-461e-97c2-9315e7eef116
└─sda7 1G swap fee8196d-f30b-4c25-9069-92e3b9eac260
sdb 3.6T
├─sdb1 128M
└─sdb2 3T ntfs /mnt/68E2A87AE2A84DDE 68E2A87AE2A84DDE
sr0 1024M

10

So, your ntfs partition is timing out.

I would convert it to a systemd-automount.

Replace the last line of your /etc/fstab with something like this:

UUID=68E2A87AE2A84DDE /mnt/68E2A87AE2A84DDE ntfs-3g defaults,noauto,x-systemd.automount,x-systemd.idle-timeout=30min,windows_names,uid=1000,gid=1000,umask=0022,fmask=0022 0 0

Before rebooting, make sure you test it.

sudo umount /mnt/68E2A87AE2A84DDE
sudo mount /mnt/68E2A87AE2A84DDE
11

Same thing happening still. This time I managed to get a screenshot of the error using my phone. It’s my swap partition that’s the problem:
error

12

The UUID of your swap partition is wrong.

Edit /etc/fstab and change it to: fee8196d-f30b-4c25-9069-92e3b9eac260

13

Hooray! It worked! You’re awesome, thank you!! BTW, do you have any idea why fstab had the wrong UUID?

14

My bet would be either your fstab or your UUID changed. :wink:

15

Well, I mean, yeah, but why? Edit: never mind the question, I’m guessing it happened when I deleted and remade my swap partition.

16

Well…yeah…that would definitely cause it to change :rofl:

1 Like
17

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.