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? > Regards, > Arno Dave. _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
