# Cannot access GRUB: grub\_cli\_set\_auth\_needed not found \[SOLVED\]

**URL:** <https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980>\
**Category:** Newbie\
**Created:** [March 13, 2025, 2:24am UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980 "2025-03-13T02:24:18Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nathan](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/nathan/32/67699_2.png) [@Nathan](https://forum.endeavouros.com/u/Nathan)\
**Post date:** [March 13, 2025, 2:24am UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/1 "2025-03-13T02:24:18Z")

</div>

I’m having the [same issue](https://forum.endeavouros.com/t/fyi-arch-pushed-out-the-buggy-grub-package-from-testing/68334) as @ajgringo619 did, but it is not at all clear to me from reading the thread how to fix the issue. Can anyone sum it up in simple steps? I’m using BTRFS if that matters.

---

<div class="post-metadata">

**Author:** ![ajgringo619](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ajgringo619/32/35599_2.png) [@ajgringo619](https://forum.endeavouros.com/u/ajgringo619)\
**Post date:** [March 13, 2025, 2:28am UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/2 "2025-03-13T02:28:09Z")

</div>

My issue was completely self-inflicted. I changed the default bootloader ID back in April of last year due to having a triple-boot with (2) other EOS installs, just didn’t see a problem until one of the core GRUB modules was updated (don’t know which one).

---

<div class="post-metadata">

**Author:** ![Nathan](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/nathan/32/67699_2.png) [@Nathan](https://forum.endeavouros.com/u/Nathan)\
**Post date:** [March 13, 2025, 2:39am UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/3 "2025-03-13T02:39:56Z")

</div>

I see. How did you begin troubleshooting? Even just doing `ls HD0` in GRUB rescue locks up the system.

---

<div class="post-metadata">

**Author:** ![ajgringo619](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ajgringo619/32/35599_2.png) [@ajgringo619](https://forum.endeavouros.com/u/ajgringo619)\
**Post date:** [March 13, 2025, 2:48am UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/4 "2025-03-13T02:48:21Z")

</div>

At first, all I did was downgrade `grub`. But @dalto figured out that my pacman hooks were installing the updated files into a different directory, hence the boot errors. Your issue is sounding more like the Arch forum post I linked to.

---

<div class="post-metadata">

**Author:** ![cactux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/cactux/32/134907_2.png) [@cactux](https://forum.endeavouros.com/u/cactux)\
**Post date:** [March 13, 2025, 2:58am UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/5 "2025-03-13T02:58:40Z")

</div>

I think you need to use a live usb, chroot to your system and reinstall the grub package to have all its bits and pieces. After that a grub-install followed perhaps by a grub update. There is an article in EndeavourOS wiki about how to rescue a system with Grub problem.

---

<div class="post-metadata">

**Author:** ![ringo](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ringo/32/66182_2.png) [@ringo](https://forum.endeavouros.com/u/ringo)\
**Post date:** [March 13, 2025, 5:36am UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/6 "2025-03-13T05:36:09Z")

</div>

Between te lines, is it possible to check bios and look if you got another entry…maybe you can boot through that. On telegram had a situation uefi os entry windows grub messed but could boot through bios…  
Otherwise check btrfsbpart to mount .[https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/](https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/)

---

<div class="post-metadata">

**Author:** ![ricklinux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ricklinux/32/110798_2.png) [@ricklinux](https://forum.endeavouros.com/u/ricklinux)\
**Post date:** [March 13, 2025, 2:18pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/7 "2025-03-13T14:18:39Z")

</div>

> [@Nathan](#):
>
> Can anyone sum it up in simple steps? I’m using BTRFS if that matters.

Are you not able to revert to a previous snapshot? Otherwise i would do as @cactux said in post #5 to arch-chroot , reinstall grub and run the update grub command.

---

<div class="post-metadata">

**Author:** ![Nathan](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/nathan/32/67699_2.png) [@Nathan](https://forum.endeavouros.com/u/Nathan)\
**Post date:** [March 13, 2025, 2:27pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/8 "2025-03-13T14:27:04Z")

</div>

> Are you not able to revert to a previous snapshot?

No, because I cannot access the GRUB menu.

> i would do as @cactux said in post #5 to arch-chroot , reinstall grub and run the update grub command.

It’s looking like this is what I’ll have to try next; I’m hesitant to chroot into the system as it seems complicated on BTRFS (I’ve done it once before and promptly forgot how), but needs must.

I’m a bit annoyed because I haven’t done anything interesting with this system at all; it just sits by the TV and I use it to play video games haha.

---

<div class="post-metadata">

**Author:** ![ricklinux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ricklinux/32/110798_2.png) [@ricklinux](https://forum.endeavouros.com/u/ricklinux)\
**Post date:** [March 13, 2025, 2:30pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/9 "2025-03-13T14:30:30Z")

</div>

> [@Nathan](#):
>
> I’m hesitant to chroot into the system as it seems complicated on BTRFS (I’ve done it once before and promptly forgot how), but needs must.

No it’s not complicated. Look under mount needed partitions & BTRFS filesystem installs.

[https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/](https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/)

Note: _Not all subvolumes need to get mounted to use arch-chroot it needs mainly the / (@) if you only want to repair grub per example_

---

<div class="post-metadata">

**Author:** ![Nathan](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/nathan/32/67699_2.png) [@Nathan](https://forum.endeavouros.com/u/Nathan)\
**Post date:** [March 13, 2025, 9:18pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/10 "2025-03-13T21:18:55Z")

</div>

So, here’s what I’ve done so far: (not 100% accurate terminal output as I’m typing on my phone)

First I boot into a live ISO.

`sudo lsblk - f` returns:

```auto
sda1 vfat FAT32
sda2 btrfs endeavouros

```

So I then mount sda2:

`sudo mount -o subvol=@ /dev/sda2 /mnt`

Then my “ESP”:

`sudo mount /dev/sda1 /mnt/boot/efi`

(Fstab shows /boot/efi, but attempting to mount here shows an error: `mount point does not exist`)

Then I use arch-chroot:

`sudo arch-chroot /mnt`

But now `ls /home` returns nothing. Any ideas where I went wrong?

---

<div class="post-metadata">

**Author:** ![Nathan](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/nathan/32/67699_2.png) [@Nathan](https://forum.endeavouros.com/u/Nathan)\
**Post date:** [March 13, 2025, 9:39pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/11 "2025-03-13T21:39:23Z")

</div>

OK, so it looks like the `ls /home` output is a non-issue. Was able to run `yay` successfully, but:

`grub-install` returns `error: install device not specified

And `grub-install --target=86_64-efi --efi-directory=/boot/efi` returns:

```auto
EFI variables are not supported on this system. 
EFI variables are not supported on this system.
grub-install: error: efibootmgr failed to register the boot entry: No such file or directory. 

```

`grub-install --target=86_64-efi /dev/sda1` returns the same as above.

---

<div class="post-metadata">

**Author:** ![Nathan](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/nathan/32/67699_2.png) [@Nathan](https://forum.endeavouros.com/u/Nathan)\
**Post date:** [March 13, 2025, 9:56pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/12 "2025-03-13T21:56:33Z")

</div>

OK, I have now run:

```auto
pacman -S grub
grub-install
grub-mkconfig -o /boot/grub/grub.cfg

```

And the issue is still present.

---

<div class="post-metadata">

**Author:** ![Nathan](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/nathan/32/67699_2.png) [@Nathan](https://forum.endeavouros.com/u/Nathan)\
**Post date:** [March 13, 2025, 10:05pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/13 "2025-03-13T22:05:23Z")

</div>

~~No, I only have UEFI OS in BIOS - nothing else.~~

I did find another entry in the boot override section. It boots succesfully. Now when I run `grub-install` I get `error: disk 'hostdisk//dev/sda1' not found`.

---

<div class="post-metadata">

**Author:** ![Nathan](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/nathan/32/67699_2.png) [@Nathan](https://forum.endeavouros.com/u/Nathan)\
**Post date:** [March 13, 2025, 10:05pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/14 "2025-03-13T22:05:44Z")

</div>

Unfortunately this didn’t solve the issue.

---

<div class="post-metadata">

**Author:** ![cactux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/cactux/32/134907_2.png) [@cactux](https://forum.endeavouros.com/u/cactux)\
**Post date:** [March 13, 2025, 10:07pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/15 "2025-03-13T22:07:54Z")

</div>

`efibootmgr`  
What is the output?

---

<div class="post-metadata">

**Author:** ![Nathan](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/nathan/32/67699_2.png) [@Nathan](https://forum.endeavouros.com/u/Nathan)\
**Post date:** [March 13, 2025, 10:13pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/16 "2025-03-13T22:13:31Z")

</div>

```auto
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0004,0000,0006,0007,0001,0005
Boot0000* endeavouros HD(1,GPT,00c8d36a-069e-4e52-975f-9cf7da0a7b24,0x1000,0x1f4000)/\EFI\ENDEAVOUROS\GRUBX64.EFI
Boot0001 Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)0000474f00004e4fc9000000080000008b004b0049004e004700530054004f004e0020005300410034003000300053003300370031003200300047000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600030101010600010003120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63000350032003000420036003700370041003700300030003900340032004100200020002000200000007fff04000000424f00004e4fbd000000080000008b004300540032003000300030004200580035003000300053005300440031000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600030101010600010003120a000400ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63300320032003000360045004400390039003000300038002000200020002000200020002000200000007fff04000000424f
Boot0004* UEFI OS HD(1,GPT,00c8d36a-069e-4e52-975f-9cf7da0a7b24,0x1000,0x1f4000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot0005 USB KEY BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0b00)0000474f00004e4fb1000000080000006f00470065006e006500720069006300200046006c0061007300680020004400690073006b00200038002e00300037000000050109000200000000010416008b12e85cec2cf040837280640e3dc8580b007fff040002010c00d041030a000000000101060001070101060003000305060001007fff040001042600ef47642dc93ba041ac194d51d01b4ce64600380045003700450035003800420000007fff04000000424f
Boot0006* UEFI: Generic Flash Disk 8.07 PciRoot(0x0)/Pci(0x7,0x1)/Pci(0x0,0x3)/USB(1,0)/CDROM(1,0x593ce0,0x58840)0000424f
Boot0007* UEFI: Generic Flash Disk 8.07, Partition 2 PciRoot(0x0)/Pci(0x7,0x1)/Pci(0x0,0x3)/USB(1,0)/HD(2,MBR,0x394f561e,0x593ce0,0x58800)0000424f

```

---

<div class="post-metadata">

**Author:** ![cactux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/cactux/32/134907_2.png) [@cactux](https://forum.endeavouros.com/u/cactux)\
**Post date:** [March 13, 2025, 10:16pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/17 "2025-03-13T22:16:26Z")

</div>

> [@Nathan](#):
>
> `Boot0004* UEFI OS HD(1,GPT,00c8d36a-069e-4e52-975f-9cf7da0a7b24,0x1000,0x1f4000)/\EFI\BOOT\BOOTX64.EFI0000424f`

Can you test this boot option?

---

<div class="post-metadata">

**Author:** ![Nathan](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/nathan/32/67699_2.png) [@Nathan](https://forum.endeavouros.com/u/Nathan)\
**Post date:** [March 13, 2025, 10:21pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/18 "2025-03-13T22:21:14Z")

</div>

So I managed to find a boot option in the BIOS, which I think is Boot0000, that allows me to boot.

The option labeled `UEFI OS` in the BIOS is the one that goes straight to GRUB rescue. When I run `grub-install` from my current boot I get `error: disk 'hostdisk//dev/sda1' not found`.

---

<div class="post-metadata">

**Author:** ![cactux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/cactux/32/134907_2.png) [@cactux](https://forum.endeavouros.com/u/cactux)\
**Post date:** [March 13, 2025, 10:23pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/19 "2025-03-13T22:23:08Z")

</div>

> [@Nathan](#):
>
> `BootOrder: 0004,0000,0006,0007,0001,0005`

Change the boot order in BIOS to have 0000 first.

---

<div class="post-metadata">

**Author:** ![Nathan](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/nathan/32/67699_2.png) [@Nathan](https://forum.endeavouros.com/u/Nathan)\
**Post date:** [March 13, 2025, 10:27pm UTC](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980/20 "2025-03-13T22:27:31Z")

</div>

~~For some reason, it isn’t available in the boot order selector, only in the “Boot Override” section?~~

I had to go into “Boot\UEFI Hard Disk Drive BBS Priorities” and swap UEFI OS with endeavouros. How bizarre. Any idea why this happened out of the blue?

I very much appreciate your help: thank you!

[Next page](https://forum.endeavouros.com/t/cannot-access-grub-grub-cli-set-auth-needed-not-found-solved/68980.md?page=2)