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:
CC: (none) => pterjan
CC: (none) => tmb
CC: (none) => thierry.vignaudSource RPM: (none) => drakx-installer-rescue
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
(In reply to comment #1) > Can you provide a tested patch? @ Rémy @ Thierry Did this bug get solved?
Keywords: (none) => NEEDINFOCC: (none) => marja11
If it would this BR would have been closed...
(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
(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 :)
I'm not irritated :-) I was just stating a fact
@ 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
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.
@ 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
Shikamaru, any news ? (as your mail works now :p )
Fixed in my git-svn treee
Status: NEW => RESOLVEDResolution: (none) => FIXED