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

I did y and it worked. Tysm everyone <3

2 Likes

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.

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

3 Likes

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.

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

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

I followed these instructions:

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:

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:

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.

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:

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

When done type exit to quit chroot. Reboot.

5 Likes

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. :heart:

4 Likes

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 :laughing: , you might want to consider not merging more here… ? :person_shrugging:

Just an opinion, nothing more. :wink:

1 Like

2022-09-07_23-49

Still warm…

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

2 Likes

OMG

2000 :rofl:

1 Like

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

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 :wink:

lsblk -f
efibootmgr

or share it:

lsblk -f >> shareinfo.txt && efibootmgr >> shareinfo.txt && cat shareinfo.txt  | eos-sendlog
1 Like

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.

I can’t solve the problem with grub, it says that there is no mnt/boot/efi: mount point does not exist.
I’m not an expert but a beginner in linux, does any kind soul have a solution?
I tried to follow the instructions from the link, but I stopped at point 4:

copy/paste of my terminal:
[liveuser@eos-2022.08.28 ~]$ sudo fdisk -l
Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: KBG40ZNS256G NVMe KIOXIA 256GB          
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: DD26DBEC-352D-3F45-91E0-B84FDB146B04

Device          Start       End   Sectors   Size Type
/dev/nvme0n1p1   4096    618495    614400   300M EFI System
/dev/nvme0n1p2 618496 500103449 499484954 238.2G Linux filesystem


Disk /dev/sda: 28.65 GiB, 30765219840 bytes, 60088320 sectors
Disk model:  SanDisk 3.2Gen1
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: 0x6ec8b20d

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


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 mount /dev/nvme0n1p2 /mnt
[liveuser@eos-2022.08.28 ~]$ sudo mount /dev/nvme0n1p1 /mnt/boot/efi
mount: /mnt/boot/efi: mount point does not exist.
       dmesg(1) may have more information after failed mount system call.
[liveuser@eos-2022.08.28 ~]$

Are you using btrfs, luks encryption or both?

1 Like
lsblk -f

would help to see filesystem used…

1 Like

Seems like I need to start working on my 2k reply post real soon :smile:

1 Like

btrfs