TL;DR for people that could be going through the same problem. I’m trying to boot into the Windows partition, that partition is being recognized by Disks Utility, but not by the BIOS or the GRUB menu. Therefore, I can only boot into Fedora. Fedora and Windows are both already installed on separated disks.
I installed Windows 10 on a 300GB partition of a 1TB HD (Left 700GB for personal use) and later installed Fedora 36 on a 500GB SSD. The output of lsblk is the following:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 279.4G 0 part /mnt/sda1
└─sda2 8:2 0 652.1G 0 part /mnt/sda2
sdb 8:16 0 465.8G 0 disk
├─sdb1 8:17 0 1G 0 part /boot
└─sdb2 8:18 0 464.8G 0 part /home
zram0 252:0 0 8G 0 disk [SWAP]
where sda1 is the partition with Windows 10, sda2 is the personal use partition, sdb1 and sdb2 are the SSD partitions with Fedora. However, when I turn on the computer and get into the BIOS boot options, there’s only one option with the Fedora boot and none for the HD’s partition with Windows. The GRUB menu only shows Fedora too. I want to boot into Windows and then include it in the GRUB menu options without reinstalling Windows.
Edit: GNOME Disks recognizes all the partitions and I can access the Windows Files through the Files Explorer (nautilus). However the boot doesn’t recognize any of the HD partitions (sda1 or sda2) for some reason. sda1 partition is called Windows Fig and as you can see I can access its files:
inxi -Fzx in terminal and post the output as </> Preformatted text here.
For me it looks like that you are booting in legacy mode. For this the Windows partition needs to be active and have a boot flag. But first we need more info’s about your system to give you more specific instructions.
If you unhook SATA cable on SSD … what happens? Windows NT and Linux have different tools for this and that, if Windows is the culprit simply use Microsoft tool kit.
You can use NTFS file system on Linux, you can also use BTRFS file system in Windows being the default file system in Fedora and used in ReactOS => Open source Winbtrfs with link in GitHub.
Both Disks are inside the laptop. But that’s a good question, that based on my experience of trial and error booting, my guess is that the computer will stop working because there could be something wrong with the Windows partition’s boot protocol.
How does having an account solves the problem? Also, I think I’ll be reinstalling because I’ve been having trouble with this for 2 days without a solution. However, I consider that this problem might be so trivial that can be solved without reinstalling everything (because I already configured Windows 10 for like 4 hours removing the bloat and spyware).
Hello @figaro ,
welcome to ,
You say that you can’t even get Win10 to boot from BIOS (I assume UEFI?)? If this is the case, you likely have somehow borked the esp, and may have to “grin and bear it” and just re-install (grub will need redoing after). In dual booting scenarios, I have chosen to increase the size of the /boot/efi partition to around 600mb since I ran into issues with the recommended size from the doc’s.
Does Fedora Linux boot from the BIOS boot menu?
maybe try grub2-probe <windows-device>? If you do any changes to grub I think grubby is the recommended tool to add/modify menu items, and grub2-mkconfig needs to be run afterwards to write the changes.
I have reinstalled Windows and Fedora, and now both work flawlessly. However I’m a bit bothered by the fact I wasted so much time (backups and customizing again) in something that maybe could be solved by using the terminal. Nonetheless I thank you for assisting correctly in my problem. I marked the reinstalling comment as a solution.
P.S. I tried the grub2-probe solution without success after reinstalling Windows 10 (before reinstalling Fedora again) and had no success even when the BIOS recognized Windows 10 as a bootable partition again. I tried all the solutions above with the same result, therefore, I reinstalled Fedora too.