[SOLVED] After installing Fedora, Windows won't boot
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have Ubuntu 18.04 LTS + Windows 10 OEM. I re-installed Windows 10, because it was broken and stuck on "Repairing", and now my Grub works fine. Is there any way to install the latest version of Fedora Workstation in UEFI mode?
p.s. I found the following thread: https://www.linuxquestions.org/quest...de-4175657780/
post the contents of ubuntu /etc/fstab.
and the files on /dev/sda5 and the ouput of
Code:
sudo parted -l
Code:
user@Lenovo-ideapad-110-17IKB:~$ sudo gedit /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda9 during installation
UUID=674caa48-d7c7-4d7c-bc00-e0ced07081d2 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=4CA0-4064 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
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:
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
5 331GB 332GB 1074MB ext4
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:~$
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.
Code:
user@Lenovo-ideapad-110-17IKB:~$ sudo cat /etc/fstab
[sudo] password for user:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda9 during installation
UUID=674caa48-d7c7-4d7c-bc00-e0ced07081d2 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=4CA0-4064 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
user@Lenovo-ideapad-110-17IKB:~$
Code:
user@Lenovo-ideapad-110-17IKB:~$ sudo efibootmgr -B
You must specify an entry to delete (see the -b option).
what are you using to boot fedora dvd, usb? If usb what did you use to install iso to usb? I found this issue with fedora 17, maybe it will work with you. https://bugzilla.redhat.com/show_bug.cgi?id=824617
Last edited by colorpurple21859; 11-03-2020 at 08:53 AM.
what are you using to boot fedora dvd, usb? If usb what did you use to install iso to usb? I found this issue with fedora 17, maybe it will work with you. https://bugzilla.redhat.com/show_bug.cgi?id=824617
Hello. I am using a USB drivbe. I used Unetbootin to install the .iso to the USB stick. I can try using Rufus on my Windows 10, if that makes a difference?
user@Lenovo-ideapad-110-17IKB:~$ sudo mount /dev/sda5 /mnt
mount: /mnt: /dev/sda5 already mounted on /mnt.
user@Lenovo-ideapad-110-17IKB:~$ ls /mnt
config-5.8.15-301.fc33.x86_64
...
/dev/sda5 contains a Fedora 33 /boot filesystem. Traditionally this means the Fedora installation was configured with another partition using LVM for everything except /boot. Given the physical placement of sda10 adjacent to sda5, apparently Fedora has switched from EXT4 to BTRFS, either to provide a home for LVM, or to house the Fedora / directly. ISTR Ubuntu does a poor job of recognizing BTRFS, or doesn't support it at all. You don't have to accept the Fedora installer's proposal, and use EXT4 instead, as well as not use LVM if you'd rather not. I use Fedora directly on EXT4, without a separate /boot, but with a separate /home.
I think unetbootin has problems in uefi mode. Rufus should work. If rufus doesn't work in the default mode, try the DD mode.
Quote:
Originally Posted by mrmazda
/dev/sda5 contains a Fedora 33 /boot filesystem. Traditionally this means the Fedora installation was configured with another partition using LVM for everything except /boot. Given the physical placement of sda10 adjacent to sda5, apparently Fedora has switched from EXT4 to BTRFS, either to provide a home for LVM, or to house the Fedora / directly. ISTR Ubuntu does a poor job of recognizing BTRFS, or doesn't support it at all. You don't have to accept the Fedora installer's proposal, and use EXT4 instead, as well as not use LVM if you'd rather not. I use Fedora directly on EXT4, without a separate /boot, but with a separate /home.
I managed to install Fedora in Uefi mode using Rufus on Windows 10. Now I have a triple-boot system. However, there are 2 instances of Fedora in BIOS, and when I set Ubuntu as my 1st operating system in BIOS, Fedora doesn't show in the grub menu. I want to have Ubuntu as my 1st OS in grub, and have Fedora in grub as well. I ran
The ? will be the partition number of fedora boot partition, (hd0,5) is what it was originally.
you may be able to look at fedora /etc/fstab to see which partition is fedora /boot.
If you provide more info we can probably better determine what's going on. We don't know if the Fedora installation changed the partitioning, which may be why the BIOS shows Fedora twice.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.