# 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:** 20\
**Page:** 60

<div class="post-metadata">

**Author:** ![anon11595408](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/a/f1d935/32.png) [@anon11595408](https://forum.endeavouros.com/u/anon11595408)\
**Post date:** [September 6, 2022, 2:44pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1202 "2022-09-06T14:44:03Z")

</div>

So `/dev/sda6` is your root-partition.

What is `/dev/sda8` ?

---

<div class="post-metadata">

**Author:** ![dotarjun](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/d/97f17d/32.png) [@dotarjun](https://forum.endeavouros.com/u/dotarjun)\
**Post date:** [September 6, 2022, 2:45pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1203 "2022-09-06T14:45:14Z")

</div>

My broken manjaro install. I need to wipe it as I distro hopped from Manjaro to EOS

---

<div class="post-metadata">

**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\
**Post date:** [September 6, 2022, 2:49pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1204 "2022-09-06T14:49:26Z")

</div>

> [@dotarjun](#):
>
> can I just downgrade grub?

Yes, from within the chroot that will work.

> [@dotarjun](#):
>
> I use yay so `downgrade` won’t work

Those two things aren’t related. downgrade should work fine

---

<div class="post-metadata">

**Author:** ![dotarjun](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/d/97f17d/32.png) [@dotarjun](https://forum.endeavouros.com/u/dotarjun)\
**Post date:** [September 6, 2022, 2:57pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1205 "2022-09-06T14:57:23Z")

</div>

rebooting after this

```auto
[root@EndeavourOS /]# downgrade grub
:: Retrieving packages...
 grub-2:2.06-5-x86_64 6.7 MiB 494 KiB/s 00:14 [------------------------------------------------------] 100%
loading packages...
warning: downgrading package grub (2:2.06.r322.gd9b4638c5-1 => 2:2.06-5)
resolving dependencies...
looking for conflicting packages...

Package (1) Old Version New Version Net Change

grub 2:2.06.r322.gd9b4638c5-1 2:2.06-5 1.08 MiB

Total Installed Size: 34.10 MiB
Net Upgrade Size: 1.08 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring [------------------------------------------------------] 100%
(1/1) checking package integrity [------------------------------------------------------] 100%
(1/1) loading package files [------------------------------------------------------] 100%
(1/1) checking for file conflicts [------------------------------------------------------] 100%
:: Processing package changes...
(1/1) downgrading grub [------------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Fix 'grub' and 'os-prober' after upgrading either of them.
===> INFO: grub-tools / grub-fix-initrd-generation:
===> INFO: /etc/grub.d/30_os-prober changed. See file /var/log/grub-fix-initrd-generation.log.
===> INFO: /etc/grub.d/10_linux changed. See file /var/log/grub-fix-initrd-generation.log.
Generating grub configuration file ...
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-lts-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-fallback.img
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 Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found Windows Boot Manager on /dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
(3/4) Checking which packages need to be rebuilt
(4/4) Updating the info directory file...
add grub to IgnorePkg? [y/N] 
[root@EndeavourOS /]# ^C
[root@EndeavourOS /]# 

```

---

<div class="post-metadata">

**Author:** ![anon11595408](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/a/f1d935/32.png) [@anon11595408](https://forum.endeavouros.com/u/anon11595408)\
**Post date:** [September 6, 2022, 2:59pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1206 "2022-09-06T14:59:37Z")

</div>

> [@dotarjun](#):
>
> ```auto
> Updating the info directory file...
> add grub to IgnorePkg? [y/N] 
> 
> ```

Should be answered with N for a one-time try to reboot.

---

<div class="post-metadata">

**Author:** ![dotarjun](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/d/97f17d/32.png) [@dotarjun](https://forum.endeavouros.com/u/dotarjun)\
**Post date:** [September 6, 2022, 3:09pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1207 "2022-09-06T15:09:48Z")

</div>

I did `y` and it worked. Tysm everyone \<3

---

<div class="post-metadata">

**Author:** ![anon11595408](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/a/f1d935/32.png) [@anon11595408](https://forum.endeavouros.com/u/anon11595408)\
**Post date:** [September 6, 2022, 3:17pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1208 "2022-09-06T15:17:10Z")

</div>

That means, grub is excluded from further updates on your system now. You need to undo that in case you want to update grub again in the future.

---

<div class="post-metadata">

**Author:** ![ceph](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ceph/32/30222_2.png) [@ceph](https://forum.endeavouros.com/u/ceph)\
**Post date:** [September 6, 2022, 3:52pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1209 "2022-09-06T15:52:05Z")

</div>

> [@dotarjun](#):
>
> `sudo mount /dev/sda6 /mnt/boot/efi`

Just helpful to remember for chroot next time, you mounted the wrong partition for EFI, I think your linux efi is probably at `/dev/sda1`, do `ls` on it to confirm or else it would be in `/dev/nvme0n1p1`

---

<div class="post-metadata">

**Author:** ![buntel](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/buntel/32/64501_2.png) [@buntel](https://forum.endeavouros.com/u/buntel)\
**Post date:** [September 7, 2022, 10:44am UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1210 "2022-09-07T10:44:43Z")

</div>

Unfortunately this didn’t helped. I deleted all my old entries and did another grup-install afterwards. If I try to boot I’m getting the same error after selecting which kernel I want to boot.

---

<div class="post-metadata">

**Author:** ![ceph](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ceph/32/30222_2.png) [@ceph](https://forum.endeavouros.com/u/ceph)\
**Post date:** [September 7, 2022, 12:12pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1211 "2022-09-07T12:12:51Z")

</div>

Is the error you are getting out of range error?  
what’s your `efibootmgr -v` now?

---

<div class="post-metadata">

**Author:** ![Radels](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/13edae/32.png) [@Radels](https://forum.endeavouros.com/u/Radels)\
**Post date:** [September 7, 2022, 2:06pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1212 "2022-09-07T14:06:37Z")

</div>

Hello everyone. I recently updated my EndeavourOS, and as you know, there were problems with grub.

I followed these instructions:

> [@The latest grub package update needs some manual intervention](https://forum.endeavouros.com/t/the-latest-grub-package-update-needs-some-manual-intervention/30689):
>
> (Grub 2:2.06.r322.gd9b4638c5-1) Grub Update Causing Unbootable OS On UEFI Systems A grub update today is causing boot issues on UEFI systems. It will make most systems unbootable so take care! with no intervention, the system will just boot directly into Firmware with no way to boot the OS. If you have this issue follow these instructions: First boot onto an EndeavourOS Live ISO. Ensure that you are booting the ISO via UEFI mode. Follow these instructions to chroot into your install: [ht…](https://discovery.endeavouros.com/system-rescue/arch-chroot-for-efi-uefi-systems/2021/03/)

[https://discovery.endeavouros.com/system-rescue/arch-chroot-for-efi-uefi-systems/2021/03/](https://discovery.endeavouros.com/system-rescue/arch-chroot-for-efi-uefi-systems/2021/03/)

But unfortunately I can’t `grub-install`. I am not experienced in OS management, and after a couple of hours of trying I decided to create this thread for help.

This is an output of `sudo fdisk -l`:

```auto
Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: SK hynix PC711 HFS512GDE9X073N          
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: 0C0B6E43-B4DE-4943-A6D2-29692E32329A

Device Start End Sectors Size Type
/dev/nvme0n1p1 4096 618495 614400 300M EFI System
/dev/nvme0n1p2 618496 1000206899 999588404 476.6G Linux filesystem

Disk /dev/sda: 14.51 GiB, 15581839360 bytes, 30433280 sectors
Disk model: Disk 2.0        
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: 0xab3ab792

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 64 3579839 3579776 1.7G 0 Empty
/dev/sda2 3579840 3788735 208896 102M ef EFI (FAT-12/16/32)

Disk /dev/loop0: 1.6 GiB, 1723146240 bytes, 3365520 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

```

I am right now sitting from live boot of my USB with an EndeavourOS.  
After trying every single combination many times, and then running `sudo arch-chroot /mnt`, I was able to chroot: after running `ls /home` I get my user directory.  
However, running `grub-install` gets me this message:

```auto
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.

```

I am very sorry if I did something incorrectly. I didn’t sleep for last 26 hours and there is an important work currently on my OS. Would appreciate any help I can get.

Thank you in advance.

---

<div class="post-metadata">

**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\
**Post date:** [September 7, 2022, 2:13pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1213 "2022-09-07T14:13:55Z")

</div>

> [@Radels](#):
>
> ```auto
> Device Start End Sectors Size Type
> /dev/nvme0n1p1 4096 618495 614400 300M EFI System
> /dev/nvme0n1p2 618496 1000206899 999588404 476.6G Linux filesystem
> 
> ```

```auto
sudo mount /dev/nvme0n1p2 /mnt
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
sudo arch-chroot /mnt
grub-install
grub-mkconfig -o /boot/grub/grub.cfg

```

If still:

> [@Radels](#):
>
> `grub-install: error: cannot find EFI directory`

try:  
`grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=enos-grub`

When done type exit to quit chroot. Reboot.

---

<div class="post-metadata">

**Author:** ![Radels](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/13edae/32.png) [@Radels](https://forum.endeavouros.com/u/Radels)\
**Post date:** [September 7, 2022, 2:26pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1214 "2022-09-07T14:26:15Z")

</div>

You are my hero. I was really worried about losing my work.

This community is amazing! Thank you, EndeavourOS community, and specifically you, pebcak, for very fast feedback. ❤

---

<div class="post-metadata">

**Author:** ![petsam](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/petsam/32/41308_2.png) [@petsam](https://forum.endeavouros.com/u/petsam)\
**Post date:** [September 7, 2022, 9:18pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1215 "2022-09-07T21:18:35Z")

</div>

To moderators:  
I suppose the hot/warm period is over. IMHO, any more similar issues would be better left to their own topic, if started individually, and those users would need personalized instructions.

Unless you have set up some goal to see how many posts could this give 😆 , you might want to consider not merging more here… ? 🤷

Just an opinion, nothing more. 😉

---

<div class="post-metadata">

**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\
**Post date:** [September 7, 2022, 9:53pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1216 "2022-09-07T21:53:52Z")

</div>

> [@petsam](#):
>
> I suppose the hot/warm period is over. IMHO

![2022-09-07_23-49](https://forum.endeavouros.com/uploads/default/original/3X/c/c/cc370c80bfa0fd7d728bfa6677b35bb409bebdf2.png)

Still warm…

endless … same on chat there are still endless users reaching out for help

---

<div class="post-metadata">

**Author:** ![anon11595408](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/a/f1d935/32.png) [@anon11595408](https://forum.endeavouros.com/u/anon11595408)\
**Post date:** [September 7, 2022, 9:55pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1217 "2022-09-07T21:55:00Z")

</div>

> [@joekamprad](#):
>
> same on chat there are still endless users reaching out for help

OMG

---

<div class="post-metadata">

**Author:** ![sradjoker](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/sradjoker/32/64224_2.png) [@sradjoker](https://forum.endeavouros.com/u/sradjoker)\
**Post date:** [September 7, 2022, 9:57pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1218 "2022-09-07T21:57:43Z")

</div>

> [@petsam](#):
>
> Unless you have set up some goal to see how many posts could this give

2000 🤣

---

<div class="post-metadata">

**Author:** ![anon11595408](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/a/f1d935/32.png) [@anon11595408](https://forum.endeavouros.com/u/anon11595408)\
**Post date:** [September 7, 2022, 10:00pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1219 "2022-09-07T22:00:02Z")

</div>

> [@joekamprad](#):
>
> Still warm…
> 
> endless …

Keeping so many communication-channels open must be very stressful in the long run, me thinks. ♥

---

<div class="post-metadata">

**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\
**Post date:** [September 8, 2022, 1:03pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1220 "2022-09-08T13:03:10Z")

</div>

if only everyone would stay on topic and only users would posting needed info when posting here… it would be only 500 posts by now 😉

```auto
lsblk -f
efibootmgr

```

or share it:

```auto
lsblk -f >> shareinfo.txt && efibootmgr >> shareinfo.txt && cat shareinfo.txt | eos-sendlog

```

---

<div class="post-metadata">

**Author:** ![buntel](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/buntel/32/64501_2.png) [@buntel](https://forum.endeavouros.com/u/buntel)\
**Post date:** [September 8, 2022, 3:18pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/1221 "2022-09-08T15:18:00Z")

</div>

Yes I get this error after selecting some kernel. After I did grup-install I can see the endeavour entry when doing efibootmgr -v. It’s also at the first position (0000).  
I think this means this part should be okay, because I can boot (don’t know how we call this part of software) endeavour where I can chose which kernel I want to use. And after this I’m getting this out of range error.

[Previous page](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653.md?page=59)

[Next page](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653.md?page=61)
