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
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
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.
CC: (none) => pterjan
CC: (none) => mageia, thierry.vignaud
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.
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 => RESOLVEDResolution: (none) => FIXED