1

I want to achieve a proper GRUB installation, so it will be able to EFI boot Arch Linux on my MSI B250M PRO-VDH without further user intervention.

Everything has been set-up as it follows:

/dev/sdc1 is the EFI Partition, FAT32 400 MB, mounted to /boot (/mnt/boot outside of chroot)

/dev/sdc2 is swap, 16 GB

/dev/sdc3 is the Linux partition in which Arch has been installed, EXT4 around 100 GB, mounted to / (/mnt outside of chroot)

Everything goes fine until the bootloader installation. Through arch-chroot I installed grub and efibootmgr, then proceeded installing, as always:

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=BOOT

No errors reported, then made the configuration file, as always:

grub-mkconfig -o /boot/grub/grub.cfg

No errors reported. Once I rebooted my system, the boot entry wasn't there at all.

I proceeded copying grubx64.efi to bootx64.efi and the boot entry finally appeared, though it always boots up to the GRUB shell instead of loading Arch Linux. Rebuilding the configuration file doesn't work either.

Plugging the drive on another EFI system successfully boots Arch Linux up without further hassles.

1 Answer 1

1

Proper solution:

The manual for the MSI B250M MORTAR notes that the Secure Boot options will only appear if the Windows 8.1/10 support is enabled. The FAQ page for the MSI B250M PRO-VDH lists the same answer for finding the Secure Boot option, so I assume this solution will work for you as well.

After enabling Windows 8.1/10 WHQL Support under Settings/Advanced/Windows OS Configuration, I re-disabled Fast Boot and disabled Secure Boot Support.

After these changes, I reinstalled GRUB without the --removable option, and it finally appeared in the boot option list.

Old answer

I had this same issue with an MSI B250M Mortar, and was able to solve it by adding the --removable flag to the grub-install command. This ends up placing the EFI binary under BOOT/BOOTX64.EFI, which as you found out makes it appear in the boot entry menu. Using this approach, I did not encounter any further GRUB shell problems.

2
  • The bit after the entry is not a signature; its purpose is more like the command line for the .efi program. Secure Boot signatures are embedded in the .efi itself (in the same format as an .exe), but if they were the problem, the unsigned grub.efi wouldn't have run at all, regardless of the file name. Commented May 5 at 17:25
  • @u1686_grawity Thanks for pointing this out! I have removed the paragraph entirely as it was kind of irrelevant speculation anyways.
    – Loek
    Commented May 5 at 18:22

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .