smartctl의 결과로 판단하면 SSD가 죽어가고 있습니까?

smartctl의 결과로 판단하면 SSD가 죽어가고 있습니까?

어제부터 SSD가 BIOS에서 누락되는 경우가 있습니다. 그런데 오늘 아침 부팅 메뉴에서 완전히 사라졌습니다. 문제 해결 과정의 일환으로 SATA 케이블을 교체하고 전원 코드를 다시 연결했는데, 어느 시점에서 부팅 시 인식이 되었습니다. 아무런 문제 없이 OS(Mint 18)에 진입했습니다.

제가 중요하게 생각하는 데이터를 백업한 후 smartctl간단한 테스트를 실행해 보니 다음과 같은 결과가 나왔습니다. 이 문제에 대해 잘 아는 사람이라면 문제의 SSD가 실제로 포기 직전인지 아니면 언급된 오류를 수정할 수 있는 희망이 있는지 확인할 수 있습니까?

smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.15.0-45-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Crucial/Micron RealSSD m4/C400/P400
Device Model:     M4-CT064M4SSD2
Serial Number:    0000000011270313DEA7
LU WWN Device Id: 5 00a075 10313dea7
Firmware Version: 070H
User Capacity:    64,023,257,088 bytes [64.0 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Mon Mar  4 13:22:22 2019 +06
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:  (0x80) Offline data collection activity
                    was never started.
                    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:        (  295) 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:    (   2) minutes.
Extended self-test routine
recommended polling time:    (   4) minutes.
Conveyance self-test routine
recommended polling time:    (   3) minutes.
SCT capabilities:          (0x003d) 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   084   084   050    Pre-fail  Always       -       17
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       18432
  9 Power_On_Hours          0x0032   100   100   001    Old_age   Always       -       9383
 12 Power_Cycle_Count       0x0032   100   100   001    Old_age   Always       -       5270
170 Grown_Failing_Block_Ct  0x0033   100   100   010    Pre-fail  Always       -       9
171 Program_Fail_Count      0x0032   100   100   001    Old_age   Always       -       483
172 Erase_Fail_Count        0x0032   100   100   001    Old_age   Always       -       0
173 Wear_Leveling_Count     0x0033   095   095   010    Pre-fail  Always       -       174
174 Unexpect_Power_Loss_Ct  0x0032   100   100   001    Old_age   Always       -       164
181 Non4k_Aligned_Access    0x0022   100   100   001    Old_age   Always       -       1555 506 1049
183 SATA_Iface_Downshift    0x0032   100   100   001    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   050    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   001    Old_age   Always       -       25
188 Command_Timeout         0x0032   100   100   001    Old_age   Always       -       0
189 Factory_Bad_Block_Ct    0x000e   100   100   001    Old_age   Always       -       49
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       0
195 Hardware_ECC_Recovered  0x003a   100   100   001    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   100   100   001    Old_age   Always       -       9
197 Current_Pending_Sector  0x0032   100   100   001    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   001    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   001    Old_age   Always       -       1019
202 Perc_Rated_Life_Used    0x0018   095   095   001    Old_age   Offline      -       5
206 Write_Error_Rate        0x000e   100   100   001    Old_age   Always       -       483

SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 3

ATA Error Count: 0
    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 0 occurred at disk power-on lifetime: 9381 hours (390 days + 21 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
  -- -- -- -- -- -- --
  00 50 08 d0 34 2c 40   at LBA = 0x002c34d0 = 2897104

  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 d0 34 2c 40 00  42d+22:22:28.928  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00  42d+22:22:28.928  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00  42d+22:22:28.928  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00  42d+22:22:28.928  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00  42d+22:22:28.928  SET FEATURES [Set transfer mode]

Error -1 occurred at disk power-on lifetime: 9381 hours (390 days + 21 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
  -- -- -- -- -- -- --
  00 50 08 d0 34 2c 40   at LBA = 0x002c34d0 = 2897104

  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 d0 34 2c 40 00  42d+22:22:28.928  READ FPDMA QUEUED
  60 00 08 c8 34 2c 40 00  42d+22:22:28.928  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00  42d+22:22:28.928  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00  42d+22:22:28.928  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00  42d+22:22:28.928  IDENTIFY DEVICE

Error -2 occurred at disk power-on lifetime: 9381 hours (390 days + 21 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
  -- -- -- -- -- -- --
  00 50 30 d0 34 2c 40   at LBA = 0x002c34d0 = 2897104

  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 30 c8 34 2c 40 00  42d+22:22:28.928  READ FPDMA QUEUED
  60 00 90 20 49 2d 40 00  42d+22:22:28.928  READ FPDMA QUEUED
  60 03 88 48 19 2d 40 00  42d+22:22:28.928  READ FPDMA QUEUED
  60 00 90 b8 38 2d 40 00  42d+22:22:28.928  READ FPDMA QUEUED
  60 00 90 e8 30 2d 40 00  42d+22:22:28.928  READ FPDMA QUEUED

Error -3 occurred at disk power-on lifetime: 9381 hours (390 days + 21 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
  -- -- -- -- -- -- --
  00 50 80 f8 f8 b4 40   at LBA = 0x00b4f8f8 = 11860216

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 80 40 0b 7c 40 00  42d+21:42:28.928  WRITE FPDMA QUEUED
  61 00 40 80 09 7c 40 00  42d+21:42:28.928  WRITE FPDMA QUEUED
  61 00 40 00 09 7c 40 00  42d+21:42:28.928  WRITE FPDMA QUEUED
  61 00 88 00 f8 b4 40 00  42d+21:42:28.928  WRITE FPDMA QUEUED
  61 00 40 00 14 58 40 00  42d+21:42:28.928  WRITE FPDMA QUEUED

Error -4 occurred at disk power-on lifetime: 9380 hours (390 days + 20 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
  -- -- -- -- -- -- --
  00 50 10 40 0b 7c 40   at LBA = 0x007c0b40 = 8129344

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 10 00 2e 17 40 00  42d+21:32:28.928  WRITE FPDMA QUEUED
  61 00 10 88 2d 17 40 00  42d+21:32:28.928  WRITE FPDMA QUEUED
  61 00 08 58 2d 17 40 00  42d+21:32:28.928  WRITE FPDMA QUEUED
  61 00 10 40 2d 17 40 00  42d+21:32:28.928  WRITE FPDMA QUEUED
  61 00 18 20 2d 17 40 00  42d+21:32:28.928  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      9383         2719472
# 2  Vendor (0xff)       Completed without error       00%      9289         -
# 3  Vendor (0xff)       Completed without error       00%      7651         -
# 4  Vendor (0xff)       Completed without error       00%      6793         -
# 5  Vendor (0xff)       Completed without error       00%      6785         -
# 6  Vendor (0xff)       Completed without error       00%      6570         -
# 7  Vendor (0xff)       Completed without error       00%      6171         -

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.

추신. 증상이 처음 나타났을 때 initramfs 명령 프롬프트에서 멈췄다는 점도 언급할 가치가 있을 것입니다. 그러다가 fschkSSD에서 한 번 실행해 봤는데 그 때 문제가 해결된 것 같았습니다.

답변1

제목 질문에 대답하자면 아니요, SMART 결과 자체는 걱정할 가치가 없습니다. 드라이브에 읽을 수 없는 섹터가 있더라도 다음에 쓸 때 내부 예비 영역에서 해당 섹터를 재할당합니다. 이제 Reallocated_Event_Count지금까지 교체를 위해 예약된 플래시 블록은 9개(그림에 표시된 대로 9 * 2048 = 18432 섹터에 해당)뿐이라고 합니다 .Reallocated_Sector_Ct

현재 읽을 수 없는 섹터가 정상적인 시스템 작동으로 덮어쓰여질 때까지 기다리지 않으려면 다음을 수행하십시오.dd또는 같은 도구를 사용하여 수동으로 작성합니다.hdparm, 그러나 확실히 마음이 약한 사람을 위한 것은 아닙니다(쓰기 위치를 설정할 때 실수를 하면 완벽하게 유효한 일부 데이터가 손실됩니다).

그러나 언급한 다른 증상(예: 전원을 켰을 때 드라이브가 인식되지 않는 경우)은 실제로 전자 장치의 수명이 다했음을 나타낼 수 있습니다. 대부분의 경우 이러한 문제는 PSU 또는 케이블 연결 문제로 인해 발생하므로 드라이브를 다른 컴퓨터에 연결하거나 PSU를 교체해 보십시오.

SMART 테스트는 일반적으로 전자 장치에 문제가 있는지 알려주지 않으며 주로 컨트롤러가 아닌 실제 저장 매체를 테스트합니다.

답변2

정보

Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed.

그리고

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      9383         2719472

드라이브에 결함이 있어 드라이브 자체가 논리 블록 주소 2719472를 올바르게 읽을 수 없음을 나타냅니다.
다음 위치에서도 커널 메시지를 찾을 수 있습니다./var/log/메시지로그는 다음과 유사합니다.이것:

100%에 가깝게 확인하려면 드라이브를 다른 호스트에 연결하고 스마트 테스트를 반복하세요. 마더보드가 노후화되어 BIOS가 드라이브를 인식하지 못하는 상황이 있었지만 다른 시스템에서는 제대로 작동했습니다.

관련 정보