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 7sC8ZO0rjT3H for ; Sun, 30 Dec 2012 19:49:49 +0100 (CET) Received: from awesome.dsw2k3.info (unknown [IPv6:2a01:198:661:1f::3]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sun, 30 Dec 2012 19:49:48 +0100 (CET) Date: Sun, 30 Dec 2012 19:49:43 +0100 From: Matthias Schniedermeyer Message-ID: <20121230184943.GA18824@citd.de> References: <20121227095229.GA9356@tansi.org> <20121228150430.GA17491@tansi.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dm-crypt] Avoiding fsck.ext4 destruction of crypto_luks data List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Emily Williams Cc: dm-crypt@saout.de On 30.12.2012 11:59, Emily Williams wrote: > > So I've taken to setting my encrypted partitions to "NetBSD Encrypted" > (a905), so when I look at the partition tables I'm reminded that there > actually isn't a Linux filesystem on the device itself, but rather > something that is encrypted that becomes a Linux filesystem via > /dev/mapper/X after cryptosetup luksOpen happens. I create a dummy partition with type 'da' (Non-FS-Data) on my HDDs. Altough 0 (Empty) sounds nice too. ;-) I say dummy partition because i don't actually use the partition for anything. It's only there to stop my encryption init-script, so that i don't accidentally kill an already initialized HDD (or one of the system-HDDs) in case i fat-fingered the device-name. -- Matthias