From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.arhont.com (mail1.arhont.com [178.248.108.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Sun, 28 Jul 2019 14:06:40 +0200 (CEST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail1.arhont.com (Postfix) with ESMTP id 23243360074 for ; Sun, 28 Jul 2019 12:57:52 +0100 (BST) Received: from mail1.arhont.com ([127.0.0.1]) by localhost (mail1.arhont.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 7P04bBAi4aIs for ; Sun, 28 Jul 2019 12:57:50 +0100 (BST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail1.arhont.com (Postfix) with ESMTP id 77E2E360BEE for ; Sun, 28 Jul 2019 12:57:50 +0100 (BST) Received: from mail1.arhont.com ([127.0.0.1]) by localhost (mail1.arhont.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id xNXRNV3AEyaz for ; Sun, 28 Jul 2019 12:57:50 +0100 (BST) Received: from mail1.arhont.com (localhost.localdomain [127.0.0.1]) by mail1.arhont.com (Postfix) with ESMTP id 3FB6A360074 for ; Sun, 28 Jul 2019 12:57:50 +0100 (BST) Date: Sun, 28 Jul 2019 12:57:50 +0100 (BST) From: "Konstantin V. Gavrilenko" Message-ID: <265658862.16.1564315066873.JavaMail.gkos@xpska> In-Reply-To: <1590255742.9.1564314256863.JavaMail.gkos@xpska> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [dm-crypt] LUKS Header crruption List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de Hi List, as a result of executing a command from the history, after a reboot, when the disk letters were changed, I have accidentally overwritten the LUKS header with the raid superblock one :( Now I can not open the cryptodisk with the "luksOpen" as it states the "No key available with this passphrase." However, when I run "luksDump" the header information is available # cryptsetup luksDump /dev/sdd1 LUKS header information for /dev/sdd1 Version: 1 Cipher name: aes Cipher mode: xts-plain64 Hash spec: sha256 Payload offset: 4096 MK bits: 256 MK digest: a6 a6 de 04 5a 19 9f 97 54 a9 79 bf f8 c1 37 89 69 44 34 76 MK salt: 7a 0b 8e cc 68 06 35 ec 09 fc 5e f9 90 e3 c9 ef 8b 11 96 10 4c 25 ab 89 a1 48 df fe 6a 88 20 96 MK iterations: 232809 UUID: 0f91c412-6f6a-405d-8040-5cc17ad17b47 Key Slot 0: ENABLED Iterations: 3724958 Salt: c4 52 ac 04 59 8a d1 4f 7a 3c 5d e8 d3 50 1a c4 11 20 0b 66 66 81 78 09 9f 7a f4 c1 dc 80 d4 40 Key material offset: 8 AF stripes: 4000 Key Slot 1: DISABLED Key Slot 2: DISABLED Key Slot 3: DISABLED Key Slot 4: DISABLED Key Slot 5: DISABLED Key Slot 6: DISABLED Key Slot 7: DISABLED The RAID superblock that was written by mdadm is default, version 1.2 that is located 4K from the beginning of the device. Providing that I have no backup of the original header and I know wht was written, is there a way to restore the header and get the data? Konstantin