[SOLVED] Efi boot entry disappears after reboot. MSI BIOS E7B05IMS.1A0

Orbio · 2019-11-24 18:32:36

I am installing a fresh version of Arch. And it seems that I have similar to this problem https://bbs.archlinux.org/viewtopic.php?id=228761 but solution doesn't help me ( I have same MSI bios)

My layout

/dev/sda disk
/dev/sda1 /boot
/dev/sda2 /

I did all according to the installation guide

Install it with grub-install

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader=ARCH

no errors

then when I check it with efibootmgr -v while chrooted I got the following error

[root@archiso /]# efibootmgr -v
BootCurrent: 000C
Timeout: 1 seconds
BootOrder: 0000,000C,000D,0001,000B
Boot0000* ARCHCould not parse device path: Invalid argument

Although when I exit chroot all seems fine

BootCurrent: 000C
Timeout: 1 seconds
BootOrder: 0000,000C,000D,0001,000B
Boot0000* ARCH HD(1,GPT,1b625911-d6d2-d442-85f2-4c5a0f8e2d90,0x800,0x100000)/File(\EFI\ARCH\grubx64.efi)
...

reboot - no efi entry in bootmanager

2. Install it manually with efibootmgr

efibootmgr -c -p 1 -d /dev/sda -L ARCH -l '\EFI\ARCH\grubx64.efi'
BootCurrent: 000C
Timeout: 1 seconds
BootOrder: 0000,000C,000D,0001,000B
Boot0001 Hard Drive
Boot000B USB KEY
Boot000C* UEFI: KingstonDataTraveler 3.0PMAP
Boot000D* UEFI: KingstonDataTraveler 3.0PMAP, Partition 2
Boot0000* ARCH

efibootmgr -v
BootOrder: 0000,000C,000D,0001,000B
Boot0000* ARCH HD(1,GPT,1b625911-d6d2-d442-85f2-4c5a0f8e2d90,0x800,0x100000)/File(\EFI\ARCH\grubx64.efi)
Boot0001 Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..GO..NO..........S.a.m.s.u.n.g. .S.S.D. .8.5.0. .E.V.O. .2.5.0.G.B...................\.,.@.r.d.=.X..........A...........................>..Gd-.;.A..MQ..L.2.S.6.R.B.N.J.0.1.5.5.3.9.9. .M. . . . ........BO
Boot000B USB KEY BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0b00)..GO..NO..........K.i.n.g.s.t.o.n.D.a.t.a.T.r.a.v.e.l.e.r. .3...0.P.M.A.P...................\.,.@.r.d.=.X..........A.......................F..Gd-.;.A..MQ..L.0.0.1.A.4.D.5.E.8.6.3.6.B.1.B.1.7.9.5.E.A.9.9.D........BO
Boot000C* UEFI: KingstonDataTraveler 3.0PMAP PciRoot(0x0)/Pci(0x14,0x0)/USB(17,0)/CDROM(1,0xa4,0x13d75c)..BO
Boot000D* UEFI: KingstonDataTraveler 3.0PMAP, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(17,0)/HD(2,MBR,0x65cc13ea,0xa4,0x20000)..BO

Then reboot and it is gone again

3. Then I booted to EFI shell, found the '\EFI\ARCH\grubx64.efi' and booted just fine.

Previously I had debian installed on this machine which was working just fine. So I tried to reinstall it just to check the bootmanager entries debian installer adds. It worked and it seems pretty the same

BootCurrent: 000C
Timeout: 1 seconds
BootOrder: 000C,000E,000D,0001,000B
Boot0001 Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..GO..NO..........S.a.m.s.u.n.g. .S.S.D. .8.5.0. .E.V.O. .2.5.0.G.B...................\.,.@.r.d.=.X..........A...........................>..Gd-.;.A..MQ..L.2.S.6.R.B.N.J.0.1.5.5.3.9.9. .M. . . . ........BO
Boot000B USB KEY BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0b00)..GO..NO..........K.i.n.g.s.t.o.n.D.a.t.a.T.r.a.v.e.l.e.r. .3...0.P.M.A.P...................\.,.@.r.d.=.X..........A.......................F..Gd-.;.A..MQ..L.0.0.1.A.4.D.5.E.8.6.3.6.B.1.B.1.7.9.5.E.A.9.9.D........BO..NO........i.J.e.t.F.l.a.s.h.T.r.a.n.s.c.e.n.d. .2.G.B. .8...0.7...................\.,.@.r.d.=.X..........A.......................&..Gd-.;.A..MQ..L.P.F.P.J.J.H.Y.5........BO
Boot000C* UEFI: KingstonDataTraveler 3.0PMAP PciRoot(0x0)/Pci(0x14,0x0)/USB(17,0)/CDROM(1,0xa4,0x13d75c)..BO
Boot000D* UEFI: KingstonDataTraveler 3.0PMAP, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(17,0)/HD(2,MBR,0x65cc13ea,0xa4,0x20000)..BO
Boot000E* debian HD(1,GPT,6b2ca01f-8b8a-4c15-a2db-cf07829705f7,0x800,0x100000)/File(\EFI\debian\grubx64.efi)..BO

