Smartctl에서 테스트를 실행하려면 파일 시스템이 필요하며, 내 드라이브는 괜찮나요?

Smartctl에서 테스트를 실행하려면 파일 시스템이 필요하며, 내 드라이브는 괜찮나요?

사용하기 전에 테스트해보고 싶은 새 드라이브가 있습니다. 방금 설치했지만 포맷/파티셔닝을 하지 않았거나 파일 시스템을 생성하지 않았습니다. 가장 먼저 한 일은 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 전에 실행해야 할 다른 테스트? 당신의 도움에 미리 감사드립니다!

답변1

  1. SMART 자체 테스트는 디스크 내에서 실행되며 운영 체제가 필요하지 않습니다. LiveCD를 실행하고 smartctl -t long /dev/sda메시지가 나타날 때까지 기다린 후 결과를 확인하십시오. 전체 테스트가 진행되는 동안 PC가 실행되고 있어야 합니다. 또한 PC를 절전 모드로 전환할 수 없습니다.
  2. 드라이브는 완벽하게 건강한 것으로 보이며 이러한 오류는 Error 3 occurred at disk power-on lifetime일반적으로 심각하지 않습니다. 10년 넘게 사용한 후에도 여전히 완벽한 상태를 유지하고 있는 하드 드라이브에도 비슷한 오류가 있습니다. smartmontools 7.3에서도 이 오류가 보고되는지 확인하세요. 이전 버전에만 해당될 수 있습니다.

그러나 RMA를 수행하려면 반드시 수행하십시오. 처음부터 SMART 실수를 저지르는 것은 기분 좋은 일이 아닙니다.

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

테스트가 완료되는 것을 허용하지 않는다는 의미입니다. 드라이브 전체 테스트를 -t long완료하는 데 약 24시간이 걸릴 수 있습니다.

나는 항상 새 드라이브에 대해 장기간 자체 테스트를 실행합니다. 나에게 약간의 마음의 평화를 가져다줍니다.

관련 정보