Bug 12070 - Regression: installer fail to unlock encrypted partition
Summary: Regression: installer fail to unlock encrypted partition
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: release_blocker major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 11704 11979
  Show dependency treegraph
 
Reported: 2013-12-21 20:02 CET by Morgan Leijström
Modified: 2014-02-03 12:02 CET (History)
6 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
/tmp/ddebug.log (11.63 KB, application/octet-stream)
2013-12-22 18:43 CET, Morgan Leijström
Details

Description Morgan Leijström 2013-12-21 20:02:12 CET
The mga4b2 64bit full DVD install iso worked on this machine: during install i selected the existing encrypted partition, clicked "use", entered key, and the LVM showed up.

Right now (some days later) i decided to redo the installation on same machine, again keeping partitions,like last time reformatting everything but /home.

Downloaded and used the boot-nonfree.iso, to redo the installation on same machine: after entering the key i see "cryptsetup failed"

drakx 16.17

Unfortunately command "bug" is not working...
(From Ctrl-Alt-F2 terminal).  Will report.

Another weirdo: keyboard shift is inverted, i need to hold it in order to get the number keys to make numbers!

Reproducible: 

Steps to Reproduce:
Comment 1 Morgan Leijström 2013-12-21 20:20:36 CET
Ah, at this stage the folder /root do not contain a drakx/ folder.
Is there a log elsewhere?

BTW the keymap seem to be AZERTY.  Maybe most developers are french?
Comment 2 Morgan Leijström 2013-12-22 18:43:37 CET
Created attachment 4658 [details]
/tmp/ddebug.log
Morgan Leijström 2013-12-22 18:45:07 CET

CC: (none) => thierry.vignaud

Comment 3 claire robinson 2014-01-25 19:59:09 CET
Confirmed while attempting to upgrade. Installed mga3 with /boot /swap and then and encrypted lvm with /root and /home

Attempting to upgrade from classic dvd 32 2nd build the lvm is not unlocked so upgrade is not offered, it goes directly to installation, asking which partitions to use & format.

The only way to unlock the partition is to then go to custom partitioning and select the lvm. It then doesn't recognise mount points or offer the upgrade though.
claire robinson 2014-01-25 20:00:08 CET

CC: (none) => ennael1, mageia, tmb

claire robinson 2014-01-25 20:01:46 CET

Priority: Normal => release_blocker
Blocks: (none) => 11704

claire robinson 2014-01-25 20:25:45 CET

CC: (none) => davidwhodgins

Comment 4 claire robinson 2014-01-25 20:27:01 CET
Oops didn't CC me :\

CC: (none) => eeeemail

claire robinson 2014-01-27 17:26:34 CET

Blocks: (none) => 11979

Comment 5 Colin Guthrie 2014-01-27 20:01:54 CET
(In reply to claire robinson from comment #3)
> Confirmed while attempting to upgrade. Installed mga3 with /boot /swap and
> then and encrypted lvm with /root and /home
> 
> Attempting to upgrade from classic dvd 32 2nd build the lvm is not unlocked
> so upgrade is not offered, it goes directly to installation, asking which
> partitions to use & format.
> 
> The only way to unlock the partition is to then go to custom partitioning
> and select the lvm. It then doesn't recognise mount points or offer the
> upgrade though.

I don't think this is a regression. Pretty sure this is the only way you can upgrade via this route. Provided you enter all the necessary info, you should be able to upgrade OK (do not format!!), even if it feels like an install up to a point.

As for the original error, I cannot reproduce here. My partitions unlocked OK, and all was well.

It seems Claire didn't actually get the same error as you (cryptsetup failed) and *could* actually continue, so this may be a relatively freak occurrence (disks and partitioning setups are a massive pain the backside to cover in terms of test matrix), but without a reliable reproduction case there isn't much we can do sadly. It worked OK for me with a similar setup when I tried to test.

(In reply to Morgan Leijström from comment #1)
> Ah, at this stage the folder /root do not contain a drakx/ folder.
> Is there a log elsewhere?

The /tmp folder should contain the logs at this stage IIRC.
Comment 6 claire robinson 2014-01-27 21:41:06 CET
I wasn't able to upgrade Colin from the DVD, it recognised there was an lvm but didnt offer to unlock it and went straight into an installation asking which partitions to use.

Using custom partitioning and selecting the lvm did ask to unlock it and could see the partitions but then wanted to format it, so couldn't upgrade.

Dave usually tests this particular setup, it's what he uses on his machine IINM, so I can't say if it is a regression. Sounds like it may be a different bug though.
Comment 7 Morgan Leijström 2014-01-28 11:07:29 CET
@ Claire: so there was no way to continue without formatting?

1) if there is not currently a way to skip that formatting, it should be improved.

2) IMHO there should be a note visible somewhere for half-newbies, like:
if you already have mageia and want to do an upgdare, do not format /
format / to do a fresh system install
if you want to keep user files, do not format /home.


Yes thanks Colin, Thierry told me about /tmp in another bug, forgot to update here.  Someone may be interested in deatils, then read
https://wiki.mageia.org/en/Drakx-installer_tips_and_tricks#Log_files.

System tested when I encopuntered the bug is for production, will test again later after making backups.

New: Yesterday when trying to install fresh i noticed that current installer forgets given mount points in a LVM, (even when not using encryption anywhere).  When i have time will try to reproduce on a a simpler setup and post another bug then.
Comment 8 Morgan Leijström 2014-01-28 18:13:37 CET
related: https://bugs.mageia.org/show_bug.cgi?id=12151#c21
Comment 9 Morgan Leijström 2014-02-03 12:02:22 CET
4 final network install works:

At custom partitioning i assign the existing old /boot partition the mopunt point /boot, click the encrypted partition, click unlock button, give the old keyphrase, and a few seconds later the tab with the LVM shows up, with the same old partitions. Recognising them by they stil have the name vg-mga/boot etc, i assign them mount points /boot and /home, let the swap be autorecognised.
In next step i let it format /boot and /, but not /home.

Success: new system, same partitions and key, kept user files.

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


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