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

[lhb1142]

@dalto

You should be following these instructions instead anyway:
UEFI: https://discovery.endeavouros.com/system-rescue/arch-chroot-for-efi-uefi-systems/2021/03/
non-UEFI: https://discovery.endeavouros.com/system-rescue/arch-chroot-for-bios-legacy-systems/2021/03/

These instructions are very complex and though I will try them, I don’t have too much hope in the outcome.

I do have two questions which just came to mind.

1. Is it possible to reinstall EndeavourOS while keeping the previous /home directory?

To give an example, when I used MxLinux many years ago, it was possible to do just that (keeping the /home directory when installing a new version). If this were possible with EOS, that would “solve” the problem for me, at least in the short run AND it would be much easier for me.

and

2. Will there be a prominent notice here on the forum when GRUB has been fixed and it is safe to update normally?

I have been using EndeavourOS on many computers for the three years it has been in existence and this is the first time there has been a major problem.

I certainly hope that it can be fixed quickly.

Lawrence

[sradjoker]

@lhb1142

These instructions are very complex and though I will try them, I don’t have too much hope in the outcome.

Keep an open mind, just go through these steps one step at a time.
You will be able to fix your system very quickly. These instructions aren’t hard. It looks challenging before you try it but just go through them slowly and you will be okay.

[Triby]

Which version did you selected for downgrade? Try a previous one.

I did the same and got a list of 4 versions available to downgrade, so I’ve typed 3 to get 2:2.06.r297.g0c6c1aff2-1 instead of 2:2.06.r322.gd9b4638c5-1

[dalto]

@lhb1142

Is it possible to reinstall EndeavourOS while keeping the previous /home directory?

Yes.

However if you do an offline install you will end up back in the same spot so make sure you do an online install.

@lhb1142

Will there be a prominent notice here on the forum when GRUB has been fixed and it is safe to update normally?

I don’t think one is needed. You can upgrade now if you run grub-install afterwards.

That would just be confusing to all the people who already upgraded.

[Triby]

@lhb1142

Is it possible to reinstall EndeavourOS while keeping the previous /home directory?

I think it is possible only if you have your home directory on a separate partition.

[Christopher67]

I have a list all the way back to the latest 2.04 version

[Triby]

I think the greater number in the list is the current version installed, for me, the list was 1 to 4 and I’ve selected 3. If you have a list from 1 to 20, just select 19 to downgrade to the previous version.

[dalto]

I just want to point out that from most people, downgrading is probably the wrong solution here. That is a short-term fix.

[Christopher67]

@dalto So repair is the best option?

@dalto 1 more question I was wanting to switch back to Plasma from Gnome, would this be a bad idea till grub is fixed upstream?

Thanks. Chris

[anon11595408]

@dalto

I just want to point out that from most people, downgrading is probably the wrong solution here. That is a short-term fix.

As no upstream-issue seems to be involved.
Again, it seems to amount to Novidia-related issues? And the constant need for Linus’ folks to fix all that crap?

[BS86]

@anon49550872

So, to replace my current efi entry, I would use UEFI OS ?

that’s weird. Translating my output to yours, Boot0004 was used on my system, and it is/was named EndeavourOS, while yours is named endeavouros-2297

but yeah, it should not make much of a difference, it is only used as display name of the boot entry in BIOS/UEFI

[endbob]

@joekamprad

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Name_it_what_you_want

I tried the above command after installing the latest grub and found it gives me the dreaded ‘out of memory’ error before showing the selection menu without any theming.

Still at least it doesn’t crash!

[dalto]

@Christopher67

So repair is the best option?

Yes, it seems to be fixed for most people by simply running grub-install.

@Christopher67

1 more question I was wanting to switch back to Plasma from Gnome, would this be a bad idea till grub is fixed upstream?

I don’t think that matters but I suppose that depends on how you are planning to switch. It isn’t even clear to me if there is an upstream issue that will be fixed or not.

@anon11595408

Again, it seems to amount to Novidia-related issues?

This is related to nvidia? Are you sure?

[anon11595408]

@dalto

This is related to nvidia? Are you sure?

Nope. Just poking around around in The Fog, here.

[endbob]

No, it affects AMD as well.

[Christopher67]

Device             Start        End   Sectors   Size Type
/dev/nvme1n1p1      4096     618495    614400   300M EFI System
/dev/nvme1n1p2    618496  981751961 981133466 467.8G Linux filesystem
/dev/nvme1n1p3 981751962 1000206899  18454938   8.8G Linux swap

I booted to the newest live iso, then did…

sudo mount /dev/nvme1n1p2 /mnt

Then Did

sudo mount /dev/nvme1n1p2 /mnt/boot/efi

Then did

sudo grub-mkconfig -o /boot/grub/grub.cfg

and i get this…

/usr/bin/grub-probe: error: failed to get canonical path of `airootfs'.

Did i miss something?

[sradjoker]

@Christopher67

sudo mount /dev/nvme1n1p2 /mnt/boot/efi

there is a typo here it should be 1 instead of 2

[Christopher67]

Haha thanks!

[garybean]

so, following adjagu’s procedure:
“sudo mount /dev/nvme0n1p7 /mnt”
“sudo mount /dev/nvme0n1p1 /mnt/boot/efi”

then:
“sudo arch-chroot /mnt”

then I get:
sudo: arch-chroot: command not found

If I have explained well enough for someone to follow, why is “arch-chroot” not found?

[dalto]

@Christopher67

Did i miss something?

You need to run grub-install. grub-mkconfig may not be enough to resolve the issue.