Dotaz: S.M.A.R.T

[LuRy]

Zdravím, může mi někdo prosím osvětlit následujicí errory ze smartu? Co znamenají a pčípadně jakou mají vypovídací hodnotu ohledně životnosti disku. Tyto chyby začli skákat od doby kdy disk byl v mdraid poli, nyní už je single, ale poslední chyba je ze včerejška.

Diky

Error 7 occurred at disk power-on lifetime: 19046 hours (793 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  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 ff ff ff 4f 00   2d+11:30:25.305  READ FPDMA QUEUED
  61 00 08 ff ff ff 4f 00   2d+11:30:23.500  WRITE FPDMA QUEUED
  61 00 e8 ff ff ff 4f 00   2d+11:30:23.499  WRITE FPDMA QUEUED
  61 00 18 ff ff ff 4f 00   2d+11:30:23.497  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00   2d+11:30:23.496  WRITE FPDMA QUEUED

Error 6 occurred at disk power-on lifetime: 19018 hours (792 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  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 ff ff ff 4f 00   1d+06:41:15.376  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00   1d+06:41:15.366  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00   1d+06:41:15.158  READ FPDMA QUEUED
  60 00 88 ff ff ff 4f 00   1d+06:41:13.630  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00   1d+06:41:13.630  READ FPDMA QUEUED

Error 5 occurred at disk power-on lifetime: 18939 hours (789 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  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 ff ff ff 4f 00  18d+01:58:44.396  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  18d+01:58:44.389  READ FPDMA QUEUED
  61 00 68 ff ff ff 4f 00  18d+01:58:44.388  WRITE FPDMA QUEUED
  61 00 30 ff ff ff 4f 00  18d+01:58:44.388  WRITE FPDMA QUEUED
  61 00 d0 ff ff ff 4f 00  18d+01:58:44.387  WRITE FPDMA QUEUED

Error 4 occurred at disk power-on lifetime: 18023 hours (750 days + 23 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  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 ff ff ff 4f 00  29d+14:17:47.232  READ FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.871  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.871  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.870  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.870  WRITE FPDMA QUEUED

Error 3 occurred at disk power-on lifetime: 15031 hours (626 days + 7 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
  -- -- -- -- -- -- --
  40 51 00 64 fd 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 02 64 fd 00 40 00   2d+04:25:00.855  READ FPDMA QUEUED
  60 00 00 7e 41 9a 47 00   2d+04:25:00.758  READ FPDMA QUEUED
  60 00 c8 b6 40 9a 47 00   2d+04:25:00.757  READ FPDMA QUEUED
  60 00 3a 7c 40 9a 47 00   2d+04:25:00.757  READ FPDMA QUEUED
  60 00 08 74 40 9a 47 00   2d+04:25:00.757  READ FPDMA QUEUED

Celý výpis smartctl

smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     ST31000525SV
Serial Number:    9VP9D842
Firmware Version: CV12
User Capacity:    1 000 204 886 016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sun Apr 14 18:56:50 2013 CEST
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:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                 ( 609) 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:        ( 179) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x10bb) 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   117   099   006    Pre-fail  Always       -       155929802
  3 Spin_Up_Time            0x0003   095   095   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       338
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   089   060   030    Pre-fail  Always       -       846770872
  9 Power_On_Hours          0x0032   079   079   000    Old_age   Always       -       19068
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       169
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   093   093   000    Old_age   Always       -       7
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       42950328409
189 High_Fly_Writes         0x003a   089   089   000    Old_age   Always       -       11
190 Airflow_Temperature_Cel 0x0022   071   054   045    Old_age   Always       -       29 (Lifetime Min/Max 15/30)
194 Temperature_Celsius     0x0022   029   046   000    Old_age   Always       -       29 (0 3 0 0)
195 Hardware_ECC_Recovered  0x001a   041   029   000    Old_age   Always       -       155929802
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

SMART Error Log Version: 1
ATA Error Count: 7 (device log contains only the most recent five errors)
        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 7 occurred at disk power-on lifetime: 19046 hours (793 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  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 ff ff ff 4f 00   2d+11:30:25.305  READ FPDMA QUEUED
  61 00 08 ff ff ff 4f 00   2d+11:30:23.500  WRITE FPDMA QUEUED
  61 00 e8 ff ff ff 4f 00   2d+11:30:23.499  WRITE FPDMA QUEUED
  61 00 18 ff ff ff 4f 00   2d+11:30:23.497  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00   2d+11:30:23.496  WRITE FPDMA QUEUED

Error 6 occurred at disk power-on lifetime: 19018 hours (792 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  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 ff ff ff 4f 00   1d+06:41:15.376  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00   1d+06:41:15.366  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00   1d+06:41:15.158  READ FPDMA QUEUED
  60 00 88 ff ff ff 4f 00   1d+06:41:13.630  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00   1d+06:41:13.630  READ FPDMA QUEUED

Error 5 occurred at disk power-on lifetime: 18939 hours (789 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  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 ff ff ff 4f 00  18d+01:58:44.396  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  18d+01:58:44.389  READ FPDMA QUEUED
  61 00 68 ff ff ff 4f 00  18d+01:58:44.388  WRITE FPDMA QUEUED
  61 00 30 ff ff ff 4f 00  18d+01:58:44.388  WRITE FPDMA QUEUED
  61 00 d0 ff ff ff 4f 00  18d+01:58:44.387  WRITE FPDMA QUEUED

Error 4 occurred at disk power-on lifetime: 18023 hours (750 days + 23 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  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 ff ff ff 4f 00  29d+14:17:47.232  READ FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.871  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.871  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.870  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.870  WRITE FPDMA QUEUED

Error 3 occurred at disk power-on lifetime: 15031 hours (626 days + 7 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
  -- -- -- -- -- -- --
  40 51 00 64 fd 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 02 64 fd 00 40 00   2d+04:25:00.855  READ FPDMA QUEUED
  60 00 00 7e 41 9a 47 00   2d+04:25:00.758  READ FPDMA QUEUED
  60 00 c8 b6 40 9a 47 00   2d+04:25:00.757  READ FPDMA QUEUED
  60 00 3a 7c 40 9a 47 00   2d+04:25:00.757  READ FPDMA QUEUED
  60 00 08 74 40 9a 47 00   2d+04:25:00.757  READ FPDMA QUEUED

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

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.

---

---

Odpovědi

[Aleš Kapica]

Vadné sektory nemáš, ale zdá se že ti nějak blbne napájení. Já bych to nejspíš tipoval na odcházející napájecí větev na zdroji.

[LuRy]

To se mi prave nezda, je to v serveru kde je 700W zdroj (2x xeon 4 quad, 4x 2gb DDR2 ECC fully buffered RAM, 3x 1GB + 750GB disky) tk se mi nezda ze by to nezvladal jako vykonove a senzory nic nehlasi ani nehlasili, ale zkusim to sledovat.

[Aleš Kapica]

Pokud ti blbne nějaká větev, tak je úplně fuk jak máš stroj výkonný. Klidně to může být i někde ve špatném kontaktu Mě dělal kupř. takovou neplechu zdroj s modulárními kabely. Prostě smart ti píše, že ti ten disk okurkuje z důvodu napájení.

[Jiří Lisický]

Z kterého údaje to lze vyčíst?

[Aleš Kapica]

"When the command that caused the error occurred, the device was active or idle." - Když příkaz narazil chybu, tak se zařízení používalo - tj. bylo ve stavu active (zapisovalo se na něj) nebo idle (čekalo na zápis). A následuje výpis operací, které se nepovedlo dokončit. Nejde o žádnou tragédii. Pouze upozornění, že je někde něco špatně. Vadný konektor, kabel, nebo něco takového. Tenhle chybový log postupem času rotuje. K jeho vynulování by došlo maximálně po upgrade firmware.

Z hlediska disku jako takového jsou podstatné jsou další dva údaje ze SMART tabulky - Raw_Read_Error_Rate a Hardware_ECC_Recovered. Oba mají shodnou hodnotu (pozor, platí pouze pro disky Seagate!). Tzn. že počet vadných sektorů odpovídá počtu automaticky opravených. Takže disk nemá žádné neopravitelné poškozené sektory - což znamená že je v pořádku.

[R]

To mas trochu pomylene... S napajanim sa tam nespomina nic. Ten zoznam je 5 poslednych prikazov, s tym, ze ten prvy v zozname (tzn. posledny podla casu) chybu sposobil.

Akurat tam nevidim dekodovanie tych stavovych registrov, asi to bude starou verziou smartctl - skus novsiu!

[LuRy]

latest smartctl

smartctl 6.2 2013-03-29 r3806 [x86_64-linux-2.6.32-5-xen-amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate SV35.5
Device Model:     ST31000525SV
Serial Number:    9VP9D842
LU WWN Device Id: 5 000c50 02ca28ae1
Firmware Version: CV12
User Capacity:    1 000 204 886 016 bytes [1,00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Mon Apr 15 15:46:49 2013 CEST
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:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  609) 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:        ( 179) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x10bb) 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   114   099   006    Pre-fail  Always       -       225291166
  3 Spin_Up_Time            0x0003   095   095   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       338
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   089   060   030    Pre-fail  Always       -       847488703
  9 Power_On_Hours          0x0032   079   079   000    Old_age   Always       -       19089
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       169
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   093   093   000    Old_age   Always       -       7
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       42950328409
189 High_Fly_Writes         0x003a   089   089   000    Old_age   Always       -       11
190 Airflow_Temperature_Cel 0x0022   068   054   045    Old_age   Always       -       32 (Min/Max 15/32)
194 Temperature_Celsius     0x0022   032   046   000    Old_age   Always       -       32 (0 3 0 0 0)
195 Hardware_ECC_Recovered  0x001a   041   029   000    Old_age   Always       -       225291166
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

SMART Error Log Version: 1
ATA Error Count: 7 (device log contains only the most recent five errors)
        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 7 occurred at disk power-on lifetime: 19046 hours (793 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 ff ff ff 4f 00   2d+11:30:25.305  READ FPDMA QUEUED
  61 00 08 ff ff ff 4f 00   2d+11:30:23.500  WRITE FPDMA QUEUED
  61 00 e8 ff ff ff 4f 00   2d+11:30:23.499  WRITE FPDMA QUEUED
  61 00 18 ff ff ff 4f 00   2d+11:30:23.497  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00   2d+11:30:23.496  WRITE FPDMA QUEUED

Error 6 occurred at disk power-on lifetime: 19018 hours (792 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 ff ff ff 4f 00   1d+06:41:15.376  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00   1d+06:41:15.366  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00   1d+06:41:15.158  READ FPDMA QUEUED
  60 00 88 ff ff ff 4f 00   1d+06:41:13.630  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00   1d+06:41:13.630  READ FPDMA QUEUED

Error 5 occurred at disk power-on lifetime: 18939 hours (789 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 ff ff ff 4f 00  18d+01:58:44.396  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  18d+01:58:44.389  READ FPDMA QUEUED
  61 00 68 ff ff ff 4f 00  18d+01:58:44.388  WRITE FPDMA QUEUED
  61 00 30 ff ff ff 4f 00  18d+01:58:44.388  WRITE FPDMA QUEUED
  61 00 d0 ff ff ff 4f 00  18d+01:58:44.387  WRITE FPDMA QUEUED

Error 4 occurred at disk power-on lifetime: 18023 hours (750 days + 23 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 ff ff ff 4f 00  29d+14:17:47.232  READ FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.871  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.871  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.870  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  29d+14:17:44.870  WRITE FPDMA QUEUED

Error 3 occurred at disk power-on lifetime: 15031 hours (626 days + 7 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
  -- -- -- -- -- -- --
  40 51 00 64 fd 00 00  Error: UNC at LBA = 0x0000fd64 = 64868

  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 02 64 fd 00 40 00   2d+04:25:00.855  READ FPDMA QUEUED
  60 00 00 7e 41 9a 47 00   2d+04:25:00.758  READ FPDMA QUEUED
  60 00 c8 b6 40 9a 47 00   2d+04:25:00.757  READ FPDMA QUEUED
  60 00 3a 7c 40 9a 47 00   2d+04:25:00.757  READ FPDMA QUEUED
  60 00 08 74 40 9a 47 00   2d+04:25:00.757  READ FPDMA QUEUED

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

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.

[R]

UNC at LBA xxx = necitatelny sektor (UNCorrectable). Skus ten sektor precitat (hdparm --read-sector xxx /dev/yyy).

BTW. Ten sektor ma podozrive cislo - nejaky bug vo firmware?

[LuRy]

Jsou tam tyhle disky dva totozna serie i velikost. Koukam ze jsou tam samy fka takze ten sektor je asi posledni .. nicemene read-sector probehl ok

 hdparm --read-sector 0x0fffffff /dev/sdb

/dev/sdb:
reading sector 268435455: succeeded
f89f e7bc f5ac e7be f9d3 d678 d93a 4306
f7b2 eccc b3d9 dfaf cd7d 443d aafa 4a75
5425 590c f7b5 6afd 5408 1259 a8cb 7999
59f1 36fa 5dbc 8f6b 75c9 e4be 9cdb 914d
a4eb d312 9744 a967 5e8c 8b7f fd58 e457
60f6 f105 167b 62f5 9ffd f941 d3ac 637b
365f fc2b bfdd 3cb9 28c2 b94c a327 316a
d506 9761 b29e 2894 7746 2567 5e9f 9230
a33e 9bf8 6ab3 0b9f 3476 95f5 de0f 4b4b
2068 0c51 8b97 7fa1 b0a0 88e5 b23b 9bcc
02c9 843d 8cc0 2967 d8c5 a2c8 b1ce fc04
f32b 6115 67b1 d7d4 5b17 c2c4 e822 445a
e894 d8fc 161d 8dee 2fec 1e78 f6f8 353f
27bd 1296 34e0 449b 6695 f444 8d40 4306
13e9 0b06 d743 9d26 af9a c42b 623d fb18
c30c 951c 89d9 74d1 7cd6 6f78 fd2d 5c8f
652c ecc9 7d5c ef93 f9ea f3f3 37af eae3
13b5 430d 24da 95d9 29a3 1087 6d9e b8e6
e500 dda3 ad7d 8a65 1ae7 b09f 1d19 a1fb
171e 9620 3e60 f9bd af7d 4d90 435d 557d
d6fa c3dc eb86 ef13 c515 b9ed 8326 4dfa
3630 d6d9 6805 c6f9 3fd8 e5b5 b232 4af1
6761 9f18 20fb c447 ace0 17de 631c 8c48
1a61 b7a2 eb8e 421d 58fe d79e 8e5a 5748
7257 367d fa52 2585 5fae b168 2608 30fe
6394 34b8 953b b08a 6360 4480 ea40 bff6
247d cfe6 bb79 5d9a 7e5a b7a5 a6da 03e2
f6d9 6009 8439 ee3c babf bf60 c7ca ef6b
fe60 1af4 537b b375 7265 e88e 5f05 8bfd
0b4f ac24 93a2 5bb6 9b37 22d4 f59b 7bcf
4b9f d0a9 dba3 7d31 b5f3 9d33 d9ca bcf1
12e6 7483 a4df 95e6 f94b fb2d fd64 bd25

[R]

Aky tam mas kernel? Nie je to tento bug? http://patchwork.ozlabs.org/patch/49616/

[LuRy]

kernel je videt v hlavicce smartctl :) [x86_64-linux-2.6.32-5-xen-amd64] - v tom bugreportu se mluvi o 2.6.34 nehlede na to ze musim mit kernel pro xen a ten v ofi repozitarich debian 6 novejsi neni

[frr]

Souhlasím, jedná se velmi pravděpodobně o tento bug. V dnešní době "starej, ale dobrej". Podle specifikací ATA 0x0FFFFFFF už není platná adresa LBA28 (ačkoli čistě teoreticky se to do 28 bitů vejde). Prostě to standard tak definuje. Proto je potřeba, aby kernel hlídal, jestli v dané transakci nepřesáhne konec bloku přes tuto adresu VČETNĚ - a pokud ano, musí použít LBA48.

Svého času jsem to zaznamenal u disků Hitachi - zatímco ostatní výrobci (včetně Seagate) spokojeně brali 0x0FFFFFFF jako platnou LBA28 adresu. Takže už i ty, Brute...

Příznaky ve SMARTu tomu přesně odpovídají. Disk se nesnaží realokovat sektory (není důvod), ani nehlásí žádné "offline uncorrectable", jenom v error logu jsou vidět chyby typu "neznámá LBA adresa". Konkrétní důvod už tam bohužel uveden není - totiž že "neznámá" v tomto případě znamená "neplatná v LBA28".

Na samém konci výše odkazovaného webu (záznam v patchworku) je triviální čtyřřádkový patch. Takže pokud chcete mít jistotu, sežeňte si zdrojáky svého kernelu a můžete si to snadno zkontrolovat, případně opravit.

[Aleš Kapica]

Podívej chytrolíne. Párkrát jsem se s tímhhle už setkal a pokaždé to vyřešila výměna zdroje.

Kdyby tam měl skutečně vadný sektor, tak by se mu neshodovaly ty dvě hodnoty o kterých jsem psal.

[LuRy]

no dobre dejme tomu ze je to zdroj, ale vsechny 4 disky jsou na stejne vetvi a ostatni funguji takhle po celou dobu bez problemu resp. bez hlasek ve smartu

[Aleš Kapica]

No právě. Mě to začalo dělat až když jsem měl těch disků více a navíc pouze při zátěži - kupř. třeba při spuštění, kdy se roztáčely všechny plotny a inicializovalo pole.

Pak jsem měl podobné errory u zdroje, který měl zdroj s modulárními kabely. Stačilo vyndat z šuplete disk a z raidu vypadnul disk, přestože byl na jiné větvi. Koupil jsem pořádný zdroj, s nemodulárními kabely, který byl sice dražší (protože pasiv), ale mám od té doby pokoj.

[LuRy]

Ja prave problem ve zdroji nevidim, je dostatecne silny, vse na jedne vetvi, dela to pouze jeden disk a navic se jeden disk nedavno pridaval a zminene errory jsou jeste davno predtim kdy tam byli dokonce jen 2 disky pridaval se 750GB na zalohy a pak ten terovej. Tohle se tahne od doby kdy byli 2x 1TB v mdraidu a obdobny problem ma i kamarad taky mdraid a erroru tohoto typu ma 36 ale tam se to vyresilo jinym SATA kabelem. Tak predpokladam ze muze byt i problem v tomto ?

[Pindal]

Hlavně tam máš abnormálně vysokou hodnotu u Command_Timeout, což je většinou známka blbého kabelu, jak datového tak napájecího. Nebo to může být právě problém zdroje. Hardisky nejsou stejný, protože součástky mají určité tolerance a proto některý můžou mít vyšší citlivost třeba na špičky nebo zvlnění napětí.

[R]

Ja si na rozdiel od teba necuciam rozumy z prstu. Autor tam ma pravdepodobne original zdroj v znackovom serveri, ziadnu desktopovu sracku. SMART jasne ukazuje, ze vznikla chyba pri citani sektora.

[Aleš Kapica]

Já nevím jaký tam má zdroj. Já jenom vím, za jakých okolností se objevují tyhle chyby.

[ewew]

Skús pozrieť tento bug report, či pomôže.