Arch Linux

traaf

Member

Registered: 2009-08-06

Posts: 10

cryptsetup fail to unlock partition

Hi
i have a full disk encrypted with cryptsetup.
i am using it since 2005.
the volume was created with ubuntu, it followed me under debian, then gentoo, and now 2 years with archlinux, without any problem.

yesterday afternoon, i updated my arch, and at reboot, i saw this new warning :

modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-ARCH/kernel/drivers/crypto/padlock-sha.ko): No such device

i ususally mount the volume manually, when i need to backup my data
it does not use luks, nor /etc/crypttab because i don't want auto mount for it

if needed, i run

cryptsetup create backup /dev/sdb1
mount /dev/mapper/backup /media/backup

but now, it returns ((bad superbloc or something like that)

mount : type erroné de syst .de fichiers, option erronée, super bloc
        erroné sur /dev/mapper/Stockage, codepage ou aide manquante ou autre erreur
       Dans quelques cas certaines informations sont utiles dans syslog - essayez
       dmesg | tail  ou quelque chose du genre

dmesg | tail
EXT3-fs error (device dm-0): ext3_check_descriptors: Block bitmap for group 0 not in group (block 848848030)!
EXT3-fs: group descriptors corrupted!

dmsetup table --showkeys
backup: 0 488392002 crypt aes-cbc-essiv:sha256 6139a5b4463734ceb57bb2ad8eaac618a8f8be348b4518ee87af7dbfb92be5f3 0 8:17 0

testdisk can not see anything on /dev/mapper/backup , so i don't think the filesystem is corrupted, testdisk should have find something, at least some corrupted datas.
i precise i regulary and manually run fsck on the volume (an ext3 partition on the whole disk)
so i think the problem is with cryptsetup or dmcrypt

lsmod 
aes_i586                6880  2
aes_generic            25834  1 aes_i586
dm_crypt               10450  1
dm_mod                 54355  2 dm_crypt
sha256_generic          9029  2

if anyone have a solution...

anykey

Member

From: Trier, Germany

Registered: 2004-06-12

Posts: 79

Re: cryptsetup fail to unlock partition

I can confirm that it is NOT filesystem corruption. I was finally able to decrypt and mount my cryptovolume from the arch linux install cd 2009.08, containing an older version of the whole software stack.

I still dont know what part of that stack caused that error.