Header corrupted?
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 />//>//>//>//>//>//>//>//>//>
Hi Sumaya,
that looks like you have a LUKS container on the raw disk. Not a problem in itself, just a bit unusual. The luksDump info looks fine.
You can still have a problem in the key-slot. To check for that, please compile and run the keyslot-checker and post its output here. If it finds something, also post the output with option -v, unless that is too long.
You find it in misc/keyslot_ckecker in the source-package. It will look for areas of possible corruption in the keyslots.
Regards,
Arno
Quoted 131 lines · Sumaya
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/sdbcrypto_LUKS(not mounted)
45c461c2-1976-48a2-804f-b3812173b0e8crypto_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/sdbVersion: 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 />//>//>//>//>//>//>//>//>//>_______________________________________________
dm-crypt mailing list
[email protected]
http://www.saout.de/mailman/listinfo/dm-crypt
Signature · 7 lines
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: [email protected] 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