Grub 2:2.06.r322.gd9b4638c5-1 won't boot and goes straight to the BIOS after update

In either case. It is needed to tell it which subvolume to boot off of.

I am not sure if order matters but I usually put it after the root="stuff" section.

@dalto Thank you…

1 Like

@dalto Just rebooted with the updated “40_file” from grub.d and still no go…Any other thoughts…My concern is that grub is not even picking up the root partition information even though the efibootmgr shows EndeavourOS-grub…using the efibootmgr -b 0000 -a (not sure if that would even be necessary) to make active generates an error:

Could not set active state for Boot0000: No such file or directory

So I am not sure if there is another complicating factor occurring…thoughts?

I’ve got it recovered enough to boot into EFI but still “broken”

I was bit by this issue today and thought it was related to a quick power click that happened at my house. So I booted the EOS Artemis install ISO and stared at the screen hoping for inspiration. I opened Firefox on the Install ISO and it immediately talked about the grub problem. I followed the instructions and got my BTRFS system back up and running.

Thanks for how quickly this was documented everywhere. I thought I was going to have to reinstall from scratch even though I had lots of snapshots.

Thanks again to the experts.

6 Likes

Ok. my first computer broke with this so I followed live usb > mount > chroot > make grub cfg > install grub
But when I boot I get the grub rescue prompt:

error: symbol grub_debug_malloc not found.
Entering rescue mode…
grub rescue>_

So, I tried with another EOS computer which I hadn’ t updated yet. Updated everything then installed grub as indicated in wiki guide.
But I had the exact problem! it boots into grub rescue with grub_debug_malloc error.

Any ideas!
thanks!

I had this same experience and decided to reformat. All my data is backed up so this was the best solution for me.

Your MMV, so ìts not a recommendation. I run btrfs wirh snapshots, but they didn’t help, nor could anyone here give solution.

Something which might or might not be relevant…

I had one computer which had been updated and affected by the issue. I was able to recover it using the directions to boot from the LiveCD and reinstall the bootloader. This worked, but it seemed like there was a long delay before the grub menu came up.

On a whim, I decided to install grub-git from the AUR, thinking there might be some updates that haven’t made it upstream yet. The package built and, oddly, is the same version as the grub package in the normal repos. I reinstalled the bootloader, however, and noticed something interesting- the binary is considerably larger than the one from the regular grub package. I’d expect some difference, but not this much as I assume both are built the same way.

Either way, grub-git seems to work fine and without the long delay.

YMMV

Screw it…after wrestling with grub errors, I just decided to go with systemd boot. Was surprisingly painless to get up and running.

1 Like

booting from f11 key works for my. (asrock f11 boot menu) :rofl: :thinking: …waiting 15 seconds

I’m just going to add grub to the HoldPkg list for now. Not permanenty but just until this settles out.

I have two OS on separate drives.

  1. EOS is located on 265GB SSD disk
  2. Windows is located on 512GB NVME disk

beside that I also have 1TB nvme and 1TB HDD disk with stuff on them

Second linux is current live which Is located on ventoy

I have to fix boot on primary EOS drive which is “Disk /dev/sda: 232.89 GiB”

In that case /dev/sdc1 is probably your EFI partition and /dev/sdc2 is probably your root partition.

I’m going to jump in here with something “ODD” in my system that may have a bearing on this----I looked at my /etc/grub.d & noticed that both os-prober & uefi-firmware were 30_ Could that make a difference? will grub execute 30_os-prober & then 30_uefi-firmware correctly? I changed 30_os-prober to 25_os-prober then ran grub-mkconfig–looks like it’s output “looks” OK…I’m leary to reboot, so do advise if this looks OK.

