sudo cryptsetup luksOpen s9_vault.img s9_vault
Key slot 0 unlocked.
Command successful.
No errors are reported so it seems that the image has decrypted correctly. I move on to mounting:
Neither of theSo I took a look with mke2fs:
sudo mke2fs -n /dev/mapper/s9vault
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with 1044480 4k blocks and 261120 inodes
Filesystem UUID: 6be51418-5a91-40b9-84aa-1459bb6f5a40
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736
I have tried every superblock suggested replacement superblocks workin this list but this error message keeps occurring.
sudo e2fsck -b 32768 /dev/mapper/s9vault
e2fsck 1.44.5 (15-Dec-2018)
e2fsck: Bad magic number in super-block 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:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
B
Additional. I have a backup that uses rsync to copy files from one disk to another which includes this image. I tried using the backup copy and got the same error. Wondering if this is something peculiar about the computer im using. The machine that first made and mounted this image has been gotten rid of and a new one put in it's place with the disks and data from the old machine.