Code: Select all
bootrec /ScanOs
bootrec /FixMbr
bootrec /FixBoot
(bootrec /RebuildBcd)
Code: Select all
bootrec /ScanOs
bootrec /FixMbr
bootrec /FixBoot
(bootrec /RebuildBcd)
Code: Select all
sudo os-prober
Code: Select all
sudo update-grub
Code: Select all
lsblk
Code: Select all
blkid
this probably says that the win bootlaoder is on the separate 500mb partition? (says Windows 10:Windows:chain)all41 wrote: ⤴Fri May 28, 2021 10:49 am With win onboard I would put the bootloader on the same partition as the linux install
and move this drive to the top of the boot order in bios.
That keeps the linux bootloader (grub) away from win updates to it's own bootloader.
Try booting into your linux installation and run the following terminal inquiry:Code: Select all
sudo os-prober
is wrong. It is applicable to legacy boot not UEFI boot. In UEFI boot you select the bootloader in BIOS, in legacy boot you select the drive the bootloader is on in BIOS.and move this drive to the top of the boot order in bios.
No. When you installed windows it will have created an EFI partition (this is where the bootloaders live). It is probably nvme0n1p1. Boot your mint install stick, open a terminal and post the output fromand the grub bootloader should be on the "nvme0n1p8" partition then, as it is 150mb in size and i know that i made that manually to be the future linux boot partition?
sudo parted --list
. Post the output between code markers (the </>
button above the reply window, more info here viewtopic.php?f=29&t=338297). When mint installed it looks for an EFI partition and installs the bootloader in it. It will have ignored nvme0n1p8 (and did you format it fat32 and set the flags esp & boot?).sudo os-prober
would be helpful. It will help us to figure out what you have done.That is just wrong!screenshot wrote: ⤴Mon Sep 27, 2021 7:16 pm multiboot system cant have uefi, so i only have legacy etc...