Boot into a LIVE ISO, double check the UUID’s of all your partitions using Gparted or kde partition manager and then mount your / partition manually and check if in /etc/fstab the correct UUID’s are set. When moving partitions sometimes the UUID’s are changed.
Then unmount the / partition again, manjaro-chroot into your install by
sudo manjaro-chroot -a
and restore the boot loader. This is needed as you most likely have changed the start sector of your / partition and grub does not find it any more.
When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, beforeANDafter the pasted text. Like this:
Or three (3) tilde signs, like this:
This will just cause it to be rendered like this:
eget nisl elit id
arcu erat varius
cursus sem quis eros.
Instead of like this:
Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.
Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.
Thereby increasing legibility thus making it easier for those trying to provide assistance.
For more information, please see:
If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:
_This will just cause the terminal output to be in English, making it easier to understand and debug.
The ESP is by default configured as the first partition on a drive – in your case, that wasnvme0n1p1 which you deleted.
The ESP typically varies in size from 200MB to maybe 300MB, depending on the distribution. The partition now marked as ‘EFI System’ is ridiculously larger – 2GB – obviously a result of combining the partitions; most likely ESP, /root and /home into one (nvme0n1p5).
Whatever operation(s) you used to combine these partitions has left you without an ESP (irrespective of the partition label remaining). An ESP has certain properties which were lost during this procedure.
Furthermore, if the whole 2GB partition inherited the underpinning fat32 filesystem of the former ESP, Linux will not work on that.
So, yes, you did remove the ESP.
A complete reinstall – without merging any partitions – is probably the best way forward for you; especially considering your current knowledge of Linux:
Sorry I didn’t fill you in.
It is used to a dual boot, partition nvme0n1p1 - nvme0n1p4 are windows relevant. I wanna expand my manjaro partition, so I delete all these partition and move after to the partition nvme0n1p7.
I change the ESP to 2GB while I install manjaro before, I didnot combine any other partition to ESP
I cannot help whith chrooting, but after you solve this problem, you should check if your newly created ESP had the correct flags - esp, boot. And 2GB is simply a lost space. The manjaro bootloader is 2 MB. I highly doubt you will install 1000 different OSes on that computer. Actually i am not sure if that massive size is not part of the problem too. A normal size for ESP is 200-300 MB max. Possibly the manjaro installer did something wrong with the ESP or assumed it is OK if it was preformatted by you before, wrongly.
Here is a reference how it has to look from gparted, you can do it and set the flags there from the live USB.
It is true. Because you can do anything you want, but when you open the box of your newly purchased laptop, it IS p1. So he deleted it and recreated it as p5 but something went wrong in the process (i suspect the flags).
Some internet recommendations are kind of city legends. Maybe it started as 200mb somewhere and everyone wanted to be on the safe side and in every next copy-paste manual or wiki page were added 100MB and by the 3rd copy-paste we were at 500MB. I cannot imagine another reason. Microsoft itself recommends at least 100MB. My lenovo came factory with win11, and a lot of recovery bootloaders and tools and 260MB
There is a nice note in the arch wiki about this. Generally, everything above 300MB is either overprovisioning, or to avoid bugs, human errors or for buggy firmware versions or special cases. Supposedly there are “tools” that “might” install there. And some laptop/firmware brands may store language translations of the firmware there. But everything else… a bootloader of any OS is a couple of Megs.
That said, since resizing is a big pain, it is better to be safe than sorry and the upper limit of 500MB cannot hurt by the current price of SSDs. But 2 GB is just nonsense. In this particular situation i would leave it as is, because 1,5GB partition cannot be used for anything anyway, and is in the beginning of the drive. But if he repartitions and wipes everything anyway there is no need to be that big.
Yes, any partition can be used as an ESP, regardless of its position.
However, the ESP typically defaults to the first partition, when created during installation of an OS. That was the point; and that remains true.
Aside;- Interesting to note is that the UEFI specification only allows one ESP instance; whereas, in practice (depending upon tools used), multiple ESP’s are possible. Any specification is only as good as how well it’s implemented, or enforced.
No, you can choose any partition as ESP, it was not the question what situation you face with a newly bought laptop.
The point is, there are many wiki infos but there is clearly no upper limit, therefore you cannot say a partition is too large as ESP, it might be much larger than needed but it will work. My answer was focussing the wrong conclusion:
Without sufficient information provided by the OP it’s easy (and often necessary) to make assumptions. The size of the ESP is anecdotal, at best; however, it’s fair to say that it is greatly in excess of the space typically used for the purpose.
Perhaps the OP can recover the situation (as @Teo alluded to) by setting appropriate flags to again make this partition a fully qualified ESP; or by recreating/restoring Grub while in a chroot environment, as you initially suggested. For the OP’s sake, I hope it’s that easy.