dustymabe added a new comment to an issue you are following: ``
That said Anaconda should be injecting the rd.lvm.lv bits on the kernel commandline and wait till they're probed.
I definitely see them on the command line
``` Oct 17 23:04:11 localhost kernel: Command line: BOOT_IMAGE=/ostree/fedora-atomic-8f228e830fca568a137305e295ef96bafa0d08b0e27aa8c133a3bd24fff07280/vmlinuz-4.18.12-300.fc29.x86_64 resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap root=/dev/mapper/fedora-root ostree=/ostree/boot.0/fedora-atomic/8f228e830fca568a137305e295ef96bafa0d08b0e27aa8c133a3bd24fff07280/0 ```
Ahh...I have an idea; ordinarily nothing else in the initramfs is waiting for devices; the systemd fstab generator will handle /etc/fstab in the initramfs and make proper device/mount units for them. But now the resume generator is going out and running before dracut waits for devices or so?
yeah that seems to be the case at least from my log output in https://pagure.io/atomic-wg/issue/513#comment-536727
OK so I can definitely reproduce this if I tweak the current FCOS config/image.ks to use LVM and have a swap partition.
+1.. I'll dig into dracut a bit. Maybe we just disable `systemd-hibernate-resume.service` on ostree systems for now, but there might be some people on silverblue that want it. Not sure. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/513