On Tue, May 02, 2017 at 02:29:06 CEST, Diagon wrote: > On 05/01/2017 02:01 PM, Arno Wagner - arno@xxxxxxxxxxx wrote: > > On Mon, May 01, 2017 at 20:45:15 CEST, Michael Kjörling wrote: > >> On 1 May 2017 22:37 +0500, from hsiddiqi@xxxxxxxxx (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@xxxxxxxxxxx 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 _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
