Bootloader installation fails while installing the system as dualboot on separate disks

Hi,

I’m trying to dualboot endeavour with windows on separate disks but the installer returns an error during the bootloader installation.
I want the bootloader to be on the same drive as windows so that it shows up automatically when turning on the computer. I managed to successfully install endeavour with the bootloader on the same drive as the OS but that causes it not to show up on startup and turn on windows automatically (I have to press F11 and choose the correct disk to access endeavour).
Here is a link to the logs that the installer generated:
https://termbin.com/uwxu
If it matters, I previously had manjaro installed on the drive I’m trying to setup endeavour on now. With manjaro the boot menu turned on automatically on startup and allowed me to choose a system.
Is it possible to get the same result with endeavour?

Thanks in advance!

Please send output of

sudo fdisk -l
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for cross-disk install.
2022-08-20 - 10:27:08 [2]: WARNING: [PYTHON JOB]: "Command 'grub-install --target=i386-pc --recheck --force /dev/nvme0n1' returned non-zero exit status 1." 
2022-08-20 - 10:27:08 [6]: [PYTHON JOB]: "stdout:Installing for i386-pc platform.\ngrub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.\ngrub-install: error: embedding is not possible, but this is required for cross-disk install."

Looks like you are doing an MBR/Legacy install on a disk with GUID partition table.

This is called BIOS/GPT :sweat_smile:
Also EndeavourOS is one of the very few distributions which is OOB capable of doing that.

Here it is
The drive I want endeavor on is IRIDIUM PRO and the one with windows is Force MP510:

Disk /dev/sda: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: IRIDIUM PRO
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8bd0d8eb

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 468858879 468856832 223.6G 7 HPFS/NTFS/exFAT

Disk /dev/sdb: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: ADATA SU800
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x3dd02f8e

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 2000406527 2000404480 953.9G 7 HPFS/NTFS/exFAT

Disk /dev/sdc: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DM003-1SB1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xa96dd874

Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 1953521663 1953519616 931.5G 7 HPFS/NTFS/exFAT

Disk /dev/nvme0n1: 894.25 GiB, 960197124096 bytes, 1875385008 sectors
Disk model: Force MP510
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A168EE3C-3DFD-4A6E-9F24-CB17FC0ECE36

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1085439 1083392 529M Windows recovery environment
/dev/nvme0n1p2 1085440 1290239 204800 100M EFI System
/dev/nvme0n1p3 1323008 1875384319 1874061312 893.6G Microsoft basic data

Disk /dev/sdd: 7.21 GiB, 7743995904 bytes, 15124992 sectors
Disk model: USB DISK 2.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0019693f

Device Boot Start End Sectors Size Id Type
/dev/sdd1 * 2048 15124991 15122944 7.2G c W95 FAT32 (LBA)

Disk /dev/loop0: 1.6 GiB, 1714974720 bytes, 3349560 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Sorry, I don’t really follow. Could you explain how I can fix it?

I have never tried it myself.

So that would mean that EnOS’ Calamares will create the required Bios boot partition on a GPT disk if you do a MBR/Legacy install?

https://wiki.archlinux.org/title/GRUB#BIOS_systems

Probably yes if you boot in Legacy mode and use an empty disk.

If I am reading the output of fdisk -l correctly, your Windows is installed in UEFI mode on a GPT disk.

I would suggest to install EnOS in UEFI mode as well.
That means you need to boot your Live USB in UEFI mode and let the installer automatically create all needed partitions for you “erase and install”.

Go into Bios and disable Legacy/CSM boot mode and then boot up your Live USB.

2 Likes

While doing what @pebcak mentioned, don’t install EnOS bootloader to Windows disk, install it to EnOS disk.

That’s something I need to test on some occasion.

That solved my problem, everything now works as intended. Many thanks!

1 Like

Glad to hear that!
Enjoy your EnOS and welcome to the community @akip!

:enos_flag: :handshake:t5:

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.