You are not logged in.
Weird behaviours like these are usually the problem of the firmware itself, check if you have options to manage/remove/add new EFI entries yourself within your UEFI settings. Which motherboard are we talking exactly?
Offline
This page from Ubuntu Grub2 might shed some light. It does say that Grub embeds itself on the sector after the MBR. Your sda1 begins on the 2048MB sector so it is possible that the magical Grub2 is embedded in that 2MB sector from 0-2047.
The OP does not appear to have a BIOS boot partition so there won't be enough room for GRUB's core.img and non-UEFI booting with GRUB will not be possible.
@OP: try this command from the GRUB prompt:
setThat should tell you where GRUB is looking for the kernel image & configuration file, along with some other details, perhaps that will help us here.
Post a picture of the screen if you want but make sure it's a link to an image hosting site to avoid incurring the displeasure of our ever-vigilant mod team.
Jin, Jîyan, Azadî
Offline
Weird behaviours like these are usually the problem of the firmware itself, check if you have options to manage/remove/add new EFI entries yourself within your UEFI settings. Which motherboard are we talking exactly?
Don't know about motherboard, it is a laptop actually called lenovo ideapad flex 10.
It doesn't have an option to add EFI entries.
Offline
the Arch ISO contains a UEFI Shell. boot it then execute 0:\EFI\BOOT\BOOTx64.efi and see what happens.
I actually don't know that much, how do i boot it ?
Offline
setThat should tell you where GRUB is looking for the kernel image & configuration file, along with some other details, perhaps that will help us here.
Post a picture of the screen if you want but make sure it's a link to an image hosting site to avoid incurring the displeasure of our ever-vigilant mod team.
cmdpath is (hd0,gpt2)/EFI/BOOT so esp partition, grub platform efi, root hd0,gpt2
Offline
This page from Ubuntu Grub2 might shed some light. It does say that Grub embeds itself on the sector after the MBR. Your sda1 begins on the 2048MB sector so it is possible that the magical Grub2 is embedded in that 2MB sector from 0-2047. As I said you can clean that sector by dd but I'm not sure if that sector is used by Windows as well so there might be risks involved.
Edit: A safe way of doing it is to clone a disk first as backup i.e. clonezilla if you have that facility then try the operation.
It is too risky for me, maybe stickng with grub is easier
Offline
boot ARCHISO that you have used to install arch, then select EFI Shell V. 2 From the menu. some motherboards include it in the firmware but for me didn't. if your bios has a such option you can use it.
if you select to boot a hard disk (e.g. select 'EFI: HARDDISK' instead of 'Windows Boot Manager' or 'Linux Boot Manager') will load EFI/BOOT/BOOTx64.efi. Also check what else is in your ESP.
deleting everything in ESP (but not EFI/Microsoft) and reinstalling systemd-boot may help you.
Also if you delete Windows Boot Manager you can restore it by selecting 'Startup Recovery' from a Windows Installation Media.
options in your boot menu (e.g. 'grub2' or 'Linux Boot Manager') are stored in nvram. if you wipe ESP they will kept. you can manage them by efibootmgr in arch or bcdedit windows.
Last edited by mmdamin (2019-06-12 03:33:54)
Offline
cmdpath is (hd0,gpt2)/EFI/BOOT so esp partition, grub platform efi, root hd0,gpt2
OK, so try copying systemd-bootx64.efi to the removable loader location:
# mount /dev/sda2 /mnt
# cp /mnt/EFI/Boot/systemd-bootx64.eif /mnt/EFI/Boot/bootx64.efiThen reboot.
Last edited by Head_on_a_Stick (2019-06-12 08:51:35)
Jin, Jîyan, Azadî
Offline