Fedora Account System
Red Hat Associate
Red Hat Customer
Installation of the system failed: Встановлення завантажувача org.fedoraproject.Anaconda.BootloaderInstallationError: boot loader install failed ---[ System & Environment Information ]--- OS: Fedora Linux 44 (Workstation Edition) Anaconda version: 44.30 Anaconda UI version: 68
Created attachment 2144475 [details] Log file: /tmp/journal.log
Created attachment 2144476 [details] Log file: /tmp/anaconda.log
Created attachment 2144477 [details] Log file: /tmp/storage.log
Created attachment 2144478 [details] Log file: /tmp/program.log
Created attachment 2144479 [details] Log file: /tmp/packaging.log
Created attachment 2144480 [details] Log file: /tmp/anaconda-webui.log
*** This bug has been marked as a duplicate of bug 2394554 ***
This looks like a misclassification — this doesn't appear to be a duplicate of bug 2394554 (the BTRFS nested subvolume NoneType/path crash during manual partitioning). The actual root cause here is a GRUB bootloader installation failure, unrelated to BTRFS subvolumes or manual mount point assignment. From program.log: INFO:program:Running in chroot '/mnt/sysroot'... grub2-install --no-floppy /dev/sdb INFO:program:Installing for i386-pc platform. INFO:program:error: ../grub-core/disk/diskfilter.c:validate_lv:531:invalid volume. INFO:program:grub2-install: warning: ../grub-core/disk/ldm.c:grub_util_ldm_embed:1062:disk isn't LDM. INFO:program:grub2-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. INFO:program:grub2-install: error: will not proceed with blocklists. DEBUG:program:Return code of grub2-install: 1 The corresponding Python traceback confirms this comes from pyanaconda/modules/storage/bootloader/grub2.py:425 (BootLoaderError: boot loader install failed), triggered from installation.py:210, which is a completely separate code path from the storage partitioning module involved in bug 2394554. The invalid volume errors suggest /dev/sdb has leftover/corrupted LVM or LDM metadata from a previous installation that wasn't fully wiped before GRUB attempted embedding. GRUB refuses to fall back to blocklists (by design, since they're unreliable), which is reasonable — but the resulting BootLoaderError then propagates up as an uncaught error caught by the frontend's ErrorBoundary (see anaconda-webui.log: [ERROR] ErrorBoundary caught an error: boot loader install failed) instead of a clear, actionable message to the user. Since this has already been reopened — should this be tracked as a separate bug from 2394554? There seem to be two distinct problems worth tracking: Anaconda not fully cleaning up stale LVM/LDM signatures on the target disk before GRUB installation The bootloader installation error not being surfaced to the user with actionable guidance (e.g. "run wipefs on the disk first"), instead crashing the WebUI's error boundary Happy to help narrow this down further if useful.