Only one system I've encountered exhibits this problem, the
lenovo st250v2. When I boot normally, all the devices are
found and boot succeeds.
When I boot through tboot, DM does not seem to be able to
find the root and swap devices.
Below are bootlog snippets from a successful boot and a failing
boot.
Can somebody tell me where to look for the source of this failure?
Is there debug code or DM utilities to help identify the problem?
Is there source code I can implement to isolate the failure point?
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
[ 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.
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/dm-devel
