Arch Linux

GNA

Member

Registered: 2011-02-15

Posts: 57

Truecrypt filesystem broken

Today out of the blue, I can no longer mount one of my truecrypt volumes.

I found this guide, which does not work for me, but at least gives me some general directions:
https://linuxexpresso.wordpress.com/201 … in-ubuntu/

I can mount the truecrypt part of it (so /dev/mapper/truecrypt2 exists) but I cant mount this mapper.

If I try to mount the volume:
dmesg | tail

[ 1930.347112] EXT4-fs (dm-2): VFS: Can't find ext4 filesystem
[ 1930.347540] EXT4-fs (dm-2): VFS: Can't find ext4 filesystem
[ 1930.347944] EXT4-fs (dm-2): VFS: Can't find ext4 filesystem
[ 1930.349238] XFS (dm-2): bad magic number
[ 1930.349243] XFS (dm-2): SB validate failed

What seems strange to me:
sudo fsck.ext4 /dev/mapper/truecrypt2

e2fsck 1.42.6 (21-Sep-2012)
ext2fs_open2: Ungültige magische Zahl im Superblock
fsck.ext2: Superblock ungültig versuche es mit Backup-Blöcken...
fsck.ext2: Ungültige magische Zahl im Superblock beim Versuch, /dev/mapper/truecrypt2 zu öffnen

SuperBlock ist unlesbar bzw. beschreibt kein gültiges ext2
Dateisystem.  Wenn Gerät gültig ist und ein ext2
Dateisystem (kein swap oder ufs usw.) enthält,  dann ist der SuperBlock
beschädigt, und sie könnten e2fsck mit einem anderen SuperBlock:
    e2fsck -b 8193 <Gerät>

english: bad magic number in superblock.
The superblock could not be read or does not describe a correct ext2.

It is an ext4 filesystem. Why does this tool think it is ext2?

I checked where the backups of the superblock should be kept and tried to use e2fsck to recover.

sudo e2fsck -b 229376 /dev/mapper/truecrypt2
Bad magic number when trying to open /dev/mapper/truecrypt2.

Is there any way to recover from this state?

Last edited by GNA (2013-01-02 14:28:42)