Bug 4229

Summary:	LUKS+LVM install ok, kernel panic at boot
Product:	Mageia	Reporter:	Tamás Hajdu <fathom>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	davidwhodgins, mageia, pterjan, thierry.vignaud
Version:	1
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Tamás Hajdu 2012-01-22 11:53:23 CET

Description of problem:
I wanted to install mageia with the following disk setup: 
-4GiB to swap
-250MiB to /boot with ext4 fs
-LVM physical with encryption (rest of my hd)
--12 GiB to / with ext4 fs
--rest to /home with ext4 fs

Installation seems ok. Tried from dual-arch iso with and without additional network sources to use. 
On boot, after password given successfully to LUKS, kernel panics.

Here is the last few lines:
Making device-mapper control mode
waiting for device sda6 to appear (timeout 1 min)
waiting for device sda6 to appear (timeout 1 min)
waiting for device sda1 to appear (timeout 1 min)
Setting up disk encryption: /dev/sda6
waiting for encrypted device sda6 to appear (timeout 1 min)
no resume binary
Creating root device
Mounting root filesystem
mount: could not find filesystem '/dev/root'
Kernel panic - not syncing: Attemted to kill init!
Pid: 1, comm: init Not tainted 2.6.38.7-desktop-1.mga #1
Call Trace:
 [<ffffffff813ec160>] ? panic+0x91/0x19c
 [<ffffffff8105c053>] ? do_exit+0x7d3/0x890
 [<ffffffff81166bff>] ? mntput+0x1f/0x30
 [<ffffffff8105c3c8>] ? do_group_exit+0x58/0xd0
 [<ffffffff8105c457>] ? sys_exit_group+0x17/0x20
 [<ffffffff81002e92>] ? system_call_fastpath+0x16/0x1b
panic occured, switching back to text console

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

How reproducible:
always

Steps to Reproduce:
1. Get the installer
2. Make the partitions as above
3. Watch a delightful kernel panic at boot

Comment 1 Dave Hodgins 2012-01-28 05:07:33 CET

As a workaround, try creating the lvm physical volume without
encryption, and then encrypting the filesystems within the
logical volumes.  I haven't tried using an encrypted /, but
have done this with /home.

CC: (none) => davidwhodgins

Comment 2 Tamás Hajdu 2012-02-16 12:41:38 CET

Yesterday I have installed couldron successfully, with encrypted lvm volume:) I will check your suggestion (whether it works), but it has not much to do with that installer error.

Thierry Vignaud 2012-04-18 16:49:34 CEST

CC: (none) => pterjan

Thierry Vignaud 2012-04-18 16:49:43 CEST

CC: (none) => mageia, thierry.vignaud

Comment 3 Pascal Terjan 2012-04-18 17:04:47 CEST

I think this bug was with mkinitrd while cauldron uses dracut by default now.
I guess there is no point in working on fixing mkinitrd now.

Comment 4 Colin Guthrie 2012-04-18 17:09:46 CEST

Well Thomas wanted to keep mkinitrd, but as it can never be used by installer, it's probably not relevant to this bug/problem.

Seeing as TamÃ¡s setup now works (although bug #5330 will still be a problem if he tries to reinstall over the top of the existing partition), I think we can now close this bug.

I've done a fair few tests of late with this kind of encrypted LVM setup so I'm fairly sure it's all quite robust now (apart from the bug mentioned above :D)

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