It needs to be 512 MiB. 
But default one 300MiB for EFI too. I mean erase disk option.
I’m sorry but I don’t understand what you mean. The EFI System Partition needs to be 512 MiB for use with GNU/Linux if you format it as FAT32. With FAT16, it may be smaller.
I know it’s a lot of wasted space, but the specifications demand it. When I first installed Manjaro, I had created my ESP at only 280 MiB, and it just wouldn’t work. 
I mean I try erase disk option and it automatic create 300MiB for EFI partition(FAT32).
1 Like
Delete that partition and create a new one in its place, 512 MiB in size, formatted as FAT32, marked with the boot flag, and set the mountpoint to /boot/efi.
You are right! it is strange that in the manual partition part, the installer says you need 512. But when doing automatic install it creates 300 MiB EFI.
I never perform any automatic partitioning, but if what you say is true, then this is definitely a bug.
I’ll invite someone from the team to come and take a look at this thread.
1 Like
Screenshot of the installer (manual partition) Manjaro (20.0.3). Even the need of /boot partition is not correct. It should be EFI partition. A boot partition cannot be vFat and it is not a must.
1 Like
Is the partitioning tool in the .iso GParted? If so, then the bug might be in GParted, rather than in Calamares.
When I installed my system here in April 2019, the installer used the KDE Partition Manager. But then again, as I said earlier, I always opt for manual partitioning. 
Yes, but I don’t see the relation.
If you choose “Manual partitioning” (without using Gparted to partition the disk before), it says you need a 512 MiB FAT32 /boot partition. Assuming the /boot part is a “typo”, then it still creates a 300 Mib FAT32. But correctly as EFI using the automatic install.
So I don’t see how this is related to Gparted.
edit: by the way doesn’t Calamares use kpmcore to manage the partitioning?
an fat32 partition can be 33mb at minima
for linux only there is few used ( 1% )
for others os , required 300Mo
Windows creates 100 MiB EFI. In dualboot with Linux, this can be shared and it seems to be enough.
Looking at:
and this:
it seems you have 2 ESPs: one on /dev/sda and one on /dev/sdb so you need to:
- go into your UEFI firmware and tell it to boot from the second disk
OR - mount the existing ESP during the install and have Manjaro write its system settings on the first ESP (and why we have GRUB: that’ll boot both Windows and Manjaro)
1 Like
Guys, you mix up the requirements for a /boot and for a /boot/efi partition. For /boot you need indeed
for an /boot/efi partition 100 MiB is more than enough, even for a dual boot.
Any advice about using 512MB for $esp is for the case you decide to mount $esp at /boot , in which case all installed kernels will reside on this and kernels are fairly large (about 50MBs each, or similar). If not mounting at /boot you don’t need that space.
2 Likes
From the Arch wiki about the EFI System Partition… 
To provide adequate space for storing boot loaders and other files required for booting, and to prevent interoperability issues with other operating systems the partition should be at least 260 MiB. For early and/or buggy UEFI implementations the size of at least 512 MiB might be needed.
That’s for the EFI System Partition (/boot/efi), not /boot.
I did try this terminal command still not working
I did I try install Linux Mint and Solus all same cannot boot. I guess my PC UEFI mode only for Windows 10…
What @stephane is trying to say is:
Execute these commands:
and copy-paste the output of every single one of them into a new answer. These commands will not solve your problem but will give us more more information so we can see what’s really going on. Now we know the symptom of the disease, but we need the actual X-Ray to know where the origin lies…
(so far you’ve taken the X-Ray, but we need to see it too!)
1 Like
These are 4 commands that are entered one after the other (not together)
inxi -Fxxxza
sudo parted -l
sudo efibootmgr -v
test -d /sys/firmware/efi && echo efi || echo bios
PLS … output format
Button </> or
```output-text```