Bug 32000 - CI/diskdrake minimum selectable size for BIOS boot / empty partition.
Summary: CI/diskdrake minimum selectable size for BIOS boot / empty partition.
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: Mageia 10
Assignee: Mageia tools maintainers
QA Contact:
Depends on:
Reported: 2023-06-09 21:57 CEST by Antony Baker
Modified: 2023-06-21 08:40 CEST (History)
1 user (show)

See Also:
Source RPM: drakxtools
Status comment:

Attachment showing 14MB created partition (even though 7MB selected). (91.88 KB, image/png)
2023-06-09 21:57 CEST, Antony Baker

Description Antony Baker 2023-06-09 21:57:03 CEST
Created attachment 13868 [details]
Attachment showing 14MB created partition (even though 7MB selected).

While using an Mga9 (Beta2) CI within a VM to generate updated screenshots for the Mga9 installer manuals, I ran into an issue creating a BIOS boot / empty partition in the installer Partitioning stage.

The relevant text in the Mga8 CI manual for this reads:
"If you are using a Legacy (also known as BIOS) system with a GPT partitioned
disk, you need to create a BIOS boot partition if it doesn't already exist.
It should be about 1 MiB with no mount point."

However, in Mga9 (Beta2) CI, the minimum selectable partition size is 7MB. Furthermore, if 7MB is selected as the size - the resulting created partition is 14MB (verified several times).

Ultimately, this inconsistency between the intaller text suggesting a size of around 1MB - and the minimum selectable of 7MB (plus also the fact that the actual created size is not 7MB, but 14MB) will be quite confusing for people.

If the Mga8 CI was able to create a minimum partition size of 1MB, and gparted currently is able also to do, then (as suggested by Dave Hodgins) this seems likely due to a change made to diskdrake.

QA ML thread:

Comment 1 Morgan Leijström 2023-06-09 22:13:57 CEST
Congratulations to the first bug report!
Thank you.
Welcome aboard :)

Assignee: bugsquad => mageiatools
CC: (none) => fri
Keywords: (none) => FOR_ERRATA9

Comment 2 Antony Baker 2023-06-10 12:28:25 CEST
Thank you Morgan.
Comment 3 Morgan Leijström 2023-06-21 08:40:49 CEST
Reconsidering: Not bad enough for errata

And setting to mga10 as we do not want to fiddle with our tools more than really needed this close to release.

Source RPM: (none) => drakxtools
Keywords: FOR_ERRATA9 => (none)
Target Milestone: --- => Mageia 10

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