Description of problem: - The installer cannot install Silverblue due to a bootloader problem (using EFI) Version-Release number of selected component (if applicable): - Fedora-Silverblue-ostree-x86_64-30-1.2.iso How reproducible: - always on my Dell Precision laptop Steps to Reproduce: 1. In the installer I choose the advanced custom partitioner to install alongside Windows. I create btrfs subvolumes for / and /home, I assign it an exclusive EFI partition. I try to avoid any future break points and to please the partitioner by omitting encryption and creating separate /boot (ext4) (why is that even necessary?). 2. the installer proceeds right to the end where a popup complains: failed to write boot loader configuration 3. Before closing the popup window I switch to console with ctrl-alt-F2. Because the destination filesystem is still mounted: # chroot /mnt/sysimage/fedora/ostree/deploy/......123.0 I notice that /etc/grub2-efi.cfg -> ../boot/efi/EFI/fedora/grub.cfg which is nonexistent (/boot/efi is mounted) and /etc/grub2.cfg -> ../boot/grub2/grub.cfg also nonexistent. As instructed in https://fedoraproject.org/wiki/GRUB_2#Updating_GRUB_2_configuration_on_UEFI_systems I run: # grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg only to get this error: /usr/sbin/grub2-probe: error: cannot find a device for / (is /dev mounted?). /dev is mounted because it is populated with my /dev/sdaX and /dev/nvme0n1pX devices Actual results: - I am left with grub shell on boot Expected results: - Silverblue boots Additional info: - user refi64 suggested this is due to btrfs: https://discussion.fedoraproject.org/t/cannot-install-silverblue-30-failed-to-write-boot-loader-configuration/2563
This is probably a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1289752
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.