主页 / unix / 问题 / 748502
Accepted
sgbrown
Asked: 2023-06-10 20:20:04 +0800 CST

Smartctl 是否需要文件系统来运行测试，我的驱动器是否可以？

  • 772

我有一个全新的驱动器，我想在使用前对其进行测试。刚刚安装它，没有格式化/分区，也没有在它上面创建文件系统。 我做的第一件事是检查 smartctl 统计数据，然后开始一个长期的俘虏测试。

等待所需的 12 小时后，我注意到测试被中断，并记录了一个错误。我又开始了两次测试，每次启动测试时都会立即记录错误。请参阅下面的 smartctl 统计信息：

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-150-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     ST8000NM017B-2TJ103
Serial Number:    WWZ2AFQF
LU WWN Device Id: 5 000c50 0e71315e1
Firmware Version: SN01
User Capacity:    8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Jun 10 08:08:32 2023 EDT
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:      (  41) The self-test routine was interrupted
                                        by the host with a hard or soft reset.
Total time to complete Offline
data collection:                (  567) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        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:        ( 702) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x70bd) SCT Status supported.
                                        SCT Error Recovery Control 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   100   100   044    Pre-fail  Always       -       9402
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   045    Pre-fail  Always       -       21867
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       17
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       1
 18 Unknown_Attribute       0x000b   100   100   050    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   253   000    Old_age   Always       -       12885098499
190 Airflow_Temperature_Cel 0x0022   067   066   000    Old_age   Always       -       33 (Min/Max 24/34)
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       39
194 Temperature_Celsius     0x0022   033   040   000    Old_age   Always       -       33 (0 24 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       0 (137 91 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       0
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       9402

SMART Error Log Version: 1
ATA Error Count: 3
        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 3 occurred at disk power-on lifetime: 17 hours (0 days + 17 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      17:21:46.602  NOP [Abort queued commands]
  b0 d4 00 82 4f c2 00 00      17:20:45.112  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 01 00 4f c2 00 00      17:20:45.112  SMART READ DATA
  ec 00 01 00 00 00 00 00      17:20:45.105  IDENTIFY DEVICE
  ec 00 01 00 00 00 00 00      17:20:45.104  IDENTIFY DEVICE
Error 2 occurred at disk power-on lifetime: 17 hours (0 days + 17 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      17:15:48.188  NOP [Abort queued commands]
  b0 d4 00 82 4f c2 00 00      17:14:46.401  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 01 00 4f c2 00 00      17:14:46.400  SMART READ DATA
  ec 00 01 00 00 00 00 00      17:14:46.392  IDENTIFY DEVICE
  ec 00 01 00 00 00 00 00      17:14:46.391  IDENTIFY DEVICE

Error 1 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      00:08:36.002  NOP [Abort queued commands]
  b0 d4 00 82 4f c2 00 00      00:07:34.853  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 01 00 4f c2 00 00      00:07:34.814  SMART READ DATA
  ec 00 01 00 00 00 00 00      00:07:34.806  IDENTIFY DEVICE
  ec 00 01 00 00 00 00 00      00:07:34.805  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended captive    Interrupted (host reset)      90%        17         -
# 2  Extended captive    Interrupted (host reset)      90%        17         -
# 3  Extended captive    Interrupted (host reset)      90%         0         -

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.

原始读取/查找错误率也相当高，但我不确定 smartctl 的格式，如果这些值只是编码......

Smartctl 不需要格式化的驱动器/带有文件系统的驱动器才能正常运行，对吗？这是意想不到的结果？如果是这样，在 RMA 之前我还应该运行其他测试吗？提前谢谢你的帮助！

hard-disk

1 个回答

  1. Best Answer
    1. SMART selt-tests 在磁盘内运行，不需要操作系统。运行任何 LiveCD，，smartctl -t long /dev/sda等待它说的时间，检查结果。在整个测试过程中，PC 必须处于运行状态。您也不能让 PC 进入睡眠状态。
    2. 您的驱动器看起来非常健康，此类错误Error 3 occurred at disk power-on lifetime通常是良性的。我有过类似错误的驱动器，在使用它们十多年后仍然处于完美状态。请检查 smartmontools 7.3 是否也报告此错误。它可能只特定于旧版本。

    不过，如果您想对其进行 RMA，请务必去做。从一开始就出现任何 SMART 错误并不是一种愉快的感觉。

    # 1  Extended captive    Interrupted (host reset)      90%        17

    意味着您不允许测试完成。-t long完整的驱动器测试可能需要大约 24 小时才能完成。

    我总是对新驱动器进行长时间的自检。让我稍微安心。

    • 1

相关问题