我是一名软件工程师，系统工程经验有限。我有几周前的“WD 4 TB Elements 便携式外置硬盘”，即 USB 4 TB 外置硬盘。我已将其安装在 Raspberry PI 上，并创建了一个独特的 ext3 分区。
昨晚，HD 几乎满了，在一次期间rsycn，它停止工作了。
我尝试快速重新启动，之后无法安装它。驱动器打开时会定期发出令人不快的“叮当”声。
安装时出现这个错误：
ubuntu@ubuntu:~$ sudo mount /dev/sdb1 /mnt/nfts/
mount: /mnt/nfts: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
我用谷歌搜索了一下，下面是我针对驱动器运行的一些命令：
来自 dmesg
[ 147.507499] sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 147.507519] sd 1:0:0:0: [sdb] tag#0 Sense Key : Aborted Command [current]
[ 147.507533] sd 1:0:0:0: [sdb] tag#0 Add. Sense: No additional sense information
[ 147.507550] sd 1:0:0:0: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[ 147.507567] blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
更多来自 dmesg
[ 278.832149] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[ 278.839728] EXT4-fs (sdb1): I/O error while writing superblock
[ 278.845737] EXT4-fs (sdb1): no journal found`
来自 tune2fs
ubuntu@ubuntu:~$ sudo tune2fs -l /dev/sdb1
tune2fs 1.45.5 (07-Jan-2020)
Filesystem volume name: <none>
Last mounted on: /mnt/nfts
Filesystem UUID: e4e0f609-7beb-4610-bb43-6a807f4f88b5
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: unsigned_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 244187136
Block count: 976745728
Reserved block count: 48837286
Free blocks: 116576385
Free inodes: 242495519
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 791
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Wed Jan 12 13:25:22 2022
Last mount time: Wed Feb 23 13:56:10 2022
Last write time: Wed Feb 23 14:07:39 2022
Mount count: 8
Maximum mount count: -1
Last checked: Wed Jan 12 13:25:22 2022
Check interval: 0 (<none>)
Lifetime writes: 2976 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 13549940-8c27-4c2a-87e2-e3f23ba4daa3
Journal backup: inode blocks
FS Error count: 279
First error time: Sun Jan 16 11:37:40 2022
First error function: ext4_mb_generate_buddy
First error line #: 744
First error inode #: 0
First error block #: 0
Last error time: Wed Feb 23 14:07:39 2022
Last error function: ext4_mb_generate_buddy
Last error line #: 744
Last error inode #: 0
Last error block #: 0
我尝试了 fsck，但一晚后没有得到明显的输出，因此停止并重新启动。
硬盘显然遇到了硬件故障，我猜有大量坏扇区。幸运的是，高清的内容是数千个小文件，我的希望是恢复尽可能多的小文件。
有人能指出我正确的方向吗？我可以做什么来进一步调查该问题并尝试恢复对仍存储在健康扇区上的任何内容的访问？
提前致谢。乔瓦尼