Dotaz: smartd.conf - jak potlačit upozornění

[vandrovnik]

Dobrý den,

na jednom serveru máme CRUCIAL MX500 SSD 2TB SATA. smartd u něj často posílá upozornění:

SMART error (CurrentPendingSector) detected on host: xxx
Device: /dev/sdb [SAT], 1 Currently unreadable (pending) sectors
Device info:
CT2000MX500SSD1, S/N:1929E21401BE, WWN:5-00a075-1e21401be, FW:M3CR023, 2.00 TB

Výpis vypadá takto:

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   100   100   000    Pre-fail  Always       -       0
  5 Reallocated_Sector_Ct   0x0032   100   100   010    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       592
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1
171 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
172 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
173 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       9
174 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
180 Unused_Rsvd_Blk_Cnt_Tot 0x0033   000   000   000    Pre-fail  Always       -       90
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   069   050   000    Old_age   Always       -       31 (Min/Max 0/50)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   000    Old_age   Always       -       0
202 Unknown_SSD_Attribute   0x0030   100   100   001    Old_age   Offline      -       0
206 Unknown_SSD_Attribute   0x000e   100   100   000    Old_age   Always       -       0
210 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
246 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       4299508085
247 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       82819314
248 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       509094854

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

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: 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
  -- -- -- -- -- -- --
  00 ec 00 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 00 00      00:00:00.000  IDENTIFY DEVICE
  ec 00 00 00 00 00 00 00      00:00:00.000  IDENTIFY DEVICE
  ec 00 00 00 00 00 00 00      00:00:00.000  IDENTIFY DEVICE
  ec 00 00 00 00 00 00 00      00:00:00.000  IDENTIFY DEVICE
  c8 00 00 00 00 00 00 00      00:00:00.000  READ DMA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%       585         -
# 2  Extended offline    Completed without error       00%       575         -

Krátké i dlouhé testy procházejí bez chyb.

SMART u toho disku je nějaký divný, protože např. Power_On_Hours ukazuje nesmyslně nízkou hodnotu (než jsem vypnul úsporné funkce, tak možná nezapočítával dobu, když spořil energii?) a zmateně vypisuje i ATA error.

Říkal jsem si, že tedy prostě potlačím upozorňování na kód 197. Nicméně nedaří se mi to správně zapsat. V zoufalství jsem to -I a -i v smartd.conf napsal, kam se dalo , ale hlášení stejně pořád chodí:

/dev/sdb -I 197 -i 197 -H -f -I 197 -i 197 -l selftest -I 197 -i 197 -l error -I 197 -i 197 -s (S/../.././00|L/../../2/03) -I 197 -i 197 -m xxx

Poradíte, prosím, jak to upozornění na změnu pole 197 vypnout?

---

---

Odpovědi

[k3dAR]

dle man asi:

/dev/sdb -f -i 197

nebo

/dev/sdb -t -I 197

[vandrovnik]

No to tam právě mám, je to v dotazu na konci. Postupně jsem zkoušel -i, -I, pak to dávat na různá místa, jestli to nemá vliv, pak jsem to tam dal na víc míst zároveň... Ale nějak to nereaguje.

[k3dAR]

no jestli tam toho nemas prave moc treba "-l 197"... parametr -l nevidim ze by podporoval zadani cisla atributu, viz man:

-l TYPE
              Reports increases in the number of errors in one of three SMART logs.  The valid arguments to this Directive are:

              error - [ATA] report if the number of ATA errors reported in the Summary SMART error log has increased since the last check.

              error  -  [NVMe]  [FreeBSD,  Linux,  Windows and Cygwin only] [NEW EXPERIMENTAL SMARTD FEATURE] report if the "Number of Error Information Log
              Entries" from the SMART/Health Information log has increased since the last check.

              xerror - [ATA] report if the number of ATA errors reported in the Extended Comprehensive SMART error log has increased since the last check.

              If both '-l error' and '-l xerror' are specified, smartd checks the maximum of both values.

              [Please see the smartctl -l xerror command-line option.]

              xerror - [NVMe] [FreeBSD, Linux, Windows and Cygwin only] [NEW EXPERIMENTAL SMARTD FEATURE] same as ´-l error´.

              selftest - report if the number of failed tests reported in the SMART Self-Test Log has increased since the last check, or  if  the  timestamp
              associated  with  the most recent failed test has increased.  Note that such errors will only be logged if you run self-tests on the disk (and
              it fails a test!).  Self-Tests can be run automatically by smartd: please see the '-s' Directive below.  Self-Tests can also be  run  manually
              by using the '-t short' and '-t long' options of smartctl and the results of the testing can be observed using the smartctl '-l selftest' com‐
              mand-line option.  [Please see the smartctl -l and -t command-line options.]

              [ATA only] Failed self-tests outdated by a newer successful extended self-test are ignored.  The warning email counter is reset if the  number
              of failed self tests dropped to 0.  This typically happens when an extended self-test is run after all bad sectors have been reallocated.

              offlinests[,ns]  -  [ATA  only]  report  if the Offline Data Collection status has changed since the last check.  The report will be logged as
              LOG_CRIT if the new status indicates an error.  With some drives the status often changes, therefore '-l offlinests' is not  enabled  by  '-a'
              Directive.  Appending ',ns' (no standby) to this directive is not implemented on Linux.

              selfteststs[,ns]  -  [ATA  only]  report  if  the  Self-Test  execution status has changed since the last check.  The report will be logged as
              LOG_CRIT if the new status indicates an error.  Appending ',ns' (no standby) to this directive is not implemented on Linux.

              scterc,READTIME,WRITETIME - [ATA only] sets the SCT Error Recovery Control settings to the specified values (deciseconds) when  smartd  starts
              up  and  has  no  further effect.  Values of 0 disable the feature, other values less than 65 are probably not supported.  For RAID configura‐
              tions, this is typically set to 70,70 deciseconds.  [Please see the smartctl -l scterc command-line option.]

