[SOLVED] After installing Fedora, Windows won't boot

whois1230 · 11-01-2020, 03:52 AM

Hello. I had dual boot Windows 10 + Linux Ubuntu 18.04 LTS. I installed Fedora on an empty partition using Legacy Support. Now when I try to set UEFI as default in BIOS, I am getting an error afterwards. I can run Ubuntu, but not Windows 10. I opened GPARTED in Ubuntu and the Windwos partition isn't deleted, but it still won't boot. I uploaded screenshots

whois1230 · 11-01-2020, 03:53 AM

2 more screenshots

yancek · 11-01-2020, 05:49 AM

Your Legacy install of Fedora Grub will not boot an EFI install of windows but will boot an EFI install of Linux. If you want Grub to boot all systems, they must match (all UEFI or all Legacy). You show both a BIOS_grub partition which is used only on GPT drives for Legacy install as well as an EFI partition. With that setup, you will need to access the BIOS to make changes needed to boot windows.
Have you tried setting the Grub boot entry for Ubuntu in your BIOS to first priority?

AFAIK, the windows default bootloader won't boot either Linux in either mode without user intervention or 3rd party software.

mrmazda · 11-01-2020, 05:54 AM

Unless you are a true expert, you must have all operating systems installed in the same boot mode, either UEFI, or legacy. Windows installed in UEFI mode cannot be booted in legacy mode. Installing Fedora "using legacy support" sounds like it was installed in legacy mode.

I'm not a Gparted user, so can only surmise that the red exclamations in the screenshot are informing you of partitions that will not be bootable using the current configuration.

You're probably going to need to revert to the partitioning in place before installing Fedora to get Windows to boot again, then install Fedora in UEFI mode. But before doing anything else, boot Ubuntu, open a terminal, and paste here using code tags ( [ # ] above the input window) input and output from:

Code:

sudo parted -l

so we might suggest with more specificity how to proceed.

whois1230 · 11-01-2020, 06:19 AM

Quote:

Originally Posted by mrmazda

Unless you are a true expert, you must have all operating systems installed in the same boot mode, either UEFI, or legacy. Windows installed in UEFI mode cannot be booted in legacy mode. Installing Fedora "using legacy support" sounds like it was installed in legacy mode.

I'm not a Gparted user, so can only surmise that the red exclamations in the screenshot are informing you of partitions that will not be bootable using the current configuration.

You're probably going to need to revert to the partitioning in place before installing Fedora to get Windows to boot again, then install Fedora in UEFI mode. But before doing anything else, boot Ubuntu, open a terminal, and paste here using code tags ( [ # ] above the input window) input and output from:

Code:

sudo parted -l

so we might suggest with more specificity how to proceed.

Code:

