From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <arno@wagner.name>
Received: from v1.tansi.org (mail.tansi.org [84.19.178.47])
 by mail.server123.net (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Tue,  2 May 2017 22:49:45 +0200 (CEST)
Received: from gatewagner.dyndns.org (77-56-144-126.dclient.hispeed.ch
 [77.56.144.126]) by v1.tansi.org (Postfix) with ESMTPA id 973EA140154
 for <dm-crypt@saout.de>; Tue,  2 May 2017 22:49:38 +0200 (CEST)
Date: Tue, 2 May 2017 22:49:44 +0200
From: Arno Wagner <arno@wagner.name>
Message-ID: <20170502204944.GA30230@tansi.org>
References: <CABE8nt-Z5=FV8RYc6_2t9ykpDEKDmTXaQYxxYm8Jp-SojJfCSg@mail.gmail.com>
 <CABE8nt_GtdBNHCfM=Nqczte5vVcNggLfcHbH25Z5S9J+D_Kz8Q@mail.gmail.com>
 <CABE8nt_paj=7iTDoa2M0A23oY4EuGrDO5oYhCKtF2D_2D89Z1Q@mail.gmail.com>
 <20170501184515.GR12539@yeono.kjorling.se>
 <20170501210139.GA19666@tansi.org>
 <5f9b9896-bf23-3769-9589-dcda43e1efd9@xoxy.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <5f9b9896-bf23-3769-9589-dcda43e1efd9@xoxy.net>
Subject: Re: [dm-crypt] (no subject)
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 Tue, May 02, 2017 at 02:29:06 CEST, Diagon wrote:
> On 05/01/2017 02:01 PM, Arno Wagner - arno@wagner.name wrote:
> > On Mon, May 01, 2017 at 20:45:15 CEST, Michael Kj=F6rling wrote:
> >> On 1 May 2017 22:37 +0500, from hsiddiqi@gmail.com (Hammad Siddiqi):
> >>> Hi Team,
> >>>
> >>> May I please get an update on this.
> >>
> >> Everyone here donates freely of their own time to help others. If you
> >> require more than volunteer effort, then I recommend that you turn to
> >> your contracted support provider to open a case with them.
> >>=20
> > Indeed. However the update here is pretty simple: It looks
> > like you have lost your LUKS container permanendly due to
> > causes unknown, likely localized corruption from bad RAM,
> > a bad bus or a bad controller somewhere. I recommend a look=20
> > into FAQ section 6, "Backup and Data Recovery" for a future=20
> > set-up.
>=20
> For my own edification, could someone clarify this for me?  If he's got
> a backup of his header, shouldn't he be able to unlock/open the device,
> even if he doesn't find a filesystem on there?

I think the statement was that there is a backup of the passphrase,
but not of the header.

Regards,
Arno
--=20
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of=20
"news" is "something that hardly ever happens." -- Bruce Schneier