Generating grub configuration file ...
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
insmod gfxmenu
loadfont ($root)/boot/grub/themes/EndeavourOS/terminus-12.pf2
loadfont ($root)/boot/grub/themes/EndeavourOS/terminus-14.pf2
loadfont ($root)/boot/grub/themes/EndeavourOS/terminus-16.pf2
loadfont ($root)/boot/grub/themes/EndeavourOS/terminus-18.pf2
loadfont ($root)/boot/grub/themes/EndeavourOS/ubuntu_regular_17.pf2
loadfont ($root)/boot/grub/themes/EndeavourOS/ubuntu_regular_20.pf2
loadfont ($root)/boot/grub/themes/EndeavourOS/unifont-regular-16.pf2
insmod png
set theme=($root)/boot/grub/themes/EndeavourOS/theme.txt
export theme
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
play 480 440 1
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
menuentry 'EndeavourOS' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-defa66bf-7526-45d2-8331-4ab969be8b5b' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod ext2
	search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
	echo	'Loading kernel linux-zen ...'
	linux	/boot/vmlinuz-linux-zen root=UUID=defa66bf-7526-45d2-8331-4ab969be8b5b rw  loglevel=3 random.trust_cpu=on ibt=off nvidia-drm.modeset=1
	echo	'Loading initial ramdisk ...'
	initrd	/boot/intel-ucode.img /boot/initramfs-linux-zen.img
}
submenu 'Advanced options for EndeavourOS' $menuentry_id_option 'gnulinux-advanced-defa66bf-7526-45d2-8331-4ab969be8b5b' {
	menuentry 'EndeavourOS, on linux-zen' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-zen-advanced-defa66bf-7526-45d2-8331-4ab969be8b5b' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
		echo	'Loading kernel linux-zen ...'
		linux	/boot/vmlinuz-linux-zen root=UUID=defa66bf-7526-45d2-8331-4ab969be8b5b rw  loglevel=3 random.trust_cpu=on ibt=off nvidia-drm.modeset=1
		echo	'Loading initial ramdisk ...'
		initrd	/boot/intel-ucode.img /boot/initramfs-linux-zen.img
	}
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-zen-fallback.img
	menuentry 'EndeavourOS, on linux-zen (fallback initramfs)' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-zen-fallback-defa66bf-7526-45d2-8331-4ab969be8b5b' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
		echo	'Loading kernel linux-zen ...'
		linux	/boot/vmlinuz-linux-zen root=UUID=defa66bf-7526-45d2-8331-4ab969be8b5b rw  loglevel=3 random.trust_cpu=on ibt=off nvidia-drm.modeset=1
		echo	'Loading initial ramdisk ...'
		initrd	/boot/intel-ucode.img /boot/initramfs-linux-zen-fallback.img
	}
	menuentry 'EndeavourOS, on linux-zen (recovery mode)' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-zen-recovery-defa66bf-7526-45d2-8331-4ab969be8b5b' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
		echo	'Loading kernel linux-zen ...'
		linux	/boot/vmlinuz-linux-zen root=UUID=defa66bf-7526-45d2-8331-4ab969be8b5b rw single 
		echo	'Loading initial ramdisk ...'
		initrd	/boot/intel-ucode.img /boot/initramfs-linux-zen-fallback.img
	}
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts.img
	menuentry 'EndeavourOS, on linux-lts' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-advanced-defa66bf-7526-45d2-8331-4ab969be8b5b' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
		echo	'Loading kernel linux-lts ...'
		linux	/boot/vmlinuz-linux-lts root=UUID=defa66bf-7526-45d2-8331-4ab969be8b5b rw  loglevel=3 random.trust_cpu=on ibt=off nvidia-drm.modeset=1
		echo	'Loading initial ramdisk ...'
		initrd	/boot/intel-ucode.img /boot/initramfs-linux-lts.img
	}
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-lts-fallback.img
	menuentry 'EndeavourOS, on linux-lts (fallback initramfs)' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-fallback-defa66bf-7526-45d2-8331-4ab969be8b5b' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
		echo	'Loading kernel linux-lts ...'
		linux	/boot/vmlinuz-linux-lts root=UUID=defa66bf-7526-45d2-8331-4ab969be8b5b rw  loglevel=3 random.trust_cpu=on ibt=off nvidia-drm.modeset=1
		echo	'Loading initial ramdisk ...'
		initrd	/boot/intel-ucode.img /boot/initramfs-linux-lts-fallback.img
	}
	menuentry 'EndeavourOS, on linux-lts (recovery mode)' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-recovery-defa66bf-7526-45d2-8331-4ab969be8b5b' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
		echo	'Loading kernel linux-lts ...'
		linux	/boot/vmlinuz-linux-lts root=UUID=defa66bf-7526-45d2-8331-4ab969be8b5b rw single 
		echo	'Loading initial ramdisk ...'
		initrd	/boot/intel-ucode.img /boot/initramfs-linux-lts-fallback.img
	}
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
	menuentry 'EndeavourOS, on linux' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-defa66bf-7526-45d2-8331-4ab969be8b5b' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
		echo	'Loading kernel linux ...'
		linux	/boot/vmlinuz-linux root=UUID=defa66bf-7526-45d2-8331-4ab969be8b5b rw  loglevel=3 random.trust_cpu=on ibt=off nvidia-drm.modeset=1
		echo	'Loading initial ramdisk ...'
		initrd	/boot/intel-ucode.img /boot/initramfs-linux.img
	}
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-fallback.img
	menuentry 'EndeavourOS, on linux (fallback initramfs)' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-defa66bf-7526-45d2-8331-4ab969be8b5b' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
		echo	'Loading kernel linux ...'
		linux	/boot/vmlinuz-linux root=UUID=defa66bf-7526-45d2-8331-4ab969be8b5b rw  loglevel=3 random.trust_cpu=on ibt=off nvidia-drm.modeset=1
		echo	'Loading initial ramdisk ...'
		initrd	/boot/intel-ucode.img /boot/initramfs-linux-fallback.img
	}
	menuentry 'EndeavourOS, on linux (recovery mode)' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-recovery-defa66bf-7526-45d2-8331-4ab969be8b5b' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root defa66bf-7526-45d2-8331-4ab969be8b5b
		echo	'Loading kernel linux ...'
		linux	/boot/vmlinuz-linux root=UUID=defa66bf-7526-45d2-8331-4ab969be8b5b rw single 
		echo	'Loading initial ramdisk ...'
		initrd	/boot/intel-ucode.img /boot/initramfs-linux-fallback.img
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/25_os-prober ###
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found EndeavourOS Linux (rolling) on /dev/nvme0n1p4
menuentry 'EndeavourOS Linux (rolling) (on /dev/nvme0n1p4)' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-8a4633de-408c-481a-935e-9fd5f83f2e6c' {
	insmod part_gpt
	insmod ext2
	search --no-floppy --fs-uuid --set=root 8a4633de-408c-481a-935e-9fd5f83f2e6c
	linux /boot/vmlinuz-linux-zen root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw loglevel=3 random.trust_cpu=on ibt=off
	initrd /boot/intel-ucode.img /boot/initramfs-linux-zen.img
}
submenu 'Advanced options for EndeavourOS Linux (rolling) (on /dev/nvme0n1p4)' $menuentry_id_option 'osprober-gnulinux-advanced-8a4633de-408c-481a-935e-9fd5f83f2e6c' {
	menuentry 'EndeavourOS (on /dev/nvme0n1p4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux-zen--8a4633de-408c-481a-935e-9fd5f83f2e6c' {
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 8a4633de-408c-481a-935e-9fd5f83f2e6c
		linux /boot/vmlinuz-linux-zen root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw loglevel=3 random.trust_cpu=on ibt=off
		initrd /boot/intel-ucode.img /boot/initramfs-linux-zen.img
	}
	menuentry 'EndeavourOS, on linux-zen (on /dev/nvme0n1p4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux-zen--8a4633de-408c-481a-935e-9fd5f83f2e6c' {
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 8a4633de-408c-481a-935e-9fd5f83f2e6c
		linux /boot/vmlinuz-linux-zen root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw loglevel=3 random.trust_cpu=on ibt=off
		initrd /boot/intel-ucode.img /boot/initramfs-linux-zen.img
	}
	menuentry 'EndeavourOS, on linux-zen (fallback initramfs) (on /dev/nvme0n1p4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux-zen--8a4633de-408c-481a-935e-9fd5f83f2e6c' {
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 8a4633de-408c-481a-935e-9fd5f83f2e6c
		linux /boot/vmlinuz-linux-zen root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw loglevel=3 random.trust_cpu=on ibt=off
		initrd /boot/intel-ucode.img /boot/initramfs-linux-zen-fallback.img
	}
	menuentry 'EndeavourOS, on linux-zen (recovery mode) (on /dev/nvme0n1p4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux-zen-root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw single-8a4633de-408c-481a-935e-9fd5f83f2e6c' {
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 8a4633de-408c-481a-935e-9fd5f83f2e6c
		linux /boot/vmlinuz-linux-zen root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw single
		initrd /boot/intel-ucode.img /boot/initramfs-linux-zen-fallback.img
	}
	menuentry 'EndeavourOS, on linux-lts (on /dev/nvme0n1p4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux-lts--8a4633de-408c-481a-935e-9fd5f83f2e6c' {
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 8a4633de-408c-481a-935e-9fd5f83f2e6c
		linux /boot/vmlinuz-linux-lts root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw loglevel=3 random.trust_cpu=on ibt=off
		initrd /boot/intel-ucode.img /boot/initramfs-linux-lts.img
	}
	menuentry 'EndeavourOS, on linux-lts (fallback initramfs) (on /dev/nvme0n1p4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux-lts--8a4633de-408c-481a-935e-9fd5f83f2e6c' {
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 8a4633de-408c-481a-935e-9fd5f83f2e6c
		linux /boot/vmlinuz-linux-lts root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw loglevel=3 random.trust_cpu=on ibt=off
		initrd /boot/intel-ucode.img /boot/initramfs-linux-lts-fallback.img
	}
	menuentry 'EndeavourOS, on linux-lts (recovery mode) (on /dev/nvme0n1p4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux-lts-root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw single-8a4633de-408c-481a-935e-9fd5f83f2e6c' {
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 8a4633de-408c-481a-935e-9fd5f83f2e6c
		linux /boot/vmlinuz-linux-lts root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw single
		initrd /boot/intel-ucode.img /boot/initramfs-linux-lts-fallback.img
	}
	menuentry 'EndeavourOS, on linux (on /dev/nvme0n1p4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux--8a4633de-408c-481a-935e-9fd5f83f2e6c' {
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 8a4633de-408c-481a-935e-9fd5f83f2e6c
		linux /boot/vmlinuz-linux root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw loglevel=3 random.trust_cpu=on ibt=off
		initrd /boot/intel-ucode.img /boot/initramfs-linux.img
	}
	menuentry 'EndeavourOS, on linux (fallback initramfs) (on /dev/nvme0n1p4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux--8a4633de-408c-481a-935e-9fd5f83f2e6c' {
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 8a4633de-408c-481a-935e-9fd5f83f2e6c
		linux /boot/vmlinuz-linux root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw loglevel=3 random.trust_cpu=on ibt=off
		initrd /boot/intel-ucode.img /boot/initramfs-linux-fallback.img
	}
	menuentry 'EndeavourOS, on linux (recovery mode) (on /dev/nvme0n1p4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux-root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw single-8a4633de-408c-481a-935e-9fd5f83f2e6c' {
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 8a4633de-408c-481a-935e-9fd5f83f2e6c
		linux /boot/vmlinuz-linux root=UUID=8a4633de-408c-481a-935e-9fd5f83f2e6c rw single
		initrd /boot/intel-ucode.img /boot/initramfs-linux-fallback.img
	}
}

