unable to select and boot dd cloned SSD identical Disk identifiers and UUID

[ketonik]

I have a Supermicro X11SCZ-F with 2 x 512 GB SSD Samsung SSD 860 Pro (SATA)

Installed configured Clear Linux currently version 30800 to /dev/sda

I made a backup clone to the second Samsung 860 Pro at /dev/sdb

sudo dd if=/dev/sda of=/dev/sdb

(The plan was to have /dev/sdb incrementally backed up possibly with Rsync on a schedule to keep it up to date with the boot SSD /dev/sda in the case sda dies I can switch boot order in BIOS and boot to the clone and get the system back online in production)

The dd command also cloned the following:

Identical Disk identifier: 9231218D-AD76-45B0-A5FB-CF8385DDE26E

All the UUID and PARTUUID

Essentially /dev/sdb is an identical clone to the lowest level.

The issue is, the cloned Samsung SSD 860 Pro does NOT show up in the boot order selection in the BIOS of the Supermicro X11SCZ-F. It is shown to be connected to SATA Port 2 in the BIOS SATA Devices section but not in the Boot Device Order section of BIOS

I suspect at the BIOS board level two storage devices with identical Disk Identifiers and UUID nullify one of the devices.

Booted into Clear Linux we can see the HW Path of the devices

sudo lshw -short
/0/1/0.0.0 /dev/sda disk 512GB Samsung SSD 860
/0/1/0.0.0/1 /dev/sda1 volume 141MiB Windows FAT volume
/0/1/0.0.0/2 /dev/sda2 volume 243MiB Linux swap volume
/0/1/0.0.0/3 /dev/sda3 volume 476GiB EXT4 volume

/0/2 scsi2 storage

/0/2/0.0.0 /dev/sdb disk 512GB Samsung SSD 860
/0/2/0.0.0/1 /dev/sdb1 volume 141MiB Windows FAT volume
/0/2/0.0.0/2 /dev/sdb2 volume 243MiB Linux swap volume
/0/2/0.0.0/3 /dev/sdb3 volume 476GiB EXT4 volume

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 477G 0 disk
├─sda1 8:1 0 142M 0 part
├─sda2 8:2 0 244M 0 part [SWAP]
└─sda3 8:3 0 476.6G 0 part /
sdb 8:16 0 477G 0 disk
├─sdb1 8:17 0 142M 0 part
├─sdb2 8:18 0 244M 0 part
└─sdb3 8:19 0 476.6G 0 part

sudo dmesg | grep 'SATA link down'
[ 0.946077] ata4: SATA link down (SStatus 0 SControl 300)
[ 0.946120] ata1: SATA link down (SStatus 0 SControl 300)
[ 0.951148] ata6: SATA link down (SStatus 0 SControl 300)
[ 0.951194] ata5: SATA link down (SStatus 0 SControl 300)

Interestingly the above shows ata links down assuming only ata2 and ata3 are UP

The Supermicro X11SCZ-F Boot/Boot Option displays:
UEFI OS P1: Samsung SSD 860 Pro 512GB) (SATA,Port:2)

Im assuming /dev/sdb is on ata3

With all this info, in a production environment it would be required to have this cloned SSD on ata3 visible and selectable as a boot option in the BIOS.

I'm assuming the issue is because the clone sdb has identical:
Disk identifier
UUID
PARTUUID

If this assumption is correct does anyone have a method to resolve this?

I can use uuidgen to create a UUID and use
sudo tune2fs /dev/sdb -U

Apparently this can only be done on the partitions Swap sdb2 and Root sdb3.
Apparently not possible to do on EFI boot sdb1

sudo tune2fs /dev/sdb -U 83c810bd-6f03-405b-9a38-fabd9a6e0ecb
tune2fs 1.45.3 (14-Jul-2019)
tune2fs: Bad magic number in super-block while trying to open /dev/sdb
/dev/sdb contains `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,1), end-CHS (0x3ff,254,63), startsector 1, 1000215215 sectors, extended partition table (last)' data

Then there is the issue and question about changing the
Disk identifier: 9231218D-AD76-45B0-A5FB-CF8385DDE26E

I've not found any information anywhere on how to change the Disk identifier

If anyone has any knowledge of this situation and issue and you have solutions to resolve
1-ability to for BIOS to detect and select the cloned SSD as a boot device
2-any methods to achieve this if it is indeed a requirement to create unique
Disk identifier
UUID
PARTUUID

Perhaps there's an alternative disk clone/bootable backup solution I should have used that wouldn't create identical identifiers as above? FYI I did also try Clonezilla, it also cloned the UUID's and Disk Identifiers :-(

Enormously appreciated for any knowledge.