From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K05mZKiSfDJa for ; Wed, 26 Sep 2012 04:12:25 +0200 (CEST) Received: from mail-oa0-f50.google.com (mail-oa0-f50.google.com [209.85.219.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Wed, 26 Sep 2012 04:12:24 +0200 (CEST) Received: by oagn16 with SMTP id n16so126673oag.37 for ; Tue, 25 Sep 2012 19:12:23 -0700 (PDT) Sender: Matthew Monaco Message-ID: <50626485.5000109@0x01b.net> Date: Tue, 25 Sep 2012 20:12:21 -0600 From: Matthew Monaco MIME-Version: 1.0 References: <504AED40.2010102@gmail.com> <5053D531.1000508@0x01b.net> <20120921100101.GA11357@tansi.org> <50614FBC.80709@0x01b.net> <506200BD.6010803@0x01b.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Encrypt all partitions with dm-crypt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 09/25/2012 05:54 PM, Stayvoid wrote: >> What distribution are you using? That sounds odd because I'd think your >> recovery >> shell is the same environment as your initrd which most certainly has >> cryptsetup. > > Parabola GNU/Linux-libre [1]. > >> If cryptsetup isn't working, try >> >> # modprobe dm-crypt > > FATAL: Module dm-crypt not found > > [1] http://mtjm.eu/releases/parabola/parabola-mips64el-20120912.tar.bz2 Ah, this is definitely an Arch Linux derivative. You need to add "encrypt" to the HOOKS setting in /etc/mkinitcpio.conf and run (as root) # mkinitcpio -p linux-libre This will add cryptsetup and the necessary modules to your initramfs. You also MUST add root=/dev/mapper/ROOT cryptdevice=/dev/sdX#:ROOT to your kernel command line (/boot/grub/menu.lst for grub-legacy, /boot/grub/grub.cfg for grub2). Where ROOT is whatever label you want and /dev/sdX# is your encrypted block device. Furthermore, you need to set crypto= to your specific settings, but I don't remember the format off the top of my head. Are you *sure* you don't want to use LUKS? It will make your life a lot easier (no crypt= kernel command line option, no need to specify ciphers and hashes when mounting manually, etc...)