Can`t boot, grub error after upgrade


After upgrading system was booting direct into setup.

I did everything written here and still can`t boot.

Now it reaches the grub_rescue with grub.debug.malloc not found error.

The output of `fdisk -l

Disk /dev/sda: 111.8 GiB, 120040980480 bytes, 2344550111 sectors
Disk model: Samsung XXX
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 0CXA5XA7-F9X6-43FF-89F5-99CCXXXXXXXX

Device         Start       End   Sectors   Size Type
/dev/sda1       2048 227110911 227108864 108.3G Linux filesystem
/dev/sda2  227110912 228159487   1048576   512M EFI System
/dev/sda5  228159488 234452991   6293504     3G Linux swap

Disk /dev/sdb: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: KINGSTON XXX
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 87FB4X96-91XX-4AAF-9D48-6A87XXXXXXXX

Device         Start       End   Sectors  Size Type
/dev/sdb1       2048 251660287 251658240  120G Linux filesystem
/dev/sdb2  251660288 252743679   1083392  529M Windows recovery environment
/dev/sdb3  252743680 252948479    204800  100M EFI System
/dev/sdb4  252948480 252981247     32768   16M Microsoft reserved
/dev/sdb5  252981248 405303062 152321815 72.6G Microsoft basic data
/dev/sdb6  405303296 406579199   1275904  623M Windows recovery environment

Disk /dev/loop0: 1.61 GiB, 1724010496 bytes, 3367208 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Output of efibootmgr

BootCurrent: 0015
Timeout: 2 seconds
BootOrder: 0001,0002,0003,0004,0019,0012,0000,0015,0011,000F,0010,0013,0014,0016,0017,0018,0008,0009
Boot0000* Windows Boot Manager	HD(3,GPT,6bd6dc10-a5ef-4f11-8a4c-ff510b2ecee3,0xf109000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000074000100000010000000040000007fff0400
Boot0001  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0002  Boot Menu	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0003  Diagnostic Splash Screen	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0004  Lenovo Diagnostics	FvFile(c9d55cc3-751f-456e-a627-aa2a456655af)
Boot0005* Manjaro	HD(2,GPT,9b7fe402-3970-48bb-9a08-bea18f64abad,0xd897000,0x100000)/File(\EFI\Manjaro\grubx64.efi)
Boot0006* EndeavourOS	HD(2,GPT,9b7fe402-3970-48bb-9a08-bea18f64abad,0xd897000,0x100000)/File(\EFI\EndeavourOS\grubx64.efi)
Boot0008  Other CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35406)
Boot0009  Other HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f606)
Boot000E* PCI LAN	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot000F* USB CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0010* USB FDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0011* ATAPI CD0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35401)
Boot0012* ATA HDD0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot0013* ATA HDD1	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
Boot0014* ATA HDD2	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f602)
Boot0015* USB HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0016* PCI LAN	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0017* ATAPI CD1	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35404)
Boot0018* ATA HDD3	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f604)
Boot0019* manjaro	HD(2,GPT,9b7fe402-3970-48bb-9a08-bea18f64abad,0xd897000,0x100000)/File(\EFI\manjaro\grubx64.efi)
Boot001A  Startup Interrupt Menu	FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot001B  ME Configuration Menu	FvFile(82988420-7467-4490-9059-feb448dd1963)
Boot001C  Rescue and Recovery	FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot001D* IDER BOOT CDROM	PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
Boot001E* IDER BOOT Floppy	PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
Boot001F* ATA HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0020* ATAPI CD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot0021* PCI LAN	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)

Tried to disable os-prober, same issue. Setup in both mode, uefi first. AHCI mode.

1 Like

If you followed everyting as advised on this forum, you should look into your bios-setup and re-arrange the boot sequence list in there, and delete unwanted entries, as not all UEFI bioses listen to what efibootmgr tells them.

Sometimes, a bios-update played-in from the hw-manufacturer helps making things a bit easier.

Welcome to EnOS forum! :enos:

what do you mean with this exactly?

UEFI/Legacy Boot option is Both
UEFI/Legacy Boot Priority is UEFI first

if OS is installed in legacy mode it will only boot in legacy mode if installed in UEFI mode it will only boot in UEFI mode…

I mean do you try to fix by using grub install methods for legacy Bios also ?
this could cause issues…
As it will write into MBR of the disk and EUEFI is using a partition instead of that… but writing MBR can cause inconsistency on the partitions…

Complexity isn’t your friend!


Thanks. First entry is the correct one tho.

Just checked and bios is upgraded. Maybe something messed in the EFI boot file, grub regenerates the entries right?

It’s installed in UEFI mode, I did not changed any bios config and it started failing to boot after upgrade.

BootOrder: 0001,0002,0003,0004,0019,0012,0000,0015,0011,000F,0010,0013,0014,0016,0017,0018,0008,0009
Boot0006* EndeavourOS	HD(2,GPT,9b7fe402-3970-48bb-9a08-bea18f64abad,0xd897000,0x100000)/File(\EFI\EndeavourOS\grubx64.efi)

So comparing the efibootmgr entries and bootorder showing that it doe snot include EndeavourOS within the number 0006

So how you do try booting it at all?

Did you do the advised grub-instal ... after the upgrade?

Yes, mounted system and efi partitions, chrooted into it and ran the commands. Output is ok but the malloc errors persists.

Then it must be bios-related, me thinks, unless you mounted the wrong partitions… as Joe hinted at.

if the installed EndeavourOS is on /dev/sda using ext4 filesystem or xfs (not BTRFS) and /dev/sda1 is the RFS with /dev/sda2 as ESP you would have needed to do the following from arch-chroot:

sudo mount /dev/sda1 /mnt
sudo mount /dev/sda2 /mnt/boot/efi
sudo arch-chroot /mnt
grub-mkconfig -o /boot/grub/grub.cfg

This would create a new efi boot entry called endeavouros (lower case)

I see that your ESP is second partition usually its the first. only to mention…


thanks @Stephane to hint on missing grub-mkconfig command :wink:

1 Like