☰

e2fsck：尝试打开 /dev/sdi 时超级块中的魔数错误

tag-icon • tag-icon fsck
e2fsck：尝试打开 /dev/sdi 时超级块中的魔数错误

我有一块 WD Mybook Live 磁盘，有一天它停止工作了。我取出硬盘并将其连接到我的 Linux 机器上，试图恢复数据，但目前还没有成功。

fdisk 显示以下内容：

Disk /dev/sdi: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Generic         
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: <XXXXXXXXXXX>

Device       Start        End    Sectors  Size Type
/dev/sdi1  1032192    5031935    3999744  1.9G Linux RAID
/dev/sdi2  5031936    9031679    3999744  1.9G Linux RAID
/dev/sdi3    30720    1032191    1001472  489M Microsoft basic data
/dev/sdi4  9031680 3907028991 3897997312  1.8T Microsoft basic data

但我无法安装磁盘。运行 e2fsck 后，我得到以下结果：

sudo e2fsck -n /dev/sdi
e2fsck 1.45.5 (07-Jan-2020)
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/sdi

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

在另一篇文章中，我尝试通过从其他副本中复制超级块来解决这个问题，但没有成功。

sudo mke2fs -n /dev/sdi4 
mke2fs 1.45.5 (07-Jan-2020)
/dev/sdi4 contains a ext4 file system
    last mounted on /CacheVolume on Wed Oct 17 21:04:47 2018
Proceed anyway? (y,N) y
Creating filesystem with 487249664 4k blocks and 121815040 inodes
Filesystem UUID: 820e42ab-4109-4dde-8ad9-545c825e5e52
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
    102400000, 214990848

sudo  e2fsck -b 20480000 /dev/sdi4 
e2fsck 1.45.5 (07-Jan-2020)
e2fsck: Bad magic number in super-block while trying to open /dev/sdi4

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>

/dev/sdi4 contains a ext4 file system
    last mounted on /CacheVolume on Wed Oct 17 21:04:47 2018

有任何想法吗 ？

相关内容