mmcblk numbers change each boot

[Arty Face]

I'm using clonezilla-live-20221023-jammy-amd64
I have an x86_64 SBC with a single emmc drive I need to image and then restore to multiple devices

Each time I boot clonezilla, the mmcblk is detected differently it should be mmcblk0 and should always be mmcblk0 since it is the only mmcblk device. But sometimes it is detected as mmcblk1 or mmcblk2

I'm trying to script this so the restore can happen automatically with no user intervention, but if the mmcblk number does not match then it errors.

Is there anyway to force it to always only find mmcblk0? I assume this come from the kernel, but why would it misnumber the only existing mmcblk?

I tried in my script to set the install target to whatever mmckblk was detected, and this stops the errors, seems to rename the partitions properly but it results in an unbootable system at the end, not configuring grub correctly maybe? The ubuntu 20.04 image that is on the device always correctly identifies the only mmcblk as mmcblk0, so not sure why the clonezilla kernel is misnumbering it, and why it can be different at each boot.

[Steven Shiau]

It's annoying to us, too. This is actually related to Linux kernel... I wish there is a good way to deal with this...
Please check this:
https://drbl.org/fine-print.php?path=./faq/2_System/133_random_block_device_name.faq#133_random_block_device_name.faq

Steven