i’m not sure, how can i check it?
Looking through the output a second time, it doesn’t seem you do. Now I just wonder what
/EFI/systemd/systemd-bootx64.efi is doing there and how it got there at the first place
Is systemd another bootloader different from grub?
If yes i tried to install Arch linux with sda1 mounted as /boot not /boot/efi, i think i got some problems with the command archinstall.
systemd-boot is systemd’s own bootmanager.
Looks like it’s leftover from your previous attempt to install Arch then.
At any rate it shouldn’t interfere with your boot process now.
i think i need to clean up some sda1
Can i trash
/EFI/systemd/
and
/EFI/EFI/manjaro/grubx64.efi
?
Did you try to install Manjaro’s bootloader a second time?
Is that why you have ./EFI/EFI/manjaro/grubx64.efi
in there as well?
Also, post the output of
efibootmgr -v
It is possible, it think i did it to restore the grub of manjaro after eos install
BootCurrent: 0012
Timeout: 0 seconds
BootOrder: 0012,0013,0014,0000,0001,0002,0003,0007,0008,0009,000A,000B,000C,000D
Boot0000 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0001 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0002 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0003 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0004 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0005 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0006 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
Boot0007* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0008* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0009* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot000A* ATA HDD1 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
Boot000B* ATA HDD2 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f602)
Boot000C* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot000D* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot000E* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
Boot000F* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
Boot0010* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0011* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot0012* manjaro HD(1,GPT,717fdfa4-e3da-439f-b116-30b6962031c4,0x800,0x100000)/File(\EFI\manjaro\grubx64.efi)
Boot0013* Windows Boot Manager HD(3,GPT,b19d8236-6cec-45f0-ab1d-670586839bc3,0x101fa000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0014* EndeavourOS HD(1,GPT,717fdfa4-e3da-439f-b116-30b6962031c4,0x800,0x100000)/File(\EFI\EndeavourOS\grubx64.efi)
Yes.
sadly nothing changed
sudo grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/sda3@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
Yes, that was only cleaning up a bit but of no consequence to the issue, the odd issue I should say, that you are having.
Agreed, it is strange.
It might be something to do with the EFI partitions and their contents.
Without knowing how you have created this system, is it possible that you make a backup of all your data and simply wipe the disk and reinstall everything? I know it is a big job…
Or simply let Manjaro’s Grub be in charge. As it seems to be working.
That may be the easiest way forward…
thanks a lot for your help, i’ll use manjaro grub and the next time i’ll format my efi partition