From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dgbaley27@0x01b.net>
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 LQMT018HAYqR for <dm-crypt@saout.de>;
 Wed, 26 Sep 2012 13:13:36 +0200 (CEST)
Received: from mail-ob0-f178.google.com (mail-ob0-f178.google.com
 [209.85.214.178])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Wed, 26 Sep 2012 13:13:36 +0200 (CEST)
Received: by obbtb18 with SMTP id tb18so410276obb.37
 for <dm-crypt@saout.de>; Wed, 26 Sep 2012 04:13:35 -0700 (PDT)
Sender: Matthew Monaco <matt@0x01b.net>
Message-ID: <5062E35B.5070102@0x01b.net>
Date: Wed, 26 Sep 2012 05:13:31 -0600
From: Matthew Monaco <dgbaley27@0x01b.net>
MIME-Version: 1.0
References: <CAK5fS_EtiBTgj7inr875UJ2N2s-1qY8qA4hHRxE5+0VhFXgaUA@mail.gmail.com>
 <CAK5fS_HqO8vHrikfbAwvxY0ZvpwXQDVJwoF3-M0eWzXEwQkxJw@mail.gmail.com>
 <CAD98N_F3D59d9R4+mc3nypgHxbL-yz=jr2anAFRpkvyf_hpGMg@mail.gmail.com>
 <CAK5fS_G=tnaCHQiYafAE1SJOE0MAaeBSVKUZTY-iNC8noMNDjg@mail.gmail.com>
 <20120921100101.GA11357@tansi.org>
 <CAK5fS_Fc54S_1TwkXzbFaZC8fVfo5s6m3BEUj3Au=y-Ev98NQA@mail.gmail.com>
 <CAK5fS_GOEwQOkZAiTFqvmM9ZC3MOSrck4z-Ld+f1Bkh-j7L3iQ@mail.gmail.com>
 <CAK5fS_FmO91CX+b6E_OWemNf=_miohiFyD_HD80mZ=Xgw75=cw@mail.gmail.com>
 <50614FBC.80709@0x01b.net>
 <CAK5fS_FO7eBRX0Gk15Ekmv2zSZao1Pchq_8vpLEnp4ENxCXNtA@mail.gmail.com>
 <CAK5fS_Ebv=1-D7wz2_T5EU1HxAf+SPz8KWH8K3ZKQ26Ek+6XqA@mail.gmail.com>
 <506200BD.6010803@0x01b.net>
 <CAK5fS_Gow2pnR0Wm00wrws+9SdvYZFP+9UU1-Y+5LSRmwZsgLQ@mail.gmail.com>
 <50626485.5000109@0x01b.net>
 <CAK5fS_H4ZEuKhN1HMyyH+1J0t_oMh1=pEGoVENBizR5kYVbx7Q@mail.gmail.com>
 <5062C9BB.5010900@0x01b.net>
 <CAK5fS_H7V_SBgXwasLuYhB=tWsrfc5mTs=z_NL=_K3NKe3iavQ@mail.gmail.com>
In-Reply-To: <CAK5fS_H7V_SBgXwasLuYhB=tWsrfc5mTs=z_NL=_K3NKe3iavQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Encrypt all partitions with dm-crypt
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 09/26/2012 04:49 AM, Stayvoid wrote:
>> You can mount to wherever you like. Once you've mapped the block
>> device to /dev/mapper/NAME, you have a block device like any other.
> 
> Will the following work from a recovery shell?
> 
> # mkdir media
> # mount /dev/mapper/main /media
> # mount -t proc none /media/proc
> # mount --rbind /dev /media/dev
> # mount --rbind /sys /media/sys
> # mount /dev/sda1 /boot
> 
> There is no /bin/bash. Can I use ash?
> 
> # chroot /media /bin/ash

Has it occurred to you to just try these things? We're getting a bit off topic
here...

That will work, assuming you mapped something to /dev/mapper/main with
cryptsetup already. Also, I think you meant /media/boot. Also, /mnt should be
available, no reason to insist on media.

ash is fine, it's what is provided by busybox in the initramfs.

I usually do:

# mount /dev/mapper/main /mnt
# mount /dev/sda1 /mnt/boot
# for m in dev proc sys; do mount --bind /$m /mnt/$m; done
# chroot /mnt