I’ve used manjaro for a long time, but I became interested in Pop!_OS and started using it, and now in this release of Manjaro 20.2, I decided to go back. But when I’m going to install partitioning manually, for some reason, there is no boot entry. Since my partitioning is identical to the automatic partitioning of the installer, I just add a /home partition on my HD
OBS: I can only install with automatic installer partitioning
OBS 2: I already installed Manjaro 20.1.2 with this same partitioning
There’s an issue with calamares in 20.02. Made me a / and /home btrfs partitions, along with /boot, set all flags correctly, but after the installer wiped the drive i got an error message with zero useful info to investigate and some tmp files in /, which i could not erase in the same session and had to reboot.
In the end i was able to move forward with the installation with everything slapped onto a single btrfs partition. Hope this works out fine.
So - yeah, seems the installer may be at fault here.
Did you create the /dev/sda1 partition with partition typeEF00 ?
Because that partition needs to be that type to be recognized as the EFI system partition
Can you be more specific about where you expect this boot entry to show up?
(eg. In the BIOS boot menu, The Grub menu, Some other bootloader’s menu, The installer, etc)
The /dev/sda1 partition is recognized as an EFI System Partition, but after install when reboot my computer. There’s no boot entry in BIOS Boot Menu and when i try to start manjaro from the grub menu from usb stick, theres an error saying “Entry not found”
There should be no issue with the partition setup from OP.
This should boot as expected.
If you have issues with this it - could be - without knowing for sure an issue with Calamares installer although this is as mature as it gets for installers - I mean years of polishing.
There is really nothing indicating what is off for your use case.
The boot flag (0xEF00) is done when you select the boot flag for the partition.
The only thing I would do extra is flagging the root partition as root (0x8304) the swap as (0x8200) and /home as (0x8302) using the appropriate flags but other than that - which is really only - sort of - cosmetic - there is nothing I would have done different.
No it is not - at least not with EFI - the Calamares boot flag is setting the partition type to 0xEF00
Now that may not be the active boot element from EFI perspective but that is later set by efibootmgr and when you boot whatever you choose to boot from - from the EFI perspective - is set as the active boot entry - designated by the * when listing boot entries using efibootmgr on a command line.
Ahhh then we spoke about different things, because a boot flag in terms of disk partitions is something different as a flag used in a menu of a software
Remember MBR partitions who needed a “boot flag”?
I know about UEFI boot entries, and that star is not related to that because it only shows the menu entry as being “active”…
Anyhow i suspect the poster is trying to boot an UEFI install on a system without UEFI mode…
which is the future way of defining - what-is-what-and-how-do-i-know - and will probably become a de-facto standard which some may approve of and some may not.
Adding to this is the BIOS/GPT variation when you add an unfomatted partition of type 0xEF02 as the partition to hold GRUB in case of non EFI system boot and this is set within Calamares when you designate a partition as bios-boot.
I know all that info too well
That’s why i suggested to mount the ESP at /efi a while back in another topic
Anyhow lets not derail from the original issue
I agree - it may not be that obvious how the comment connect to the OP - but nonetheless - it is very much related how you define your partitions and in/under which circumstance you are defining them which in the end will define if your system are booting or not.
