I am experiencing a boot slowdown in my bootup of Bodhi 5.0.0. I see the following message:

A start job is running for dev-disk-by/x2duuid-ib0bf28/x2e40e7/x2e9bad/x2e5cc3rr411e862.device (1s / 1min 30sec)

I counts down exactly 90 seconds before continuing.

Why is there a 90-second countdown for something I don't recognize?

I have tried to type the message correctly but may have typoed somewhere.

A search doesn't bring up the Bodhi-specific answer you most likely want, so I hope there will be more replies from our forum experts ... but while you are waiting for them to 'chime in' you may want to look here and see if any of what you will read fits your case. What you will read goes beyond the 'why' of your question and suggests a variety of fixes that have worked for others, for both Debian-related and non-Debian GNU-Linux operating systems.

Note, the fourth down from the top in the search results does mention a 'slow boot', and that one is Ubuntu-related. With DDG, your search results should be the same as what I just saw.

1 members found this post helpful.

By any chance, have you formatted/used an encrypted USB/removable device?? If so, there may be an entry in /etc/crypttab, which is now waiting for that device to come online...which it won't, since its been removed. You can safely remove that offending line from that file...but if there are others, do NOT touch them, unless you know what you're doing.

You can also look in your /etc/fstab file for that line; if found, copy that file to another location, and then only remove that one line. And be sure to have a bootable media nearby, in case of problems.

1 members found this post helpful.

This is systemd doing something with the disk referenced. You can look in the logs (journalctl) to see if they provide more detail. Some folks get messages like this on shutdown as well: 90 seconds seems to be the wait time used by systemd in general when something doesn't happen immediately.

1 members found this post helpful.

similarly to journalctl dmesg can show system log entries. i mention that because my journalctl list goes on over 1000 lines. with dmesg you can add a level option (maybe journalctl as well. i'm just not as familiar with it) to see a bit less info that may prove to be helpful with (usually a shorter list for me) or

You can get journalctl to show entries in reverse order (newest at top) but I can't remember how: "b" switch maybe.

1 members found this post helpful.

also a good idea. looks like -r --reverse shows newest entries (from the man page), -f --follow shows most recent entries and

Generally this is because you have an entry in fstab with this UUID that is no longer valis - swap is usually the best bet, especially if you have re-installed. Also look at your boot options - notably the "resume=...".

1 members found this post helpful.

Nope. Don't even know how to do that.

The most promising comment I saw was that systemd can't find the /data location; the is to remove /data from fstab ... and I'm too stupid to know how to do that.

A couple of those articles said to use Ctrl-C to stop the process on a one-time basis. I'm here to say it doesn't work.

Fire up a terminal, run these and post the output - all of it.

2 members found this post helpful.

No, you are not stupid!! I can guarantee, no one on this forum was born knowing how to edit fstab. Look at this!

First step, backup fstab to something like fstab.old. After the renaming, the operating system will ignore it, but you can always reactivate it by bringing back the original name.

With the fstab file open in a text editor, instead of deleting lines straight-away, do this:
# The following line was inactivated on (date)
# The line you want to delete is here.

Then save.
Any line beginning with #[space] becomes a comment line, and so is ignored with the OS reads the file. After some time has passed and all is well, you can always come back to 'tidy up' the entries by really deleting them.

2 members found this post helpful.

So instead of asking how, you don't even consider it? Those are just two, plain-text files...nothing special. You can just type:
...and there they are. Look for a matching line in either...if you find one, type in "sudo vi /etc/<whatever file has the line". Arrow down to that line. Press ":dd" to remove it. Press ":wq" to save and exit. Done.

Before changing either, copy those file somewhere else. Use the cp command to do that: "sudo cp /etc/fstab /etc/old-fstab" is a good example.

1 members found this post helpful.

zaivala@zaivala-ThinkPad-T430:~$ journalctl -b 0 | grep -i uuid
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start timed out.
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device.
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: Dependency failed for /dev/disk/by-uuid/1b0b9f28-4745-40e7-9bad-5cc3ff41e862.
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap/start failed with result 'dependency'.
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start failed with result 'timeout'.
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: Listening on UUID daemon activation socket.
Apr 17 05:34:18 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start timed out.
Apr 17 05:34:18 zaivala-ThinkPad-T430 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device.
Apr 17 05:34:18 zaivala-ThinkPad-T430 systemd[1]: Dependency failed for /dev/disk/by-uuid/1b0b9f28-4745-40e7-9bad-5cc3ff41e862.
Apr 17 05:34:18 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap/start failed with result 'dependency'.
Apr 17 05:34:18 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start failed with result 'timeout'.
Apr 17 05:38:22 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start timed out.
Apr 17 05:38:22 zaivala-ThinkPad-T430 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device.
Apr 17 05:38:22 zaivala-ThinkPad-T430 systemd[1]: Dependency failed for /dev/disk/by-uuid/1b0b9f28-4745-40e7-9bad-5cc3ff41e862.
Apr 17 05:38:22 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap/start failed with result 'dependency'.
Apr 17 05:38:22 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start failed with result 'timeout'.
Apr 17 05:48:56 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start timed out.
Apr 17 05:48:56 zaivala-ThinkPad-T430 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device.
Apr 17 05:48:56 zaivala-ThinkPad-T430 systemd[1]: Dependency failed for /dev/disk/by-uuid/1b0b9f28-4745-40e7-9bad-5cc3ff41e862.
Apr 17 05:48:56 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap/start failed with result 'dependency'.
Apr 17 05:48:56 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start failed with result 'timeout'.
zaivala@zaivala-ThinkPad-T430:~$ 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/sda4 during installation
UUID=f243d2a0-bbfc-4917-a06d-04fc714a5d3d / ext4 errors=remount-ro 0 1
# swap was on /dev/sda1 during installation
UUID=1b0b9f28-4745-40e7-9bad-5cc3ff41e862 none swap sw 0 0
zaivala@zaivala-ThinkPad-T430:~$