關于使用e2fsck修復磁盤bad magic number的問題-有解無憂

是這樣的我用oopenmediavault程序中，經常出現checksum invalid的錯誤，
一般重啟后會進入emergency mode，用fsck -y /dev/xxx處理后，又能運行，
但幾次后發現檔案出現丟失，因此想使用extundelete來恢復檔案

執行extundelete 后提示

參考

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

于是我用e2fsck檢查對應的磁盤和磁區，
磁盤是sdb，磁區是sdb1，整個磁盤只做了一個磁區

fdisk -l /dev/sdb

參考

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-43E4-BFB6-62AAD360C71F

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

對sdb1磁區做e2fsck時正常，

對sdb磁盤做e2fsck時報錯
e2fsck /dev/sdb

參考

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 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 gpt partition table in /dev/sdb

我找了網上的資料，用mke2fs -n 方式找了下備份block位置

mke2fs -n /dev/sdb

參考

mke2fs 1.43.4 (31-Jan-2017)
Found a gpt partition table in /dev/sdb
Proceed anyway? (y,N) y
Creating filesystem with 1953506646 4k blocks and 244191232 inodes
Filesystem UUID: 24fbea24-74cb-4ea6-8e0e-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

然后再執行
e2fsck -b 32768 /dev/sdb
但是仍然不能繼續

參考

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 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>

想請問各位大佬，這種情況我該怎么恢復我的資料，萬分感謝，謝謝

轉載請註明出處，本文鏈接：https://www.uj5u.com/caozuo/130207.html

標籤：系統維護與使用區

上一篇：安裝虛擬機出現這個錯誤

下一篇：QT