resume errors with LVM?

[cboettig]

Anyone else experience resume errors after configuring a distro using LVM?

I see the following error on startup

Failed to connect to lvmetad. Falling back to device scanning.

this is mostly annoying because it seems the lvmetad connection waits 30 seconds before it gives up and falls back on device scanning, creating a 30 sec delay in boot or resume from sleep. I believe it is this confirmed bug in Ubuntu Bionic: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230, the work-around of deleting /etc/initramfs-tools/conf.d/resume seems to eliminate the wait time for boot but not for resume?

[mpalourdio]

I have had this problem after a dist upgrade. My swap partition had the wrong uuid.

I think I did something like that to fix it : https://forums.linuxmint.com/viewtopic.php?t=242867

Edit : I have found the exact post that solved my problem : https://forums.linuxmint.com/viewtopic.php?t=277375

I have found the problem / solution.
There was a wrong UUID of the swap-drive in /etc/initramfs-tools/conf.d/resume.
I have absolutely no clue, where it came from.
Was it me?! Was it the installation-/configuration-process of the OS?!
I took the correct UUID from blkid and put it into resume.
After this, i ran sudo update-initramfs -u.

[cboettig]

Hmm, I've tried setting the UUID for the swap (given by blkid) in /etc/initramfs-tools/conf.d/resume and in /etc/fstab, but still see this same delay. (seems like some other users do as well: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/comments/69). Not sure if this is under the scope of the kernel, I'm running 4.19.7 to resolve #109 ...

[mpalourdio]

Well no idea then. That what fixed my long boot delay :/