Skip to main content
The 2024 Developer Survey results are live! See the results

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Hello there. Thanks for the reply. I mentioned I'd tried this in the question but didn't test all of the backup superblocks. I've tried it again with every superblock backup and this is the result each time: e2fsck: Invalid argument while trying to open /dev/mapper/s9vault The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
    – Oni
    Commented Jan 7, 2021 at 10:08
  • @Oni Did you execute the commands after decrypting the drive? And what does mke2fs -n /dev/mapper/s9vault output? Please update your question with the output instead of posting the information in the comments. Commented Jan 7, 2021 at 10:15
  • 1
    Right-o. I wasn't sure where to post the update so I'll add it into the question
    – Oni
    Commented Jan 8, 2021 at 15:58