/boot != /boot/efi
/boot/efi is now filled with 26MB and I think 100MB would be more than enough
/boot needs to hold several Linux kernels and initramdisks
size matters here definetly
I know and was just sharing my experience.
As you said it might be enough but it’s better to have it bigger because no dual booter came across this kind of an issue until you.
Let’s just agree to disagree and have a good day.
YMMD
this is near to a well known philosophical saying
I did a test to see if this issue was caused due to an issue with the new ISO or if it was because of the small size of the UEFI partion.
The test was done in a VM using 120 GB qcow2 HDD file, 4096 GB RAM, 2 vCPU Cores, and the ISO used endeavouros-2021.08.27-x86_64. Also, UEFI is enabled from the chipset and this is not a dual boot it’s just eos.
First I tried creating a /boot/efi partition which would be the size of 100 MB.
As shown in the above image /boot/efi/ → 100.0 MiB
And more images to make things clear.
As you can see the boot flag is also set. So this /boot/efi partition is within acceptable parameters.
Now I clicked on continue to proceed to the next screen and vola the described issue.
So back to the partitioning area.
Increased the /boot/efi partition from 100 MB to 550 MB (this is the size what I normally use for my /boot/efi).
After increasing the size again clicked on continue. No error or no warnings Clemaris just allowed it.
To clarify more the screen just before I started the installation.
Clicked on “Install Now” and now it’s being installed.
So as I said size does matter.
The 100 MB partition size is the minimum. Though there is no specification set by UEFI for a minimum size. But, Microsoft recommends this 100 MB size for it’s Operating Systems.
Let’s think we need the EFI partition to be formatted using the FAT32 file system. The minimum partition size of FAT32 drive is calculated as sector_size x 65527.
In Advanced Format 4K Native drives, there is 4 KB per sector. In that case, the minimum partition size for FAT32 drive is calculated as 4 KB x 65527 = 256 MB. That’s why recommended minimum size for 4K drives is 260 MB.
But in Advanced Format 512e drives, the emulated sector size is 512 bytes. In that case, the minimum partition size for FAT32 drive is calculated as 512 bytes x 65527 = 32 MB, which is less than the 100 MB minimum size for this partition.
Must a EFI partition be a certain size for the system to recognize it?
Though Microsoft recommends 100 MB for its operating systems, the Linux forums suggest more for Linux based operating systems or for any dual boot or multi booting situations.
The author of gdisk suggests 550 MiB.
As per the Arch Linux forum, to avoid potential problems with some EFIs, ESP size should be at least 512 MiB. 550 MiB is recommended to avoid MiB/MB confusion and accidentally creating FAT16.
So, most common size guideline for EFI System Partition is between 100 MB to 550 MB. One of the reason behind this is it is difficult to resize later as it is the first partition on the drive.
Edit: Arch recommends 512-550
1 Like
I understand all the arguments for the EFI partition to be >> 100MB.
The only complaint I have is to the Calamares installer for the misleading error message;
it should be: “Sorry but your EFI partition should be much bigger; we recommend 600MB” or similar.
This should avoid a lot of misunderstandings.
The famous exception is btrfs, where if /boot is in the root directory, it is not possible to use GRUB_SAVEDEFAULT=true in grub (we had that issue recently). So what then, how do I create the boot partition with Calamares? Questions over questions, after answering them you are not really smarter.
Use manual partitioning and create a /boot that is ext4.
Sorry, I had overlooked that 
2 Likes
If the question is allowed HERE: Does it matter on an SSD if the swap partition is BEFORE the / partition or does the order not matter? I have always done it so far that swap comes after /.
I personally don’t think it matters but maybe @dalto would be better to answer that one.
1 Like
On an SSD, the order shouldn’t matter much.
1 Like
If you have a lot of RAM the placement of the swap really doesn’t matter. Also, as @dalto said if your distro is on an SSD then again swap placement doesn’t matter because SSDs are faster. But if you use a mechanical drive (HDD) then it’s best to put it as the first partition for better perfomance.
1 Like
thanks @dalto @ricklinux @s4ndm4n 
2 Likes
It isn’t because SSDs are faster, it is because there is no difference with SSDs based on where on the SSD the data is. Further, you have no control over where the data goes even if there was a difference.
On an HDD, you often get better seek performance when accessing the innermost tracks on a disk so placing it at the beginning may make sense.
3 Likes
Those were my ulterior motives as well, hence the question.
1 Like