From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nlpi129.prodigy.net (nlpi129.sbcis.sbc.com [207.115.36.143]) by mail.saout.de (Postfix) with ESMTP for ; Sun, 21 Feb 2010 18:10:55 +0100 (CET) Message-ID: <4B81691C.9020500@gmail.com> Date: Sun, 21 Feb 2010 09:10:52 -0800 From: Bryan Kadzban MIME-Version: 1.0 References: <6294c32a1002171625m77251de0pd665b2cf0c4983ac@mail.gmail.com> <20100220085539.GA4809@resivo.wgnet.de> <6294c32a1002202042i7640ebbrd9899c5bfb33b49c@mail.gmail.com> In-Reply-To: <6294c32a1002202042i7640ebbrd9899c5bfb33b49c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] configuration files List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Selim Levy Cc: dm-crypt@saout.de Selim Levy wrote: > The contents of the rescue's /etc/crypttab, for which I've tried various > things is: > # cat crypttab > sdb3_crypt /dev/sdb3 none luks So, from 1000 miles away... Doesn't Debian's initramfs bring up udev and let you use the /dev/disk/by-*/ symlinks in crypttab? That's a *LOT* better way to find this drive (in your case, by-id might work, and by-uuid will almost definitely work, assuming a new-enough udev that can find the UUID of a LUKS volume). Maybe poke around in /dev/disk when you're at the busybox prompt, and see what you can find. (If it doesn't bring up udev and let you use those symlinks, then ... why not? :-P Not a question for you obviously, but more for the Debian maintainers.) Anyway, then you don't care which sd* name is given to this device, since you're using an explicitly-guaranteed-stable name for it.