Re: [dm-crypt] Can't mount my LUKS crypted disk after kernel update / reboot

["Javier Juan Martínez Cabezón" <tazok.id0@gmail.com>]

I think I answer too fast before, sorry.

Did strings answer something known in the device?

Are you sure that this is true?   aes-xts-essiv:sha256
Which cipher did you use with cryptsetup 1.1?


On 13/12/12 21:36, Philipp Durrer - Nexus Informatik wrote:
> Hi
> 
> 
> 
> I've got a very serious issue, I can't mount my LUKS crypted
> software raid disk after a regular kernel update (Ubuntu 11.10,
> Kernel 3.0.0-12-generic to 3.0.0-17-generic) and a following
> reboot.
> 
> 
> 
> After the reboot the raid disks start properly and are active:
> 
> 
> 
>> cat /proc/mdstat
> 
>> Personalities : [raid0] [raid1] [linear] [multipath] [raid6]
>> [raid5]
> [raid4] [raid10]
> 
>> md0 : active raid1 sda2[0] sdb2[1]
> 
>> 488269 blocks super 1.2 [2/2] [UU]
> 
>> 
> 
>> md2 : active raid1 sda4[0] sdb4[1]
> 
>> 3905214 blocks super 1.2 [2/2] [UU]
> 
>> 
> 
>> md126 : active raid0 sda5[0] sdb5[1]
> 
>> 5832190976 blocks super 1.2 512k chunks
> 
>> 
> 
>> md1 : active raid1 sda3[0] sdb3[1]
> 
>> 9764529 blocks super 1.2 [2/2] [UU]
> 
>> 
> 
>> md127 : active raid0 sdd1[1] sdc1[0]
> 
>> 5860530176 blocks super 1.2 512k chunks
> 
>> 
> 
>> unused devices: <none>
> 
> 
> 
> The LUKS header looks fine aswell:
> 
>> cryptsetup luksDump /dev/md126
> 
>> LUKS header information for /dev/md126
> 
>> 
> 
>> Version:        1
> 
>> Cipher name:    aes
> 
>> Cipher mode:    xts-essiv:sha256
> 
>> Hash spec:      sha1
> 
>> Payload offset: 4096
> 
>> MK bits:        512
> 
>> MK digest:      f0 59 ac a8 13 3c e1 XX YY ZZ ce 0f ba cd 63 0a
>> 4a d0 25 b2
> 
>> MK salt:        e8 3f fc 25 3a 0e a3 XX XX YY ZZ 45 1c 12 31 f6
> 
>> cb ea 03 d2 51 66 f9 4c 51 c4 29 4d 97 4f 17 0f
> 
>> MK iterations:  33375
> 
>> UUID:           1686eb8f-be62-462b-9326-319a7cc8e087
> 
>> 
> 
>> Key Slot 0: ENABLED
> 
>> Iterations:             133653
> 
>> Salt:                   c1 d9 a0 ff 6e 7a XX XX YY ZZ a7 67 dc
>> 8f
> 10 93
> 
>> 4e a2 9c 9e d8 39 4f 91 37 3d e3 8f df 24
> dc 60
> 
>> 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
> 
> 
> 
> I can aswell open the Disk successful without compaints:
> 
>> cryptsetup -d /keystore/tempstuff1 luksOpen /dev/md126 stuff
> 
>> cryptsetup status stuff
> 
>> /dev/mapper/stuff is active.
> 
>> type:    LUKS1
> 
>> cipher:  aes-xts-essiv:sha256
> 
>> keysize: 512 bits
> 
>> device:  /dev/md126
> 
>> offset:  4096 sectors
> 
>> size:    11664377856 sectors
> 
>> mode:    read/write
> 
> 
> 
> But when I try to mount the device mapper disk I get compaints:
> 
>> mount /dev/mapper/stuff /home/crypt/
> 
>> mount: you must specify the filesystem type
> 
> 
> 
>> mount -t ext4 /dev/mapper/stuff /home/crypt/
> 
>> mount: wrong fs type, bad option, bad superblock on
>> /dev/mapper/stuff,
> 
>> missing codepage or helper program, or other error
> 
>> In some cases useful info is found in syslog - try
> 
>> dmesg | tail  or so
> 
> 
> 
>> dmesg | tail
> 
>> [12124.435471] EXT4-fs (dm-5): VFS: Can't find ext4 filesystem
> 
> 
> 
> Filesystem check doesn't work either :(
> 
> 
> 
>> fsck.ext4 /dev/mapper/stuff
> 
>> e2fsck 1.41.14 (22-Dec-2010)
> 
>> fsck.ext4: Superblock invalid, trying backup blocks...
> 
>> fsck.ext4: Bad magic number in super-block while trying to open
> /dev/mapper/stuff
> 
>> .
> 
> 
> 
> I can't see any updated dependencies of cryptsetup that are related
> to this issue, I had the default cryptsetup version 1.1.3 on the
> box and now tried with 1.5.1 with no success :(
> 
> Any ideas ? I would greatly appreciate any inputs helping me, that
> I don't lose about 12 TB  of precious data. -.-
> 
> 
> 
> Thank you.
> 
> Regards
> 
> 
> 
> 
> 
> _______________________________________________ dm-crypt mailing
> list dm-crypt@saout.de 
> http://www.saout.de/mailman/listinfo/dm-crypt