user@Lenovo-ideapad-110-17IKB:~$ sudo parted -l
[sudo] password for user: 
Model: ATA WDC WD10JPCX-24U (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: pmbr_boot

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  274MB  273MB   fat32        EFI system partition          boot, esp
 2      274MB   290MB  16,8MB               Microsoft reserved partition  msftres
 3      290MB   331GB  330GB   ntfs         Basic data partition          msftdata
 4      331GB   331GB  1049kB                                             bios_grub
 5      331GB   332GB  1074MB  ext4
10      332GB   650GB  318GB   btrfs
 9      650GB   957GB  307GB   ext4
 6      957GB   984GB  26,8GB  ntfs         Basic data partition          msftdata
 7      984GB   985GB  1049MB  ntfs         Basic data partition          hidden, diag
 8      985GB   999GB  14,2GB  ntfs         Basic data partition          hidden, diag


user@Lenovo-ideapad-110-17IKB:~$

whois1230 · 11-01-2020, 06:31 AM

Quote:

Originally Posted by yancek

Have you tried setting the Grub boot entry for Ubuntu in your BIOS to first priority?

Yes, but it isn't showing. Take a look at the screenshots that I posted

colorpurple21859 · 11-01-2020, 08:03 AM

Quote:

Originally Posted by whois1230

Yes, but it isn't showing. Take a look at the screenshots that I posted

I think this is your problem:

Quote:

Disk Flags: pmbr_boot

open a terminal

Code:

parted /dev/sda
(parted) disk_set pmbr_boot off
(parted) quit

reboot
See if you now have the option to set ubuntu as first in boot option. Running "sudo update-grub" in ubuntu should give you options to boot fedora.

whois1230 · 11-01-2020, 08:52 AM

Quote:

Originally Posted by colorpurple21859

I think this is your problem:

open a terminal

Code:

parted /dev/sda
(parted) disk_set pmbr_boot off
(parted) quit

reboot
See if you now have the option to set ubuntu as first in boot option. Running "sudo update-grub" in ubuntu should give you options to boot fedora.

Hello, I ran the commands and Ubuntu and Windows Boot Manager are showing again, however, when I try to boot Windows 10 it gets stuck at "Repairing" and I can't boot into Windows.

Code:

user@Lenovo-ideapad-110-17IKB:~$ sudo update-grub
[sudo] password for user: 
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-52-generic
Found initrd image: /boot/initrd.img-5.4.0-52-generic
Found linux image: /boot/vmlinuz-5.4.0-51-generic
Found initrd image: /boot/initrd.img-5.4.0-51-generic
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done
user@Lenovo-ideapad-110-17IKB:~$

p.s. I restored an earlier version of Windows using a Windows 10 installation CD. This could have something to do with Windows not booting

colorpurple21859 · 11-01-2020, 09:11 AM

Code:

p.s. I restored an earlier version of Windows using a Windows 10 installation CD. This could have something to do with Windows not booting

You may be able to fix using the windows10 iso.

to get fedora boot menu add a menuentry in /etc/grub.d/40_custom something like this

Code:

menuentry 'fedora config file'{
configfile (hd0,?)/grub2/grub.cfg
}

where ? is the partition fedora grub directory is on. grub counts partitions starting at one. It maybe /boot/grub2/grub.cfg
Then rerun update-grub

whois1230 · 11-01-2020, 01:20 PM

Quote:

Originally Posted by colorpurple21859

Code:

p.s. I restored an earlier version of Windows using a Windows 10 installation CD. This could have something to do with Windows not booting

You maybe able to fix using the windows10 iso.

to get fedora boot menu add a menuentry in /etc/grub.d/40_custom something like this

Code:

menuentry 'fedora config file'{
configfile (hd0,?)/grub2/grub.cfg
}

where ? is the partition fedora grub directory is on. grub counts partitions starting at one. It maybe /boot/grub2/grub.cfg
Then rerun update-grub

I wiped the Fedora partition completely and tried to install Fedora in Uefi mode, but it gets stuck and won't install.

mrmazda · 11-01-2020, 02:04 PM

More info seems to be called for, to learn where Ubuntu is, and what Fedora did and may be trying to do:

Code:

mount | grep sda
sudo blkid
sudo efibootmgr -v

I'm thinking the bios_grub partition may be the impediment to getting Fedora to install in UEFI mode.

computersavvy · 11-01-2020, 03:59 PM

Quote:

Originally Posted by mrmazda

More info seems to be called for, to learn where Ubuntu is, and what Fedora did and may be trying to do:

Code:

mount | grep sda
sudo blkid
sudo efibootmgr -v

I'm thinking the bios_grub partition may be the impediment to getting Fedora to install in UEFI mode.

There was a blocking bug in the most recent release of fedora that had something to do with Ubuntu, Windows, and BIOS. IIRC it was that the latest release of Ubuntu accepted and made permanent a change by windows that blocks most other distros from booting on a machine with dual or multi boot. It seems to be something about a new signature or something that windows has not released to other distros so for the interim (until the sig is released by windows) Fedoras new release was OKed with the caveat that on machines where Ubuntu 20 had already been installed that fedora would not boot.

I am going by memory from reading the discussion and was unable to find the post on askfedora that discussed it but will keep searching.

UPDATE:
Apparently the issue was related to secure boot, and it already affected F32 so they decided that F33 could be released. There is a fedora magazine article that discusses the secure boot issue here.

On some machines turning off secure boot will allow fedora to boot, but it may also interfere with windows and/or Ubuntu since the change apparently forces secure boot on for those systems.

Ubuntu has apparently removed the dbx update that triggered the problem but that won't help already existing installs.

The full details of the fedora release meeting and about the bug can be found here for those who are interested. The gist of it is that fedora may not install or boot with secure boot on and other OSes may not boot with secure boot off.

UPDATE2
Here is the actual bug related to secure boot with fedora.

whois1230 · 11-02-2020, 03:12 AM

Quote:

Originally Posted by mrmazda

More info seems to be called for, to learn where Ubuntu is, and what Fedora did and may be trying to do:

Code:

mount | grep sda
sudo blkid
sudo efibootmgr -v

I'm thinking the bios_grub partition may be the impediment to getting Fedora to install in UEFI mode.

Code:

user@Lenovo-ideapad-110-17IKB:~$ sudo
usage: sudo -h | -K | -k | -V
usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user]
            [command]
usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
            prompt] [-T timeout] [-u user] [VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
            prompt] [-T timeout] [-u user] file ...
user@Lenovo-ideapad-110-17IKB:~$ su
Password: 
root@Lenovo-ideapad-110-17IKB:/home/user# mount | grep sda
/dev/sda9 on / type ext4 (rw,relatime,errors=remount-ro)
/dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
root@Lenovo-ideapad-110-17IKB:/home/user# sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda1: LABEL="SYSTEM_DRV" UUID="4CA0-4064" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="bbca276a-71b2-44d4-8063-c1737eb0e017"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="99c747c1-3da4-46c2-befa-9eaa1e6e4f80"
/dev/sda3: LABEL="Windows" UUID="7A1CA2401CA1F773" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="8906664c-6b4e-4087-9a70-75e8acc658e9"
/dev/sda5: UUID="b9232b0f-5cd5-455a-bd28-442685f468b2" TYPE="ext4" PARTUUID="cea226cd-313b-46d2-a757-94d8a14bb682"
/dev/sda6: LABEL="LENOVO" UUID="14FC6F46FC6F20EA" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="1c0aa318-8e4f-4df9-abb9-859bc9f8f7fa"
/dev/sda7: LABEL="WINRE_DRV" UUID="DADC9FFBDC9FD05D" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="0dc08548-8888-4200-b836-8ca373552ce5"
/dev/sda8: LABEL="LENOVO_PART" UUID="F6E07325E072EB6F" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="663d5e44-2446-4f03-af05-23aa14acc85b"
/dev/sda9: UUID="674caa48-d7c7-4d7c-bc00-e0ced07081d2" TYPE="ext4" PARTUUID="7c498140-ec41-43a2-a58c-333a9f0d3da6"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
/dev/loop20: TYPE="squashfs"
root@Lenovo-ideapad-110-17IKB:/home/user# sudo efibootmgr -v
BootCurrent: 0006
Timeout: 0 seconds
BootOrder: 0006,0000,2003,2001,2002
Boot0000* Windows Boot Manager	HD(1,GPT,bbca276a-71b2-44d4-8063-c1737eb0e017,0x800,0x82000)/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.}....................
Boot0003* EFI Network 0 for IPv4 (54-E1-AD-0B-AF-B6) 	PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(54e1ad0bafb6,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0004* EFI Network 0 for IPv6 (54-E1-AD-0B-AF-B6) 	PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(54e1ad0bafb6,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0006* ubuntu	HD(1,GPT,bbca276a-71b2-44d4-8063-c1737eb0e017,0x800,0x82000)/File(\EFI\ubuntu\shimx64.efi)RC
Boot0007* EFI Network 0 for IPv4 (54-E1-AD-0B-AF-B6) 	PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(54e1ad0bafb6,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0008* EFI Network 0 for IPv6 (54-E1-AD-0B-AF-B6) 	PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(54e1ad0bafb6,0)/IPv6([::]:<->[::]:,0,0)RC
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC
root@Lenovo-ideapad-110-17IKB:/home/user#

mrmazda · 11-02-2020, 04:03 AM

One more, to see if it suggests what's on /dev/sda5:

Code:

cat /etc/fstab

You could find out yourself by mounting /dev/sda5 to /mnt and taking a looksee if it has the usual / directories or something else, and if it's / entries, what /mnt/etc/os-release contains.

I've never seen efibootmgr produce network entries before. Do you have any sense as to why they are there? Unless you are PXE booting, I have to guess they could and should be removed using efibootmgr -B.

colorpurple21859 · 11-02-2020, 05:32 AM

Quote:

I wiped the Fedora partition completely and tried to install Fedora in Uefi mode, but it gets stuck and won't install.

Did you get fedora re-installed?

Quote:

but it gets stuck and won't install.

where does it get stuck, during the partitioning stage did you select /dev/sda1 to be mounted at /boot/efi?