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

stonemax · September 8, 2022, 6:42pm

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 ~]$

dalto · September 8, 2022, 7:34pm

Are you using btrfs, luks encryption or both?

joekamprad · September 8, 2022, 8:30pm

lsblk -f

would help to see filesystem used…

CrazyOrca · September 8, 2022, 8:43pm

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

stonemax · September 8, 2022, 9:00pm

btrfs

stonemax · September 8, 2022, 9:01pm

[liveuser@eos-2022.08.28 ~]$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squash 4.0 0 100% /run/archiso/airootfs
sda iso966 Jolie EOS_202208
2022-08-28-20-55-34-00 0 100% /run/archiso/bootmnt
├─sda1 iso966 Jolie EOS_202208
│ 2022-08-28-20-55-34-00
└─sda2 vfat FAT16 ARCHISO_EFI
A2D6-6CDF
nvme0n1
├─nvme0n1p1
│ vfat FAT32 NO_LABEL 46E6-9F87
└─nvme0n1p2
btrfs c829046a-99c4-4f44-8dca-9ca168feb434 145.8G 38% /mnt
[liveuser@eos-2022.08.28 ~]$

dalto · September 8, 2022, 9:01pm

Instead of this step:

sudo mount /dev/nvme0n1p2 /mnt

Do this:

sudo mount /dev/nvme0n1p2 /mnt -o subvol=@

stonemax · September 8, 2022, 9:19pm

what next, according to what instructions? thanks
I followed these For BTRFS subvol schemes, but again it says that I am making a mistake somewhere in the steps:

[liveuser@eos-2022.08.28 ~]$ sudo mount /dev/nvme0n1p2 /mnt -o subvol=@
mount: /mnt: /dev/nvme0n1p2 already mounted on /mnt.
dmesg(1) may have more information after failed mount system call.
[liveuser@eos-2022.08.28 ~]$ sudo umount /mnt
[liveuser@eos-2022.08.28 ~]$ sudo mount -o subvol=@ /dev/nvme01p2 /mnt
mount: /mnt: special device /dev/nvme01p2 does not exist.
dmesg(1) may have more information after failed mount system call.
[liveuser@eos-2022.08.28 ~]$

dalto · September 8, 2022, 9:24pm

You have typo in the device name.

stonemax · September 8, 2022, 9:25pm

addition - I think we are making progress

[liveuser@eos-2022.08.28 ~]$ sudo mount /dev/nvme0n1p2 /mnt -o subvol=@
[liveuser@eos-2022.08.28 ~]$ sudo btrfs subvolume list -p /mnt
ID 256 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-03-24_23-40-45/@
ID 257 gen 23058 parent 5 top level 5 path @home
ID 258 gen 23057 parent 5 top level 5 path @cache
ID 259 gen 23058 parent 5 top level 5 path @log
ID 260 gen 26 parent 256 top level 256 path timeshift-btrfs/snapshots/2022-03-24_23-40-45/@/var/lib/portables
ID 261 gen 27 parent 256 top level 256 path timeshift-btrfs/snapshots/2022-03-24_23-40-45/@/var/lib/machines
ID 263 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-03-22_21-13-40/@
ID 275 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-07-13_11-49-40/@
ID 278 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-05-20_23-47-12/@
ID 279 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-05-30_17-24-30/@
ID 280 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-06-15_08-54-22/@
ID 281 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-06-17_11-48-33/@
ID 282 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-06-30_08-23-07/@
ID 283 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-07-06_14-06-57/@
ID 284 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-07-13_08-41-53/@
ID 285 gen 23059 parent 5 top level 5 path @
ID 286 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-07-19_20-53-51/@
ID 287 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-07-26_18-16-35/@
ID 288 gen 21242 parent 5 top level 5 path timeshift-btrfs/snapshots/2022-08-23_15-09-57/@
[liveuser@eos-2022.08.28 ~]$

dalto · September 8, 2022, 9:25pm

Now keep going. Mount your efi partition.

stonemax · September 8, 2022, 9:27pm

ok

stonemax · September 8, 2022, 9:37pm

done:
[liveuser@eos-2022.08.28 ~]$ sudo umount /mnt
[liveuser@eos-2022.08.28 ~]$ sudo mount -o subvol=@ /dev/nvme0n1p2 /mnt
[liveuser@eos-2022.08.28 ~]$ sudo mount -o subvol=@log /dev/nvme0n1p2 /mnt/var/log
[liveuser@eos-2022.08.28 ~]$ sudo mount -o subvol=@cache /dev/nvme0n1p2 /mnt/var/cache
[liveuser@eos-2022.08.28 ~]$ sudo mount -o subvol=@home /dev/nvme0n1p2 /mnt/home

Do I now need:
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
or
sudo mount /dev/nvme0n1p2 /mnt/boot/efi

dalto · September 8, 2022, 9:43pm

This one:

stonemax · September 8, 2022, 9:46pm

done!!!
sudo mount /dev/nvme0n1p1 /mnt/boot/efi,
and now:
sudo arch-chroot /mnt ?

dalto · September 8, 2022, 9:47pm

Yes

stonemax · September 8, 2022, 9:55pm

this is ok?
[root@EndeavourOS /]# sudo grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file …
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
ERROR: mkdir /var/lock/dmraid
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
Adding boot menu entry for UEFI Firmware Settings …
done
[root@EndeavourOS /]#

I continue with?

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

dalto · September 8, 2022, 10:01pm

Just run

grub-install

stonemax · September 8, 2022, 10:03pm

done:
[root@EndeavourOS /]# grub-install
Installing for x86_64-efi platform.
Installation finished. No error reported.
[root@EndeavourOS /]#

and now …
9: Exit Arch-Chroot:

exit

10: Unmount mounts:

sudo umount /mnt/boot/efi
sudo umount /mnt

11: Reboot:

sudo reboot

After rebooting I choose EndeavourOS-grub from my computers BIOS UEFI boot menu.
is that ok?

dalto · September 8, 2022, 10:05pm

Yes, you may not have to switch the boot entry. See if it “just works” first