Bug 22795

Summary:	The rescue system could detect and tell if user need to unlock LUKS and/or LVM
Product:	Mageia	Reporter:	Morgan Leijström <fri>
Component:	Installer	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	Low	CC:	marja11, pterjan, thierry.vignaud
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	MGA7TOO
Source RPM:	drakx-installer-rescue	CVE:
Status comment:
Attachments:	Photo of screen after i answered y anyway and grub.sh failed

Description Morgan Leijström 2018-03-17 18:31:14 CET

Description of problem:
The rescue system fails when system use LUKS (at least when on LVM inside it)


Version-Release number of selected component (if applicable):
Mga6 iso tested, setting version=6 as we intend to ship 6.1.


How reproducible: seem to be LUKS is the culprit?
- should be made to ask for password if needed.


___Steps to Reproduce:

1. Have a Mageia system installed as follows, using installer to partition:  a separate ext4 /boot, then a large partition LVM, encrypted; and in that /, /home, swap 

Pretend grub got busted and you want to repair it:

2. Launch Rescue mode, i mean in this menu
http://doc.mageia.org/installer/6/en/content/installer.html#d4e219

3. It do not find the correct place to put grub. I tried anyways and it failed of course. (at least it did not wreck anything :) )

I will attach screenshots.
I did not understand how to save a log from rescue mode.


Should also be tested by developer:
Try rescue on a UEFI system set up like described above, formatted drive also have a EFI partition, and a windows partition.  It seemed even more confused.  If it matters that was a nVME SSD drive, GPT formatted.



Related: Bug 22794 - Installer fail to offer upgrade when partitioning use encryption (at least encrypted LVM)

Morgan Leijström 2018-03-17 18:33:12 CET

Whiteboard: (none) => (MGA6) MGA6.1TOO
Assignee: bugsquad => mageiatools
CC: (none) => marja11, pterjan

Comment 1 Morgan Leijström 2018-03-17 19:32:38 CET

Created attachment 10052 [details]
Photo of screen after i answered y anyway and grub.sh failed

Comment 2 Lewis Smith 2019-09-23 20:53:17 CEST

See also bug 25466, which might possibly be a duplicate of this one; but I cannot judge. The Description here is rather confused.

Comment 3 Morgan Leijström 2019-09-24 12:37:53 CEST

Yes sorry.
When writiting this bug i did not realise we need to use shell to unlock LUKS partitions, and use LVM tools (without symlinks like vgscan) before it can try to repair.

Changing this to an enhancement request:

The rescue system could detect and tell if user need to unlock LUKS and/or LVM
(and possibly assist)

Priority: Normal => Low
Severity: normal => enhancement
Whiteboard: (MGA6) MGA6.1TOO => MGA7TOO
Summary: The rescue system fails when system use LUKS (at least when on LVM inside it) => The rescue system could detect and tell if user need to unlock LUKS and/or LVM

Comment 4 Thierry Vignaud 2020-03-20 16:07:48 CET

Fixed in git

Resolution: (none) => FIXED
Status: NEW => RESOLVED
CC: (none) => thierry.vignaud

Comment 5 Thierry Vignaud 2020-03-20 16:16:58 CET

*** Bug 22786 has been marked as a duplicate of this bug. ***