Calamares did something to my other drive

When I installed, selected the drive and it created that 16M extra partition, I thought that would be the ESP

Its the 465,76 GiB drive

/dev/nvme1n1p1  2048     34815     32768    16M Microsoft reserved
/dev/nvme1n1p2 34816 976773119 976738304 465,7G Microsoft basic data

Edit:

I think so because I was using F8 to select the OS to boot to

That looks to me like Legacy type of partitioning. Normally Windows installer create a 100 MB FAT32-formatted ESP for a UEFI install.

1 Like

That is strange, my BIOS is with the default settings, didn’t enable anything regarding legacy boot in BIOS.
Also, I was using Windows 11, so, it was also with secure boot enabled, TPM and all that…

Edit: Windows was showing in the UEFI along with Enos…

@anon49550872
You shouldn’t be pressing F8 during boot process to switch to another OS. When you install Windows in UEFI it creates an efi partition and normally you would use that same efi partition when you install EOS. When EOS installs the bootloader (grub). It is grub that boots both Windows and EOS even if Windows is on another drive. Then you should be booting from the drive that has EOS installed on it because it is grub that boots both. No need to switch drives to boot another OS. Even if you used a separate efi on EOS it is still grub that boots both not the Windows bootloader.

Edit: But of course you need the Windows one for it to boot Windows so if it gets trashed then your pooched as they say!

1 Like

It beats me. It is rather odd. I see @ricklinux is replying. He will surely have something to say about this.

1 Like

Thanks pebcak, you guys are always rescuing me… =)

ricklinux, I’ll proceed with the grub option to check if it fixes the problem, one sec.

1 Like

There is something very wrong here… I’ll create the windows ISO and try to restore from there to see what happens.

$ sudo LANG=C grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux-hardened
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-hardened.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-hardened-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
done
1 Like

yes try to recover winboot

1 Like

Sure things can go wrong and it can overwrite the windows bootloader too. If you use the Windows ISO to recreate the Windows bootloader depending on how you do it you’ll most likely have to come back and run update grub because it’s the one supposed to be controlling the boot. That is if you are using grub! :wink:

1 Like

Thanks rick, I have a Enos live USB here to comeback in case of that happening :slight_smile:

image

1 Like

You know what they say … there’s more than one way to boot Windows. Easiest way is to boot it the hell off the drive! :laughing:

3 Likes

My favorite way to boot windows. . . is on someone else’s computer.

2 Likes

Had to reinstall the Windows… The boot auto repair did nothing.
It wasn’t so bad because my main system is Enos… Windows is just for gaming…
So just installed, updated a bunch of stuff and it’s good to go now…

2 Likes

System reinstalled…

$ sudo efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0000,0001,000A
Boot0000* Windows Boot Manager	HD(1,GPT,36d588c4-a11a-6243-8d18-00802ffc3e5e,0x1000,0x96000)/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.4.7.9.5.}...o................
Boot0001* endeavouros-7347	HD(1,GPT,36d588c4-a11a-6243-8d18-00802ffc3e5e,0x1000,0x96000)/File(\EFI\ENDEAVOUROS-7347\GRUBX64.EFI)
Boot000A* UEFI OS	HD(1,GPT,36d588c4-a11a-6243-8d18-00802ffc3e5e,0x1000,0x96000)/File(\EFI\BOOT\BOOTX64.EFI)..BO

$ sudo efibootmgr
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0000,0001,000A
Boot0000* Windows Boot Manager
Boot0001* endeavouros-7347
Boot000A* UEFI OS
1 Like

Out of curiosity, what was the partition scheme created by Windows’ installer?

image

1 Like

That’s interesting! Similar to the one you had before, that is, only with two partitions and no ESP. Perhaps something has changed with Windows 11.

1 Like

Yes, it seems so… I didn’t set anything manually during the installation.

2021-12-05_14-10

My ms-11 upgraded from win-10…

But indeed strange that it seems win 11 do not use ESP to boot…

1 Like

What I remember from previous installation of Win 10 is that it would set up a 100 MB FAT32-formatted ESP.

From

Boot0000* Windows Boot Manager	HD(1,GPT,36d588c4-a11a-6243-8d18-00802ffc3e5e,0x1000,0x96000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS........

it seems that it is using the first partition of the disk as the location of its bootloader but it is not marked as ESP. It is Microsoft reserved!

So would this mean that it cannot be shared to accommodate Linux bootloader as previously with ESP?