Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What's a fuse device, how do I find it?
What's a volume device in my case?
In the code, that page says:
Code:
$ ./truecrypt -t --filesystem=none /data/data_for_testdisk/truecrypt.dd
Enter password for /data/data_for_testdisk/truecrypt.dd:
Enter keyfile [none]:
Protect hidden volume? (y=Yes/n=No) [No]:
Enter system administrator password:
$ mount
...
truecrypt on /tmp/.truecrypt_aux_mnt1 type fuse.truecrypt (rw,nosuid,nodev,allow_other)
$ sudo testdisk /tmp/.truecrypt_aux_mnt1/volume
What is /data/data_for_testdisk/truecrypt.dd in my case?
Is the password the trucrypt volume password?
PS: Ext4 filesystem
Last edited by wearetheborg; 05-18-2018 at 12:14 AM.
Error: mount: wrong fs type, bad option, bad superblock on..
Given the above error, I reviewed your post to find what filesystem you might have on either/both partitions and found nothing. Posting that info would be a good first step. Methods to repair corrupted filesystem, if that is the problem, will vary with filesystem. With regard to fuse, the link below should be helpful.
Given the above error, I reviewed your post to find what filesystem you might have on either/both partitions and found nothing. Posting that info would be a good first step. Methods to repair corrupted filesystem, if that is the problem, will vary with filesystem. With regard to fuse, the link below should be helpful.
Did you mount sdb2 manually and if so, what exact command did you use?
Problems with filesystems can be somewhat resolved by running a filesystem check, fsck with various options is commonly used on Linux. You can get more details on options using the Search option here at LQ or doing an online search. I don't use encryption so I don't know what effect that might have.
The first thing I would do if I were you is make exact duplicates of both drives to an external medium, if you have sufficient capacity. You don't want to do any further damage to either filesystem in the process of trying to recover them (or, if you do, you want to be able to revert).
For /dev/sdb2, is it TrueCrypt that is generating the "bad superblock" error?
Did you mount sdb2 manually and if so, what exact command did you use?
Problems with filesystems can be somewhat resolved by running a filesystem check, fsck with various options is commonly used on Linux. You can get more details on options using the Search option here at LQ or doing an online search. I don't use encryption so I don't know what effect that might have.
The first thing I would do if I were you is make exact duplicates of both drives to an external medium, if you have sufficient capacity. You don't want to do any further damage to either filesystem in the process of trying to recover them (or, if you do, you want to be able to revert).
For /dev/sdb2, is it TrueCrypt that is generating the "bad superblock" error?
Yes, for sdb2, it is Truecrypt which is generating the error.
And I get read errors on sdb1, generated from normal cp. Is there any way to fix the read errors?
I would recommend that you look at ddrescue instead of dd.
Also, you should back up to a completely different device.
Once you have backed up, if you decide to do that (that decision depends on the value of the data you might lose if you don't), use TrueCrypt to mount the first partition and run a fsck on it. You need to concentrate on one of the partitions at a time, and that is the most suitable to start with as you can actually mount it.
Did you check the cables?
Another thing you should do is check the SMART data from the HDD. The drive could be failing.
I would recommend that you look at ddrescue instead of dd.
Also, you should back up to a completely different device.
Once you have backed up, if you decide to do that (that decision depends on the value of the data you might lose if you don't), use TrueCrypt to mount the first partition and run a fsck on it. You need to concentrate on one of the partitions at a time, and that is the most suitable to start with as you can actually mount it.
Did you check the cables?
Another thing you should do is check the SMART data from the HDD. The drive could be failing.
Thanks. I will use ddrescue (to a different device.
It's an internal HDD (I have two internal HDDs), so I don't have cable to worry about.
The drive is failing. SMART checks were quiting with read errors.
Thanks. I will use ddrescue (to a different device.
It's an internal HDD (I have two internal HDDs), so I don't have cable to worry about.
The drive is failing. SMART checks were quiting with read errors.
Internal HDDs still have cables to connect them to the motherboard, but that's of no importance if the drive is failing. After you've made an image of it, try to rescue as much as you can from it using e.g. TestDisk & Photorec (was there much on that drive?), not easy when TrueCrypt is also involved.
In the future, it would be much better to make regular backups rather than wait for problems to occur (but easy to say in hindsight).
Internal HDDs still have cables to connect them to the motherboard, but that's of no importance if the drive is failing. After you've made an image of it, try to rescue as much as you can from it using e.g. TestDisk & Photorec (was there much on that drive?), not easy when TrueCrypt is also involved.
In the future, it would be much better to make regular backups rather than wait for problems to occur (but easy to say in hindsight).
Thought I'd give an update
I ran ddrescue on both sdb1 (200GB) and sdb2(500GB partions).
The lost data according to ddrescue was about 3MB for sdb1 and 300kb for sdb2.
Unfortunately the recovered image from sdb1 did not mount under truecrypt.
I tried to repair using testdisk and fsck, but fsck asked to be run manually due to unexpected errors, and after recovery (in which a bunch of things were changed), 50GB is gone, and the rest is in lost+found.
sdb2 was a success story, the image mounts under truecrypt.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
Linux tools don't always account for encryption. Use with caution. The thing about encryption is you can't do a normal rescue, because for that the drive has to be totally unmounted.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
