Je disk vadný? Rady + výpisy ze SMARTu

[Blacksphere]

Zdravim vo spolok,
kedze uloziska idu trochu mimo mna, prisiel som si ku Vam po radu. Poslednu dobu som mal problem s niektorymi subormi na disku E, tak som sa rozhodol spustit Crystal Disk. Znamena to, ze disk je na odchode a bolo by co najlepsie kupit novy a subory prehodit?
https://imgur.com/a/gYckqxW
Vdaka

[Baneshee]

Ano, má tam plno problémových/vadných sektorů, tady bych to viděl na zálohu a výměnu HDD. Některé soubory už i tak můžou být poškozené nebo nečitelné

[Blacksphere]

@Baneshee
Dakujem za potvrdenie mojich domnienok. Ako si napisal, niektore subory/foldery mi uz hodili hlasku, ze su corrupted/unreadable. Nastastie neslo o kriticke data. Spravil som si teda zalohu toho, co som potreboval. Teraz uz len kupit novy HDD.
Vdaka

[-+_[]]

Pěkný den přeji. Stala se mi taková podivnost. Na disku se mi objevilo několik (konkrétně 16) pending sektorů (C5). Soubor, který byl na těchto sektorech, opravdu nešel otevřít/zkopírovat jinde (CRC chyba). Potuď vše v pořádku, standardní chování. Tak jsem soubor vymazal a nahrál ho znova na disk ze zálohy. Soubor se zapsal do stejných sektorů, jako ten původní. A najednou se ve SMARTu už žádný pending sektor neobjevil, znuvunahraný soubor šel normálně otevřít/zkopírovat. Následně jsem tedy provedl test povrchu disku a ten také žádné chyby neobjevil. Sluší se ještě dodat, že sektory se nepřesunuly do stavu 05 nebo C6 ( realoc. nebo offline uncorr.) - obojí hodnoty jsou 0, čili SMART hlásí že disk je OK. Může být na vině něco jiného než disk samotný? Třeba že by byla vysoká teplota disku, když se tam na něj onen inkriminovaný soubor, který pak nešel přečíst, vytvářel? Sice se mi to nezdá, že by se mi disky přehřívaly, ale nic jiného mne nenapadá. Od té doby (asi týden) se mi nic takového znovu nestalo a disk šlape jako hodinky.

[DOC_ZENITH]

Ne, pokud byl sektor vadnej a při přepisu se přesunul opět do good, ne do offline nebo realocated, tak se disku nedá věřit a zbavil bych se ho. Tohle jsem párkrár zažil, nejvíce u Seagatů se shitóznim FW. I když teď třeba šlape zdánlivě ok nevěřil bych mu, Disk co tají vlastní vady je cesta do pekel.

[ifkopifko]

Zas by som to tak nehrotil. Z princípu sa žiadnemu disku nedá veriť, preto sa vymysleli zálohy. Odísť alebo poškodiť sa môže aj nový super-duper datacenter-grade disk... kedykoľvek.

Ak pending sektor zmizol, tak by som to bral ako OK stav. Tiež mám taký disk (pending sektory zmizli po kontrole povrchu) a odvtedy ho používam už minimálne 4 roky a stále všetko ok. Skrátka zaznamenal nejaký reálny problém čo sa HW týka a pri kontrole sa mu nepotvrdil. Samozrejme, môže to byť ako píše DOC a disk tají svoje vady, ale spravil si kontrolu povrchu a tá vyšla ok. Sprav ju opakovane ak chceš mať väčšiu istotu.

Ale zaujímalo by ma ako si zistil, že sa súbor zo zálohy nahral na tie isté sektory ako bol ten poškodený súbor. Len na základe toho, že zmizli pending sektory?

[-+_[]]

Dík vám za odpovědi . No přišel jsem na to tak, že třeba v DiskGeniusu se můžeš přímo podívat, na jakých sektorech je daný soubor zapsán. Tak jsem se podíval před výmazem na starý soubor, kde byl zapsán a pak hned na nový. A zapsal se přesně tam, kde ten starý. Jednalo se o identické soubory (byl to soubor vedle z disku ze zálohy, rar archiv). Jelikož se jednalo o relativně nový disk a bylo na něj zapisováno poprvé, tak byl navíc na disku v jednom chunku.

[sajty]

Zdravím. Je tento disk vadný nebo se jedná o běžné opotřebení zápisy?

[Baneshee]

