DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sumaya <Sumaya1960@gmx.de>
To: dm-crypt@saout.de
Subject: [dm-crypt] Header corrupted?
Date: Mon, 18 Jan 2016 12:53:13 +0100	[thread overview]
Message-ID: <569CD229.4070206@gmx.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2419 bytes --]

Hi everybody, thank you very much for all responses! I could not follow 
up, I was very sick. Sorry! Here we go again... It would be great to 
have any suggestions! Thanks to everybody! Thanks a lot!!! Dumps: ASCII
blkid		
/dev/sdb crypto_LUKS (not mounted) 45c461c2-1976-48a2-804f-b3812173b0e8 
crypto_Luks 	(not mounted)

parted -l
Fehler: /dev/sdb: unbekannte Partitionstabelle
Modell: ThinkPad Secure 1TB 3.0 (scsi)
Festplatte /dev/sdb: 1000GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: unknown
Disk Flags:

luksDump


		
	
LUKS hader information for /dev/sdb 	
	
	

	
	
	
Version: 1 	
	
	
Cipher name: aes 	
	
	
Cipher mode: xts-plain64 	
	
	
Hash spec: sha512 	
	
	
Payload offset: 4096 	
	
	
MK bits: 512 	
	
	
MK digest: 23 93 9a 2a ed f5 d1 3c d9 2b 7e 3f fb 30 46 68 f0 5d a1 6a 	
	
	
MK salt: 8c c2 23 61 b1 73 e6 82 3f 32 a2 3e fb 89 ec fa 	
	
	
75 f8 f9 d9 0c 25 6d f0 57 e1 62 64 8e 13 51 97 	
	
	
MK iterations: 102500 	
	
	
UUID:
	
	
	

	
	
	
Key Slot 0: ENABLED 	
	
	
Iterations: 409204 	
	
	
Salt: f9 7a ee a2 e5 bb 8a d0 a1 4c 4d e2 0b ac e2 86 	
	
	
37 f5 ce fe 2a 9c 65 a0 ac cc fe 35 2e 0d 11 8e 	
	
	
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 	
	
	

	
	
	

Hi there, Please resend the dumps in ASCII as Arno suggested. Meanwhile: 
It seems the disk has no partition and starts with a LUKS-Header right 
away. While the LUKS-Header itself seems to be consistent (at first 
glance) the keyslot itself could of course be damaged. Regards -Sven Am 
14.01.2016 um 11:02 schrieb sumaya1960 at gmx.de 
<http://www.saout.de/mailman/listinfo/dm-crypt>: >//>//>/Hi everybody, 
/>//>/I am a bit lost now. I tried (why so ever) to connect my (ext4) 
/>/encrypted disk to a Windows 10 System - (what a big stupid idea - I 
know />/- very very stupid).... />//>/Now I can not access my encrypted 
disk anymore and wonder if the Header />/is damaged? My pass-phrase is 
absolute correct, but not accepted with />/luksOpen! />//>//>/luksDump 
gives />//>//>//>//>/blkid shows />//>//>//>/What happened to my 
external disk? I am running Cent OS7... />/For any help I would be so 
thankful!!! Really very very thankful!!! />/Thanks a lot! />//>/Kind 
regards, />/Sumaya />//>//>//>//>//>//>//>//>//>

[-- Attachment #2: Type: text/html, Size: 22455 bytes --]

             reply	other threads:[~2016-01-18 11:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 11:53 Sumaya [this message]
2016-01-18 15:17 ` [dm-crypt] Header corrupted? Arno Wagner
  -- strict thread matches above, loose matches on Subject: below --
2016-01-11 16:45 [dm-crypt] Header? sumaya1960
2016-01-14 10:02 ` [dm-crypt] Header corrupted? sumaya1960
2016-01-14 23:55   ` Arno Wagner
2016-01-15  4:05   ` David Christensen
2016-01-15 11:32   ` Sven Eschenberg

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=569CD229.4070206@gmx.de \
    --to=sumaya1960@gmx.de \
    --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