Bonjour parfait
Vous pouvez voir que la partition ESP a / boot / efi et que grub est installé sur / dev / sda
Le partitionnement est correct. Voici comment c’est supposé être.
Bon exemple.
Great way to display it.
1 Like
do not forget to click on the top one
Same problem with the latest iso.
This are the partition. I tried several times and one of the trial it worked but it won’t boot into the os and it didn’t recognize my os drive.
This is the mentioned problem. Installation failed and when reboot the primary drive is not recognized and boots into bios…
- Why mount the boot partition at
/boot/efiif you aren’t planning on encrypting system or dual-booting?
Anyways, show us the output of:
efibootmgr --verbose && dmesg | grep Secure && mount | grep efivars
and if you mind give us the install log so we can see exactly what is going wrong.
cat /home/liveuser/endeavour-install.log | curl -F 'f:1=<-' ix.io
I don’t understand this?
If it’s an EFI system then why wouldn’t it be mounting /boot/efi? It doesn’t have to be a dual boot or encryption.
What i mean was i don’t understand the comment: Why mount the boot partition at /boot/efi “if you aren’t planning on encrypting system or dualboot?”
I had understood, other not on the partitionnent
@Chrysostomus from Manjaro dev team explains it well.
boot is the place where your system keeps its kernels. As pointed out, separate /boot partition is usually unnecessary.
ESP is the small fat partition where all your operating systems keep their bootloaders. This can be mounted to either /boot or /boot/efi. The difference is that if you mount it to /boot, your system keeps also its kernels in the ESP partition.
/boot/efi us usually preferred mount point because
- It doesn’t limit how many kernels you can have
- It is better if you multiboot Linux systems, because their kernels don’t get mixed
- It lets you have encrypted /boot directory. ESP partition can never be encrypted
/boot/ is needed if you
- Use systemd-boot as bootloader
- Want to use refind as only bootloader while having encrypted root.
- Need separate /boot, but want to have minimum amount of partitions.
You need separate /boot very rarely these days. Grub supports even btrfs and f2fs root. One of the few things that still needs separate /boot is btrfs with zstd compression.
I understand all that. I don’t understand your point? What does that have to do with dual boot or encryption? The user is just trying to get EndeavourOS installed and his sytem is UEFI. This is the standard way a lot of installations create the partitions on the install like Antergos did. Most of the users coming to EndeavourOS just want to install Arch an easy way and not have difficulty. I’m sorry but i do not see what your explanation has to do with the users issue. Most users coming to EndeavourOS are relying on the installer. What i’m saying is it doesn’t matter if he is using a separate boot partition and EFI . I have that myself and it’s not an issue. I’m only interested in why the installer is failing to create the boot files on the install. This is not the first person to have this issue with the installer. What i do see is that his partition /dev/nvme0n1p2 shows ext4 /run/media. Why isn’t it /root?
Hello @noir12 Would it be possible for you to send the logs that @joekamprad has asked for? We really want to help you figure out what caused this install failure and this information is very helpful. I’m sorry that this issue has happened but we want to help you solve it.
Thanks.
I’ve explained the reasoning backing my inquiry. OP doesn’t have to choose /boot over /boot/efi. Still, there are circumstances such as the ones outlined by @Chrysostomus where proverbial prerequisites demand moderate consideration.
- OP is not multi-booting.
- OP won’t use FDE (with the exception of ESP).
Knowing OP is at least sufficiently versed in linux, enough to partition manually; why still do /boot/efi as opposed to /boot? Simple, unobtrusive curiosity, and nothing more.
You need to cool down, @ricklinux. 
I am always cool don’t take it the wrong way. Just didn’t understand your point. If i was installing it i would be choosing /boot/efi whether i was dual booting or not because it is UEFI. Yes i could do it another way. Or various ways for that matter.
1 Like
Oh, alright! 
I thought you lost it for a moment there. 
1 Like
Don’t go Arch on me! 
1 Like
@ricklinux @Computer issue from help searching user is not related to wrong partition scheme, he was creating it the standard way for EFI systems.
an ESP fat32 partition with 500mb mounted under /boot/efi the same that calamares would create automatically.
it is more likely real issue is linked to what is shown inside the error:
And @noir12 should provide the logs, and try to erase the drive with gparted prior installation.
1 Like