On Mon, Jun 06, 2022 at 11:43:58AM -0400, Tony Camuso wrote: > Successful bootlog snippet: > > [ 3.843911] sd 5:0:0:0: [sda] Attached SCSI disk > [ 3.848370] sd 6:0:0:0: [sdb] Attached SCSI disk > [ 3.925639] md126: detected capacity change from 0 to 1900382519296 > [ 3.946307] md126: p1 p2 p3 Are the MD array partitions being used as the PVs for the rhel_lenovo volume group? It's the major difference in the two snippets other than timing, and would account for why the volume group cannot be discovered in the tboot case. > [ OK ] Found device /dev/mapper/rhel_lenovo--st250v2--02-root. > [ OK ] Reached target Initrd Root Device. > [ OK ] Found device /dev/mapper/rhel_lenovo--st250v2--02-swap. > Starting Resume from hibernation us…r/rhel_lenovo--st250v2--02-swap... > [ OK ] Started Resume from hibernation usi…per/rhel_lenovo--st250v2--02-swap. > [ OK ] Reached target Local File Systems (Pre). > > Failing bootlog snippet: > > [ 4.578205] sd 5:0:0:0: [sda] Attached SCSI disk > [ 4.581000] sd 6:0:0:0: [sdb] Attached SCSI disk > [ TIME ] Timed out waiting for device dev-ma…dst250v2\x2d\x2d02\x2dswap.device. > [DEPEND] Dependency failed for Resume from h…per/rhel_lenovo--st250v2--02-swap. Any differences in kernel command line/dracut arguments between the two cases? Especially the rd.md.* bits? Regards, Bryn. -- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