takze mozna to ty parametry ignoruje cele, zkus pustit (pokud bys to v textu prehlidnul, ukonceni pres ctrl+\):

smartd --debug

[vandrovnik]

Používám tam "malé i" a "velké i", jen jsem si neuvědomil, že když to vložím sem, použije se font, kde "velké i" a "malé L" vypadají stejně

Mám tam:

/dev/sdb -I 197 -i 197 -H -f -I 197 -i 197 -l selftest -I 197 -i 197 -l error -I 197 -i 197 -s (S/../.././00|L/../../2/03) -I 197 -i 197 -m xxx

Na začátku jsem zkoušel každý z těch parametrů samostatně, pak je dát na různá místa, teď jsem je tam nechal mnohokrát, ale chová se to furt stejně. Když vidím výstup toho debug, tak si říkám, jestli není problém "type changed from 'scsi' to 'sat'" versus "[ATA only]", ale píše to "Monitoring 3 ATA".

       -i ID  [ATA  only] Ignore device Attribute number ID when checking for failure of Usage Attributes.  ID must be a decimal integer in
              the range from 1 to 255.  This Directive modifies the behavior of the ´-f´ Directive and has no effect without it.

              This is useful, for example, if you have a very old disk and don´t want to keep getting messages about the  hours-on-lifetime
              Attribute (usually Attribute 9) failing.  This Directive may appear multiple times for a single device, if you want to ignore
              multiple Attributes.

       -I ID  [ATA only] Ignore device Attribute ID when tracking changes in the Attribute values.  ID must be a  decimal  integer  in  the
              range  from 1 to 255.  This Directive modifies the behavior of the ´-p´, ´-u´, and ´-t´ tracking Directives and has no effect
              without one of them.

              This is useful, for example, if one of the device Attributes is the disk temperature (usually Attribute  194  or  231).  It´s
              annoying  to get reports each time the temperature changes.  This Directive may appear multiple times for a single device, if
              you want to ignore multiple Attributes.

Výstup:

smartd 6.3 2018-03-10 r4719 [x86_64-linux-3.0.101-108.84-default] (SUSE RPM)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

Opened configuration file /etc/smartd.conf
Configuration file /etc/smartd.conf parsed.
Device: /dev/sda, type changed from 'scsi' to 'sat'
Device: /dev/sda [SAT], opened
Device: /dev/sda [SAT], WDC WD2003FYYS-02W0B1, S/N:WD-WMAY04239093, WWN:5-0014ee-00322a218, FW:01.01D02, 2.00 TB
Device: /dev/sda [SAT], found in smartd database: Western Digital RE4
Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD2003FYYS_02W0B1-WD_WMAY04239093.ata.state
Device: /dev/sdb, type changed from 'scsi' to 'sat'
Device: /dev/sdb [SAT], opened
Device: /dev/sdb [SAT], CT2000MX500SSD1, S/N:1929E21401BE, WWN:5-00a075-1e21401be, FW:M3CR023, 2.00 TB
Device: /dev/sdb [SAT], not found in smartd database.
Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.CT2000MX500SSD1-1929E21401BE.ata.state
Device: /dev/sdc, type changed from 'scsi' to 'sat'
Device: /dev/sdc [SAT], opened
Device: /dev/sdc [SAT], TOSHIBA MK2002TSKB, S/N:4213K7XYF, WWN:5-000039-3fb800080, FW:MT2A, 2.00 TB
Device: /dev/sdc [SAT], found in smartd database: Toshiba 3.5" HDD MK.002TSKB
Device: /dev/sdc [SAT], is SMART capable. Adding to "monitor" list.
Device: /dev/sdc [SAT], state read from /var/lib/smartmontools/smartd.TOSHIBA_MK2002TSKB-4213K7XYF.ata.state
Monitoring 3 ATA and 0 SCSI devices
Device: /dev/sda [SAT], opened ATA device
Device: /dev/sdb [SAT], opened ATA device
Device: /dev/sdc [SAT], opened ATA device
Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD2003FYYS_02W0B1-WD_WMAY04239093.ata.state
Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.CT2000MX500SSD1-1929E21401BE.ata.state
Device: /dev/sdc [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_MK2002TSKB-4213K7XYF.ata.state

[Zoufalec]

A spate of somewhat alarming flaky SMART errors on Crucial MX500 SSDs

[NN]

Tady novejsi firmware nepomohl:

Device info:
CT2000MX500SSD1, S/N:1929E21401BE, WWN:5-00a075-1e21401be, FW:M3CR023, 2.00 TB<

[Zoufalec]

Myslel jsem to jako psychickou podporu.

[vandrovnik]

Děkuju za psychickou podporu Popis problému přesně odpovídá tomu našemu disku - ten poslal první hlášení o pending sektoru možná 3 dny po instalaci a většinou tak jedna až dvě hlášky za týden přijdou. A přesně jak píšou v odkazovaném článku - i když se "okamžitě" (+- minuta, než mi přijde mail a odentruju příkaz v putty) podívám pomocí smartctl, už tam nikdy pending sektory nevidím.

Proto jsem si říkal, že nejjednodušší bude u tohohle disku ten atribut 197 ignorovat, jenže bohužel se mi nedaří v smartd.conf to ignorování správně nastavit.

[Zoufalec]

Vypadá to na firmware bug.

[vandrovnik]

Tak jsem zkusil přidat -C 0 a uvidíme časem, jestli to pomohlo.

[vandrovnik]

11 dní a hláška zatím žádná (dřív chodila tak po 2-4 dnech), tak se zdá, že pomohlo.