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

how do i make it trustfull?
I tried selecting some grub file. That created an entry, that produces the out of range error.

and do you tried to remove/move the complete entry path in your ESP?

in chroot or if booted into OS under /boot/efi/EFI

and run grub-install again to create a new one.

i deleted entries via efibootmgr -b [entry-nr] -B and the created new one with grub-install.

What stands ESP for?

Efi-System-Partition the fat32 one used to write the efi entries to be readable by the firmware :wink:

If you run grub-install without any options given it will use the distributor entry from /etc/default/grub file in lowercase letters and overwrite or create the entry-path with this naming…
GRUB_DISTRIBUTOR=“EndeavourOS”

will create use this path:
/boot/efi/EFI/endeavouros

and the entry name in firmware will be the same it will be called endeavouros

I am not sure if it could happen that using the same path is always the best option could be recreating it fully can help remove some id or keys inside by recreating them…

2 Likes

If secureboot is off it should see in te bios? This issue can also be about the bios entrance. Each is unique also

Hello everybody,

I’m new to this forum and only some expierence with Linux. With that said, I encountered a problem, while trying to reinstall grub. The answer might be very trivial but I couldn’t figure out a solution (searching this forum and looking for answers on other forums)
I followed the instructions (for encrypted systems): https://forum.endeavouros.com/t/the-latest-grub-package-update-needs-some-manual-intervention/30689 but when I try to reinstall grub with grub-install, this error shows up:

[root@EndeavourOS /]# grub-install
Installing for x86_64-efi platform.
grub-install: error: /boot/efi doesn’t look like an EFI partition.

My linux partition is an ext4 and I assume thats the reason for this error.

For context this is the console output:

Console Output
[liveuser@eos-2022.08.28 ~]$ sudo fdisk -l
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850 
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: 

Device      Start       End   Sectors   Size Type
/dev/sda1    4096    618495    614400   300M EFI System
/dev/sda2  618496 976768064 976149569 465.5G Linux filesystem


Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
...

Partition 1 does not start on physical sector boundary.


Disk /dev/sdc: 14.46 GiB, 15525216256 bytes, 30322688 sectors
Disk model: v212w           
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: dos
Disk identifier: 

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdc1  *     2048 30322687 30320640 14.5G  c W95 FAT32 (LBA)


Disk /dev/loop0: 1.6 GiB, 1720696832 bytes, 3360736 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
[liveuser@eos-2022.08.28 ~]$ sudo lsblk -f
NAME FSTYPE FSVER LABEL     UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0
     squash 4.0                                                        0   100% /run/archiso/airootfs
sda                                                                             
├─sda1
│    vfat   FAT32 NO_LABEL  05EB-C810                                           
└─sda2
     crypto 1               a253cf75-44e0-4935-b360-4085a84f8fa1                
sdb                                                                             
...                              
sdc                                                                             
└─sdc1
     vfat   FAT32 EOS_202208
                            4A13-8C08                              12.7G    12% /run/archiso/bootmnt
[liveuser@eos-2022.08.28 ~]$ sudo cryptsetup open /dev/sda2 mycryptdevice
Enter passphrase for /dev/sda2: 
[liveuser@eos-2022.08.28 ~]$ sudo mount /dev/mapper/mycryptdevice /mnt
[liveuser@eos-2022.08.28 ~]$ sudo mount /dev/mapper/mycryptdevice /mnt/b
bin/  boot/ 
[liveuser@eos-2022.08.28 ~]$ sudo mount /dev/mapper/mycryptdevice /mnt/boot/efi/
[liveuser@eos-2022.08.28 ~]$ sudo arch-chroot /mnt
[root@EndeavourOS /]# grub-install
Installing for x86_64-efi platform.
grub-install: error: /boot/efi doesn't look like an EFI partition.
[root@EndeavourOS /]# exit
exit
[liveuser@eos-2022.08.28 ~]$ sudo lsblk -f
NAME FSTYPE FSVER LABEL     UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0
     squash 4.0                                                        0   100% /run/archiso/airootfs
sda                                                                             
├─sda1
│    vfat   FAT32 NO_LABEL  05EB-C810                                           
└─sda2
     crypto 1               a253cf75-44e0-4935-b360-4085a84f8fa1                
  └─mycryptdevice
     ext4   1.0             0267b39a-6f47-427e-8541-b9a01f0fcf63  350.6G    18% /mnt/boot/efi
                                                                                /mnt
sdb                                                                             
...
                              
sdc                                                                             
└─sdc1
     vfat   FAT32 EOS_202208
                            4A13-8C08                              12.7G    12% /run/archiso/bootmnt

sdb is a second HDD with some files so I deleted the output to make it more compact.

Thanks for any help/advice in advance!

This part is wrong.

It should be:

sudo mount /dev/mapper/mycryptdevice /mnt
sudo mount /dev/sda1 /mnt/boot/efi

I would reboot to get a clean setup and try again.

3 Likes

Thank you so much for your quick response and solution!

2 Likes

Did you reinstall grub when you used arch-chroot and then run the grub update command? I also had this on mine amongst other things.

2 posts were split to a new topic: Pamac fails to update

Im trying to fix my laptop after the update where I have to install grub via booting from a usb using the guide.

However at the stage where I have to mount my disk I’m having trouble,

Sudo mount /dev/nvme0n1p1 /mnt/boot/efi

Returns that /mnt/boot/efi mount point does not exist. I’m not sure how to get around this, would making that directory and installing grub there work?

I appreciate any help, thanks

No. That means that you mounted the wrong thing on /mnt

If you use btrfs make sure you follow the instructions for btrfs.

If not, please share the terminal output from and all the commands from the beginning so we can see what it going wrong.

Im definitely not using btrfs, here is my terminal output.
image

Can we see ls /mnt

Oh, it is a little blurry but it looks like you mounted your EFI partition at /mnt

The device that ends in 2 should be mounted at /mnt and the one which ends in 1 should be mounted at /mnt/boot/efi

you’re mounting the wrong way,
first umount your p1 partition:

sudo umount /mnt 

The mount it this way:

sudo mount /dev/nvme0n1p2 /mnt
sudo mount /dev/nvme0n1p1 /mnt/boot/efi

There is only EFI for ls /mnt

See above

Those device names seem to missing characters

I fixed it now. I’m really missing the lightbox feature. Or a new magnifying glass feature

1 Like

/mnt/boot/efi Mount Point does not exist

You need to share the whole session output so we can see what went wrong.