I tried to boot using debian entry but replaced the kernel to Arch but it drops to grub rescue shell.

Last edited by Orbio (2019-11-25 06:45:48)

Slithery · 2019-11-24 18:49:05

Sounds like faulty firmware. Install the bootloader to the fallback location as well...
https://wiki.archlinux.org/index.php/GR … _boot_path

Orbio · 2019-11-24 18:54:06

Slithery wrote:

Sounds like faulty firmware. Install the bootloader to the fallback location as well...
https://wiki.archlinux.org/index.php/GR … _boot_path

But why debian installer works just fine?

Slithery · 2019-11-24 19:00:51

I have no idea, you'd have to ask them.

Orbio · 2019-11-24 19:09:36

Slithery wrote:

Sounds like faulty firmware. Install the bootloader to the fallback location as well...
https://wiki.archlinux.org/index.php/GR … _boot_path

It helped, thank you.

g2g591 · 2019-11-26 11:57:01

Orbio wrote:

Slithery wrote:
Sounds like faulty firmware. Install the bootloader to the fallback location as well...
https://wiki.archlinux.org/index.php/GR … _boot_path
It helped, thank you.

I have an msi motherboard as well. it does indeed have screwy firmware. It will automatically delete any boot entries referring to an ESP on any drive besides the one that I dual boot with a factory install of windows... unless there is a file present in the fallback location, then adding and keeping boot entries to it works normally.

Last edited by g2g591 (2019-11-26 11:57:43)

agapito · 2019-12-01 01:45:47

I bought a MSI motherboard (B450 PRO CARBON AC) 5 months ago and never had a problem until today. I turned on my computer this morning and the grub entry disappeared like when I install Windows on the same hard drive. Ok, no problem i chrooted my Arch installation using the Arch Installer CD and i restored my grub entry using this command as usual:

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

I booted up my Arch local installation and I worked in a long session and after restarting the computer my motherboard didn't post. I tried to post several times and finally i could unplugging the HDMI connector from my monitor and what I saw when plugging it in again was the Windows login screen. I lost my grub entry again...

If this does not change, I will rename the EFI/Archlinux/grubx64.efi to EFI/Microsoft/Boot/bootmgfw.efi since the entry to boot Windows is never lost.

V1del · 2019-12-01 19:37:15

MSI's are notorious for this and overriding the windows boot loader is not the correct approach and not what is being booted, follow the alternate install method posted in slithery's link.

agapito · 2020-12-15 08:22:12

V1del wrote:

MSI's are notorious for this and overriding the windows boot loader is not the correct approach and not what is being booted, follow the alternate install method posted in slithery's link.

The alternate install method didn´t work as expected, grub entry is still deleted randomly. So...

agapito wrote:

If this does not change, I will rename the EFI/Archlinux/grubx64.efi to EFI/Microsoft/Boot/bootmgfw.efi since the entry to boot Windows is never lost.

And this is what I finally did, tired of this MSI nonsense. I renamed the original Microsoft bootmgfw.efi to bootmgfw2.efi and then copied grubx64.efi to the Microsoft folder as the new bootmgfw.efi , changed grub.cfg to find Windows on EFI/Microsoft/Boot/bootmgfw2.efi and luckily Windows can boot.

Arch Linux

#1 2019-11-24 18:32:36

[SOLVED] Efi boot entry disappears after reboot. MSI BIOS E7B05IMS.1A0

#2 2019-11-24 18:49:05

Re: [SOLVED] Efi boot entry disappears after reboot. MSI BIOS E7B05IMS.1A0

#3 2019-11-24 18:54:06

Re: [SOLVED] Efi boot entry disappears after reboot. MSI BIOS E7B05IMS.1A0

#4 2019-11-24 19:00:51

Re: [SOLVED] Efi boot entry disappears after reboot. MSI BIOS E7B05IMS.1A0

#5 2019-11-24 19:09:36

Re: [SOLVED] Efi boot entry disappears after reboot. MSI BIOS E7B05IMS.1A0

#6 2019-11-26 11:57:01

Re: [SOLVED] Efi boot entry disappears after reboot. MSI BIOS E7B05IMS.1A0

#7 2019-12-01 01:45:47

Re: [SOLVED] Efi boot entry disappears after reboot. MSI BIOS E7B05IMS.1A0

#8 2019-12-01 19:37:15

Re: [SOLVED] Efi boot entry disappears after reboot. MSI BIOS E7B05IMS.1A0

#9 2020-12-15 08:22:12

Re: [SOLVED] Efi boot entry disappears after reboot. MSI BIOS E7B05IMS.1A0

Board footer