Podle mě je v pořádku, nevidím tam problém. Jen chybná interpretace CrystalDisku

[sajty]

Díky.

[Gerak]

Zdravím.

Ako mám rozumieť tomuto:

12 --- Read Recovery Attempts
3 --- Number of Reported Uncorrectable Errors

Znamená to, že disk je vadný?
Ostatné disky (2x WD a 2x Seagate) majú tieto parametre na 0.
Je to na reklamáciu?
Do konca záruky zostáva už len pár týždňov.

Kód: Vybrat vše

smartctl 6.6 2017-11-05 r4594 [x86_64-w64-mingw32-w10-b19044] (sf-6.6-1)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD60EFRX-68L0BN1
LU WWN Device Id: 5 0014ee 2660208c3
Firmware Version: 82.00A82
User Capacity:    6 001 175 126 016 bytes [6,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5700 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Feb 04 02:24:14 2022 
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:   Disabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, NOT FROZEN [SEC1]

=== 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:      (   0) The previous self-test routine completed
          without error or no self-test has ever 
          been run.
Total time to complete Offline 
data collection:    ( 3584) 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:    ( 689) minutes.
Conveyance self-test routine
recommended polling time:    (   5) minutes.
SCT capabilities:          (0x303d) 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    -    0
  3 Spin_Up_Time            POS--K   197   197   021    -    9116
  4 Start_Stop_Count        -O--CK   099   099   000    -    1061
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   100   253   000    -    0
  9 Power_On_Hours          -O--CK   082   082   000    -    13386
 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    -    575
192 Power-Off_Retract_Count -O--CK   200   200   000    -    39
193 Load_Cycle_Count        -O--CK   198   198   000    -    8650
194 Temperature_Celsius     -O---K   123   107   000    -    29
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--   100   253   000    -    0
                            ||||||_ 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
0x04       GPL,SL  R/O      8  Device Statistics 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
0x0c       GPL     R/O   2048  Pending Defects 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
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data 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      54  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: 18
  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 18 [17] occurred at disk power-on lifetime: 12885 hours (536 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 01 9c 3c 77 81 40 00  Error: UNC at LBA = 0x19c3c7781 = 6916175745

  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 01 00 00 00 00 01 9c 3c 18 38 40 00     00:30:20.942  READ FPDMA QUEUED
  60 01 00 00 00 00 01 9c 3c 17 38 40 00     00:30:20.941  READ FPDMA QUEUED
  60 01 00 00 00 00 01 9c 3c 16 38 40 00     00:30:20.929  READ FPDMA QUEUED
  60 01 00 00 00 00 01 9c 3c 15 38 40 00     00:30:20.928  READ FPDMA QUEUED
  60 01 00 00 00 00 01 9c 3c 14 38 40 00     00:30:20.927  READ FPDMA QUEUED

Error 17 [16] occurred at disk power-on lifetime: 12837 hours (534 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 00 5c 40 77 40 00  Error: UNC at LBA = 0x005c4077 = 6045815

  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 01 00 00 00 00 00 00 5c 40 30 40 00     00:01:36.172  READ FPDMA QUEUED
  60 01 00 00 08 00 00 00 5c 3f 30 40 00     00:01:36.171  READ FPDMA QUEUED
  60 01 00 00 00 00 00 00 5c 3e 30 40 00     00:01:36.171  READ FPDMA QUEUED
  60 01 00 00 08 00 00 00 5c 3d 30 40 00     00:01:36.170  READ FPDMA QUEUED
  60 01 00 00 00 00 00 00 5c 3c 30 40 00     00:01:36.169  READ FPDMA QUEUED

Error 16 [15] occurred at disk power-on lifetime: 8074 hours (336 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     01:25:12.479  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     01:25:12.474  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     01:25:12.473  SMART WRITE LOG
  60 01 00 00 c0 00 02 1f d3 81 58 40 00     01:25:08.468  READ FPDMA QUEUED
  60 01 00 00 b8 00 02 1f d3 80 58 40 00     01:25:08.468  READ FPDMA QUEUED

Error 15 [14] occurred at disk power-on lifetime: 8074 hours (336 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     01:25:12.474  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     01:25:12.473  SMART WRITE LOG
  60 01 00 00 c0 00 02 1f d3 81 58 40 00     01:25:08.468  READ FPDMA QUEUED
  60 01 00 00 b8 00 02 1f d3 80 58 40 00     01:25:08.468  READ FPDMA QUEUED
  60 01 00 00 b0 00 02 1f d3 7f 58 40 00     01:25:08.468  READ FPDMA QUEUED

Error 14 [13] occurred at disk power-on lifetime: 8074 hours (336 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     01:25:12.473  SMART WRITE LOG
  60 01 00 00 c0 00 02 1f d3 81 58 40 00     01:25:08.468  READ FPDMA QUEUED
  60 01 00 00 b8 00 02 1f d3 80 58 40 00     01:25:08.468  READ FPDMA QUEUED
  60 01 00 00 b0 00 02 1f d3 7f 58 40 00     01:25:08.468  READ FPDMA QUEUED
  60 01 00 00 a8 00 02 1f d3 7e 58 40 00     01:25:08.468  READ FPDMA QUEUED

Error 13 [12] occurred at disk power-on lifetime: 3592 hours (149 days + 16 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:55:12.542  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:55:12.537  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:55:12.536  SMART WRITE LOG
  60 00 40 00 f0 00 02 66 03 12 f8 40 00     02:55:12.508  READ FPDMA QUEUED
  60 00 40 00 e8 00 02 66 03 10 c0 40 00     02:55:12.500  READ FPDMA QUEUED

Error 12 [11] occurred at disk power-on lifetime: 3592 hours (149 days + 16 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:55:12.537  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:55:12.536  SMART WRITE LOG
  60 00 40 00 f0 00 02 66 03 12 f8 40 00     02:55:12.508  READ FPDMA QUEUED
  60 00 40 00 e8 00 02 66 03 10 c0 40 00     02:55:12.500  READ FPDMA QUEUED
  60 00 40 00 e0 00 02 66 1f e7 78 40 00     02:55:12.197  READ FPDMA QUEUED

Error 11 [10] occurred at disk power-on lifetime: 3592 hours (149 days + 16 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:55:12.536  SMART WRITE LOG
  60 00 40 00 f0 00 02 66 03 12 f8 40 00     02:55:12.508  READ FPDMA QUEUED
  60 00 40 00 e8 00 02 66 03 10 c0 40 00     02:55:12.500  READ FPDMA QUEUED
  60 00 40 00 e0 00 02 66 1f e7 78 40 00     02:55:12.197  READ FPDMA QUEUED
  60 00 40 00 d8 00 02 66 20 b3 18 40 00     02:55:12.190  READ FPDMA QUEUED

Error 10 [9] occurred at disk power-on lifetime: 3540 hours (147 days + 12 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:40:18.339  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:40:18.338  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:40:18.338  SMART WRITE LOG
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     02:39:49.045  SMART READ DATA
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     02:39:42.763  SMART READ DATA

Error 9 [8] occurred at disk power-on lifetime: 3540 hours (147 days + 12 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:40:18.338  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:40:18.338  SMART WRITE LOG
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     02:39:49.045  SMART READ DATA
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     02:39:42.763  SMART READ DATA
  b0 00 d1 00 01 00 00 00 c2 4f 01 a0 00     02:39:29.883  SMART READ ATTRIBUTE THRESHOLDS [OBS-4]

Error 8 [7] occurred at disk power-on lifetime: 3540 hours (147 days + 12 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     02:40:18.338  SMART WRITE LOG
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     02:39:49.045  SMART READ DATA
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     02:39:42.763  SMART READ DATA
  b0 00 d1 00 01 00 00 00 c2 4f 01 a0 00     02:39:29.883  SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     02:39:29.879  SMART READ DATA

Error 7 [6] occurred at disk power-on lifetime: 3538 hours (147 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:36:28.777  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:36:28.776  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:36:28.776  SMART WRITE LOG
  27 00 00 00 00 00 00 00 00 00 00 e0 00     00:35:47.956  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 01 00 00 00 00 00 00 e0 00     00:35:47.955  IDENTIFY DEVICE

Error 6 [5] occurred at disk power-on lifetime: 3538 hours (147 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:36:28.776  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:36:28.776  SMART WRITE LOG
  27 00 00 00 00 00 00 00 00 00 00 e0 00     00:35:47.956  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 01 00 00 00 00 00 00 e0 00     00:35:47.955  IDENTIFY DEVICE
  ec 00 00 00 01 00 00 00 00 00 00 e0 00     00:35:47.954  IDENTIFY DEVICE

Error 5 [4] occurred at disk power-on lifetime: 3538 hours (147 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:36:28.776  SMART WRITE LOG
  27 00 00 00 00 00 00 00 00 00 00 e0 00     00:35:47.956  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 01 00 00 00 00 00 00 e0 00     00:35:47.955  IDENTIFY DEVICE
  ec 00 00 00 01 00 00 00 00 00 00 e0 00     00:35:47.954  IDENTIFY DEVICE
  ec 00 00 00 01 00 00 00 00 00 00 e0 00     00:35:47.954  IDENTIFY DEVICE

Error 4 [3] occurred at disk power-on lifetime: 3538 hours (147 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:35:47.936  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:35:47.936  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:35:47.935  SMART WRITE LOG
  60 00 10 00 48 00 00 00 00 00 00 40 00     00:35:47.586  READ FPDMA QUEUED
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     00:32:42.827  SMART READ DATA

Error 3 [2] occurred at disk power-on lifetime: 3538 hours (147 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:35:47.936  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:35:47.935  SMART WRITE LOG
  60 00 10 00 48 00 00 00 00 00 00 40 00     00:35:47.586  READ FPDMA QUEUED
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     00:32:42.827  SMART READ DATA
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     00:26:53.062  SMART READ DATA

Error 2 [1] occurred at disk power-on lifetime: 3538 hours (147 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
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 10 00 00 00 00 00 00 a0 00  Error: ABRT

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 a0 00     00:35:47.935  SMART WRITE LOG
  60 00 10 00 48 00 00 00 00 00 00 40 00     00:35:47.586  READ FPDMA QUEUED
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     00:32:42.827  SMART READ DATA
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     00:26:53.062  SMART READ DATA
  b0 00 d0 00 01 00 00 00 c2 4f 01 a0 00     00:21:36.354  SMART READ DATA

Error 1 [0] occurred at disk power-on lifetime: 1706 hours (71 days + 2 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 5c 3b b0 40 00  Error: UNC at LBA = 0x005c3bb0 = 6044592

  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 01 00 00 98 00 00 00 5c 41 b0 40 00     02:02:45.174  READ FPDMA QUEUED
  60 01 00 00 90 00 00 00 5c 40 b0 40 00     02:02:45.174  READ FPDMA QUEUED
  60 01 00 00 88 00 00 00 5c 3f b0 40 00     02:02:45.174  READ FPDMA QUEUED
  60 01 00 00 80 00 00 00 5c 3e b0 40 00     02:02:45.174  READ FPDMA QUEUED
  60 01 00 00 68 00 00 00 5c 3b b0 40 00     02:02:43.162  READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Conveyance offline  Completed without error       00%         0         -
# 2  Short offline       Completed without error       00%         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.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    29 Celsius
Power Cycle Min/Max Temperature:     29/29 Celsius
Lifetime    Min/Max Temperature:     19/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 (156)

Index    Estimated Time   Temperature Celsius
 157    2022-02-03 18:27    29  **********
 ...    ..(106 skipped).    ..  **********
 264    2022-02-03 20:14    29  **********
 265    2022-02-03 20:15     ?  -
 266    2022-02-03 20:16    29  **********
 267    2022-02-03 20:17    30  ***********
 ...    ..(  2 skipped).    ..  ***********
 270    2022-02-03 20:20    30  ***********
 271    2022-02-03 20:21    31  ************
 272    2022-02-03 20:22    31  ************
 273    2022-02-03 20:23    32  *************
 ...    ..(  2 skipped).    ..  *************
 276    2022-02-03 20:26    32  *************
 277    2022-02-03 20:27    33  **************
 ...    ..(  5 skipped).    ..  **************
 283    2022-02-03 20:33    33  **************
 284    2022-02-03 20:34    34  ***************
 ...    ..(  5 skipped).    ..  ***************
 290    2022-02-03 20:40    34  ***************
 291    2022-02-03 20:41    35  ****************
 ...    ..(  8 skipped).    ..  ****************
 300    2022-02-03 20:50    35  ****************
 301    2022-02-03 20:51    36  *****************
 ...    ..( 10 skipped).    ..  *****************
 312    2022-02-03 21:02    36  *****************
 313    2022-02-03 21:03    37  ******************
 ...    ..( 12 skipped).    ..  ******************
 326    2022-02-03 21:16    37  ******************
 327    2022-02-03 21:17     ?  -
 328    2022-02-03 21:18    29  **********
 ...    ..(305 skipped).    ..  **********
 156    2022-02-04 02:24    29  **********

SCT Error Recovery Control:
           Read:     70 (7,0 seconds)
          Write:     70 (7,0 seconds)

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 2) ==
0x01  0x008  4             575  ---  Lifetime Power-On Resets
0x01  0x010  4           13386  ---  Power-on Hours
0x01  0x018  6     38250817188  ---  Logical Sectors Written
0x01  0x020  6       191469886  ---  Number of Write Commands
0x01  0x028  6     54927931826  ---  Logical Sectors Read
0x01  0x030  6       243977859  ---  Number of Read Commands
0x03  =====  =               =  ===  == Rotating Media Statistics (rev 1) ==
0x03  0x008  4           13174  ---  Spindle Motor Power-on Hours
0x03  0x010  4            9009  ---  Head Flying Hours
0x03  0x018  4            8690  ---  Head Load Events
0x03  0x020  4               0  ---  Number of Reallocated Logical Sectors
0x03  0x028  4              12  ---  Read Recovery Attempts
0x03  0x030  4               0  ---  Number of Mechanical Start Failures
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4               3  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4               0  ---  Resets Between Cmd Acceptance and Completion
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1              29  ---  Current Temperature
0x05  0x010  1              32  ---  Average Short Term Temperature
0x05  0x018  1              30  ---  Average Long Term Temperature
0x05  0x020  1              45  ---  Highest Temperature
0x05  0x028  1              23  ---  Lowest Temperature
0x05  0x030  1              44  ---  Highest Average Short Term Temperature
0x05  0x038  1              24  ---  Lowest Average Short Term Temperature
0x05  0x040  1              39  ---  Highest Average Long Term Temperature
0x05  0x048  1              26  ---  Lowest Average Long Term Temperature
0x05  0x050  4               0  ---  Time in Over-Temperature
0x05  0x058  1              60  ---  Specified Maximum Operating Temperature
0x05  0x060  4               0  ---  Time in Under-Temperature
0x05  0x068  1               0  ---  Specified Minimum Operating Temperature
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4            1930  ---  Number of Hardware Resets
0x06  0x010  4             696  ---  Number of ASR Events
0x06  0x018  4               0  ---  Number of Interface CRC Errors
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

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
0x000d  2            0  Non-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           36  Vendor specific

[DOC_ZENITH]

Jako udělej si test povrchu v HDtunu ale tohle obvykle znamená už počátek potíží, tohle nejsou random nepodstatné chybičky, tohle už jsou chyby že ňákej sektor nešel přečíst. Měl by ale v testu povrchu bejt vidět. Pakliže bude, screenshot a reklamace.

[nou]

Kód: Vybrat vše

[11623.805102] ata11.00: exception Emask 0x0 SAct 0xffffffff SErr 0x0 action 0x0
[11623.805113] ata11.00: irq_stat 0x40000008
[11623.805117] ata11.00: failed command: READ FPDMA QUEUED
[11623.805120] ata11.00: cmd 60/08:78:00:b8:f9/00:00:72:00:00/40 tag 15 ncq dma 4096 in
                        res 41/40:08:00:b8:f9/00:00:72:00:00/00 Emask 0x409 (media error) <F>
[11623.805129] ata11.00: status: { DRDY ERR }
[11623.805132] ata11.00: error: { UNC }
[11623.806051] ata11.00: configured for UDMA/133
[11623.806110] sd 10:0:0:0: [sde] tag#15 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
[11623.806114] sd 10:0:0:0: [sde] tag#15 Sense Key : Medium Error [current] 
[11623.806116] sd 10:0:0:0: [sde] tag#15 Add. Sense: Unrecovered read error - auto reallocate failed
[11623.806119] sd 10:0:0:0: [sde] tag#15 CDB: Read(10) 28 00 72 f9 b8 00 00 00 08 00
[11623.806120] blk_update_request: I/O error, dev sde, sector 1928968192 op 0x0:(READ) flags 0x4000 phys_seg 1 prio class 0
[11623.806144] ata11: EH complete
[11629.425301] md/raid:md0: read error corrected (8 sectors at 1928966144 on sde1)
[11858.388254] md: md0: data-check done.

Tak som pustil po dlhsej dobe scrub na RAID5 poli. Pred spustenim 32 vadnych sektorov na prvom disku. Po dokonceni je objavenie sa 312 vadnych sektorov na tretom disku. Opravenych muselo byt 59 chyb. Disk je Seagate ST1000VX000 1TB.

No nic uz su objednane nove disky.

[Gerak]

Jako udělej si test povrchu v HDtunu ale tohle obvykle znamená už počátek potíží, tohle nejsou random nepodstatné chybičky, tohle už jsou chyby že ňákej sektor nešel přečíst. Měl by ale v testu povrchu bejt vidět. Pakliže bude, screenshot a reklamace.

Ďakujem za odpoveď. Disk nemá vadné sektory. Takže tie UNC chyby nie sú na reklamáciu? Ako rieši reklamácie diskov Alza? Posiela to výrobcovi? Overil som SN na stránke WD a disk už nie je v záruke.

[zsdx]

Western ma WDDiag (jako Seagate SeaTools) - k reklamaci staci prilozit chybovy vysledek z nej.

[Trottel]

Ahoj, v NAS s OMV6 mi nyní dva disky ve SMART ukazují chyby.

Skoro 10 let starý SSD disk Crucial M4 128GB zobrazuje od včerejška toto:

Kód: Vybrat vše

173 Wear_Leveling_Count PO--CK 010 010 010 NOW 2700 Prefail Bad

A něco přes dva roky starý HDD Seagate BarraCuda 4TB ukazuje už asi půl roku tohle:

Kód: Vybrat vše

187 Reported_Uncorrect -O--CK 082 082 000 - 18 Old-age Bad

Co tyto chyby pro mě znamenají a jak rychle mám případně shánět nové disky?

[DOC_ZENITH]

Nic dramatického. ta M4ka je už prostě 10+ let stará a dává ti najevo že jí docházej spare sektory, tzn měla by se po zásluze vyměnit než doslouží úplně.

Ten Seagate ti dává najevo že má errory na ECC interfacu. Může to bejt blbej kontakt, kabel, odcházející řadič nebo elektronika disku. Jeden či dva za roky provozu ale nejsou reálnej problém. Problém by byl kdyby tam přibejvaly denně. Pořádně ho otestuj a pokud bude mít všechny sektory i výkon ok můžeš ho dál používat.

[Trottel]

Díky. Crucial M4 tedy vyměním, ten už si to zaslouží. Hlavně na něm mám úložiště dockeru pro NAS, takže všechna data kontejnerů, a o to bych nechtěl přijít. Koukal jsem buď na Crucial MX500 nebo o něco levnější Apacer AS350X. V tuhle chvíli mám ze 128GB zaplněnou sotva půlku. Vyplatí se koupit 256GB nebo 512GB, že by se tolik nepřepisovaly jednotlivé buňky a disk by déle vydržel? Nebo je moje úvaha nesmysl?

Seagate si to nezaslouží, ten mě naštval. Chybu nahlásil měsíc po vypršení záruky. Ale když už polezu do skříně, zkusím vyměnit kabel a pořádně ho docvaknout, jinak ho nechám. V informaci v e-mailu, kterou NAS každý den zasílá, je celou dobu hodnota 24 vadných sektorů. Až kdyby se to začalo zhoršovat, koupím jiný určený pro NAS.

[DOC_ZENITH]

Měl by jsi ho prostě strčit do do PC a project HDtunem ať vidíš co se tam opravdu děje no. Tyhlenty výpisy z Nasky jsou vždy poměrně vágní.

Co se toho SSD týče, tak vzhledem k tomu že jsi ten crucial defakto upsal k smrti (i když ještě mrtvej neni jen se tomu blíží) a je to sice malinká verze, ale MLC drive, tak náhrana něčim jako je MX500 což je TLC drive neni vhodná. Ten by odešel mnohem dříve fakt by to nertvalo 10+ let. Navíc, MX500 je good ale není jí dobře bez TRIMu, a nevim jestli v tý nasce na tomhhle účelu je TRIM. Podle mě by bylo mnohem lepší sehnat ňákej starší málo jetej ještě MLC drive. Evidentně ti nejde o kapacitu a takové Samsungy 860PRO 256-512GB musej bejt už dost cheap a byl by to ideální kandidát.

[nou]

SMART 187 oznacuje kolko citani sa nepodarilo opravit cez ECC pri citani z disku. Seagate reportuje chyby pri prenose cez kabel na 199 UDMA_CRC_Error_Count ktory sa zvysoval aj mne ked som mal zly kabel. Po vymene mi to prestalo.

Pekna statistika ze nenulova hodnota 187 znamena vysoku pravdepodobnost zlyhania disku je tu https://www.backblaze.com/blog/hard-drive-smart-stats/