Linux – How to fsck.ext3 a TrueCrypt Volume

ext3linuxtruecrypt

I have a truecrypt file that contains an ext3 file system. Not sure exactly how to word this, but is there a way I can mount the truecrypt volume without actually mounting the filesystem within it so I can attempt to repair it with fsck?

So I have (ext3 filesystem(TrueCrypt File( Ext 3 Filesystem ))). I want to run the check on the one in bold.

I have of course made a copy of the file already. I can still mount it, but I have deleted files and df still shows as full, so I am thinking there is maybe a bad superblock?

Best Answer

Followed the instructions in http://www.cgsecurity.org/wiki/Recover_a_TrueCrypt_Volume. The only thing is that I had to recover from one of the backup super blocks. You can use the testdisk program described in that page to find the other superblocks (there are other methods), and then you just specify it like:

/sbin/fsck.ext3 -b 24577 /tmp/.truecrypt_aux_mnt1/volume

Related Solutions

Backup on disc using TrueCrypt corruption problem

I have not used TrueCrypt before so I am assuming that the copying part is just a plain disk to disk procedure. My suggestion would be to use xcopy to attempt to copy the files.

More specifically with the command -> xcopy /S /C

From the xcopy help : /S Copies directories and subdirectories except empty ones. /C Continues copying even if errors occur.

Hope it helps

Linux – filesystem mounting problem

Is /dev/sdc really a device not a file? That would explain why '-o loop' works.

The other thing is: you create a ext2 file system (mke2fs and mkfs.ext2 without '-j' option will create ext2, not ext3 file system) and are trying to mount it as ext3. Though, it is strange the loop mount succeeds.

'-o loop' mount options attaches a file (given as 'device' parameter to the mount command) to a loop device (/dev/loop0 by default if it is free) and then mounts that loop device. Loop device is a 'virtual' block device that represents a regular file on other filesystem.

mount -o loop some_file /mnt

is equivalent of:

losetup /dev/loop0 some_file
mount /dev/loop0 /mnt

And IMHO '-o loop' should not make any difference in recognizing and mounting a file system from a regular block device. If it works with regular block devices at all.

Whatever happens, there should be something about the problem in kernel logs (dmesg output).

Best Answer

Related Solutions

Backup on disc using TrueCrypt corruption problem

Linux – filesystem mounting problem

Related Topic