# 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:** 42

<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:** [August 29, 2022, 12:39pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/838 "2022-08-29T12:39:17Z")

</div>

At your request, I wrote you specific instructions for your specific system, here: [Grub 2:2.06.r322.gd9b4638c5-1 won't boot and goes straight to the BIOS after update - #799 by dalto](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/799)

---

<div class="post-metadata">

**Author:** ![BeeWay](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/b/f14d63/32.png) [@BeeWay](https://forum.endeavouros.com/u/BeeWay)\
**Post date:** [August 29, 2022, 1:22pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/839 "2022-08-29T13:22:37Z")

</div>

> [@dalto](#):
>
> Of course, the installer has to run `grub-install` after installing grub.

Hehe OK, fair enough. The reason why I asked was because I thought the online installer might use the live USB’s own version of grub to run grub-install before actually downloading the grub package. Glad that’s not the case.

After a new online install is completed with version r322…-1 and later grub is updated to the upcoming r322…-3, there is no extra action required, correct? Because the existing grub version would already be recent enough?

---

<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:** [August 29, 2022, 1:24pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/840 "2022-08-29T13:24:10Z")

</div>

> [@BeeWay](#):
>
> After a new online install is completed with version r322…-1 and later grub is updated to the upcoming r322…-3, there is no extra action required, correct?

Yes. Both because it is after the transition and there is no technical difference between those two packages.

---

<div class="post-metadata">

**Author:** ![Dimoi](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/d/ecccb3/32.png) [@Dimoi](https://forum.endeavouros.com/u/Dimoi)\
**Post date:** [August 29, 2022, 1:33pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/841 "2022-08-29T13:33:32Z")

</div>

It Works !  
Thank you very much 👍

---

<div class="post-metadata">

**Author:** ![spsf64](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/spsf64/32/58346_2.png) [@spsf64](https://forum.endeavouros.com/u/spsf64)\
**Post date:** [August 29, 2022, 2:11pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/842 "2022-08-29T14:11:47Z")

</div>

This could be a solution for such problem like grub?  
There could be 2 different repos; one before arch repos (even if it is empty) to hold any problematic packages as soon it is discovered and the current one at the end.

---

<div class="post-metadata">

**Author:** ![MindTheGAAP](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mindthegaap/32/47060_2.png) [@MindTheGAAP](https://forum.endeavouros.com/u/MindTheGAAP)\
**Post date:** [August 29, 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/843 "2022-08-29T14:26:38Z")

</div>

Hi, I have crypto\_luks + BTRFS setup and can’t seem to chroot.

Also followed the instruction in here [https://discovery.endeavouros.com/system-rescue/arch-chroot-for-bios-legacy-systems/2021/03/](https://discovery.endeavouros.com/system-rescue/arch-chroot-for-bios-legacy-systems/2021/03/) but no luck.

I first typed

1. `cryptsetup open /dev/sda1 mycryptdevice`
2. input my key phrase
3. I get the message saying `Device mycryptdevice already exists.`
4. Then i typed `mount /dev/mapper/mycryptdevice /mnt`
5. Then `mount /dev/sda1`
6. I get message saying `mount: /dev/sda1: can't find in /etc/fstab.`
7. I also typed `sudo mount /dev/sda1 /mnt -o subvol=@`
8. but get message saying `mount: /mnt: unknown filesystem type 'crypto_LUKS'. dmesg(1) may have more information after failed mount system call.`

Here is the output of `lsblk -f`

![image](https://forum.endeavouros.com/uploads/default/original/3X/f/5/f54ffa9b9e88f4e130db7e55b2d903c975ba73b4.jpeg)

Here is the output of `lsblk -l`

![image](https://forum.endeavouros.com/uploads/default/original/3X/0/6/0685c04d9d2ca05f40b50e53c33321e945ec1fb6.png)

Any help would be greatly appreciate it.

Thank you.

---

<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:** [August 29, 2022, 2:27pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/844 "2022-08-29T14:27:13Z")

</div>

> [@spsf64](#):
>
> There could be 2 different repos; one before arch repos

We have discussed the option of adding an overlay repo like that but a decision has not been made on that yet.

---

<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:** [August 29, 2022, 2:28pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/845 "2022-08-29T14:28:19Z")

</div>

Actually that doesn’t look like a UEFI system.

BIOS systems aren’t impacted by this issue.

What is the issue you are having specifically?

---

<div class="post-metadata">

**Author:** ![noroot](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/e5b9ba/32.png) [@noroot](https://forum.endeavouros.com/u/noroot)\
**Post date:** [August 29, 2022, 2:29pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/846 "2022-08-29T14:29:50Z")

</div>

I was, obviously, also bitten by this issue. But thanks to the help here, in the blog and on telegram it’s fixed. Inconvenient, but that sadly happens.

I do have one remaining issue though. I have encrypted `/` with luks. Decrypting it at boot is suddenly _very_ slow. When I installed eos I had to change the iterations (because there is no hardware support at boot and the installer that tests the iterations for 2s was not usable at boot).

![afbeelding](https://forum.endeavouros.com/uploads/default/original/3X/7/a/7ad301504c478f98812dd5800b88912280d634d9.png)

This is what I tried to fix it again, but to no avail. Anyone encountered something similar? And hopefully a tip on how to fix this?

---

<div class="post-metadata">

**Author:** ![MindTheGAAP](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mindthegaap/32/47060_2.png) [@MindTheGAAP](https://forum.endeavouros.com/u/MindTheGAAP)\
**Post date:** [August 29, 2022, 2:42pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/847 "2022-08-29T14:42:51Z")

</div>

You are correct that I am not affected but wanted to chroot and downgrade and wait for new release.

can you share the link to chroot again please?

I am also learning to chroot crypted drive 😛

---

<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:** [August 29, 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/848 "2022-08-29T14:44:08Z")

</div>

> [@MindTheGAAP](#):
>
> You are correct that I am not affected

You only need to chroot if your affected.

If your system is not impacted you can just downgrade from your normal system.

The purpose of the chroot is to rescue a broken system.

That being said, why would you downgrade?

> [@MindTheGAAP](#):
>
> can you share the link to chroot again please?

Keep in mind, this is for a UEFI system. The only real difference is mounting it EFI partition at `/boot/efi` so you can just skip that step and it should be the same.

> [@Grub 2:2.06.r322.gd9b4638c5-1 won't boot and goes straight to the BIOS after update](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/628):
>
> Hello, Just in case it can help others, here is what I did to solve this grub issue on encrypted btrfs disk. First boot on live usb from the last EndeavourOS iso downloaded on the website. Then I followed the expected procedure: [The latest grub package update needs some manual intervention](https://forum.endeavouros.com/t/the-latest-grub-package-update-needs-some-manual-intervention/30689) But since it might not be obvious to everyone, here his a quick summary. Get the actual partitions name: sudo fdisk -l sda1: EFI sda2: Linux File System (pay attention to adapt the partition name to you…

---

<div class="post-metadata">

**Author:** ![edoxedox555](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/e/f14d63/32.png) [@edoxedox555](https://forum.endeavouros.com/u/edoxedox555)\
**Post date:** [August 29, 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/849 "2022-08-29T14:44:16Z")

</div>

endeavouros online installer and grub-2-2-06-r322-gd9b4638c5-1 boot fine 👍

---

<div class="post-metadata">

**Author:** ![MindTheGAAP](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mindthegaap/32/47060_2.png) [@MindTheGAAP](https://forum.endeavouros.com/u/MindTheGAAP)\
**Post date:** [August 29, 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/850 "2022-08-29T14:49:04Z")

</div>

understood but wanted to give it a shot using chroot and good learning experience for future needs 🤓

---

<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:** [August 29, 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/851 "2022-08-29T14:49:51Z")

</div>

Search discovery, there should be instructions there

---

<div class="post-metadata">

**Author:** ![MindTheGAAP](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mindthegaap/32/47060_2.png) [@MindTheGAAP](https://forum.endeavouros.com/u/MindTheGAAP)\
**Post date:** [August 29, 2022, 2:51pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/852 "2022-08-29T14:51:24Z")

</div>

I followed the link in [Discovery](https://discovery.endeavouros.com/system-rescue/arch-chroot-for-bios-legacy-systems/2021/03/) but didn’t get too far but Dalto’s link above seems to be a good reference which I will try now

---

<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:** [August 29, 2022, 2: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/853 "2022-08-29T14:52:10Z")

</div>

> [@MindTheGAAP](#):
>
> understood but wanted to give it a shot using chroot and good learning experience for future needs

I edited my post and added them in.

> [@sradjoker](#):
>
> Search discovery, there should be instructions there

This whole conversation started with him trying to follow those instructions.

---

<div class="post-metadata">

**Author:** ![MindTheGAAP](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mindthegaap/32/47060_2.png) [@MindTheGAAP](https://forum.endeavouros.com/u/MindTheGAAP)\
**Post date:** [August 29, 2022, 3:01pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/854 "2022-08-29T15:01:52Z")

</div>

thanks bunch @dalto and @Lugh. The above steps worked 🙂

![image](https://forum.endeavouros.com/uploads/default/original/3X/7/c/7c7ff4f0f173f39de285ff826c55320e82aa770e.jpeg)

---

<div class="post-metadata">

**Author:** ![xiukosh](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/x/e5b9ba/32.png) [@xiukosh](https://forum.endeavouros.com/u/xiukosh)\
**Post date:** [August 29, 2022, 4:07pm UTC](https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653/855 "2022-08-29T16:07:52Z")

</div>

After an update that require system restart, my system not boot anymore, im redirected to BIOS settings while the boot, no text is shown on screen. I am on live cd with Endeavour os now, can i do anything to solve this?

---

<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:** [August 29, 2022, 4: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/856 "2022-08-29T16:09:07Z")

</div>

> [@xiukosh](#):
>
> I am on live cd with Endeavour os now, can i do anything to solve this?

Yes. Take a look at the instructions here:

> [@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/)

---

<div class="post-metadata">

**Author:** ![xiukosh](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/x/e5b9ba/32.png) [@xiukosh](https://forum.endeavouros.com/u/xiukosh)\
**Post date:** [August 29, 2022, 4: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/857 "2022-08-29T16:45:45Z")

</div>

I mount the partition and enter in chroot with exit, but i see this error when try “grub-install”:

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

```

[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=41)

[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=43)
