Bug 2359710 - bootloader setup to a second MBR drive crashes
Summary: bootloader setup to a second MBR drive crashes
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda-webui
Version: 43
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Katerina Koukiou
QA Contact:
URL:
Whiteboard: https://discussion.fedoraproject.org/...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-15 10:10 UTC by Kamil Páral
Modified: 2025-08-29 07:09 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda.log (8.04 KB, text/plain)
2025-04-15 10:11 UTC, Kamil Páral
no flags Details
dbus.log (3.91 KB, text/plain)
2025-04-15 10:11 UTC, Kamil Páral
no flags Details
packaging.log (18.56 KB, text/plain)
2025-04-15 10:11 UTC, Kamil Páral
no flags Details
program.log (1.68 KB, text/plain)
2025-04-15 10:11 UTC, Kamil Páral
no flags Details
storage.log (168.80 KB, text/plain)
2025-04-15 10:11 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2025-04-15 10:10:45 UTC
Description of problem:
If I try to install F42 Workstation to a second drive that has MBR, bootloader setup crashes.


Version-Release number of selected component (if applicable):
anaconda-42.27.12-1.fc42.x86_64
anaconda-webui-33-1.fc42.noarch
cockpit-storaged-336.2-1.fc42.noarch


How reproducible:
tried once so far, but I expect always

Steps to Reproduce:
1. prepare two empty disks with a MBR part table created
2. in anaconda select both disks for installation
3. in storage editor, add /boot (ext4) and / (ext4) to the second drive. Keep the first drive untouched.
4. start the installation, it crashes during bootloader setup

Comment 1 Kamil Páral 2025-04-15 10:11:08 UTC
Created attachment 2085032 [details]
anaconda.log

Comment 2 Kamil Páral 2025-04-15 10:11:11 UTC
Created attachment 2085033 [details]
dbus.log

Comment 3 Kamil Páral 2025-04-15 10:11:14 UTC
Created attachment 2085034 [details]
packaging.log

Comment 4 Kamil Páral 2025-04-15 10:11:17 UTC
Created attachment 2085035 [details]
program.log

Comment 5 Kamil Páral 2025-04-15 10:11:20 UTC
Created attachment 2085036 [details]
storage.log

Comment 6 Kamil Páral 2025-04-15 10:53:40 UTC
Common Issue description:
https://discussion.fedoraproject.org/t/common-issue/148708

Comment 7 Adam Williamson 2025-08-25 17:17:52 UTC
I can reproduce this with the 20250824 F43 Workstation live, following kparal's reproducer exactly.

Obviously the reproducer is a bit artificial - in that case, you could just *not* select the first disk - but I think it's meant to be a simplified reproducer of a 'real world' case where you do want to put *some* partitions on the first disk, but you want /boot and / (or maybe just /boot ?) on the second disk.

Comment 8 Lukas Ruzicka 2025-08-25 19:21:15 UTC
Discussed at the 2025-08-25 Blocker review meeting:

We kicked this around a bit and reproduced it, but decided to punt the blocker discussion to a week where the reporter (kparal) is present to provide more info and background.

[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-08-25/f43-blocker-review.2025-08-25-16.00.log.html

Comment 9 Kamil Páral 2025-08-28 12:44:28 UTC
(In reply to Adam Williamson from comment #7)
> Obviously the reproducer is a bit artificial - in that case, you could just
> *not* select the first disk - but I think it's meant to be a simplified
> reproducer of a 'real world' case where you do want to put *some* partitions
> on the first disk, but you want /boot and / (or maybe just /boot ?) on the
> second disk.

You expect me to know in advance what I want to do? :-) No, I just select both disks, and then decide to utilize just the second one. No hidden motive.

However, as explained in the blocker review ticket [1], I don't think this blocks anymore.

[1] https://pagure.io/fedora-qa/blocker-review/issue/1856

Comment 10 Adam Williamson 2025-08-28 15:14:06 UTC
Well, as you nominated it as a blocker, you can just un-nominate it if you so desire - just clear the Blocks: field.


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