EndeavourOS bootloader disappear after windows 11 update (dual boot)

[askery]

Hi everyone. I am very new to both EndeavourOS/ Arch Linux.

I am using EndeavourOS because it was the only distro working perfectly with an Acer predator laptop with RTX4090.

I could dualboot and I was using it well until I had the idea of checking Windows and updating it.

I know my problem is similar to

EndeavourOS bootloader missing after BIOS update (dual boot)

Hello everyone, I recently installed EndeavourOS and I am loving it. I keep windows (different ssd from linux) mostly for gaming and sadly, yesterday my Legion 5 Pro decided to update the bios and now I cannot boot into endeavouros. I tried setting the boot order but my linux ssd shows as windows bootloader and thus I cannot set it from the bios. I already downloaded and flashed a usb drive so that I will try to fix it from there. Could you guide me through? I saw some related/similar issues but…

But I could not solve it. To facilitate any help, after using live usb, the output of sudo parted -l is

Model: Micron_3400_MTFDKBA2T0TFH (nvme)
Disk /dev/nvme0n1: 2048GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name                          Flags
 1      1049kB  274MB   273MB   fat32           EFI system partition          boot, esp
 2      274MB   290MB   16.8MB                  Microsoft reserved partition  msftres
 3      290MB   437GB   436GB   ntfs            Basic data partition          msftdata
 4      437GB   651GB   215GB   ext4
 5      651GB   720GB   68.7GB  linux-swap(v1)                                swap
 6      720GB   721GB   1074MB  fat32                                         msftdata
 7      2047GB  2048GB  1074MB  ntfs            Basic data partition          hidden, diag

And the output of efibootmgr is

BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 2001,0000,0003,0002,2002,2003
Boot0000* ubuntu	HD(1,GPT,31f52e47-29b8-4d50-ad21-03aeff839c54,0x800,0x82000)/File(\EFI\ubuntu\shimx64.efi) File(.䍒)
Boot0001* USB HDD: Generic Flash Disk	UsbWwid(58f,6387,0,38034F6)/HD(1,MBR,0x20c2b,0x800,0xf3b800)RC
Boot0002* HDD0: Micron_3400_MTFDKBA2T0TFH	PciRoot(0x0)/Pci(0xe,0x0)/NVMe(0x1,00-A0-75-01-30-32-C3-D1)/HD(6,GPT,23fdd8f2-cad8-49fd-b441-8f9a297d4b5e,0x53d71000,0x200000)RC
Boot0003* Windows Boot Manager	HD(1,GPT,31f52e47-29b8-4d50-ad21-03aeff839c54,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000007e000100000010000000040000007fff0400
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

I am almost sure I was using GRUB, but not completely sure.

Thanks in advance.

[pebcak]

For better readability, please edit your post and format the posted output.

Highlight the text and press Ctrl-E to format.

[pebcak]

Could you boot up your live usb and post:

sudo blkid

Also mount your system partition:

sudo mount /dev/nvme0n1p4 /mnt

and post the output of:

cat /mnt/etc/fstab

[askery]

The output of sudo blkid is

/dev/nvme0n1p7: LABEL="Recovery" BLOCK_SIZE="512" UUID="9AC821BCC8219791" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a8068ff9-3592-42fc-9291-e1829cea80b0"
/dev/nvme0n1p5: LABEL="swap" UUID="de08eabe-af69-4d81-b44a-09a28b7249b6" TYPE="swap" PARTUUID="625d899e-ca9e-40fd-95ae-6c42dfe83d2a"
/dev/nvme0n1p3: LABEL="Acer" BLOCK_SIZE="512" UUID="FCDA2170DA2127FA" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="656d2e17-72b3-4bdf-9ae8-cd68aa7e988a"
/dev/nvme0n1p1: LABEL_FATBOOT="ESP" LABEL="ESP" UUID="0620-D38B" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="31f52e47-29b8-4d50-ad21-03aeff839c54"
/dev/nvme0n1p6: LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="CAE4-E07F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="23fdd8f2-cad8-49fd-b441-8f9a297d4b5e"
/dev/nvme0n1p4: LABEL="root" UUID="bb8e5919-51ab-45c4-92ec-5a7ce7cd9f40" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="cd29e8bb-6dd4-4807-bc8e-ae40ea4ccef1"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="3d95cf1d-a3c9-4618-94dd-bc59385d189a"
/dev/loop0: BLOCK_SIZE="1048576" TYPE="squashfs"
/dev/sda1: LABEL="EOS_202305" UUID="0E74-0E1F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="00020c2b-01"

The output of cat /mnt/etc/fstab after sudo mount /dev/nvme0n1p4 /mnt is

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=bb8e5919-51ab-45c4-92ec-5a7ce7cd9f40 /              ext4    defaults,noatime 0 1
UUID=de08eabe-af69-4d81-b44a-09a28b7249b6 swap           swap    defaults   0 0
UUID=CAE4-E07F                            /boot/efi      vfat    defaults,noatime 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

Thank you

[pebcak]

Thanks!

You are indeed using Grub as you mentioned before.

Please follow the following steps to reinstall your bootloader:

1. sudo mount /dev/nvme0n1p4 /mnt (skip if already mounted)

2. sudo mount /dev/nvme0n1p6 /mnt/boot/efi

3. sudo arch-chroot /mnt

In chroot:

1. grub-install

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

If everything is fine, quit chroot by typing exit followed by enter.

Check with efibootmgr to see if a new efi boot entry for EnOS has been created.

If all is well, reboot.

Please note, if you are getting any error messages at any steps described above, please don’t go any further and post the error message back here.

[askery]

Thank you very much @pebcak

It solved the problem. The only added step using live usb was installing arch-chroot via

pacman -S arch-install-scripts

Thank you a lot!

[pebcak]

@askery

The only added step using live usb was installing arch-chroot via

pacman -S arch-install-scripts

I see. This should normally be included in the ISO but it might have changed recently.
Glad that you figured it all out and could resolve the issue!

Also, welcome to EnOS’ community @askery !