jaid@jaid-vm:~/Desktop$     fsck.ext4 ddrescue.img
e2fsck 1.45.5 (07-Jan-2020)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open ddrescue.img

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>

Found a dos partition table in ddrescue.img
jaid@jaid-vm:~/Desktop$     fsck.ext4 -b 32768 ddrescue.img
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Bad magic number in super-block while trying to open ddrescue.img

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>

Found a dos partition table in ddrescue.img
jaid@jaid-vm:~/Desktop$     fsck.ext4 -b 98304 ddrescue.img
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Bad magic number in super-block while trying to open ddrescue.img

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>

Found a dos partition table in ddrescue.img
jaid@jaid-vm:~/Desktop$     fsck.ext4 -b 163840 ddrescue.img
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Bad magic number in super-block while trying to open ddrescue.img

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>

Found a dos partition table in ddrescue.img
jaid@jaid-vm:~/Desktop$     fsck.ext4 -b 229376 ddrescue.img
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Bad magic number in super-block while trying to open ddrescue.img

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>

Found a dos partition table in ddrescue.img
jaid@jaid-vm:~/Desktop$     fsck.ext4 -b 294912 ddrescue.img
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Bad magic number in super-block while trying to open ddrescue.img

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>

Found a dos partition table in ddrescue.img
jaid@jaid-vm:~/Desktop$     fsck.ext4 -b 819200 ddrescue.img
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Attempt to read block from filesystem resulted in short read while trying to open ddrescue.img
Could this be a zero-length partition?
jaid@jaid-vm:~/Desktop$     fsck.ext4 -b 884736 ddrescue.img
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Attempt to read block from filesystem resulted in short read while trying to open ddrescue.img
Could this be a zero-length partition?
jaid@jaid-vm:~/Desktop$     fsck.ext4 -b 1605632 ddrescue.img
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Attempt to read block from filesystem resulted in short read while trying to open ddrescue.img
Could this be a zero-length partition?
jaid@jaid-vm:~/Desktop$     fsck.ext4 -b 2654208 ddrescue.img
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Attempt to read block from filesystem resulted in short read while trying to open ddrescue.img
Could this be a zero-length partition?
jaid@jaid-vm:~/Desktop$     fsck.ext4 -b 4096000 ddrescue.img
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Attempt to read block from filesystem resulted in short read while trying to open ddrescue.img
Could this be a zero-length partition?