Bug 2088113 - Custom partitioning with 2 drives selected, bootloader fails to install due to one drive not having a BIOS Boot partition
Summary: Custom partitioning with 2 drives selected, bootloader fails to install due t...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F37FinalBlocker, FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2022-05-18 17:59 UTC by Chris Murphy
Modified: 2022-08-09 13:16 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
anaconda.log (52.88 KB, text/plain)
2022-05-18 18:01 UTC, Chris Murphy
no flags Details
program.log (14.64 KB, text/plain)
2022-05-18 18:02 UTC, Chris Murphy
no flags Details
storage.log (816.43 KB, text/plain)
2022-05-18 18:02 UTC, Chris Murphy
no flags Details

Description Chris Murphy 2022-05-18 17:59:54 UTC
Description of problem:

Choosing 2 drives for installation in Custom partitioning. Upon adding a BIOS Boot partition, the right side manual partitioning UI shows 2 devices for this partition. But two BIOS Boots are not created by the installer. Subsequently, the installer issues grub2-install on both drives, but the second command fails because its target drive has no BIOS boot partition


Version-Release number of selected component (if applicable):
anaconda 36.16.5-1.fc36

How reproducible:
Always


Steps to Reproduce:
1. boot a VM with two virtual drives, and use inst.gpt parameter
2. choose both drives in installation destination, use Custom partitioning
3. create a BIOS Boot mount point, and notice on the right side both drives are selected for this by default implying each drive will get a BIOS Boot partition
4. proceed to create a /boot on raid1 with ext4 mount point, and a / on btrfs raid1

Actual results:

Installation fails with a bootloader related error

Expected results:

The installation should succeed

Additional info:


On installation destination page, click the bottom "link" to the bootloader configuration dialog, this dialog refuses to let me choose both drives for the bootloader. So there is an additional set of bugs here : (a) the dialog doesn't let me choose both (b) never the less the installer issues grub2-install on both drives anyway.

Comment 1 Chris Murphy 2022-05-18 18:01:42 UTC
Created attachment 1881028 [details]
anaconda.log

Comment 2 Chris Murphy 2022-05-18 18:02:01 UTC
Created attachment 1881029 [details]
program.log

Comment 3 Chris Murphy 2022-05-18 18:02:13 UTC
Created attachment 1881030 [details]
storage.log

Comment 4 Chris Murphy 2022-05-18 18:27:07 UTC
When I precreate BIOS Boot on the two drives, and then just ignore them (do not delete, do not create new) in manual partioning, the installation succeeds without error. grub2-install is pointed to each drive, and each drive has a BIOS Boot so this works.

/tmp/storage.log:INFO:program:Running in chroot '/mnt/sysroot'... grub2-install --no-floppy /dev/vda
/tmp/storage.log:INFO:program:Running in chroot '/mnt/sysroot'... grub2-install --no-floppy /dev/vdb
/tmp/storage.log:INFO:program:Running in chroot '/mnt/sysroot'... grub2-install --no-floppy /dev/vda
/tmp/storage.log:INFO:program:Running in chroot '/mnt/sysroot'... grub2-install --no-floppy /dev/vdb

Not sure why these commands are being run twice each though.

Comment 5 Peter Boy 2022-05-29 10:10:18 UTC
On a physical system using server 36 DVD you can use the advanced custom GUI to create a biosboot partition on each raid drive (raid1), create the /boot partition and a LVM containing root (both in a raid 1). The installation runs without error messages, but the system is unable to boot (Error: No boot disk has been detected)

Comment 6 Fedora Blocker Bugs Application 2022-06-06 00:16:26 UTC
Proposed as a Blocker for 37-final by Fedora user chrismurphy using the blocker tracking app because:

 There's a few violations:

The installer must allow the user to choose which disk the system bootloader will be installed to, and to choose not to install one at all. 
https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Bootloader_disk_selection

The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration. 
https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Disk_layouts

A system installed without a graphical package set must boot to a state where it is possible to log in through at least one of the default virtual consoles.
https://fedoraproject.org/wiki/Basic_Release_Criteria#Expected_installed_system_boot_behavior


Custom allows me to create bootable raid1 setup with two disks, but (a) doesn't automatically create a 2nd BIOS Boot, (b) will not let me create one, (c) subsequently fails to complete the installation as a result of the first two, and (d) doesn't boot afterward.

Comment 7 Ben Cotton 2022-08-09 13:16:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.


Note You need to log in before you can comment on or make changes to this bug.