So today I updated my MSI PRO Z690-A bios. I run duel boot between windows and linux. After the update, there was no linux boot. I disabled safe boot, and booted a live endevouros on my pc to reinstall grub (my OS used grub).
[root@EndeavourOS boot]# sudo parted -l
Model: Kingston DataTraveler 3.0 (scsi)
Disk /dev/sda: 62.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 2799MB 2969MB 170MB primary fat32 esp
Model: WD_BLACK SN850X HS 1000GB (nvme)
Disk /dev/nvme0n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 106MB 105MB fat32 EFI system partition boot, esp, no_automount
2 106MB 123MB 16.8MB Microsoft reserved partition msftres, no_automount
3 123MB 632GB 632GB ntfs Basic data partition msftdata
5 632GB 999GB 367GB btrfs endeavouros
4 999GB 1000GB 778MB ntfs hidden, diag, no_automount
I then tried this but I got an error
[root@EndeavourOS /]# sudo mount /dev/nvme0n1p5 /mnt
[root@EndeavourOS /]# 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.
I also tried again but got the same error
[root@EndeavourOS /]# sudo mount /dev/nvme0n1p5 /mnt
[root@EndeavourOS /]# sudo arch-chroot /mnt
mount: /mnt/proc: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
==> ERROR: failed to setup chroot /mnt
[liveuser@eos-2024.09.22 ~]$ sudo mount -m /dev/nvme0n1p5 /mnt
[liveuser@eos-2024.09.22 ~]$ sudo mount -m /dev/nvme0n1p1 /mnt/boot/efi
[liveuser@eos-2024.09.22 ~]$ sudo arch-chroot /mnt
mount: /mnt/proc: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
==> ERROR: failed to setup chroot /mnt
[liveuser@eos-2024.09.22 ~]$
[liveuser@eos-2024.09.22 ~]$ sudo mkdir /mnt/proc
[liveuser@eos-2024.09.22 ~]$ sudo mount -m /dev/nvme0n1p5 /mnt
[liveuser@eos-2024.09.22 ~]$ sudo mount -m /dev/nvme0n1p1 /mnt/boot/efi
[liveuser@eos-2024.09.22 ~]$ sudo arch-chroot /mnt
mount: /mnt/sys: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
==> ERROR: failed to setup chroot /mnt
[liveuser@eos-2024.09.22 ~]$ sudo mkdir /mnt/sys
[liveuser@eos-2024.09.22 ~]$ sudo mount -m /dev/nvme0n1p5 /mnt
[liveuser@eos-2024.09.22 ~]$ sudo mount -m /dev/nvme0n1p1 /mnt/boot/efi
[liveuser@eos-2024.09.22 ~]$ sudo arch-chroot /mnt
mount: /mnt/dev: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
==> ERROR: failed to setup chroot /mnt
[liveuser@eos-2024.09.22 ~]$
I think are you using the right commands? I see you have btrfs but no subvolumes? This isn’t the way endeavouros sets up btrfs on the install. Or maybe I’m not familiar with your way of arch-chroot on btrfs?
Okay I figured out what I had to do. So I found out my subvolumes:
[liveuser@eos-2024.09.22 ~]$ sudo mount /dev/nvme0n1p5 /mnt
[liveuser@eos-2024.09.22 ~]$ df -Th | grep /mnt
/dev/nvme0n1p5 btrfs 342G 73G 270G 22% /mnt
[liveuser@eos-2024.09.22 ~]$ sudo btrfs subvolume list /mnt
ID 256 gen 57679 top level 5 path @
ID 257 gen 57675 top level 5 path @home
ID 258 gen 57675 top level 5 path @cache
ID 259 gen 57675 top level 5 path @log
ID 260 gen 26 top level 256 path @/var/lib/portables
ID 261 gen 26 top level 256 path @/var/lib/machines
Here are my notes from obsidian that restored my bootloader and helped a few souls out. Sorry if its chaotic as thats how I tend to keep notes short. It may not be exact either or require every step.