Arch Linux

cmonty14

Member

Registered: 2019-10-05

Posts: 58

EFI boot fails with error: symbol 'grub_debug_malloc' not found

Hello,

I get this error when booting UEFI OS:
symbol 'grub_debug_malloc' not found.

Please check attached screenshot for details.

This is the output of efibootmgr showing the related line Boot0001* UEFI OS:

BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0000,0001,0004,0005,0006,0007,0008
Boot0000* Windows Boot Manager  HD(1,GPT,086a16e1-9116-4b12-afd6-298d82a78ac9,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot0001* UEFI OS       HD(1,GPT,086a16e1-9116-4b12-afd6-298d82a78ac9,0x800,0x32000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot0002* ARCHLINUX     HD(1,GPT,086a16e1-9116-4b12-afd6-298d82a78ac9,0x800,0x32000)/File(\EFI\ARCHLINUX\GRUBX64.EFI)
Boot0004* UEFI: PXE IP4 Intel(R) I211 Gigabit  Network Connection       PciRoot(0x0)/Pci(0x1c,0x5)/Pci(0x0,0x0)/MAC(309c23e3847b,1)/IPv4(0.0.0.00.0.0.0,0,0)0000424f
Boot0005* UEFI: PXE IP4 Intel(R) Ethernet Connection (H) I219-V PciRoot(0x0)/Pci(0x1f,0x6)/MAC(309c23e3847a,0)/IPv4(0.0.0.00.0.0.0,0,0)0000424f
Boot0006* Hard Drive    BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)0000474f00004e4fc50000000100000085005700440043002000570044003100360030003000420045004b0054002d0030003800500056004d00540031000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce62000200020002000570020002d00440058005700310033003100410038003100380038003400390000007fff04000000424f00004e4fbf000000010000008500530061006e004400690073006b00200053004400390053004e003800570031003200380047000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000100ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63800310036003200380039003000380038003100330038002000200020002000200020002000200000007fff04000000424f
Boot0007* Network Card  BBS(Network,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0600)0000474f00004e4fc7000000010000008700490042004100200047004500200053006c006f007400200030003300300030002000760031003500370038000000050109000600000000010416008b12e85cec2cf040837280640e3dc85806007fff040001041a00ae84b11df581724e85442bab0c2cac5c0300000200007fff040001044200ef47642dc93ba041ac194d51d01b4ce6490042004100200047004500200053006c006f0074002000300033003000300020007600310035003700380000007fff04000000424f00004e4fc7000000010000008700490042004100200043004c00200053006c006f007400200030003000460045002000760030003100300034000000050109000600000000010416008b12e85cec2cf040837280640e3dc85806007fff040001041a00ae84b11df581724e85442bab0c2cac5c001f060200007fff040001044200ef47642dc93ba041ac194d51d01b4ce6490042004100200043004c00200053006c006f0074002000300030004600450020007600300031003000340000007fff04000000424f
Boot0008* UEFI: Built-in EFI Shell      VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f

My investigation pointed me to this statement here.
EFI\boot\bootx64.efi: Fallback bootloader path
This is the only bootloader pathname that the UEFI firmware on 64-bit X86 systems will look for without any pre-existing NVRAM boot settings, so this is what you want to use on removable media.

This directory structure is confirmed on my PC:

$ ll /efi/EFI/BOOT/
.rwxr-xr-x root root 272 KB Fri Jul 26 18:22:04 2019  BOOTX64.EFI

My question now is:
Why do I get a Grub failure when booting this "Fallback bootloader path"?

If it only generates an error, can it be removed safely?

THX

Last edited by cmonty14 (2022-10-09 10:15:29)