这是关于我的可能损坏的硬盘的 SMART 信息：
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.18.0-15-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MK..76GSX
Device Model: TOSHIBA MK3276GSX
Serial Number: 9296Y9FOF
LU WWN Device Id: 5 000039 44d00306b
Firmware Version: GS001C
User Capacity: 320,072,933,376 bytes [320 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Fri May 17 11:29:47 2019 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x51) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 81) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0027 100 100 050 Pre-fail Always - 0
3 Spin_Up_Time 0x0023 100 100 002 Pre-fail Always - 1223
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 5405
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x002f 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0025 100 100 050 Pre-fail Offline - 0
9 Power_On_Minutes 0x0032 089 089 000 Old_age Always - 75h+35m
10 Spin_Retry_Count 0x0033 208 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 5380
183 Runtime_Bad_Block 0x0032 100 100 001 Old_age Always - 0
184 End-to-End_Error 0x0033 100 100 097 Pre-fail Always - 0
185 Unknown_Attribute 0x0032 100 100 001 Old_age Always - 65535
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 599
188 Command_Timeout 0x0032 100 099 000 Old_age Always - 8
189 High_Fly_Writes 0x003a 100 100 001 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 070 047 040 Old_age Always - 30 (Min/Max 29/30)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 557
192 Power-Off_Retract_Count 0x0022 100 100 000 Old_age Always - 10092698
193 Load_Cycle_Count 0x0032 088 088 000 Old_age Always - 127749
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 1
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 1515 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 1515 occurred at disk power-on lifetime: 4512 hours (188 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 3a ed c8 de 6b Error: UNC at LBA = 0x0bdec8ed = 199149805
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 38 e8 c8 de 40 08 03:59:07.091 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 03:59:07.090 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 03:59:07.090 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 03:59:07.090 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 00 03:59:07.090 SET FEATURES [Enable SATA feature]
Error 1514 occurred at disk power-on lifetime: 4512 hours (188 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 c2 ed c8 de 6b Error: UNC at LBA = 0x0bdec8ed = 199149805
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 c0 e8 c8 de 40 08 03:59:03.044 READ FPDMA QUEUED
61 28 b8 c0 c8 de 40 08 03:59:03.044 WRITE FPDMA QUEUED
ef 10 02 00 00 00 a0 00 03:59:03.043 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 03:59:03.043 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 03:59:03.043 SET FEATURES [Set transfer mode]
Error 1513 occurred at disk power-on lifetime: 4512 hours (188 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 4a ed c8 de 6b Error: UNC at LBA = 0x0bdec8ed = 199149805
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 48 e8 c8 de 40 08 03:58:59.012 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 03:58:59.012 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 03:58:59.011 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 03:58:59.011 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 00 03:58:59.010 SET FEATURES [Enable SATA feature]
Error 1512 occurred at disk power-on lifetime: 4512 hours (188 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 ba ed c8 de 6b Error: UNC at LBA = 0x0bdec8ed = 199149805
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 b8 e8 c8 de 40 08 03:58:54.985 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 03:58:54.984 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 03:58:54.983 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 03:58:54.983 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 00 03:58:54.983 SET FEATURES [Enable SATA feature]
Error 1511 occurred at disk power-on lifetime: 4512 hours (188 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 0a ed c8 de 6b Error: UNC at LBA = 0x0bdec8ed = 199149805
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 08 e8 c8 de 40 08 03:58:50.953 READ FPDMA QUEUED
60 80 f8 28 c9 de 40 08 03:58:50.953 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 03:58:50.952 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 03:58:50.952 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 03:58:50.951 SET FEATURES [Set transfer mode]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90% 4508 199149805
# 2 Short offline Completed: read failure 90% 4508 199149805
# 3 Short offline Completed: read failure 90% 4507 199149805
# 4 Extended offline Completed: read failure 90% 4507 199149805
# 5 Short offline Completed: read failure 90% 4507 199149805
# 6 Extended offline Completed: read failure 90% 4507 199149805
# 7 Short offline Completed without error 00% 2 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Current_Pending_Sector的值是1且Error: UNC at LBA = 0x0bdec8ed = 199149805已发出 8 次信号。我也badblocks使用 Ubuntu 18.04 运行，但出现8/0/0错误。从199149800到 的扇区199149807被视为已损坏。
我读过一些关于这些参数的有争议的观点。在这个答案，例如，建议Current_Pending_Sector健康的磁盘不应该增加。其他人则建议任何非零值都是更换磁盘的强烈建议。
- 该硬盘的状况有多严重？
- 我可以运行其他更明确的测试吗？
答案1
硬盘有 8 个坏扇区不是问题(*)。
随着时间的推移，坏扇区的数量预计会增加慢慢地。
在写入磁盘时，控制器会注意到写入错误并将该数据写入磁盘上的另一个扇区。磁盘检查程序仍会将其显示为坏块，但那里没有写入任何内容。因此，你实际上并不关心。
(*) 出现问题的地方是块失败后这个已经写完了。这将在您的应用程序中显示为读取错误。然后，乐趣就开始了。您可以从备份中检索它或重新创建它吗？如果是的话，它将被写入另一个块。如果没有......
如果您的驱动器没有性能问题（即引发读/写错误），请不要担心。每年检查几次坏扇区的数量。
如果您遇到读/写错误的性能问题（注意，这不是开发人员/用户抱怨系统有多慢）。您会注意到坏块的数量显着增加。这表明磁盘出现故障。
曾几何时，我有一个数字（占总区块的百分比），这个数字是可以接受的坏的（也许是 5%？）。当这个数字开始增长（可能高达 8%？）时，您就可以开始考虑在有钱和停机时间的情况下更换驱动器了。
如今，驱动器的可靠性已经提高。一些硬件制造商甚至声称他们的驱动器上没有坏扇区。 （ROTFL）。
也许其他人有一个很好的数字来说明有多少坏扇区需要担心。
恕我直言，磁盘没有出现故障。完全不用担心。
0.02 美元
答案2
首先要做的就是备份、备份、备份！在任何情况下，重要数据都必须在不同的磁盘上有一个计划的备份系统（而不是在同一磁盘上分区）
首先回到基础，如果机器电源100%稳定，没有任何电力变化，硬盘始终打开，温度/空气/湿度条件最佳，这将避免99%的磁盘故障，确实在这些条件下不经常满足（这是为了让您优化这些条件）。
当您使用机械磁盘时，预期寿命在很大程度上取决于磁盘上的数据碎片状态以及磁盘的使用频率，因为这两个事实使磁盘头移动很多或不移动那么多，从而消耗磁盘的使用寿命，我建议您检查数据碎片，并最终在需要时按计划修复它......
大多数情况下，机械磁盘在即将发生故障时会开始发出异常噪音，因此请仔细聆听磁盘的噪音。
尽可能避免断电，这对机械磁盘非常不利。
回到你的问题，坏扇区是否值得关注？根据我的恢复经验，我想说这取决于每个磁盘型号，有些会在 1000 个坏扇区后保持坚如磐石，而另一些则在出现坏扇区后很快就会死掉，即使整体技术相同，每个制造商都在应用它甚至一个模型与另一个模型也不同。对于所有磁盘来说，可以肯定的是，您必须密切关注该值，因为它往往会增长。
大多数现代系统文件 NTFS/EXT4 和磁盘固件都有一个良好的坏扇区管理系统，当磁盘只有很少的坏扇区时，您不必担心，但请记住，需要注意这一点，因为它可能会导致数据丢失腐败。
一些制造商拥有专有工具，可以更深入地检查我为您的情况找到的磁盘ToshibaStorageDiagnosticTool，但这似乎并没有提供与您已有的信息相比更多的信息；归根结底，这些工具只能向我们发出有关某些情况的警报，我建议始终处于警报模式（备份等），因为我知道很多磁盘在停机之前不会发出警告。
最后，有一些技术可以恢复坏扇区，如果您的磁盘是那种在有坏扇区时保持稳定的磁盘，这会很有帮助。 硬盘再生器非常擅长这一点。 （我认为他们是该技术的发明者）
结论：无论 SSD 或 HDD 是否有坏扇区，请观察您的磁盘并在不同的设备上定期进行备份。