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

**URL:** <https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653>\
**Category:** General system\
**Created:** [August 25, 2022, 8:47am UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653 "2022-08-25T08:47:28Z")\
**Posts on this page:** 1\
**Showing post:** 1276

<div class="post-metadata">

**Author:** ![pntrx](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/p/a183cd/32.png) [@pntrx](https://forum.endeavouros.com/u/pntrx)\
**Post date:** [September 11, 2022, 2:38pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1276 "2022-09-11T14:38:42Z")

</div>

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](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**
>
> ```plaintext
> [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!

---

_[View the full topic](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653)._