### END /etc/grub.d/25_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
Adding boot menu entry for UEFI Firmware Settings ...
fwsetup --is-supported
if [ "$grub_platform" = "efi" -a "$?" = 0 ]; then
	menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
		fwsetup
	}
fi
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry 'Windows 10' {
    search --fs-uuid --no-floppy --set=root EC96-41E7
    chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###
done

OK—I ran my updates I need to—then ran sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EndeavourOS then sudo grub-mkconfig. Crossed my fingers & rebooted. The only thing I noticed was that the grub menu was a different font size than before…what else should I be looking for?

I do have grub-tools installed & am running the current grub.

It shouldn’t matter that they both start with 30.

Im using an encrypted BTRFS. I managed to chroot, downgraded grub but I must have messed something up. On next bootup it booted up into a blank screen with frozen prompt. I had to do a hard reset and now on startup after entering the passphrase it enters grub rescue with

error: file /0/boot/grub/x86_64-efi/normal.mod' not found.

Load the live usb back up, go through the same steps:
sudo cryptsetup open /dev/nvme0n1p2 mycryptdevice
enter in my passphrase and then
sudo mount /dev/mapper/mycryptdevice /mnt -o subvol=@
which errors
mount: /mnt: can't read superblock on /dev/mapper/mycryptdevice. dmesg(1) may have more information after failed mount system call.

I’ve tried running sudo btrfs rescue super-recover but it says All supers are valid, no need to recover

dmesg gives

263.013959] BTRFS critical (device dm-0): corrupt leaf: root=1 block=30408704 slot=0, invalid root generation, have 104979 expect (0, 104977] [ 263.013964] BTRFS error (device dm-0): block=30408704 read time tree block corruption detected [ 263.014256] BTRFS critical (device dm-0): corrupt leaf: root=1 block=30408704 slot=0, invalid root generation, have 104979 expect (0, 104977] [ 263.014258] BTRFS error (device dm-0): block=30408704 read time tree block corruption detected [ 263.014261] BTRFS warning (device dm-0): failed to read fs tree: -5 [ 263.014962] BTRFS error (device dm-0): open_ctree failed

