我的 USB 硬盘开始发出蜂鸣声，然后停止工作。我必须重新插入硬盘才能使其再次工作。一段时间后，听到同样的声音，它再次停止工作。我的 USB 硬盘是 Transcend StoreJet。
我的 USB 硬盘快不行了吗？我不确定，所以我在下面添加了系统日志输出文件。
顺便说一句，我使用的是Ubuntu 12.04 Beta 2。是否是因为Ubuntu beta版本的影响？
Mar 31 22:25:48 talk kernel: [13337.448109] usb 2-3: new high-speed USB device number 8 using ehci_hcd
Mar 31 22:25:48 talk kernel: [13337.582406] usb-storage 2-3:1.0: Quirks match for vid 152d pid 2329: 8020
Mar 31 22:25:48 talk kernel: [13337.582473] scsi7 : usb-storage 2-3:1.0
Mar 31 22:25:48 talk mtp-probe: checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-3"
Mar 31 22:25:48 talk mtp-probe: bus: 2, device: 8 was not an MTP device
Mar 31 22:25:49 talk kernel: [13338.622683] scsi 7:0:0:0: Direct-Access StoreJet Transcend PQ: 0 ANSI: 2 CCS
Mar 31 22:25:49 talk kernel: [13338.624995] sd 7:0:0:0: Attached scsi generic sg2 type 0
Mar 31 22:25:49 talk kernel: [13338.627119] sd 7:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Mar 31 22:25:49 talk kernel: [13338.629874] sd 7:0:0:0: [sdb] Write Protect is off
Mar 31 22:25:49 talk kernel: [13338.629885] sd 7:0:0:0: [sdb] Mode Sense: 28 00 00 00
Mar 31 22:25:49 talk kernel: [13338.630727] sd 7:0:0:0: [sdb] No Caching mode page present
Mar 31 22:25:49 talk kernel: [13338.630738] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Mar 31 22:25:49 talk kernel: [13338.633992] sd 7:0:0:0: [sdb] No Caching mode page present
Mar 31 22:25:49 talk kernel: [13338.634002] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Mar 31 22:25:49 talk kernel: [13338.656453] sdb: sdb1 sdb2
Mar 31 22:25:49 talk kernel: [13338.659225] sd 7:0:0:0: [sdb] No Caching mode page present
Mar 31 22:25:49 talk kernel: [13338.659232] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Mar 31 22:25:49 talk kernel: [13338.659238] sd 7:0:0:0: [sdb] Attached SCSI disk
Mar 31 22:26:06 talk kernel: [13354.935136] usb 2-3: USB disconnect, device number 8
Mar 31 22:26:06 talk kernel: [13354.939147] sd 7:0:0:0: [sdb] Unhandled error code
Mar 31 22:26:06 talk kernel: [13354.939153] sd 7:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Mar 31 22:26:06 talk kernel: [13354.939160] sd 7:0:0:0: [sdb] CDB: Read(10): 28 00 1d 1d 4b 3d 00 00 6f 00
Mar 31 22:26:06 talk kernel: [13354.939177] end_request: I/O error, dev sdb, sector 488459069
Mar 31 22:26:06 talk kernel: [13354.939320] sd 7:0:0:0: [sdb] Unhandled error code
Mar 31 22:26:06 talk kernel: [13354.939324] sd 7:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Mar 31 22:26:06 talk kernel: [13354.939329] sd 7:0:0:0: [sdb] CDB: Read(10): 28 00 1d 1d 4b ac 00 00 5f 00
Mar 31 22:26:06 talk kernel: [13354.939344] end_request: I/O error, dev sdb, sector 488459180
Mar 31 22:26:06 talk kernel: [13354.939470] FAT-fs (sdb2): FAT read failed (blocknr 72482)
Mar 31 22:26:59 talk kernel: [13408.240101] ieee80211 phy0: wlan0: No probe response from AP 00:0c:f6:ad:0d:e8 after 500ms, disconnecting.
Mar 31 22:26:59 talk wpa_supplicant[960]: CTRL-EVENT-DISCONNECTED bssid=00:0c:f6:ad:0d:e8 reason=4
Mar 31 22:26:59 talk kernel: [13408.300676] cfg80211: All devices are disconnected, going to restore regulatory settings
Mar 31 22:26:59 talk kernel: [13408.300687] cfg80211: Restoring regulatory settings
Mar 31 22:26:59 talk kernel: [13408.300698] cfg80211: Calling CRDA to update world regulatory domain
Mar 31 22:26:59 talk NetworkManager[860]: <info> (wlan0): supplicant interface state: completed -> disconnected
Mar 31 22:26:59 talk kernel: [13408.309382] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
Mar 31 22:26:59 talk kernel: [13408.309390] cfg80211: World regulatory domain updated:
Mar 31 22:26:59 talk kernel: [13408.309393] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Mar 31 22:26:59 talk kernel: [13408.309399] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mar 31 22:26:59 talk kernel: [13408.309403] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Mar 31 22:26:59 talk kernel: [13408.309407] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Mar 31 22:26:59 talk kernel: [13408.309411] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mar 31 22:26:59 talk kernel: [13408.309416] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mar 31 22:26:59 talk NetworkManager[860]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Mar 31 22:27:00 talk wpa_supplicant[960]: Trying to authenticate with 00:0c:f6:ad:0d:e8 (SSID='SitecomAD0DE8' freq=2462 MHz)
Mar 31 22:27:00 talk kernel: [13409.598576] wlan0: authenticate with 00:0c:f6:ad:0d:e8 (try 1)
Mar 31 22:27:00 talk wpa_supplicant[960]: Trying to associate with 00:0c:f6:ad:0d:e8 (SSID='SitecomAD0DE8' freq=2462 MHz)
Mar 31 22:27:00 talk NetworkManager[860]: <info> (wlan0): supplicant interface state: scanning -> associating
Mar 31 22:27:00 talk kernel: [13409.600886] wlan0: authenticated
Mar 31 22:27:00 talk kernel: [13409.601164] wlan0: associate with 00:0c:f6:ad:0d:e8 (try 1)
Mar 31 22:27:00 talk kernel: [13409.605796] wlan0: RX ReassocResp from 00:0c:f6:ad:0d:e8 (capab=0x431 status=0 aid=1)
Mar 31 22:27:00 talk kernel: [13409.605803] wlan0: associated
Mar 31 22:27:00 talk wpa_supplicant[960]: Associated with 00:0c:f6:ad:0d:e8
Mar 31 22:27:00 talk NetworkManager[860]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Mar 31 22:27:00 talk wpa_supplicant[960]: WPA: Key negotiation completed with 00:0c:f6:ad:0d:e8 [PTK=CCMP GTK=CCMP]
Mar 31 22:27:00 talk wpa_supplicant[960]: CTRL-EVENT-CONNECTED - Connection to 00:0c:f6:ad:0d:e8 completed (reauth) [id=0 id_str=]
Mar 31 22:27:00 talk NetworkManager[860]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Mar 31 22:27:16 talk kernel: [13425.516140] usb 2-3: new high-speed USB device number 9 using ehci_hcd
Mar 31 22:27:16 talk kernel: [13425.667791] usb-storage 2-3:1.0: Quirks match for vid 152d pid 2329: 8020
Mar 31 22:27:16 talk kernel: [13425.667849] scsi8 : usb-storage 2-3:1.0
Mar 31 22:27:16 talk mtp-probe: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-3"
Mar 31 22:27:16 talk mtp-probe: bus: 2, device: 9 was not an MTP device
Mar 31 22:27:17 talk kernel: [13426.710254] scsi 8:0:0:0: Direct-Access StoreJet Transcend PQ: 0 ANSI: 2 CCS
Mar 31 22:27:17 talk kernel: [13426.711635] sd 8:0:0:0: Attached scsi generic sg2 type 0
Mar 31 22:27:17 talk kernel: [13426.716360] sd 8:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Mar 31 22:27:17 talk kernel: [13426.717212] sd 8:0:0:0: [sdb] Write Protect is off
Mar 31 22:27:17 talk kernel: [13426.717219] sd 8:0:0:0: [sdb] Mode Sense: 28 00 00 00
Mar 31 22:27:17 talk kernel: [13426.717965] sd 8:0:0:0: [sdb] No Caching mode page present
Mar 31 22:27:17 talk kernel: [13426.717973] sd 8:0:0:0: [sdb] Assuming drive cache: write through
Mar 31 22:27:17 talk kernel: [13426.720716] sd 8:0:0:0: [sdb] No Caching mode page present
Mar 31 22:27:17 talk kernel: [13426.720723] sd 8:0:0:0: [sdb] Assuming drive cache: write through
答案1
Ubuntu 的测试版状态与您的驱动器问题是否有关系非常值得怀疑。
您的驱动器出现问题，但是根据您的日志输出，无法确定问题是否是致命的。这些是指示问题的相关行：
Mar 31 22:26:06 talk kernel: [13354.939177] end_request: I/O error, dev sdb, sector 488459069
Mar 31 22:26:06 talk kernel: [13354.939344] end_request: I/O error, dev sdb, sector 488459180
如果这些错误是由读取引起的，则可以通过简单地覆盖物理磁盘扇区来挽救它们。由于电源故障，扇区可能会写入错误的校验和。后续读取这些扇区将产生 I/O 错误，因为校验和与数据不匹配。覆盖这些扇区将修复校验和，并且读取该扇区将再次起作用。我已经用这种方法修复了几个驱动器。
但也可能是物理块确实发生了故障，并且您的驱动器已用完备用块来替换它们。在这种情况下，驱动器应该报废。
您现在应该做的是购买替换驱动器并从有问题的驱动器中复制数据。完成后，您可以尝试覆盖坏扇区并查看 I/O 错误是否消失。
答案2
我以前经历过这种情况，但你的问题可能有所不同。不管怎样，如果我所做的对你有帮助那就太好了。
有些 USB 线很旧，无法传输足够的电力来为要求更高的设备供电。一些 USB 端口很旧，也无法传输足够的电力。
我的硬盘配有 USB 线，有 2 个两个头可连接到计算机。在较新的 PC 上，我可以只使用带有“较粗”电线的 USB 头。在较新的 PC 上，我必须将两个头都插入计算机，一个用于数据传输，另一个用于传输 haddrive 开始更快旋转时可能需要的任何额外电源。
您的 USB 线是否旧了？我想除非你把 USB 线混在一起，否则不会。你的电脑比较旧吗？也许是 USB 端口本身无法为硬盘提供电力。
如果您可以将设备插入“现代”计算机而没有任何问题，那么我将问题归咎于 USB 端口。
硬盘驱动器将旋转到需要消耗更多功率的程度，然后当它没有获得功率时，它会断断续续，发出嘟嘟声，因为事情没有按计划进行，然后“重新启动”并尝试再次旋转或闲置直到您重新连接它，具体取决于驱动器。
我可能完全错了，但它发生在我身上。