Ask Your Question
2

Windows is not available in the boot menu after installing Fedora

asked 2018-12-18 07:50:27 -0500

suman1112 gravatar image

updated 2018-12-19 04:37:50 -0500

Before beginning into details I want to share some basic information. I am using a pc which comes with pre-installed Windows 10. I installed fedora 27 KDE version in this machine by creating a separate disk partition. Before installing fedora I installed CentOS but I don't know what happened the Windows disappeared from the boot menu though the installation was completed successfully. That time I thought that something went wrong and installed fedora.

The installation was ok everything done perfectly but after installation I found that the same problem exists, there are no option for the Windows 10 in the grub menu. Below is the information of disk partition -

[root@localhost surv4]# fdisk -l

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
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: gpt
Disk identifier: CAE0BBBF-F586-44E1-9FBE-2E5EF6B732E6
Device          Start        End   Sectors   Size Type
/dev/sda1        2048     739327    737280   360M EFI System
/dev/sda2      739328    1001471    262144   128M Microsoft reserved
/dev/sda3     1001472  486903807 485902336 231.7G Microsoft basic data
/dev/sda4   486903808 1306103807 819200000 390.6G Microsoft basic data
/dev/sda5  1306103808 1510905855 204802048  97.7G Microsoft basic data  
/dev/sda6  1920503808 1922510847   2007040   980M Windows recovery environment
/dev/sda7  1922510848 1953513471  31002624  14.8G Microsoft basic data
/dev/sda8  1510905856 1511643135    737280   360M Microsoft basic data
/dev/sda9  1511643136 1513740287   2097152     1G Linux filesystem    
/dev/sda10 1513740288 1530103807  16363520   7.8G Linux swap
/dev/sda11 1530103808 1920503807 390400000 186.2G Linux filesystem

And I get the below result after executing the blkid command -

[root@localhost c_surv4]# blkid
/dev/sda1: SEC_TYPE="msdos" UUID="5360-B8E4" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="a7f9b7af-1f76-4713-9a9b-7564c0c2ffb5"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="7fa82623-4fa0-4bad-8071-2fa24f4c1fac"
/dev/sda3: LABEL="Windows" UUID="80D62602D625F8D4" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="defb8011-a9c6-4718-9b44-84f25ecd8d6c"
/dev/sda3: LABEL="Windows" UUID="80D62602D625F8D4" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="defb8011-a9c6-4718-9b44-84f25ecd8d6c"
/dev/sda4: LABEL="New Volume" UUID="F07286F37286BDBA" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="ecc2934b-b666-4098-a3d6-9f9933c2cf60"
/dev/sda5: LABEL="New Volume" UUID="3C4E8A7F4E8A3226" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d70c65d8-41db-44b4-b25d-19b4671f7ea5"
/dev/sda6: LABEL="Windows RE tools" UUID="62806C7D806C5995" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="93485f6d-1f96-4081-93ef-6f688d920470"
/dev/sda7: LABEL="Recovery Image" UUID="869693729693618B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="42107af7-b69d-4c87-9a45-7968ac18ea6c"
/dev/sda8: UUID="ebd8d32a-9881-499d-8a85-fa934f10a520" TYPE="xfs" PARTUUID="e0cf8a4a-3860-43ca-a626-7b5e00bd6cad"
/dev/sda9: UUID="512c55b3-e363-46c4-915f-c8b0c86e00b3" TYPE="ext4" PARTUUID="efbe135c-17d0-4d4e-8b30-56407190c0dc"
/dev/sda10: UUID="684e5398-c238-4f26-8503-a8fe31f675bc" TYPE="swap" PARTUUID="d3134724-33fc-4587-b1b8-5b58d19fb581"
/dev/sda11: UUID="573f1b0a-dba5-49d4-aa37-b27f4dd54bff" TYPE="ext4" PARTUUID="f9720df9-75a8-4ab5-9996-54b7ff8d8495"

I also tried the following command to find if any other os exist - grub2-mkconfig -o /boot/grub2/grub.cfg but nothing found else than linux.

Let me know how to get back the Windows 10.

edit retag flag offensive close merge delete

Comments

