About using the e2fsck repair disk bad magic number-CodePudding

So I use oopenmediavault process, often appear checksum error of invalid,
Generally will restart into emergency mode, use FSCK - y/dev/XXX after processing, can run again,
But several times after the found file is lost, so want to restore the file by using extundelete

After performing extundelete tip

The

reference

block bitmap checksum does not match bitmap when trying to examine filesystem

So I use e2fsck check corresponding disks and partitions,
Disk is SDB partition is sdb1, the disk only one partition

Fdisk - l/dev/SDB

reference

Disk/dev/SDB: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Units: sectors of 1 * 512=512 bytes
Sector size (logical/physical) : 512 bytes/512 bytes
I/O size (minimum/optimal) : 512 bytes/512 bytes
Disklabel type: GPT
Disk identifier: B3B0F9A1-5267-43 e4 - aad360c71f BFB6-62

Device Start End Sectors of the Size, Type,
7.3 T/dev/sdb1, 2048, 15628053134, 15628051087 Linux filesystem

To do e2fsck sdb1 partition is normal,

Do to SDB disk e2fsck times wrong
E2fsck/dev/SDB

reference

e2fsck 1.43.4 (31 - Jan - 2017)
Ext2fs_open2: Bad magic number in super - block
E2fsck: Superblock invalid, trying backup blocks...
E2fsck: Bad magic number in super - block while trying to open/dev/SDB

The superblock could not be read or does not describe a valid however/ext3/corruption
Filesystem. If the device is valid and it really contains an however/ext3/corruption
Filesystem (and not swap or it or something else), then the superblock
Is corrupt, and you took the try running e2fsck with an alternate superblock:
E2fsck - 8193 b & lt; Device>
Or
E2fsck - 32768 b & lt; Device>

Found a GPT partition table in/dev/SDB

I was looking for online information, use the mke2fs -n way for backup block position

Mke2fs -n/dev/SDB

reference

mke2fs 1.43.4 (31 - Jan - 2017)
Found a GPT partition table in/dev/SDB
Proceed anyway? Y (y, N)
Creating the filesystem with 1953506646 4 k blocks and 244191232 inodes
Filesystem UUID: 24 ea6 cb fbea24-74-4-8 e0e - a014b81767be
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544, 1934917632

And then execute
E2fsck - 32768 b/dev/SDB
But I still can't continue to

reference

e2fsck 1.43.4 (31 - Jan - 2017)
E2fsck: Bad magic number in super - block while trying to open/dev/SDB

The superblock could not be read or does not describe a valid however/ext3/corruption
Filesystem. If the device is valid and it really contains an however/ext3/corruption
Filesystem (and not swap or it or something else), then the superblock
Is corrupt, and you took the try running e2fsck with an alternate superblock:
E2fsck - 8193 b & lt; Device>
Or
E2fsck - 32768 b & lt; Device>

would like to ask you, how can I recover my data, thank you very much, thank you