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

No. That means that you mounted the wrong thing on /mnt

If you use btrfs make sure you follow the instructions for btrfs.

If not, please share the terminal output from and all the commands from the beginning so we can see what it going wrong.

Im definitely not using btrfs, here is my terminal output.
image

Can we see ls /mnt

Oh, it is a little blurry but it looks like you mounted your EFI partition at /mnt

The device that ends in 2 should be mounted at /mnt and the one which ends in 1 should be mounted at /mnt/boot/efi

you’re mounting the wrong way,
first umount your p1 partition:

sudo umount /mnt 

The mount it this way:

sudo mount /dev/nvme0n1p2 /mnt
sudo mount /dev/nvme0n1p1 /mnt/boot/efi

There is only EFI for ls /mnt

See above

Those device names seem to missing characters

I fixed it now. I’m really missing the lightbox feature. Or a new magnifying glass feature

1 Like

/mnt/boot/efi Mount Point does not exist

You need to share the whole session output so we can see what went wrong.

Nvm I figured it out and ran with no errors, I will now try to continue with the guide.

Thank you so much for your help

1 Like

It’s best to write down what the problem was and how you solved it. That way others can relate.

It’s fixed now!

so basically I was mounting it wrong,
The right way was first mounting
/dev/nvme0n1p2 /mnt
This was my Linux file system, then I mounted
/dev/nvme0n1p1 /mnt/boot/efi
Which was my EFI system.

I believe the guide could have said that to avoid this issue.

it does not say that?
2022-09-14_15-03

Couldn’t be any clearer! Maybe it needs a special font. :upside_down_face:

Sorry I understand now, however I believe it shouldn’t abbreviate it. As to me (a novice) it just looks like something that is above my understanding, I fell like it should say.

sudo mount /dev/(Linux File System partition) /mnt
sudo mount /dev/(EIF partition) /mnt/boot/eif

This is because when running ‘sudo fdisk -l’ It shows and labels those partitions as is. This might not be the same for all systems but at least say the root file system then give an example etc.

I say this because using sdXn for both commands make it seem like I should use the same partition for both. So adding a bit more detail for novices would clear up confusion, which I personally feel like it is lacking in the guide.

But anyway I appreciate your help!
Cheers

X stays for letter and n for number … usual variables to replace such… but mainly to avoid having a command that could cause harm if simply copy pasting…

You may be right that the way it is formatted can confuse someone not knowing about how device naming on Linux is working in general… this is very basic knowledge … I was simply not considering someone who does not know how it works.

But I do add some more details to the wiki, always nice to get such feedback, thanks for hinting me.

1 Like

@CauseTripod
Have a look at the Arch wiki. It is no different in the way it is delivered.

https://wiki.archlinux.org/title/chroot#Using_arch-chroot

they have it different using XY :wink:
2022-09-15_14-38

Yes i know XY XZ but it is a similar manner. I always explain that the user needs to mount the root partition first then they have to mount the efi partition which is boot. That’s my way of explaining it and what ever those are needs to be confirmed with a command. :man_shrugging:

Yes it is the case that you need to read the wiki article from top to bottom also, it includes all details and hints needed to find out what to do for your installed system.