Error file
https://termbin.com/xbvz
What are the possible reasons this could have happened? I will be happy to hardware logs as well if that feels necessary.
It looks like you tried to mount an ext2 partition to /efi and you didn’t format it.
Did you use manual partitioning? If so, you need to use a vfat/fat32 partition for /efi and ensure it has a valid filesystem on it.
1 Like
https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/
Article has the info on requirements for partitions.
I chose the replace a partition option. I did not really touch the EFI part of it, I was mounting it to an already existing one which EnOS seemed to know by itself. Should I format it as well beforehand?
No, you don’t have to format it before it beforehand. You can tell the installer to do it.
You mounted it as ext2 partition. The EFI partition can’t be ext2. It wouldn’t work.
That is really strange then.
1 Like
I think the problem is based on the article that systemd-bootloader says the minimum EFI size has to be 1024MB but since I used grub with Arch Linux before it was only 500MB or so, I will try changing it’s size.
The EFI partition can’t be ext2. It wouldn’t work.
Then what file type should I make it?
fat32
1 Like
I see some very strange partitions here…
Assuming the concern is the fat32 partitions in the middle, those are where I am booting from. I have the option to boot directly from an efi file on my HP Notebook (not sure how common that feature is, because of how rarely I have seen it mentioned). Then the Swap is well swap memory and though, I have not yet figured out how to set it during installation, I will probably figure it out later using a swapfile. And the rest are Windows partitions, that I have learnt better than to touch.
so you did use manual partition option not replacing? As replacing a partition would have checked for valid usable EFI partition and in case of systemd-boot it would have created a new one as none would get validated to be usable.
Minimum 1024 MB mounted under /efi and flagged boot… For the ESP …
It looks like a Calamares bug. Like Qt/whatever is a high level language.
I prefer bash, or manual installation for a reason… 
It would fail to install manually too if you set the ESP go ext2 
The error is somehow misleading…
2024-06-29 - 03:02:30 [1]: ERROR: Error while running: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/calamares-root-4e3h57bq/efi/loader/loader.conf' this is what is causing it.
so you did use manual partition option not replacing?
I did choose that option and replace the empty ext4 partition that I had formatted beforehand with gparted and added the swap because that is how I had installed last time a couple of years ago.
As replacing a partition would have checked for valid usable EFI partition
It did, and for some reason it had selected /dev/sda6 which already existed because it was my old EFI partition but did not meet the new criteria. I did check the New option that it offered, but did not select it because it did not make sense to me to make a new EFI partition when I had one.
Minimum 1024 MB mounted under /efi and flagged boot…
Those are the choices it made for the New option but I did not notice last time.
Thanks. That was the issue alongside the small sized partition. I got it installed successfully.
1 Like