I feel like jumping off a bridge right now, had about a months worth of work not backed up. Is there any to fix this? Should I run sudo btrfs check --repair /dev/mapper/mycryptdevice?

To avoid this update until the problem is fixed, you can edit the pacman.conf file and add grub to the IgnorePkg line. To do this , edit the file:

sudo nano /etc/pacman.conf

Under the [options] section we look for the line:

#IgnorePkg

Let’s see an example of what we will find:

[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   =
#IgnoreGroup =

What we will have to do is uncomment the line (remove the # character) and add grub. So the line will look like this:

IgnorePkg   = grub

Save the file (Ctrl+o) and exit (Ctrl+x).

This can also be used after updating and having obtained the error, they have corrected it. The change will have to be kept until grub is updated and the error is fixed. When this happens, we will have to edit the pacman.conf file again, and then add the # character to this line (to comment it out), and also remove the file name (grub), leaving it like this:

#IgnorePkg
1 Like

OK–I left it that way for better (in my own mind) housekeeping…

2 Likes

This sounds interesting @JKMooney
As I saw on your profile you are experienced and not so noob like me!
Just curious:

  • as systemd boot is part of the systemd, this means it is ALWAYS there and will NEVER break? (I mean much less prone to bugs and glitches?)

  • I am on BTRFS, Snapper, and only EOS installed, would it be OK with systemd boot?

  • How can I install and use systemd boot (to test, may stick with it but may revert back).

  • IF there is a system update that breaks things, can I still boot? Restore an earlier snapshot?

Any feed back highly appreciated!