我正在尝试使用内部 2.5 英寸 HDD 作为我的外部存储介质和备份。在我的一些文件损坏之前,该 HDD 之前已经在 Windows 计算机上运行了很长时间,因此我只是将其更改为SSD。CrystalDiskInfo 报告驱动器的运行状况为“良好”,但是 HDDScan 显示“UltraDMA CRC 错误”警告。
smartctl -a
这是其运行结果:
smartctl 7.3 2022-02-28 r5338 [x86_64-w64-mingw32-w10-21H2] (sf-7.3-1)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Mobile HDD
Device Model: ST1000LM035-1RK172
Firmware Version: SDM1
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database 7.3/5319
ATA Version is: ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x71) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 169) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 072 051 006 Pre-fail Always - 15037148
3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 065 065 020 Old_age Always - 36007
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 080 060 045 Pre-fail Always - 22014115380
9 Power_On_Hours 0x0032 100 086 000 Old_age Always - 55 (236 20 0)
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 092 020 Old_age Always - 56
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 3990
188 Command_Timeout 0x0032 100 081 000 Old_age Always - 30067195949
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 068 049 040 Old_age Always - 32 (Min/Max 29/32)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 197
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 69
193 Load_Cycle_Count 0x0032 064 064 000 Old_age Always - 73637
194 Temperature_Celsius 0x0022 032 051 000 Old_age Always - 32 (0 18 0 0 0)
197 Current_Pending_Sector 0x0012 100 051 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 051 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 3
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 12591 (154 139 0)
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 98336960706
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 114926523300
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 3475 (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 3475 occurred at disk power-on lifetime: 29 hours (1 days + 5 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 51 00 88 7d f4 09 Error: UNC at LBA = 0x09f47d88 = 167017864
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 00 08 88 7d f4 49 00 00:38:49.208 READ FPDMA QUEUED
60 00 08 80 7d f4 49 00 00:38:49.195 READ FPDMA QUEUED
60 00 08 b0 a8 21 49 00 00:38:49.182 READ FPDMA QUEUED
60 00 08 a8 a8 21 49 00 00:38:49.181 READ FPDMA QUEUED
60 00 08 a0 a8 21 49 00 00:38:49.181 READ FPDMA QUEUED
Error 3474 occurred at disk power-on lifetime: 29 hours (1 days + 5 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 51 00 80 7d f4 09 Error: UNC at LBA = 0x09f47d80 = 167017856
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 00 08 80 7d f4 49 00 00:38:46.657 READ FPDMA QUEUED
60 00 08 78 7d f4 49 00 00:38:46.625 READ FPDMA QUEUED
ef 10 03 00 00 00 a0 00 00:38:46.615 SET FEATURES [Enable SATA feature]
ef 10 02 00 00 00 a0 00 00:38:46.605 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 00:38:46.578 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 3473 occurred at disk power-on lifetime: 29 hours (1 days + 5 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 51 00 78 7d f4 09 Error: UNC at LBA = 0x09f47d78 = 167017848
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 00 08 78 7d f4 49 00 00:38:44.127 READ FPDMA QUEUED
60 00 08 70 7d f4 49 00 00:38:44.095 READ FPDMA QUEUED
ef 10 03 00 00 00 a0 00 00:38:44.085 SET FEATURES [Enable SATA feature]
ef 10 02 00 00 00 a0 00 00:38:44.076 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 00:38:44.049 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 3472 occurred at disk power-on lifetime: 29 hours (1 days + 5 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 51 00 70 7d f4 09 Error: UNC at LBA = 0x09f47d70 = 167017840
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 00 08 70 7d f4 49 00 00:38:41.598 READ FPDMA QUEUED
60 00 08 68 7d f4 49 00 00:38:41.566 READ FPDMA QUEUED
ef 10 03 00 00 00 a0 00 00:38:41.556 SET FEATURES [Enable SATA feature]
ef 10 02 00 00 00 a0 00 00:38:41.547 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 00:38:41.520 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 3471 occurred at disk power-on lifetime: 29 hours (1 days + 5 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 51 00 68 7d f4 09 Error: UNC at LBA = 0x09f47d68 = 167017832
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 00 08 68 7d f4 49 00 00:38:39.013 READ FPDMA QUEUED
60 00 08 60 7d f4 49 00 00:38:38.987 READ FPDMA QUEUED
ef 10 03 00 00 00 a0 00 00:38:38.977 SET FEATURES [Enable SATA feature]
ef 10 02 00 00 00 a0 00 00:38:38.968 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 00:38:38.941 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
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% 22 282912
# 2 Extended offline Completed: read failure 90% 20 282912
# 3 Extended offline Completed: read failure 90% 18 282912
# 4 Conveyance offline Completed: read failure 90% 18 282912
# 5 Short offline Completed: read failure 80% 18 282912
# 6 Extended offline Completed: read failure 90% 17 282912
# 7 Extended offline Completed: read failure 90% 2 64400520
# 8 Extended offline Completed: read failure 90% 2 64400520
# 9 Extended offline Completed: read failure 90% 2 64400520
#10 Extended offline Completed without error 00% 9245 -
#11 Short offline Completed without error 00% 4741 -
#12 Short offline Completed without error 00% 4667 -
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.
这让我有点困惑。该驱动器通过 USB(适配器)连接到我的计算机,其上没有品牌名称,但smartctl
显示它是“USB JMicron”。此“USB JMicron”适配器是否导致“UltraDMA CRC 错误”或其他问题?
由于我不确定是什么导致了当时的数据损坏,我想知道根据来自 的信息,该驱动器是否实际上安全可靠smartctl
。任何有关破译诊断信息的帮助将不胜感激。
答案1
USB-sATA:此类设备必须将USB命令集转换为sATA命令集。最重要和最常见的是读取扇区(块)和写入它的命令。某些 USB/sATA 设备不转换其他命令,因此smartctl
无法hdparm
获取服务信息。有些(包括 JMicron)会翻译所有命令。新smartctl
版本可以自动检测芯片组并使用它。
您smartctl
可以启动磁盘自动测试,也可以仅收集保存的记录信息。对于磁盘来说,这一点194 Temperature
很重要,因为如果温度接近居里温度,磁性能会发生不可逆的退化。工作温度保持在40摄氏度以下是安全的。 (越少越好)。一些 HD 也会记住温度历史。
硬盘通常有一些保留扇区(块)供 mg 的某些部分使用。表面状况不佳。此类扇区的数量为5 Reallocated_Sector_Ct
。如果该数字小于 100,则不得表示磁盘不可用。跳转到保留扇区时,负载可能会增加一些。如果这个数字随着时间的推移而增加,那就更危险了。在这种情况下,不建议使用它。
这197 Current_Pending_Sector
可能会更烦人,因为磁盘控制器无法通过其 CRC 确认扇区内容。有时,此类扇区可能是意外创建的,并且可以在重写后将其消除,但在某些情况下,它是在重新分配之前。
我真的不确定 Seagate 的意思,199 UDMA_CRC_Error_Count
但是当磁头飞过 mg 表面时,就会发生寻道错误,就像代表读取的 0.01% 以下的读取错误一样。
SSD 不会因高温而性能下降太多,并且通常不会消耗太多功率。它们还有一些备用块(不是扇区,而是更大的块),因为需要立即擦除和写入该块。 SSD 控制器对块进行大量处理,因为每次写入操作都会缩短其寿命。因此你必须观看241 Total_LBAs_Written
。
你可以看到SSD的TBW参数是什么缩写太字节写入。
如果将此数字除以 SSD 容量,您可以看到,在便宜的 SSD 中,一个块可以写入不到 100 次,而 cca 则可以写入 500 次。只有用于服务器的 SSD 才能使一个块的写入次数超过 10000 次。
我的意见:你的磁盘看起来状况良好(不是很好),但请记住,它的磁头已经飞了近一年半了,所以我建议购买一个外部盒子并使用该磁盘进行备份或存档。在下次使用之前,您可以将整个磁盘清零并smartctl -x
再次检查。如果没有或只有很小的变化,那就可以了。
答案2
自动离线数据收集:已禁用 — 对于某些驱动器,此设置会导致 SMART 值无法正确更新,因此请考虑启用它。
UDMA CRC 错误有时会发生。如果该值很高并且持续上升,您可能需要更换 SATA 电缆或端口(或整个 USB 外壳)。
开机时间计数器似乎已溢出(对于长时间运行的驱动器来说是正常的)或被故意重置为 0(有时会发生在 Ebay 上销售的驱动器上)。
该驱动器的真正问题是它当前在自检中存在读取错误;总的来说,这似乎是一个较旧的驱动器,现在显示出故障的迹象(这些读取故障已经丢失了数据)。
如果您仍需要恢复该驱动器的任何数据,ddrescue
请执行下一步。
如果您不关心驱动器上的数据,则可以在破坏性写入模式下运行坏块测试(非破坏性写入模式不会覆盖读取错误,因此无助于重新分配扇区)或使用其他工具覆盖它。
然后再次检查 SMART 并运行另一个自检。
不管怎样,我不会再对这个驱动器抱有太大的信任。
答案3
你只有 3 个这样的错误,我不会担心这个。
然而,我担心的是 Command_Timeout ,它非常高(30,067,195,949),但如果您没有任何明显的减速,则无需担心。这并不意味着驱动器即将失效,但可能表明存在一些问题,例如接口问题。