Why do I have multiple EFI partitions

And which one do I attempt to edit the config.plist from? Trying to fix audio problem after update to Mojave.

I am quite confused about how these EFI partitions work, and I cannot find concise information on what they are and how they work. But I have got an EFI mounter to attempt finding the files on the EFI partition in order to edit config.plist.

When I go to mount the partition (I assume this is how you "reveal them) I found that I have 4 of them, and then the "current" bootdisc (unselectable for what reason?). Can someone please explain what is going on here? Should I have so many and should I get rid of some?

Thanks in advance.

interobang said:

When I go to mount the partition (I assume this is how you "reveal them) I found that I have 4 of them, and then the "current" bootdisc (unselectable for what reason?). Can someone please explain what is going on here? Should I have so many and should I get rid of some?

Click to expand...

Use an app that at least shows the UUUIDs or other device information of the partitions so you have some chance of knowing which is which.

You should be able to access your boot disk (disk4s1) simply by scrolling down in the displayed window. I guess your system settings are such that the scrollbar only appears when your mouse approaches it?!
So then you will be able to access the EFI partition of your boot drive.

The "current boot disk" is the one your currently running system booted from, which basically is the hard disk that is selected in your BIOS/UEFI as first priority to look for an operating system(*).
I think, but I´m not too sure right now, that every (macOS) disk has an EFI partition. But for hackintoshing normally only the one containing the macOS operating system is relevant, because Clover and related files are installed into it.

If you are using more than one boot drive (e.g. a bootable backup with a separate version of Clover installed on) than it might get confusing.
You can determine the disk(x) value using disk utility. It shows you the disk(x) value of the drive that you want to modify the related EFI folder from.
What I do to keep a better overview of which EFI folder I currently have mounted is simple: I added a new folder into it - named like the disk the EFI is located on.

(*)It can be more complicated, but that is normally implemented by you:
Your BIOS/UEFI setting determines from which drive your computer should boot.
It will look for an OS and will find: Clover.
Clover will than generally boot from the same drive, but that behaviour can be modified!
If the config.plist contains a dedicated drive to boot from, than Clover will use the the OS on the dedicated drive.
This can cause Clover, which was started from "disk(a)" as determined by the BIOS/UEFI settings, to use the macOS files on "disk(b)", but still using the Clover settings from "disk(a)".

Update:
I guess now I know what your issue is (or has been, as you never replied).
It happened to me now on a fresh install of Mojave with a NVMe SSD as boot device formatted as AFPS.

The EFI mounter will state your "current boot is diskx1." But in the related window there is no diskx displayed.

I had a look at that disk in diskutility. There is my NVMe device and it contains a container disk labeled diskx. This disk itself contains my boot device as diskxs1.
The interesting and for nonAFPS users relevant part is, that the NVMe device itself has a different disk number x-1.
And that is the part where your desired EFI partition is located.
So when your boot disk is disk5 just mount the EFI volume on disk4.

Edit: Just noticed that it must not be necessarily be x-1. Seems that disks can be mounted in random sequence. Always crosscheck with disk utility!