I'm trying to recover data from damaged 3TB drive. I'm using ddrescue to make an image of it, but it takes forever while there are lots of read errors. I was wondering if I can have some luck with first 200GB (with large wholes in it) that I already copied. I read the partition table with gdisk and found the offset of ext4 file system that I'm interested in reading. Then created loop device to have a nice way of interacting with the partition:
sudo losetup -f --show -o $((xxxxxxxxxxx*512))
sudo tune2fs -l /dev/loop16 gives me some info so I think I'm on a right track.
Unfortunately I can't mount it because of the file system errors and e2fsck won't fix anything as it's trying to read beyond the image file boundaries. I suppose there may be some important file system data in later areas of the partition. Do you have any advice on how I could trick the system to ignore the errors and try to work with incomplete inode structure and within the truncated image?