Bug 15700 - At diskdrake, please select 2048 as default starting sector for the first partition.
Summary: At diskdrake, please select 2048 as default starting sector for the first par...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-15 09:49 CEST by Alejandro Vargas
Modified: 2015-04-15 10:58 CEST (History)
5 users (show)

See Also:
Source RPM: drakxtools (Diskdrake)
CVE:
Status comment:


Attachments

Description Alejandro Vargas 2015-04-15 09:49:03 CEST
When you create a partition with diskdrake in a clear disk, it offers to start at sector 1 by default. Nowdays, all partitioning programs (fdisk, gdisk, etc.) deafults to 2048 instead of 1 because grub2 needs room for it's modules.

It is specially annoying at the installer because you could be installing the system in a RAID or LVM and grub2 needs extra modules to read it. If you partitions the system starting at sector 1, grub2 installation will fail and you will nedd to start all the instalation from beginning.

Reproducible: 

Steps to Reproduce:
Samuel Verschelde 2015-04-15 10:12:11 CEST

CC: (none) => stormi
Blocks: (none) => 41

Samuel Verschelde 2015-04-15 10:12:47 CEST

Blocks: 41 => (none)

Rémi Verschelde 2015-04-15 10:21:57 CEST

CC: (none) => rverschelde, thierry.vignaud, zen25000

Comment 1 Thierry Vignaud 2015-04-15 10:58:07 CEST
That's what you see in the GUI.
But we already align to MB boundaries:
http://gitweb.mageia.org/software/drakx/commit/perl-install?id=adbddb6198ae7d11bf27de847dfdaf8957507a0e

I just checked, it makes diskdrake creates the first partition at 2Mb...

BTWo One thing that we could do is round the end too as we waste a little bit space at end as next part is aligned too

Status: NEW => RESOLVED
CC: (none) => anssi.hannula
Resolution: (none) => INVALID


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