flyzy博客
分享便宜VPS与网络优惠
搬瓦工

硬盘坏道会自己消失吗?

前天ovh独服看到197 Current_Pending_Sector 数值变成1,然后用badblock扫描坏道果然发现了4个,我也没继续修复。只是开始备份数据准备找客服换硬盘。
结果今天数据快拷完了重新检测了下发现smart 197又变成0了,重扫之前坏道的块也扫不到坏道了。这是怎么回事?

黑龙江省网友说:这个叫unstable

山东省网友说:我觉得取决于扫描软件

安徽省网友说:root@ns3148808:~# smartctl -l error /dev/sdb
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-19-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 20 (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 20 occurred at disk power-on lifetime: 19896 hours (829 days + 0 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  — — — — — — —
  40 43 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  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 20 80 6a 80 40 08  42d+22:21:33.350  READ FPDMA QUEUED
  61 08 28 10 9a c7 40 08  42d+22:21:30.905  WRITE FPDMA QUEUED
  ea 00 00 00 00 00 a0 08  42d+22:21:30.901  FLUSH CACHE EXT
  60 08 00 88 0e 4c 40 08  42d+22:21:30.873  READ FPDMA QUEUED
  60 08 80 80 0e 4c 40 08  42d+22:21:30.872  READ FPDMA QUEUED

Error 19 occurred at disk power-on lifetime: 19896 hours (829 days + 0 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  — — — — — — —
  40 43 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  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 b0 80 6a 80 40 08  42d+22:21:30.675  READ FPDMA QUEUED
  60 08 08 60 0e 4c 40 08  42d+22:21:29.729  READ FPDMA QUEUED
  61 08 a8 e8 27 04 40 08  42d+22:21:29.422  WRITE FPDMA QUEUED
  61 08 a0 f8 27 04 40 08  42d+22:21:29.422  WRITE FPDMA QUEUED
  60 08 98 38 bf f8 40 08  42d+22:21:29.343  READ FPDMA QUEUED

Error 18 occurred at disk power-on lifetime: 19896 hours (829 days + 0 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  — — — — — — —
  40 43 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  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 98 80 6a 80 40 08  42d+22:21:28.042  READ FPDMA QUEUED
  60 08 a8 98 6e 3e 40 08  42d+22:21:25.588  READ FPDMA QUEUED
  61 08 a0 28 99 c7 40 08  42d+22:21:25.588  WRITE FPDMA QUEUED
  ea 00 00 00 00 00 a0 08  42d+22:21:25.584  FLUSH CACHE EXT
  60 08 68 50 73 f7 40 08  42d+22:21:25.535  READ FPDMA QUEUED

Error 17 occurred at disk power-on lifetime: 19896 hours (829 days + 0 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  — — — — — — —
  40 43 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  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 60 80 6a 80 40 08  42d+22:21:25.375  READ FPDMA QUEUED
  60 08 78 78 87 3f 40 08  42d+22:21:25.364  READ FPDMA QUEUED
  61 08 10 20 4c 44 40 08  42d+22:21:25.085  WRITE FPDMA QUEUED
  60 08 c8 e0 16 c1 40 08  42d+22:21:24.035  READ FPDMA QUEUED
  60 08 48 48 73 f7 40 08  42d+22:21:23.145  READ FPDMA QUEUED

Error 16 occurred at disk power-on lifetime: 19896 hours (829 days + 0 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  — — — — — — —
  40 43 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  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 78 80 6a 80 40 08  42d+22:21:22.434  READ FPDMA QUEUED
  60 00 40 10 9f 22 40 08  42d+22:21:19.997  READ FPDMA QUEUED
  60 00 38 10 9e 22 40 08  42d+22:21:19.997  READ FPDMA QUEUED
  61 48 a8 28 98 c7 40 08  42d+22:21:19.996  WRITE FPDMA QUEUED
  61 b8 70 00 58 cc 40 08  42d+22:21:19.995  WRITE FPDMA QUEUED

甘肃省网友说:坏道是物理损坏,只能把这片区域屏蔽掉不用…不会消失

青海省网友说:如果自己消失了你还敢用吗?

广东省网友说:机械一般直接屏蔽那个坏道,你扫完他就当好了

辽宁省网友说:c5 相当大一部分都是可以自动修复,但是我有时候备份数据后一般都是标准格式化一次,一般情况下会修复这种错误,如果标准格式化没有清除这种错误,那么很大概率就是物理坏道了

四川省网友说:可以屏蔽继续用

赞(0) 打赏
关注我们
未经允许不得转载:flyzy博客 » 硬盘坏道会自己消失吗?
分享到: 更多 (0)

这是一种鼓励

支付宝扫一扫打赏

微信扫一扫打赏