On Mon, Jun 17, 2019 at 3:58 AM Lennart Poettering wrote:
>
> On Sa, 08.06.19 15:34, Chris Murphy (li...@colorremedies.com) wrote:
>
> > However, in the failing case, that doesn't happen, and systemd hangs
> > indefinitely waiting for it to appear. And in the early debug shell,
> > 'blkid' sees it
On Sa, 08.06.19 15:34, Chris Murphy (li...@colorremedies.com) wrote:
> However, in the failing case, that doesn't happen, and systemd hangs
> indefinitely waiting for it to appear. And in the early debug shell,
> 'blkid' sees it. That means the kernel and libblkid see it. I've got
> no idea why sy
Best as I can tell, for some reason the failure case, systemd doesn't
see the formatted swap device appear.
In a working case it looks like this:
[ 23.310555] flap.local systemd[1]:
dev-disk-by\x2duuid-dcae3053\x2d1cc2\x2d4890\x2da33b\x2d6d71b3dc97df.device:
Changed dead -> plugged
[ 23.310639
Hi,
I'm having a heck of a time trying to troubleshoot an indefinite hang
on startup due to setting up crypto swap on one of my laptops. At this
point it seems computer specific. I can't reproduce it on two other
(dissimilar) computers or any qemu-kvm VM.
Without any debugging enabled, the proble