EndeavourOS is removed on its own

Hey guys, I had a dual-booted endeavor and window last week. It was all fine till yesterday. but today I found my endeavor gone. I check the UEFI boot order and stuff and couldn’t find the endeavor and my secure boot was automatically set to enabled. altho I disabled it now but still, the grub ain’t showing. it’s straight booting into the window. i couldn’t think of anything I did in Window which can cause this.

please help me to recover my endeavor os

Welcome to EnOS’ forum @spectkiller!

Endaveour os is removed on its own

This would be a highly extraordinary occurrence :astonished:

Please boot up your EnOS usb installer and provide the output of the following commands:

sudo parted -l

efibootmgr -v

Copy the terminal output as text an paste it into your reply, highlight it and click on </> button to format it.

Also you could have a look at the following wiki pages:

1 Like

Did you issue a system update?

Probably one of the following happened:
Windows went rogue and nuked your UEFI boot entries. This might be true but AFAIK you can’t enable/disable secure boot after OS has loaded so doesn’t seem likely to me.


Your UEFI reset itself, possibly because your CMOS battery died. You mentioned you had disabled secure bıot again, can you check again if ti is disabled?

1 Like

Sudo parted -l

[liveuser@eos-2022.04.08 ~]$ sudo parted -l
Model: ATA ST1000LM049-2GH1 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  983GB   983GB   ntfs         Basic data partition  msftdata
 2      983GB   1000GB  16.9GB  ntfs         Basic data partition  msftdata

Model: SanDisk Ultra (scsi)
Disk /dev/sdb: 30.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name     Flags
 1      1049kB  30.7GB  30.7GB               Ventoy   msftdata
 2      30.7GB  30.8GB  33.6MB  fat16        VTOYEFI  hidden, msftdata

Model: WD Blue SN570 500GB (nvme)
Disk /dev/nvme0n1: 500GB
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
 2      106MB   123MB  16.8MB                  Microsoft reserved partition  msftres
 3      123MB   285GB  285GB   ntfs            Basic data partition          msftdata
 5      285GB   285GB  537MB   fat32                                         boot, esp
 6      285GB   287GB  2147MB  linux-swap(v1)                                swap
 7      287GB   322GB  34.4GB  btrfs
 8      322GB   499GB  178GB   btrfs
 4      499GB   500GB  633MB   ntfs                                          hidden, diag

efrbootmgr -v

[liveuser@eos-2022.04.08 ~]$ efibootmgr -v
BootCurrent: 0005
Timeout: 1 seconds
BootOrder: 0005,0000,0002,0003,0004
Boot0000* Windows Boot Manager	HD(1,GPT,2484615f-459d-4ed7-9e15-c59233dd358f,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.}...a................
Boot0002* UEFI OS	HD(5,GPT,5bca990b-0329-2c4d-b744-be172428f372,0x21257800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0003* UEFI: PXE IP4 Killer E2600 Gigabit Ethernet Controller	PciRoot(0x0)/Pci(0x1,0x4)/Pci(0x0,0x0)/MAC(00d8618a7956,0)/IPv4(,0,0)..BO
Boot0004* UEFI: PXE IP6 Killer E2600 Gigabit Ethernet Controller	PciRoot(0x0)/Pci(0x1,0x4)/Pci(0x0,0x0)/MAC(00d8618a7956,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0005* UEFI: SanDisk, Partition 2	PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(6,0)/HD(2,GPT,9bf520b6-f7ab-4a83-b364-c80d6a3e294a,0x3937b00,0x10000)..BO

yes it is disabled and no I didn’t issue any system update

Try putting Boot0002 to the top of boot order. I don’t remember the exact command, efibootmgr --help may assist you.

1 Like

Could you give some more details about how you installed your system?

Did you choose manual installation?
Which one is the root/system partition? Explain in details your disk setup.
Where did you install Grub?
What is that second FAT32 partition:

5 285GB 285GB 537MB fat32 boot, esp


I am guessing 1-4 is used by Win, 5-8 is used by EnOS. @spectkiller might have shrunk part 3 and have assigned the unallocated space to Calamares.

1 Like

That might be it!
In that case, in the live session:

sudo efibootmgr -o 0005,0002,0000,0003,0004

yes, I choose manual installation

that partition no. 3 was originally 500 Gb size which I shrunk to 285

among the free space which I got after the shrinking, I choose 537 MB for the boot partition, 2 gb for swap, 34 gb for root, and 178 gb for the home partition.

yessir, you’re right

Try the command in my previous post in the live session.
Reboot and see if you get the Grub.

If not, you might need to chroot to your installation and re-install the bootloader.
Please refer to the link in my first post.

yeah i tried and it still straight boot to window and also 002 isn’t endaveour, its some uefi os. so it was expected. as endeavor isn’t showing in boot order at all

Alright. Then I guess chrooting and reinstalling the bootloader is the way to go.
Please read the articles I linked to and if you have any doubts, ask the forum.

Are you sure? It could be a firmware or BIOS update on Windows. I had that recently and Windows does put back secureboot.

Anyway to avoid this, just install Refind and when Windows throws in another surprise, just go into the BIOS and disable secure boot, then Refind will always return.

EDIT: To install Refind read this

1 Like

thanks a lot but before that le me try to recover my endeavour os.

btw how did you then recover your endeavor and its data?

You can install Refind through Arch chroot, it saves you a lot of hoops. :wink:

There’s nothing to recover, because the system is still there. The only issue you are having is that Windows overrides Linux at start up.