Bug 18284

Summary: Mga6dev1 installer forget mountpoint of LVM LV after unlocking encrypted part for *another* LVM
Product: Mageia Reporter: Morgan Leijström <fri>
Component: RPM PackagesAssignee: Pascal Terjan <pterjan>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Normal CC: marja11, thierry.vignaud
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: drakxtools CVE:
Status comment:
Attachments: report.bug (tar.gz compressed) generated at end of complete install

Description Morgan Leijström 2016-04-28 12:05:42 CEST 
Scenario: fresh install (not upgrade) of mga6dev1 over existing mga5 partitions.
(not altering any partitioning, and keeping content in home)
I select custom partitioning

It correctly displays the three physical partitions on disk
§ ext4
§ encrypted partition for the LVM named "bamse"
§ PV for plain LVM named "okrLVM"

My actions:

1) I select the tab okrLVM, and set mount point for the existing / partition.
there are also already a swap partition and another ext4 partition i do not select for now.

2) I choose the physical ext4 partition as /boot

3) I select the encrypted partition, and unlocks it
It take loong time, more than a minute before sometning happens so i go for lunch... when i am back the tab "bamse" for the encrypted LVM have shown up, i select it and set mount point for /home

4) I go back to review "okrLVM" LVM and see the / mount is forgotten !
I set it again and proceed, everything then finishes OK :)

BTW:
In next installer step, the formatting of select partitions, / is preselected and /home not, OK so far.
But why did it not preselect /boot for formatting?
Maybe there is a reason i do not understand, but i guess not formatting it may cause havoc?
Comment 1 Morgan Leijström 2016-04-28 12:09:38 CEST 
Created attachment 7700 [details]
report.bug (tar.gz compressed) generated at end of complete install
Marja Van Waes 2016-04-28 19:50:34 CEST

CC: (none) => marja11, thierry.vignaud
Assignee: bugsquad => pterjan

Comment 2 sturmvogel 2022-08-13 19:12:12 CEST 
Morgan, this bug was filed against mga6dev1.

Mageia 6 was supported until September 30th, 2019.

Can we close this one OLD?
Comment 3 Morgan Leijström 2022-08-21 12:31:53 CEST 
I believe no work have been done to resolve it.
I have during the years filed numerous bugs abut quirks on diskdrake.
I think we should leave then open and test when there is a real changes being made.
Maybe until then the bugs collect evidence enough to find the culprit :)