clonezilla /dev/sda 순서 랜덤으로 바뀌는 현상에 대해서

[동우]

https://drbl.org/fine-print.php?path=./faq/2_System/133_random_block_device_name.faq#133_random_block_device_name.faq 

The name of block devices change randomly after booting Clonezila live. Sometimes sda, sometime sdb, or sdc. Why?

This is due to a change in Linux kernel 5.3, and it's a feature, not a bug.
In this article, this behavior of Linux kernel is well described. Of course, there are some ways to set the persistent names for block devices, as mentioned here.

However, the methods mentioned are not feasible for Clonezilla live. We have no idea about the live system will run on which block devices.

Clonezila 라이브 부팅 후 블록 장치의 이름이 무작위로 변경됩니다. 때로는 sda, 때로는 sdb 또는 sdc. 왜요?

이것은 Linux 커널 5.3의 변경으로 인한 것이며 버그가 아니라 기능입니다.
이 기사에서는 Linux 커널의 이러한 동작에 대해 잘 설명합니다. 물론 여기에 언급된 것처럼 블록 장치의 영구 이름을 설정하는 몇 가지 방법이 있습니다.

그러나 언급된 방법은 Clonezilla 라이브에 적합하지 않습니다. 라이브 시스템이 어떤 블록 장치에서 실행될지는 알 수 없습니다.

병렬로 되기 때문에 불가능 하다고

my name is Michael, I'm Senior Support Engineer in SUSE Support Services.
Thank you for your feedback. It's an interesting suggestion which could make life easier, I agree.
No one likes to write down 58something characters as a device name where sda can be typed in a splitsecond.

Unfortunately it's not that easy, if not impossible to have that as a general approach.
Until 5.3 the kernel went through all pci busses sequentially and activated the storage adapters one by one.
Then it was by e.g. the SATA host adapter to activate the devices that were connected to it.
Next one may have been a fiberchannel host and so on

There was a good chance, the SATA with only a couple devices was faster than the fiberchannel and then SATA got sda and sdb and maybe sdc

Since 5.3 the kernel starts recognition in parallel all over the system, there is no serialization anymore and it's completely unpredictable which device appears first. Sadly there is no way to turn that off again for all users, or make that destinction you suggest

In case you have only a small number of device, you can "hardcode" the device names via a handcrafted udev rule.

I cannot make specific suggestions as I  don't know anything about your system, but you should be able to write a udev rule with the examples in
/usr/lib/udev/rules.d/60-persistent-storage.rules

with the scsi_id  command you can find out any values you need for your rule and then place your rules file in /etc/udev/rules.d/ and name it like 40-my-scsi.rules. Make sure to recreate the initrd (mkinitrd, resp. "dracut -f")

Note: this has the potential to make the system unbootable, so make sure to have a plan B and a rescue system from which you can reset the custom rule.