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 TGdNMCOFfXwL for ; Fri, 28 Dec 2012 00:19:56 +0100 (CET) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Fri, 28 Dec 2012 00:19:56 +0100 (CET) Received: by mail-ee0-f54.google.com with SMTP id c13so4842700eek.27 for ; Thu, 27 Dec 2012 15:19:55 -0800 (PST) Sender: "Richard Z." Date: Thu, 27 Dec 2012 21:29:35 +0100 From: Richard Message-ID: <20121227202935.GA7991@rz> References: 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 Thu, Dec 27, 2012 at 01:12:09AM -0500, Emily Williams wrote: > Today I made a rather large mistake, running fsck.ext4 on the raw volume > (/dev/sdk1) instead of the mapped volume > (/dev/mapper/whatever-i-choose-to-call-it). I assume it is not possible to > recover from this once it is done and the cryptosetup lukeOpen passphrase > no longer works. something strange going on fsck.ext4 will never do a destructive action without asking. Don't reboot, don't panic perhaps something can be saved. No idea what really happened though. Richard --- Name and OpenPGP keys available from pgp key servers