Bug 448

Summary:	Rescue mod cannot find partitions if they are located on an encrypted lvm
Product:	Mageia	Reporter:	Rémy CLOUARD (shikamaru) <shikamaru>
Component:	Installer	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	Normal	CC:	marja11, pterjan, thierry.vignaud, tmb
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	drakx-installer-rescue	CVE:
Status comment:

Description Rémy CLOUARD (shikamaru) 2011-03-19 13:17:20 CET

Description of problem:
When entering in rescue mode and choosing "mount your partitions under /mnt" you cannot if you have your root partition on an encrypted lvm.

Expected behaviour would be to be prompted for a password to open the Luks and run vgscan/vgchange

Version-Release number of selected component (if applicable):
alpha2

How reproducible:
always

Steps to Reproduce:
1. Install with root on lvm on luks
2. reboot in rescue mode
3. try to mount your partitions under /mnt

Workaround (I call it easy because thatâs not the default partitioning scheme, if you choose this one you are expected to know how to unlock a luks volume and detect lvm volumes) :
1. go to console
2. modprobe the following modules
  - dm-mod
  - dm-crypt
  - aes-generic
  - sha256-generic
  - cbc
3. open the encrypted volume with cryptsetup luksOpen <device> <name>
4. run lvm2 vgscan
5. run lvm2 vgchange -ay
6. mount your partitions yourself

Reproducible: 

Steps to Reproduce:

Ahmad Samir 2011-03-19 17:48:04 CET

CC: (none) => pterjan

Ahmad Samir 2011-03-19 17:48:13 CET

CC: (none) => tmb

Thierry Vignaud 2011-08-05 21:28:58 CEST

CC: (none) => thierry.vignaud
Source RPM: (none) => drakx-installer-rescue

Comment 1 Thierry Vignaud 2011-08-08 10:59:48 CEST

Can you provide a tested patch?

The rescue is provided as a squashfs image in install/stage2/rescue.sqfs
on mirrors.

You can just uncompress it with unsquashfs in some temp directory (as root in order to be able to create fifos and the like in squashfs-root/dev/).

The file ./usr/bin/rescue-gui is the GUI
It cames from drakx-installer-binaries

Comment 2 Marja Van Waes 2011-10-10 06:55:46 CEST

(In reply to comment #1)
> Can you provide a tested patch?

@ Rémy
@ Thierry

Did this bug get solved?

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 3 Thierry Vignaud 2011-10-10 10:09:25 CEST

If it would this BR would have been closed...

Comment 4 Marja Van Waes 2011-10-10 12:18:01 CEST

(In reply to comment #3)
> If it would this BR would have been closed...

Sorry if I irritated you!

Some other bugs did get closed, however, because we asked this question, so it doesn't feel good to stop asking

Comment 5 Thomas Backlund 2011-10-10 12:20:03 CEST

(In reply to comment #4)
> (In reply to comment #3)
> > If it would this BR would have been closed...
> 
> Sorry if I irritated you!
> 
> Some other bugs did get closed, however, because we asked this question, so it
> doesn't feel good to stop asking


It's ok to "ping" bugs so they dont get forgotten.

Keep up the good work :)

Comment 6 Thierry Vignaud 2011-10-10 13:19:55 CEST

I'm not irritated :-) I was just stating a fact

Comment 7 Marja Van Waes 2011-10-10 22:18:33 CEST

@ Thierry

Sorry for misinterpreting, but I still don't know how to interpret your statement.
Does it mean that you're not capable of forgetting a bug once it had been assigned to you? (If so: lucky you! :) )

Keywords: NEEDINFO => (none)
Assignee: bugsquad => thierry.vignaud

Comment 8 Thierry Vignaud 2011-10-11 08:01:16 CEST

That's the purpose of saves searches (https://bugs.mageia.org/userprefs.cgi?tab=saved-searches).
The goal is to reduce them. So I always close a bug when I commits its fix.

Comment 9 Marja Van Waes 2011-10-11 08:40:01 CEST

@ Thierry
Great :D

Bug 1025 learns me, you reassign a bug when it is wrongly assigned to you, if I ping you. So from now on I'll just ping or ask for news when nothing happened > 2mnths

Comment 10 Manuel Hiebel 2011-12-08 22:21:53 CET

Shikamaru, any news ?
(as your mail works now :p )

Comment 11 Thierry Vignaud 2012-01-25 17:17:06 CET

Fixed in my git-svn treee

Status: NEW => RESOLVED
Resolution: (none) => FIXED