CrunchBang Linux

TdC

Member

From: Dutchy-Scotia

Registered: 2010-08-05

Posts: 12

Website

Statler a2: anything in the guided LVM partition setup will not boot

Hi guys,

several tries with my recently downloaded Statler A2 iso for AMD64 to use the guided setups for LVM / encrypted filesystems + LVM results in the boot process stopping just after grub with a "Loading..."

I tried both vanilla LVM and encryption+LVM guided setups, and neither worked. The vanilla slices thing with ext3 works just fine.

Currently I am thinking that either the grub boot/root statements may contain errors when the installation completes, or the kernel needs (assumption) aes to not be a module or something like that.

Anyone else had this? It's on a Sony Vaio Z21 laptop with a Kingston 128GB SSD drive fully given over to CrunchBang.

---

recent #! convert
Sony Vaio Z21 - Statler A2

Panzer

Member

Registered: 2010-02-06

Posts: 49

Re: Statler a2: anything in the guided LVM partition setup will not boot

I will also like to have a guide that explains step by step how to install LVM / encrypted filesystems. I will install #! in a laptop and I want it to be encrypted.

TdC

Member

From: Dutchy-Scotia

Registered: 2010-08-05

Posts: 12

Website

Re: Statler a2: anything in the guided LVM partition setup will not boot

Hi there

I've been trying again with both the guided and manual installs. On it's own, it won't boot for me as I explained in my first post. Tonight I tried a little harder, and I am semi certain that it is the initrd.img that doesn't contain the correct scripts in relation to LVM and/or luks when you choose to use those options.

Or at least, it messes up at boot time. When I tried it by hand, it wasn't pleased with what I tried with grub, but I could get it up into the initrd by entering the linux <path to linux kernel>, initrd <path to initrd.img> items and then boot command.

From this, the automation in the initrd will break eventually and drop me into a shell. From the shell, I can open the encrypted volume, issue a vgchange -ay, mount stuff, bind mount /dev /proc and /sys and finally chroot into the operating environment, but as you can guess it's not pleased. I'm not really clued into where I am in the boot sequence, but anything like init 3 or so fails.

So, therefor I conclude that stuff does work, but the automation is deeply unhappy when you use the more exotic options from the installer.

People's thoughts are very much appreciated

---

recent #! convert
Sony Vaio Z21 - Statler A2