FS#11953 - LiveCD doesn't boot (itself) on arch with an encrypted root.
Attached to Project:
Release Engineering
Opened by Winston Smith (1984) - Friday, 31 October 2008, 16:11 GMT
Last edited by Gerhard Brauer (GerBra) - Saturday, 01 August 2009, 15:46 GMT
Opened by Winston Smith (1984) - Friday, 31 October 2008, 16:11 GMT
Last edited by Gerhard Brauer (GerBra) - Saturday, 01 August 2009, 15:46 GMT
|
Details
Steps to reproduce:
1. Install Arch with an encrypted root partition like described here: http://wiki.archlinux.org/index.php/System_Encryption_with_LUKS_for_dm-crypt 2. Shut down your machine 3. Try to boot from the LiveCD (and boot the LiveCD from there, not the installed system) <= it gets a kernel panic and is useless here |
This task depends upon
Closed by Gerhard Brauer (GerBra)
Saturday, 01 August 2009, 15:46 GMT
Reason for closing: Works for me
Saturday, 01 August 2009, 15:46 GMT
Reason for closing: Works for me
::: Adding new union branch: /bootmnt/addons/default-config.sqf
loop: module loaded
ERROR: Cannot mount loop device /dev/loop0
Couldn't mount all addons
Waiting for devices to settle...done.
Root device `` doesn't exist, attempting to create it
ERROR: Failed to parse block device name for ``
ERROR: Unable to create/detect your root device ``
Dropping to a recovery shell...type 'exit' to reboot
[...]
thats it :) Would be nice if someone could fix it.
so we probably should make it load the necessary modules in initramfs but what would the order be? eg we can't know if the user has lvm on top of dm_crypt or the other way around for example. (but then again i'm not 100% familiar with the early userspace stuff)
I don't think our iso's should actually do the "making available of dm_crypt /lvm volumes" during boot up, but they should be capable of booting up normally, after which the user can unlock his encrypted volumes and bring up his lvm volumes.
I will assign this to 2009.08-rc because we have to think about this.
If Winston have currently any problems he could make a reopen request...