One possibility is this: Win10 boots in UEFI mode, linux (both Centos and Fedora) can be installed and booted in both UEFI and BIOS (legacy?) modes. If you have installed Centos and later Fedora in BIOS mode, I think (can't be 100% sure) grub won't see Windows 10 (as it can't be booted in BIOS mode).

Please post here output of cat /etc/fstab command to see if your Fedora was installed in UEFI mode or not.

Night Romantic gravatar imageNight Romantic ( 2018-12-19 01:32:38 -0500 )edit

This is the output -

[root@localhost c_surv4]# cat /etc/fstab
# /etc/fstab
# Created by anaconda on Sun Dec 16 04:52:30 2018
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info    
UUID=573f1b0a-dba5-49d4-aa37-b27f4dd54bff /                       ext4    defaults        1 1
UUID=512c55b3-e363-46c4-915f-c8b0c86e00b3 /boot                   ext4    defaults        1 2
UUID=5360-B8E4          /boot/efi               vfat    umask=0077,shortname=winnt 0 2
UUID=684
suman1112 gravatar imagesuman1112 ( 2018-12-19 02:29:12 -0500 )edit

If Fedora was installed in BIOS/MBR mode the disk should have a bios-grub partition. Without it grub can't install the master boot record on a gpt disk unit. Therefore it is highly unlikely Fedora was installed in Non-UEFI mode.

villykruse gravatar imagevillykruse ( 2018-12-19 03:10:52 -0500 )edit

As we have /boot/efi in fstab, then Fedora/grub is installed in UEFI mode, so my initial guess is wrong.

Please provide output of cat /etc/default/grub, sudo ls -lh /etc/grub.d/, as well as @villykruse's request in his comment below.

Night Romantic gravatar imageNight Romantic ( 2018-12-19 03:39:33 -0500 )edit

*[root@localhost c_surv4]# cat /etc/default/grub

GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rhgb quiet" GRUB_DISABLE_RECOVERY="true

suman1112 gravatar imagesuman1112 ( 2018-12-19 04:31:12 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
2

answered 2018-12-18 12:02:11 -0500

villykruse gravatar image

updated 2018-12-19 06:11:21 -0500

On UEFI systems, the command is:

grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

/boot/grub2/grub.cfg is only used on classic BIOS/MBR boot and not on UEFI boot.

If at any time the EFI file system was re-formatted during installation of linux, the Windows boot loaders will be gone, and therefore you will not be able to boot windows until you have recovered the Windows boot loaders. This probably involves a bootable Windows DVD or similar.

edit flag offensive delete link more

Comments

Also when you issue grub2-mkconfig -o ... it will output all the OSes it have found and added to the boot menu. You should see something like "Found Windows boot manager on sda2" (actual text will be a bit different).

If would be useful if you post here the output of grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg command.

Night Romantic gravatar imageNight Romantic ( 2018-12-19 01:04:25 -0500 )edit

Output of grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg -

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.18.19-100.fc27.x86_64
Found initrd image: /boot/initramfs-4.18.19-100.fc27.x86_64.img
Found linux image: /boot/vmlinuz-4.13.9-300.fc27.x86_64
Found initrd image: /boot/initramfs-4.13.9-300.fc27.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-9c3bc205917545059bff3b1eb21cef9e
Found initrd image: /boot/initramfs-0-rescue-9c3bc205917545059bff3b1eb21cef9e.img
done
suman1112 gravatar imagesuman1112 ( 2018-12-19 02:36:11 -0500 )edit
1

The EFI file system could have been wiped out by mistake during installing of the linux system. If that is the case, only a Microsoft recovery can fix the situation.

Post the output of find /boot/efi to check this.

villykruse gravatar imagevillykruse ( 2018-12-19 03:15:16 -0500 )edit

[root@localhost c_surv4]# find /boot/efi /boot/efi /boot/efi/EFI /boot/efi/EFI/centos /boot/efi/EFI/centos/fonts /boot/efi/EFI/centos/fonts/unicode.pf2 /boot/efi/EFI/centos/shimx64-centos.efi /boot/efi/EFI/centos/grubx64.efi /boot/efi/EFI/centos/BOOT.CSV /boot/efi/EFI/centos/BOOTX64.CSV /boot/efi/EFI/centos/MokManager.efi /boot/efi/EFI/centos/mmx64.efi /boot/efi/EFI/centos/shim.efi /boot/efi/EFI/centos/grubenv /boot/efi/EFI/centos/shimx64.efi /boot/efi/EFI/centos/grub.cfg /boot/efi/EFI/BOOT /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/fallback.efi /boot/efi/EFI/BOOT/fbx64.efi

suman1112 gravatar imagesuman1112 ( 2018-12-19 04:42:38 -0500 )edit

/boot/efi/EFI/BOOT/BOOTIA32.EFI /boot/efi/EFI/BOOT/fbia32.efi /boot/efi/EFI/fedora /boot/efi/EFI/fedora/fonts /boot/efi/EFI/fedora/fonts/unicode.pf2 /boot/efi/EFI/fedora/shimia32-fedora.efi /boot/efi/EFI/fedora/BOOT.CSV /boot/efi/EFI/fedora/BOOTIA32.CSV /boot/efi/EFI/fedora/BOOTX64.CSV /boot/efi/EFI/fedora/MokManager.efi /boot/efi/EFI/fedora/gcdia32.efi /boot/efi/EFI/fedora/gcdx64.efi /boot/efi/EFI/fedora/grubia32.efi /boot/efi/EFI/fedora/grubx64.efi /boot/efi/EFI/fedora/mmia32.efi /boot/efi/EFI/fedora/mmx64.efi /boot/efi/EFI/fedora/shim.efi /boot/efi/EFI/fedora/grubenv

suman1112 gravatar imagesuman1112 ( 2018-12-19 04:44:08 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

2 followers

Stats

Asked: 2018-12-18 07:50:27 -0500

Seen: 53 times

Last updated: Dec 19 '18