Statler won't boot after installation when using lvm

[Johan Vervloet]

If you use lvm volumes for your partitions, crunchbang Statler won't boot after installation, because the package lvm2 is not installed.

You can work around the problem by after installation booting from the live cd

sudo bash
apt-get update
apt-get install lvm2
modprobe dm-mod
mount /dev/lvmvolume/root /mnt # replace by correct lvm volume
mount /dev/sdax /mnt/boot # when using lvm, boot is always a separate partition
# if you have partitions for usr, var,..., mount them as well under /mnt
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
chroot /mnt
apt-get update
apt-get install lvm2
exit
umount /mnt/proc
umount /mnt/dev
# umount partitions you mounted above
umount /mnt/boot
umount /mnt
reboot

[corenominal (corenominal)]

Thank you for reporting this and for providing the fix. I will add the required package to the build list. Hopefully the next release should be fixed. :)

[Tim Jones (tim+jones)]

I am having this same issue, with install image Chrunchbang 10 "Statler" r20110207

Only when I chroot into my mounted lvm system, I cannot run 'apt-get update' as the DNS won't resolve. To fix this, I can temporarily edit /etc/network/interfaces and add the setup I need there.
Unfortunately, even after that, when I run 'apt-get install lvm2' it tells me that it already has the newest version. So either the base system now has lvm2 and mine isn't working for other reasons, or for some other reason after I 'chroot /mnt' apt is still reading the packages from the Live system.

Any thoughts?

[Tim Jones (tim+jones)]

Apologies, it seems as the problem was with the RAID config rather than LVM.