Hey all, I went to install Endeavor on a second hard drive on my PC, and it seemed to destroy the Win11 MBR and only allow me to boot into Endeavor (I’m not sure thats actually what happened, just the result).
When I originally did this, it didn’t happen. Am I missing something in the install process to have a proper multi-boot system?
Perhaps or perhaps not.
We need some more info:
Is your Win 11 installed in MBR/Legacy/Bios mode?
Did you install EndeavourOS also in MBR mode? If so where did you choose to install Grub’s bootloader?
Post the output of:
test -d /sys/firmware/efi && echo UEFI || echo BIOS
sudo parted -l
cat /etc/fstab
efibootmgr
I’m not sure. I had to reinstall Windows for work stuff, so it blew away the ability to work in Endeavor. So I don’t have access to Endeavor at the moment.
I’m not sure I understand everything so, pardon if I don’t use the right terminology. I have a UEFI, so I don’t believe I installed in Legacy/Bios mode, and maybe not MBR (I thought there was an MBR regardless of bios type, so that sounds like I don’t understand that)
I used the Endeavor Defaults for everything, as that’s what I did last time. Windows wasn’t on the Grub screen when it was done, and I also wasn’t able to choose the windows drive from the UEFI Bios boot options any longer either.
Please use your EnOS live usb and post the output of the commands in my previous post.
[liveuser@eos-2024.06.25 ~]$ test -d /sys/firmware/efi && echo UEFI || echo BIOS
sudo parted -l
cat /etc/fstab
efibootmgr
UEFI
Model: ATA TEAM T253512GB (scsi)
Disk /dev/sda: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 630MB 629MB fat32 EFI System Partition boot, esp
2 630MB 1704MB 1074MB xfs
3 1704MB 512GB 510GB lvm
Model: ATA TEAM T253512GB (scsi)
Disk /dev/sdb: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 2097kB 1076MB 1074MB fat32 EFI boot, esp
2 1076MB 503GB 502GB ext4 endeavouros
3 503GB 512GB 9449MB linux-swap(v1) swap
Model: ATA WDC WDS500G2B0A (scsi)
Disk /dev/sdc: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 32.8kB 500GB 500GB primary boot
Model: ATA ST3000DM007-1WY1 (scsi)
Disk /dev/sdd: 3001GB
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 3001GB 3001GB ntfs Basic data partition msftdata
Model: General USB Flash Disk (scsi)
Disk /dev/sde: 32.3GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 2738MB 2901MB 163MB primary fat16 esp
Model: Samsung SSD 990 PRO 2TB (nvme)
Disk /dev/nvme0n1: 2000GB
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 2000GB 2000GB ntfs Basic data partition msftdata
Model: HP SSD EX950 2TB (nvme)
Disk /dev/nvme1n1: 2000GB
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 2000GB 1999GB ntfs Basic data partition msftdata
4 2000GB 2000GB 805MB ntfs hidden, diag, no_automount
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0003,0004
Boot0000* Windows Boot Manager HD(1,GPT,4e7bf4a8-0503-4079-83a1-77b551b6ffca,0x800,0x32000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000033000100000010000000040000007fff0400
Boot0001* RedHat Boot Manager HD(1,GPT,5e7f1ff6-82f9-452f-94b6-328d60a7a645,0x800,0x12c000)/\EFI\REDHAT\SHIMX64.EFI0000424f
Boot0002* UEFI OS HD(1,GPT,f2471687-f9c5-435a-8db4-4f3a0011a78d,0x1000,0x200000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot0003* UEFI: General USB Flash Disk 1100 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(6,0)/CDROM(1,0x519980,0x4da98)0000424f
Boot0004* UEFI: General USB Flash Disk 1100, Partition 2 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(6,0)/HD(2,MBR,0xe06d72b0,0x519980,0x4d800)0000424f
I’m gonna bump this in case someone can help, I’d love to reinstall EOS, but want to make sure I have access to both my installs. 
For next time: always always always unplug the WIN HDD when you install on the other drive. I’ve never gone wrong that way. You will have separate boots.
you could unplug endeavour and use MS recovery disk to get yer mbr back right?
2 cents
Looks like to me you have the device as mbr instead of gpt
it looks like boot expects gpt
Boot0002* UEFI OS HD(1,GPT,f2471687-f9c5-435a-8db4-4f3a0011a78d,0x1000,0x200000)/\EFI\BOOT\BOOTX64.EFI0000424f
when using EFI you need GPT and not MBR
Did you choose Systemd-boot in the install or grub?
I have a couple experimental drives in this system, I could probably pull those.
When it comes to the install, I don’t specifically remember which one it was, but it was whatever the default of EOS is.
So my windows drive is under the GPU. 
That is a bit of a herculean task to do this, are there any other suggestions to get the multiboot system, or any resources for it you can suggest?
can you answer this question?
You have a gpt disk but your booting mbr so I suspect you are using legacy boot however it appears you installed for UEFI boot
Of course there are resources for that. I followed https://wiki.archlinux.org/title/Dual_boot_with_Windows
But, honestly, your experimental drive setup looks scary. I do not want to even start reading it, it is too much 