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

General system
366

Well, I never manually updated the installed grub in my time using linux (using it for almost 2 decades now) and grub always updated itself, once or twice even with new features that I wanted to use becoming available, so definitely not just the Header line in grub telling the version that got updated with mkconfig.

There must be some other mechanism, like maybe symlinks in the bootloader that load the grub from filesystem or something like that and this time they got broken with the update. The files needed to run grub are in /boot/grub/x86_64-efi so they would be available to be accessed by the bootloader itself.

367

Seems Arco also warns not to update but also not to downgrade …

https://arcolinuxforum.com/viewtopic.php?p=13045#p13045

368

What should sudo ls /boot/efi/EFI/ contain in the end?
For me it contains:
boot EndeavourOS EndeavourOS-grub tools
I guess I could delete EndeavourOS since I followed the pinned post and the name of the boot enrty is now EndeavourOS-grub?

369

mine shows: boot endeavouros-3873 when i do sudo ls /boot/efi/EFI/

370

Sorry I did not mean to reply to you directly.

371

no problem

372

Had this problem too, thanks for a solution :slight_smile:

373

hey so i tried the instructions on this thread by @sradjoker. the grub-install command showed no errors, i rebooted and was welcomed by the pink endeavour grub screen but then i got this:

IMG_20220826_110327

and after pressing some key and exiting i arrived at this screen:

IMG_20220826_110337

i picked the second option and was able to boot normally.

374

Hey there. Tried to chroot into my system but when im trying to mount my partition running following:

sudo mount /dev/sdb1 /mnt/boot/efi

but i get the following error:

mount: /mnt/boot/efi: mount point does not exist.

This is my sudo fdisk -l output

Disk /dev/sdb: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: SanDisk SSD PLUS
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: 8B8E6563-B17F-1B4C-85F9-C4F347B001F0

Device Start End Sectors Size Type
/dev/sdb1 4096 1052671 1048576 512M EFI System
/dev/sdb2 1052672 433048124 431995453 206G Linux filesystem
/dev/sdb3 433048125 468857024 35808900 17.1G Linux swap

Can someone help what am i doing wrong? why i cant mount?

edit: im currently running these commands on live endeavouros and have the exact grub error

375

Hi, I need some help to reset the grub on my system. I was using zotero for my research and suddenly my laptop froze and I had to reboot the system. I am already into the live-USB but I am unsure which partition to choose I know my disk is a 30Gb samsung SSD but I am not clear on how to reset the grub, I don’t have a btrfs system or anything like that. Could you please help me? It’s 3:33Am and in the morning I have classes.

[liveuser@eos-2021.12.17 ~]$ sudo fdisk -l
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA MQ01ABF0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6D566981-3D7C-B944-A702-C7FAA866582E

Device         Start       End   Sectors   Size Type
/dev/sda1       2048 443025407 443023360 211.3G Linux filesystem
/dev/sda3  958313126 976768064  18454939   8.8G Linux swap
/dev/sda4  443025408 505890815  62865408    30G Linux filesystem
/dev/sda5  505890816 958312447 452421632 215.7G Microsoft basic data

Partition 3 does not start on physical sector boundary.
Partition table entries are not in disk order.


Disk /dev/sdb: 29.82 GiB, 32017047552 bytes, 62533296 sectors
Disk model: SAMSUNG MZMPC032
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: 92BB3A65-DE16-9241-9B55-68CCA2241DCD

Device       Start      End  Sectors  Size Type
/dev/sdb1     4096  1052671  1048576  512M EFI System
/dev/sdb2  1052672 62524979 61472308 29.3G Linux filesystem


Disk /dev/sdc: 14.54 GiB, 15614803968 bytes, 30497664 sectors
Disk model: DataTraveler 3.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: 0xad1fa572

Device     Boot    Start      End  Sectors  Size Id Type
/dev/sdc1  *        2048 30432127 30430080 14.5G  7 HPFS/NTFS/exFAT
/dev/sdc2       30432128 30497663    65536   32M ef EFI (FAT-12/16/32)


Disk /dev/mapper/ventoy: 1.88 GiB, 2023485440 bytes, 3952120 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
Disklabel type: dos
Disk identifier: 0x6abbeac5

Device                   Boot   Start     End Sectors  Size Id Type
/dev/mapper/ventoy-part1 *         64 3742559 3742496  1.8G  0 Empty
/dev/mapper/ventoy-part2      3742560 3951455  208896  102M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 1.68 GiB, 1808896000 bytes, 3533000 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
376

You need to mount /dev/sdb1 and /dev/sdb2

sdb1 is your EFI and sdb2 is you linux filesystem

377

Is your live USB the most upto date version?

378

Yes it is. Its the latest endeavouros

1 Like
379

Thanks! I almost made the mistake of mounting sda4.

380

You may have fixed this, I haven’t got to the end of the thread!!!

arch-chroot on BTRFS:

sudo mount  /dev/sda2  /mnt -o subvol=@  #(Your root partition on disk)
sudo mount  /dev/sda1  /mnt/boot/efi
sudo arch-chroot /mnt

Then, log into wifi if needed:

downgrade grub

Follow instructions, type exit to leave chroot (important!).

This will give you a working system. Then to permanently fix follow the instructions above. Basically:

  • Remove from IgnorePkg
  • Update - do not reboot
  • Reinstall grub
  • Rebuild grub
  • Reboot
381

can i create boot and efi folders myself and try that way?

382 
sudo mount  /dev/sdb2  /mnt 
sudo mount  /dev/sdb1  /mnt/boot/efi
sudo arch-chroot /mnt

Does that work? In order…

383

Why would you? I don’t think it’s even possible. I mean as in to create the whole ESP by hand.

384

For what it’s worth, I updated yesterday shortly after the notice was posted, ran grub-install as instructed in the pinned post and haven’t had any problem, it boots normally to the grub menu and works fine on both my installed kernels (regular and LTS). I’m on a 2020 Lenovo Ideapad Gaming 3, no dual boot, ext4, and hadn’t touched grub files from the default eOS installation (April 2021 release, IIRC) except for making it select the last chosen kernel.

385

The whole fiasco isn’t “how do I fix it” but “why is this happening?”

2 Likes