Problem with IPL of cloned SLES15 SP5 running in LPAR in remote location

I have a mainframe machine in location A, where the SLES15 SP5 system is running on LPAR on disks 9f0d-9f15. The /etc/fstab file in location A is shown below. The system is cloned to location B on DASD disks with addresses 2100-2108. What to do and how to configure SLES15 SP5 in location A so that it starts in location B from disks 2100-2108. The IPL of the SLES15 SP5 system in location B tries to mount the disk with address 9f0e to /boot. Disks 9f0d-9f15 are not available in location B. Additional information is that the systems after interrupting the cloning process (using the Hitachi Universal Replicator) should work in both locations. Editing files in location B is difficult because the system starts on the HMC console of the mainframe processor in the “Operating System Messages” window

sles15l2:~ # cat /etc/fstab
/dev/vg_root/lv_root / ext4 defaults 0 1
/dev/vg_system/lv_var /var ext4 data=ordered 0 2
/dev/vg_system/lv_usr /usr ext4 data=ordered 0 2
/dev/vg_system/lv_tmp /tmp ext4 data=ordered 0 2
/dev/vg_boss/lv_opt /opt ext4 data=ordered 0 2
/dev/vg_system/lv_home /home ext4 data=ordered 0 2
/dev/disk/by-path/ccw-0.0.9f0e-part1 /boot ext4 data=ordered 0 2