Boot timeout on non-existent device

[Patrick O'Callaghan]

On booting, I get a pause of around 90 seconds, and the following
messages in the journal:

Aug 17 13:40:58 bree systemd[1]: dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd\x2d8633\x2d1cf878c6b2a1.device: Job dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd\x2d8633\x2d1cf878c6b2a1.device/start timed out.
Aug 17 13:40:58 bree systemd[1]: Timed out waiting for device /dev/disk/by-uuid/1431e6d2-531e-46cd-8633-1cf878c6b2a1.
Aug 17 13:40:58 bree systemd[1]: Dependency failed for Resume from hibernation using device /dev/disk/by-uuid/1431e6d2-531e-46cd-8633-1cf878c6b2a1.
Aug 17 13:40:58 bree systemd[1]: systemd-hibernate-resume@dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd\x2d8633\x2d1cf878c6b2a1.service: Job systemd-hibernate-resume@dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd>
Aug 17 13:40:58 bree systemd[1]: dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd\x2d8633\x2d1cf878c6b2a1.device: Job dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd\x2d8633\x2d1cf878c6b2a1.device/start failed with r>

However the UUID being flagged is not one of the devices I have:

$ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Aug 17 13:40 15d273c5-488c-48d6-a864-e11968ee970e -> ../../sda4
lrwxrwxrwx 1 root root 10 Aug 17 13:41 1C36E53036E50B98 -> ../../sdc5
lrwxrwxrwx 1 root root 10 Aug 17 13:41 2224823A248210C9 -> ../../sdc4
lrwxrwxrwx 1 root root 10 Aug 17 13:40 4a81c9ba-d8b0-48ab-af60-714a53842c48 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug 17 13:40 6496d6da-6b7a-4cdd-9bb8-767c08d1c84e -> ../../sdb1
lrwxrwxrwx 1 root root 10 Aug 17 13:40 6881-A320 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Aug 17 13:40 6a9a800c-309b-4b69-b269-884ad495e7b9 -> ../../sda3
lrwxrwxrwx 1 root root 10 Aug 17 13:41 6d5929d8-fd35-49e6-a8bf-aab5309dad77 -> ../../sda1
lrwxrwxrwx 1 root root 10 Aug 17 13:40 DEC47E01C47DDBE9 -> ../../sdc1

So where is this coming from? The mention of "hibernation" in the third
message above is curious, as I'm not using hibernation.

poc

[Tom Horsley]

On Sat, 17 Aug 2019 14:07:52 +0100
Patrick O'Callaghan wrote:
> However the UUID being flagged is not one of the devices I have:

Run blkid as root to be sure. Sounds very much like the
kernel believes there is a swap area with that uuid which
has a hibernate image it is trying to restore.

[Tom Horsley]

On Sat, 17 Aug 2019 14:07:52 +0100
Patrick O'Callaghan wrote:
> However the UUID being flagged is not one of the devices I have:

Also check your grub.cfg file to see if there is some
leftover nonsense in there that mentions that uuid.

[Patrick O'Callaghan]

On Sat, 2019-08-17 at 11:25 -0400, Tom Horsley wrote:
> On Sat, 17 Aug 2019 14:07:52 +0100
> Patrick O'Callaghan wrote:
> > However the UUID being flagged is not one of the devices I have:
>
> Also check your grub.cfg file to see if there is some
> leftover nonsense in there that mentions that uuid.

Good catch, that was it.

Thanks.

poc