hey david, On 25/04/2010 David Simpson wrote: > When I try to mount an encrypted container I get the following: > > # mount /dev/mapper/container1 /mnt/container1 > > wrong fs type, bad option, bad superblock on /dev/mapper/container1, > missing codepage or helper program, or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > # dmesg > [511.590000] EXT3-fs error (device dm-0): ext3_check_descriptors: Block > bitmap > for group 0 not in group (block 1825591687)! > [511.620000] EXT3-fs: group descriptors corrupted!
please provide more information about your dm-crypt setup. which command do you use in order to unlock the dm-crypt device? is it a LUKS encrypted device, or do you use plain dm-crypt? > I am running this on a SheevaPlug with a USB external harddrive. > > If I try the same container on an updated Squeeze installed on an AthlonXP > 2800 desktop > (2.6.32-trunk-686 #1 SMP), I get the same error. However, if I try with > Ubuntu 9.10 on > the same Athlon desktop, this same container mounts successfully. > > Back on the Sheeva Plug, if I downgrade the package to > cryptsetup_2%3a1.1.0~rc2-1_armel.deb, > the same container mounts successfully, but fails to mount if I then upgrade > to the next latest > that I have in my package archive: cryptsetup_2%3a1.1.0-2_armel.deb. i guess that you use plain dm-crypt and didn't set cipher, hash and hash size in the crypttab, thus running into issues with the changed defaults. > For the failure cases, testdisk fails to find any valid superblocks on the > mapped device. Both > of my (ext3) containers are showing the same problem. greetings, jonas
signature.asc
Description: Digital signature
