Hello!
Windows updated and made EFI entry for Endeavour OS disapear and not be listed on EFI boot list from motherboard EFI boot list. I need to rebuild it from Windows to recover access to it. Is that possible?
Thanks in advance!
1 Like
The common procedure for solving this sort of issues is to boot up your EnOS’ live usb and have a look at what might have gone wrong.
chrooting into your system and reinstalling the bootloader may solve the issue.
We would need more info about your setup.
From live session, post the output of the following commands to begin with:
sudo parted -l
efibootmgr
I`m on live session now.
Parted output:
Model: ATA ST31000528AS (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 1000GB 1000GB primary ntfs
Model: ATA ST8000NM017B-2TJ (scsi)
Disk /dev/sdb: 8002GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 17.4kB 16.8MB 16.8MB Microsoft reserved partition msftres
2 16.8MB 8002GB 8002GB ntfs Basic data partition msftdata
Model: ATA KINGSTON SUV400S (scsi)
Disk /dev/sdc: 480GB
Sector size (logical/physical): 512B/4096B
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 479GB 479GB ntfs Basic data partition msftdata
4 479GB 480GB 755MB ntfs hidden, diag, no_automount
Model: ATA Samsung SSD 840 (scsi)
Disk /dev/sdd: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 2097kB 1051MB 1049MB fat32 boot, esp
2 1051MB 120GB 119GB ext4 endeavouros
Model: USB SanDisk 3.2Gen1 (scsi)
Disk /dev/sde: 30.8GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 30.8GB 30.8GB primary fat32 boot, lba
Model: KINGSTON SNV2S1000G (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 17.4kB 16.8MB 16.8MB Microsoft reserved partition msftres
2 16.8MB 790GB 790GB ntfs Basic data partition msftdata
3 790GB 1000GB 210GB ext4
efibootmgr:
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0000,0001,0002
Boot0000* Windows Boot Manager HD(1,GPT,d0e1f51d-6474-45af-a6a9-05085aff2a13,0x800,0x32000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000006f000100000010000000040000007fff0400
Boot0001* Windows Boot Manager HD(1,GPT,c9250c5f-782d-4416-8bbf-0b689b7a569e,0x1000,0x1f4000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI0000424f
Boot0002* UEFI: USB, Partition 1 PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/USB(2,0)/HD(1,MBR,0x87c4fe0,0x800,0x394d7e0)0000424f
Boot info for EndeavourOS is on ATA Samsung SSD 840. Or at least should be there…
1 Like
In the live session, open a terminal and mount your system partition:
sudo mount /dev/sdd2 /mnt
Check the content of your fstab to see if your ESP is mounted at /boot/efi or /efi:
cat /mnt/etc/fstab
Use the mountpoint to mount your ESP:
- sudo
/dev/sdd1 /mnt/boot/efi(for grub) orsudo mount /dev/sdd1 /mnt/efi(for systemd-boot)
Chroot into your system:
sudo arch-chroot /mnt
Inside chroot:
a. if using Grub (ESP mounted at /boot/efi) run:
5a. grub-install
6a. grub-mkconfig -o /boot/grub/grub.cfg
b. if using systemd-boot (ESP mounted at /efi)
5.b bootctl install
6.b reinstall-kernels
When all is done and you haven’t got any errors to report:
exitfollowed by enter to quit chroot.
Reboot.
1 Like
Thank you very much for this tutorial. EFI entry is back now and boot is working as before!
1 Like
You are welcome! Glad you got it sorted out and your system is back up and running!
Also, welcome to EnOS’ community @tamodolo!
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.