HDD smart report - kritisch?

AgentHawk

Lieutenant
Registriert
Mai 2012
Beiträge
911
Moin

ich bekomme bei unraid aktuell die Warnung zu einer Platte - habe dann den Test gemacht und werde da noch nicht so schlau draus.
Das ist eine meiner Parity Drives - Tauschen oder geht noch?

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

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD40EFRX-68WT0N0
Serial Number:    WD-WCC4E3DNLN1C
LU WWN Device Id: 5 0014ee 26362d556
Firmware Version: 82.00A82
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Sep  4 11:52:41 2021 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: 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:      ( 121)    The previous self-test completed having
                    the read element of the test failed.
Total time to complete Offline
data collection:         (51720) 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:      ( 517) minutes.
Conveyance self-test routine
recommended polling time:      (   5) minutes.
SCT capabilities:            (0x703d)    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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    1089
  3 Spin_Up_Time            POS--K   180   171   021    -    7958
  4 Start_Stop_Count        -O--CK   098   098   000    -    2560
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   045   045   000    -    40425
 10 Spin_Retry_Count        -O--CK   100   100   000    -    0
 11 Calibration_Retry_Count -O--CK   100   100   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    256
192 Power-Off_Retract_Count -O--CK   200   200   000    -    174
193 Load_Cycle_Count        -O--CK   176   176   000    -    73000
194 Temperature_Celsius     -O---K   116   107   000    -    36
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    6
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb6  GPL,SL  VS       1  Device vendor specific log
0xb7       GPL,SL  VS      39  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 31 (device log contains only the most recent 24 errors)
    CR     = Command Register
    FEATR  = Features Register
    COUNT  = Count (was: Sector Count) Register
    LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
    LH     = LBA High (was: Cylinder High) Register    ]   LBA
    LM     = LBA Mid (was: Cylinder Low) Register      ] Register
    LL     = LBA Low (was: Sector Number) Register     ]
    DV     = Device (was: Device/Head) Register
    DC     = Device Control Register
    ER     = Error register
    ST     = Status register
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 31 [6] occurred at disk power-on lifetime: 40179 hours (1674 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 00 44 44 58 40 00  Error: UNC at LBA = 0x00444458 = 4473944

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 02 78 00 90 00 00 00 44 56 c8 40 08     00:01:48.795  READ FPDMA QUEUED
  60 02 c8 00 48 00 00 00 44 54 00 40 08     00:01:48.795  READ FPDMA QUEUED
  60 05 40 00 40 00 00 00 44 4e c0 40 08     00:01:48.790  READ FPDMA QUEUED
  60 00 28 00 88 00 00 00 44 4e 98 40 08     00:01:48.375  READ FPDMA QUEUED
  60 05 40 00 78 00 00 00 44 49 58 40 08     00:01:48.375  READ FPDMA QUEUED

Error 30 [5] occurred at disk power-on lifetime: 40032 hours (1668 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 05 db 6d 80 40 00  Error: UNC at LBA = 0x05db6d80 = 98266496

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 08 00 a8 00 01 61 ac 50 e0 40 08     00:11:35.405  READ FPDMA QUEUED
  60 05 40 00 a0 00 00 05 db 69 20 40 08     00:11:35.405  READ FPDMA QUEUED
  60 00 40 00 98 00 00 05 db 68 e0 40 08     00:11:35.395  READ FPDMA QUEUED
  60 05 40 00 90 00 00 05 db 63 a0 40 08     00:11:35.395  READ FPDMA QUEUED
  60 05 40 00 88 00 00 05 db 5e 60 40 08     00:11:34.952  READ FPDMA QUEUED

Error 29 [4] occurred at disk power-on lifetime: 38414 hours (1600 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 01 33 83 60 40 00  Error: UNC at LBA = 0x01338360 = 20153184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 40 00 a0 00 00 01 33 83 30 40 08 24d+02:38:29.675  READ FPDMA QUEUED
  ea 00 00 00 00 00 00 00 00 00 00 e0 08 24d+02:38:29.660  FLUSH CACHE EXT
  61 00 08 00 68 00 00 01 8a c3 c8 40 08 24d+02:38:29.659  WRITE FPDMA QUEUED
  61 00 08 00 60 00 00 01 33 83 28 40 08 24d+02:38:29.652  WRITE FPDMA QUEUED
  60 00 08 00 58 00 00 01 8a c3 c8 40 08 24d+02:38:29.646  READ FPDMA QUEUED

Error 28 [3] occurred at disk power-on lifetime: 38337 hours (1597 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 01 33 a3 70 40 00  Error: UNC at LBA = 0x0133a370 = 20161392

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 08 00 b0 00 00 01 81 1f c8 40 08 20d+21:49:38.741  READ FPDMA QUEUED
  60 00 10 00 a0 00 00 01 33 a3 68 40 08 20d+21:49:38.741  READ FPDMA QUEUED
  ea 00 00 00 00 00 00 00 00 00 00 e0 08 20d+21:49:38.741  FLUSH CACHE EXT
  ea 00 00 00 00 00 00 00 00 00 00 e0 08 20d+21:49:38.162  FLUSH CACHE EXT
  61 00 08 00 98 00 01 61 b7 be 30 40 08 20d+21:49:38.162  WRITE FPDMA QUEUED

Error 27 [2] occurred at disk power-on lifetime: 38161 hours (1590 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 76 40 2a b8 40 00  Error: WP at LBA = 0x76402ab8 = 1983916728

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 78 00 28 00 01 61 b8 44 d8 40 08 13d+14:09:45.473  WRITE FPDMA QUEUED
  60 02 c0 00 20 00 00 76 40 2e a8 40 08 13d+14:09:45.455  READ FPDMA QUEUED
  60 05 40 00 18 00 00 76 40 29 68 40 08 13d+14:09:45.451  READ FPDMA QUEUED
  60 00 e0 00 f8 00 00 76 40 28 88 40 08 13d+14:09:45.437  READ FPDMA QUEUED
  60 01 e0 00 b8 00 00 76 40 26 a8 40 08 13d+14:09:45.433  READ FPDMA QUEUED

Error 26 [1] occurred at disk power-on lifetime: 38161 hours (1590 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 76 40 09 a8 40 00  Error: UNC at LBA = 0x764009a8 = 1983908264

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 05 40 00 78 00 00 76 40 11 68 40 08 13d+14:09:41.608  READ FPDMA QUEUED
  60 05 40 00 70 00 00 76 40 0c 28 40 08 13d+14:09:41.606  READ FPDMA QUEUED
  60 02 08 00 68 00 00 76 40 0a 20 40 08 13d+14:09:41.602  READ FPDMA QUEUED
  60 01 98 00 60 00 00 76 40 08 88 40 08 13d+14:09:41.206  READ FPDMA QUEUED
  60 01 e0 00 58 00 00 76 40 06 a8 40 08 13d+14:09:41.205  READ FPDMA QUEUED

Error 25 [0] occurred at disk power-on lifetime: 37811 hours (1575 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 01 33 a9 70 40 00  Error: UNC at LBA = 0x0133a970 = 20162928

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 05 40 00 70 00 00 01 33 a9 90 40 08 48d+16:22:40.041  READ FPDMA QUEUED
  60 05 00 00 60 00 00 01 33 a4 90 40 08 48d+16:22:40.029  READ FPDMA QUEUED
  60 00 08 00 58 00 01 61 b7 aa 20 40 08 48d+16:22:37.922  READ FPDMA QUEUED
  61 00 08 00 50 00 01 5c 8a 9f 58 40 08 48d+16:22:37.922  WRITE FPDMA QUEUED
  61 00 08 00 48 00 01 5c 8a 9f 48 40 08 48d+16:22:37.922  WRITE FPDMA QUEUED

Error 24 [23] occurred at disk power-on lifetime: 37618 hours (1567 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 01 33 ae 48 40 00  Error: WP at LBA = 0x0133ae48 = 20164168

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 30 00 88 00 00 01 58 b5 70 40 08 40d+15:29:40.386  WRITE FPDMA QUEUED
  61 01 40 00 80 00 00 01 53 e7 10 40 08 40d+15:29:40.384  WRITE FPDMA QUEUED
  61 01 80 00 78 00 00 01 53 e5 50 40 08 40d+15:29:40.384  WRITE FPDMA QUEUED
  61 00 c0 00 70 00 00 01 53 ec d0 40 08 40d+15:29:40.379  WRITE FPDMA QUEUED
  61 00 08 00 58 00 00 01 53 ec 50 40 08 40d+15:29:40.379  WRITE FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%     40423         4477480
# 2  Short offline       Completed: read failure       40%     40423         4477480

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.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
Device State:                        Active (0)
Current Temperature:                    36 Celsius
Power Cycle Min/Max Temperature:     28/37 Celsius
Lifetime    Min/Max Temperature:      3/45 Celsius
Under/Over Temperature Limit Count:   0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (288)

Index    Estimated Time   Temperature Celsius
 289    2021-09-04 03:55    37  ******************
 ...    ..(114 skipped).    ..  ******************
 404    2021-09-04 05:50    37  ******************
 405    2021-09-04 05:51    36  *****************
 ...    ..(155 skipped).    ..  *****************
  83    2021-09-04 08:27    36  *****************
  84    2021-09-04 08:28    37  ******************
 ...    ..( 53 skipped).    ..  ******************
 138    2021-09-04 09:22    37  ******************
 139    2021-09-04 09:23    36  *****************
 ...    ..( 86 skipped).    ..  *****************
 226    2021-09-04 10:50    36  *****************
 227    2021-09-04 10:51    37  ******************
 ...    ..( 60 skipped).    ..  ******************
 288    2021-09-04 11:52    37  ******************

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            0  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            1  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4       164102  Vendor specific
 
Smart Werte schauen besser aus nutzt man Crystal Disk Info
 
  • Gefällt mir
Reaktionen: AgentHawk
Die Fehlermeldungen und #ID 3 bzw. 200 zeigen, dass sie gelegentlich Probleme beim Lesen und Schreiben hat.
Problematische Sektoren oder CRC-Fehler gibt es jedoch scheinbar nicht.
Damit scheint der Lese/Schreibkopf die Probleme zu haben.

Ich denke, dass ist noch nicht kritisch, aber mit 40k Stunden (4,5 Jahre) ist sie aber auch nicht mehr die juengste .

Das ist jedoch nur meine Interpretation.
Ich wuerde die Daten sichern und sie zeitnah in den verdienten Ruhestand schicken.
 
  • Gefällt mir
Reaktionen: AgentHawk
Der letzte Eintrag ist bereits 246 Betriebsstunden her, das war Einer der gemeldeten 1089 Lesefehler.
Der letzte Schreibfehler der 6 Gelisteten war bei 38161 Betriebsstunden.

Mehr als @Scientist gibts nicht zu sagen.
 
Zuletzt bearbeitet: (Ein m gekauft.)
  • Gefällt mir
Reaktionen: AgentHawk
Zurück
Oben