From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] (no subject)
Date: Tue, 2 May 2017 22:49:44 +0200 [thread overview]
Message-ID: <20170502204944.GA30230@tansi.org> (raw)
In-Reply-To: <5f9b9896-bf23-3769-9589-dcda43e1efd9@xoxy.net>
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örling 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.
> >>
> > 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
> > into FAQ section 6, "Backup and Data Recovery" for a future
> > set-up.
>
> 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
--
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
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2017-05-02 20:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 17:48 [dm-crypt] (no subject) Hammad Siddiqi
2017-04-29 18:30 ` Arno Wagner
2017-04-29 19:19 ` Hammad Siddiqi
2017-05-01 17:37 ` Hammad Siddiqi
2017-05-01 18:45 ` Michael Kjörling
2017-05-01 21:01 ` Arno Wagner
2017-05-02 0:29 ` Diagon
2017-05-02 20:49 ` Arno Wagner [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-18 21:40 RAS RAS
2016-06-20 7:52 ` Milan Broz
[not found] ` <1466423154.44272313@f313.i.mail.ru>
2016-06-20 12:02 ` Milan Broz
2015-05-04 14:50 janemba
2015-05-04 16:41 ` Arno Wagner
2014-02-07 13:51 Redwood Hyd
2013-03-17 21:30 .. ink ..
2012-12-29 22:22 .. ink ..
2012-12-29 22:46 ` Milan Broz
2012-12-29 23:15 ` .. ink ..
2012-12-29 23:39 ` Milan Broz
2012-12-29 23:53 ` .. ink ..
2012-12-30 7:12 ` .. ink ..
2012-12-30 9:05 ` Milan Broz
2012-12-30 9:19 ` .. ink ..
2012-12-30 10:51 ` Milan Broz
2012-12-30 11:49 ` .. ink ..
2012-10-10 21:11 ffrizzy
2012-10-10 21:09 ffrizzy
2012-10-10 23:13 ` Claudio Moretti
2012-10-09 6:24 ffrizzy
2012-10-09 6:21 ffrizzy
2012-09-04 1:20 Anil
2012-09-04 1:29 ` Arno Wagner
2011-09-18 10:58 Ingo Schmitt
2011-03-09 2:04 Rookcifer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170502204944.GA30230@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox