Post by Jani on Sept 15, 2016 18:40:24 GMT
As you are using legacy Clover then the sequence is as follow:
1. BIOS started MBR zero sector from the drive you choose to boot. This is disk2. There is a boot0af boot sector written into.
2. This program boot0af search for EFI System Partition on the drive, load sector 1 from the partition and start it. There is boot1f32 boot sector written into.
3. This program boot1f32 search for a file with name boot on the partition. This is CloverEFI. It also can be Chameleon.
4. The CloverEFI make initialization of hardware and search for /EFI/CLOVER/CLOVERX64.EFI but it forgot from where it was loaded. So why it may load the file from disk0 and other files from disk0 installation.
5. The same issue if you have USB stick inserted. Clover from HDD will load USB Clover installation.
This issue is not repairable so I may just suggest you to make only way to boot.
1. BIOS started MBR zero sector from the drive you choose to boot. This is disk2. There is a boot0af boot sector written into.
2. This program boot0af search for EFI System Partition on the drive, load sector 1 from the partition and start it. There is boot1f32 boot sector written into.
3. This program boot1f32 search for a file with name boot on the partition. This is CloverEFI. It also can be Chameleon.
4. The CloverEFI make initialization of hardware and search for /EFI/CLOVER/CLOVERX64.EFI but it forgot from where it was loaded. So why it may load the file from disk0 and other files from disk0 installation.
5. The same issue if you have USB stick inserted. Clover from HDD will load USB Clover installation.
This issue is not repairable so I may just suggest you to make only way to boot.
