A system with a root file system on a multipath device does not start normally

Issue

• In our environment, the root file system is built on a multipath device. There were occasional boot failures that resulted in the system entering Emergency mode. We found that the root device was configured with a UUID on the kernel command line. Therefore, the root device was incorrectly identified as a device that is part of a multipath, not a multipath device.

[    0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-4.18.0-372.9.1.el8.x86_64 root=UUID=edbb1349-a970-4b3f-9ed3-524a1db97976 ...
:
[  OK  ] Started File System Check on /dev/d…edbb1349-a970-4b3f-9ed3-524a1db97976.
         Mounting /sysroot...
[   16.607900] sd 3:0:1:0: Power-on or device reset occurred
[   16.627118] device-mapper: multipath service-time: version 0.3.0 loaded
[   16.644975] SGI XFS with ACLs, security attributes, quota, no debug enabled
[   16.654829] /dev/sdc3: Can't open blockdev
[FAILED] Failed to mount /sysroot.
See 'systemctl status sysroot.mount' for details.
[DEPEND] Dependency failed for Initrd Root File System.
[DEPEND] Dependency failed for Reload Configuration from the Real Root.

How should I solve it?