Originally Posted by salasi
Gosh, is that really true? If you have an encrypted drive and there is a problem with it, does that mean that there are no tools you can use to fix it, or is it a matter of using fsck with some obscure options, or something?
No you can still use fsck in the usual manner. However, the important part is that you realise that your filesystem is on the luks device /dev/mapper/luksname and not the underlying partition.
To run fsck on a luks encrypted filesystem, the filesystem should be unmounted and the luks device unlocked (OPEN). Then you just run fsck on the /dev/mapper/luksname device in the usual manner.
Running fsck on the partition directly as airstuff has unfortunately discovered, is a very bad idea.