我无法解决我的硬盘问题！我不知道这是否是正确的部分，但是当我在 Debian 上复制文件时突然出现这个问题。
问题是我的外部 Seagate 硬盘无法以任何方式访问...我也尝试将其连接到 Windows 计算机，但我总是遇到同样的问题...
所以我尝试在Debian上执行一些命令：
# fdisk -l
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
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: FEE5A68A-D30E-49D6-ADBD-79D7FE3FEEDA
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 961667071 960616448 458,1G Linux filesystem
/dev/sda3 961667072 976771071 15104000 7,2G Linux swap
现在，奇怪的是，如果磁盘已连接（打开/dev/sdb），该命令会打印输出，停止一段时间并结束，而如果磁盘未连接，则会显示输出并立即停止。无论如何，我的设备不在列表中。
我尝试使用lsusb，并显示磁盘，并使用lsscsi。即使在这种情况下也会显示磁盘。
我尝试过dmesg | grep sdb，这是输出的一部分：
# dmesg | grep sdb
[15564.910834] Buffer I/O error on dev sdb, logical block 3, async page read
[15565.020720] sd 2:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[15565.020757] sd 2:0:0:0: [sdb] tag#4 Sense Key : Medium Error [current]
[15565.020764] sd 2:0:0:0: [sdb] tag#4 Add. Sense: Unrecovered read error
[15565.020771] sd 2:0:0:0: [sdb] tag#4 CDB: Read(10) 28 00 00 00 00 04 00 00 01 00
[15565.020777] blk_update_request: critical medium error, dev sdb, sector 4
[15565.020787] Buffer I/O error on dev sdb, logical block 4, async page read
[15565.130678] sd 2:0:0:0: [sdb] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[15565.130700] sd 2:0:0:0: [sdb] tag#5 Sense Key : Medium Error [current]
[15565.130706] sd 2:0:0:0: [sdb] tag#5 Add. Sense: Unrecovered read error
[15565.130715] sd 2:0:0:0: [sdb] tag#5 CDB: Read(10) 28 00 00 00 00 05 00 00 01 00
[15565.130724] blk_update_request: critical medium error, dev sdb, sector 5
[15565.130737] Buffer I/O error on dev sdb, logical block 5, async page read
[15565.240859] sd 2:0:0:0: [sdb] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[15565.240898] sd 2:0:0:0: [sdb] tag#6 Sense Key : Medium Error [current]
[15565.240904] sd 2:0:0:0: [sdb] tag#6 Add. Sense: Unrecovered read error
[15565.240912] sd 2:0:0:0: [sdb] tag#6 CDB: Read(10) 28 00 00 00 00 06 00 00 01 00
[15565.240917] blk_update_request: critical medium error, dev sdb, sector 6
[15565.240927] Buffer I/O error on dev sdb, logical block 6, async page read
[15565.351140] sd 2:0:0:0: [sdb] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[15565.351180] sd 2:0:0:0: [sdb] tag#7 Sense Key : Medium Error [current]
[15565.351186] sd 2:0:0:0: [sdb] tag#7 Add. Sense: Unrecovered read error
[15565.351193] sd 2:0:0:0: [sdb] tag#7 CDB: Read(10) 28 00 00 00 00 07 00 00 01 00
[15565.351199] blk_update_request: critical medium error, dev sdb, sector 7
[15565.351209] Buffer I/O error on dev sdb, logical block 7, async page read
[15565.461412] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[15565.461443] sd 2:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[15565.461450] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[15565.461457] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
[15565.461463] blk_update_request: critical medium error, dev sdb, sector 0
[15565.461472] Buffer I/O error on dev sdb, logical block 0, async page read
[15565.570662] sd 2:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[15565.570701] sd 2:0:0:0: [sdb] tag#1 Sense Key : Medium Error [current]
[15565.570707] sd 2:0:0:0: [sdb] tag#1 Add. Sense: Unrecovered read error
[15565.570714] sd 2:0:0:0: [sdb] tag#1 CDB: Read(10) 28 00 00 00 00 01 00 00 01 00
[15565.570720] blk_update_request: critical medium error, dev sdb, sector 1
[15565.570730] Buffer I/O error on dev sdb, logical block 1, async page read
然后，我尝试了：
# sudo e2fsck -p /dev/sdb
e2fsck: Errore di input/output nell'aprire /dev/sdb
/dev/sdb:
The super-blocco could not be read or does not describe a valid ext2/ext3/ext4
file system. If the device is valid and it really contains an ext2/ext3/ext4
file system (and not swap or ufs or something else), then the super-blocco
is corrupt, and you might try running e2fsck with an alternate super-blocco:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
但是，当我遵循建议时，我总是会遇到错误......（超级块=超级块）。
Windows 检测磁盘并安装驱动程序，将其显示在设备列表和磁盘管理中（作为未分配且未初始化的磁盘）。如果我尝试初始化磁盘，则会出现循环冗余检查错误。
如果我chkdsk在 Windows 上尝试，它不起作用，因为它没有检测到磁盘。
奇怪的是，当我第一次使用 Debian 插入磁盘时，它立即检测到它！
请帮帮我，我已经好几天面对这个问题而没有找到解决方案了！
答案1
出现此行为的原因是硬盘驱动器的电子设备和接口可能工作正常，但物理部分（旋转盘片/磁头）出现问题。如果接口或电子设备本身无法工作，您将无法正常工作。根本无法检测到驱动器。当要求驱动器访问磁盘时，如果检测到错误，它会重试多次，这就是为什么在尝试读取数据时会出现长时间延迟的原因。
你可能能够使用恢复工具恢复一些数据，例如摄影记录，但这取决于驱动器是否可读。如果驱动器本身无法读取磁盘，那么再多的软件也无法帮助您从驱动器上获取数据：您需要将其带到磁盘恢复服务处。