GRUB doesnt work correctly

General system Newbie
1

Hi everyone!

I recently installed EndeavourOS with a Windows 11 dual boot setup. However, when I start the PC, I encounter the following error:

error: no such device: (UUID of the EndeavourOS partition)
error: unknown filesystem
Entering rescue mode…
grub rescue>

Interestingly, if I enter the UEFI settings and then exit without making any changes, the PC automatically reboots, and everything works as expected until the next reboot.

2

You need to enter UEFI and select the proper entry to boot from and save it before exiting the Bios settings.

3

Thanks for your reply. I only have the option to boot from OS-Boot-Manager, USB-Flash-Drive, and CD/DVD drives. OS-Boot-Manager is already selected.

4

Did you install using grub as the bootloader or was it the default which is systemd-boot?

5

I installed GRUB as the bootloader.

6

What happens if you run the grub update command and reboot?

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

7

Still the same issue.

8

What is the output of efibootmgr?

See if you get a different result if you reinstall Grub first.

sudo grub-install

Then regenerate the Grub config again.

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

BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0000
Boot0000* Windows Boot Manager HD(1,GPT,7454e1a1-1e88-4762-b3dd-a9131ace4f5e,0x800,0x82000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000026000100000010000000040000007fff0400
Boot0001* endeavouros HD(1,GPT,7454e1a1-1e88-4762-b3dd-a9131ace4f5e,0x800,0x82000)/\EFI\endeavouros\grubx64.efi

It stays the same before and after reinstall except that endeavouros\grubx64.efi was written in capital letters before.

10

Hmm, that is interesting. :thinking:

Check if UEFI mode is set to “UEFI only” (not Legacy BIOS). If your BIOS has CMS try disabling it.

11

It should be in UEFI because I only have UEFI Boot order and there is not even an option related to legacy boot.

12

That’s right, it should be. Don’t forget to check for CSM as well (it might be called something else).

Post the output of these commands into the thread, in case there is a clue in the output.

It may be worth checking if there is a BIOS update available for your motherboard.

13

Installing for x86_64-efi platform.
Installation finished. No error reported.

Generating grub configuration file …
Found background: /usr/share/endeavouros/splash.png
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: initramfs-linux-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings …
done

14

Looks good to me. If you continue to have an issue, my guess would be there is a problem with your UEFI configuration.

15

That still didnt change anything sadly.

What could I still try then?

16

What does command
df -hT
show?

Just wondering what filesystem the EFI partition has…

17 
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/sda2      ext4      672G   12G  627G   2% /
devtmpfs       devtmpfs  4,0M     0  4,0M   0% /dev
tmpfs          tmpfs     7,8G     0  7,8G   0% /dev/shm
efivarfs       efivarfs  192K   32K  156K  17% /sys/firmware/efi/efivars
tmpfs          tmpfs     3,1G  1,8M  3,1G   1% /run
tmpfs          tmpfs     7,8G   28K  7,8G   1% /tmp
tmpfs          tmpfs     1,0M     0  1,0M   0% /run/credentials/systemd-journald.service
tmpfs          tmpfs     1,0M     0  1,0M   0% /run/credentials/systemd-udev-load-credentials.service
tmpfs          tmpfs     1,0M     0  1,0M   0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs          tmpfs     1,0M     0  1,0M   0% /run/credentials/systemd-sysctl.service
tmpfs          tmpfs     1,0M     0  1,0M   0% /run/credentials/systemd-sysusers.service
tmpfs          tmpfs     1,0M     0  1,0M   0% /run/credentials/systemd-tmpfiles-setup-dev.service
tmpfs          tmpfs     1,0M     0  1,0M   0% /run/credentials/systemd-vconsole-setup.service
/dev/nvme0n1p1 vfat      256M   83M  174M  33% /boot/efi
tmpfs          tmpfs     1,0M     0  1,0M   0% /run/credentials/systemd-tmpfiles-setup.service
tmpfs          tmpfs     1,6G  116K  1,6G   1% /run/user/1000
18

That is interesting that you have two disks, the EFI partition on one and the root partition on the other. What is on /dev/sda1?

Did you check these things? You did not say either way.

Other than those:

  • Look for a “Fast Boot” option and disable it.
  • Double-check the boot order in the BIOS settings to ensure that the UEFI firmware is set to boot from the correct disk (the NVMe drive with the EFI system partition).
  • Some BIOSes have a “Disk Detection” or “Disk Initialization” option that can affect how disks are detected and initialized during the boot process. If you have something like this, try disabling it to see if it makes a difference.
  • Check that the SATA controller is set to AHCI mode (not IDE or RAID mode).
  • Since your EFI partition is on the NVMe disk, check that the NVMe controller is set to PCIe mode.
19

You may try adding a timeout for UEFI boot, with efibootmgr.
Test a high number like 10 sec. If it works, you may go down to find a shorter one.

20

Thats Additional Windows storage in case I ever need it.

I thought I had already said that. I have but I didnt see anything wrong with them.

That could be it but Im having trouble finding out if theres a newer version cause the devices arent really recognized correctly.

That actually was still on RAID but that still didnt fix the problem :frowning:

I think i should try updating the BIOS in case there is any newer version. I think its likely that the current one is a bit outdatet.