Festplatte defekt? - end_request: I/O error, dev sda

d3p · Mar 1, 2015

Hallo,

Ich hab bei meiner Routineuntersuchung gerade festgestellt, dass eine Festplatte Fehler ausspuckt.

Die Platte hat rund 731 Tage auf dem Buckel, geht also eigentlich noch.

Code:

root@server # smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-4-amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     ST33000650NS
Serial Number:    Z292S9CJ
LU WWN Device Id: 5 000c50 04d2fee04
Firmware Version: 0004
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Size:      512 bytes logical/physical
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 Mar  1 13:00:11 2015 CET
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:      ( 241) Self-test routine in progress...
                                        10% of test remaining.
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:        ( 255) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x10bd) 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   082   060   044    Pre-fail  Always       -       170593875
  3 Spin_Up_Time            0x0003   092   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       12
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       317789849
  9 Power_On_Hours          0x0032   080   080   000    Old_age   Always       -       17551
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       12
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   097   097   000    Old_age   Always       -       3
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   058   054   045    Old_age   Always       -       42 (Min/Max 24/44)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       6
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       12
194 Temperature_Celsius     0x0022   042   046   000    Old_age   Always       -       42 (0 13 0 0)
195 Hardware_ECC_Recovered  0x001a   031   004   000    Old_age   Always       -       170593875
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: 6 (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 6 occurred at disk power-on lifetime: 17491 hours (728 days + 19 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 33 94 b3 02  Error: UNC at LBA = 0x02b39433 = 45323315

  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 00 80 92 b3 42 00  19d+21:46:16.679  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00  19d+21:46:16.679  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00  19d+21:46:16.679  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00  19d+21:46:16.678  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00  19d+21:46:16.678  READ NATIVE MAX ADDRESS EXT

Error 5 occurred at disk power-on lifetime: 17491 hours (728 days + 19 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 d4 93 b3 02  Error: UNC at LBA = 0x02b393d4 = 45323220

  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 00 80 92 b3 42 00  19d+21:46:06.887  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00  19d+21:46:06.887  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00  19d+21:46:06.886  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00  19d+21:46:06.886  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00  19d+21:46:06.886  READ NATIVE MAX ADDRESS EXT

Error 4 occurred at disk power-on lifetime: 17491 hours (728 days + 19 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 2c 94 b3 02  Error: UNC at LBA = 0x02b3942c = 45323308

  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 00 80 92 b3 42 00  19d+21:45:56.777  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00  19d+21:45:56.777  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00  19d+21:45:56.776  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00  19d+21:45:56.745  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00  19d+21:45:56.745  READ NATIVE MAX ADDRESS EXT

Error 3 occurred at disk power-on lifetime: 17491 hours (728 days + 19 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 f1 93 b3 02  Error: UNC at LBA = 0x02b393f1 = 45323249

  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 00 80 92 b3 42 00  19d+21:45:46.644  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00  19d+21:45:46.644  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00  19d+21:45:46.643  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00  19d+21:45:46.643  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00  19d+21:45:46.643  READ NATIVE MAX ADDRESS EXT

Error 2 occurred at disk power-on lifetime: 17491 hours (728 days + 19 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 e2 93 b3 02  Error: UNC at LBA = 0x02b393e2 = 45323234

  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 00 80 92 b3 42 00  19d+21:45:36.468  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00  19d+21:45:36.468  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00  19d+21:45:36.467  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00  19d+21:45:36.427  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00  19d+21:45:36.427  READ NATIVE MAX ADDRESS EXT

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%     17551         -
# 2  Extended offline    Completed without error       00%     16615         -
# 3  Short offline       Completed without error       00%     16448         -
# 4  Extended offline    Completed without error       00%     15633         -
# 5  Extended offline    Completed without error       00%     15602         -
# 6  Extended offline    Completed without error       00%     15321         -
# 7  Extended offline    Completed without error       00%     15290         -
# 8  Extended offline    Completed without error       00%     10518         -
# 9  Extended offline    Completed without error       00%         7         -

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.

dmesg.log

Code:

[6000019.061087] ata1.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0
[6000019.061119] ata1.00: irq_stat 0x40000008
[6000019.061142] ata1.00: failed command: READ FPDMA QUEUED
[6000019.061171] ata1.00: cmd 60/00:30:80:92:b3/04:00:02:00:00/40 tag 6 ncq 524288 in
[6000019.061172]          res 41/40:00:2d:94:b3/00:04:02:00:00/00 Emask 0x409 (media error) <F>
[6000019.061268] ata1.00: status: { DRDY ERR }
[6000019.061291] ata1.00: error: { UNC }
[6000019.110357] ata1.00: configured for UDMA/133
[6000019.110395] ata1: EH complete
[6000029.246300] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x0
[6000029.246331] ata1.00: irq_stat 0x40000008
[6000029.246356] ata1.00: failed command: READ FPDMA QUEUED
[6000029.246384] ata1.00: cmd 60/00:40:80:92:b3/04:00:02:00:00/40 tag 8 ncq 524288 in
[6000029.246386]          res 41/40:00:e2:93:b3/00:04:02:00:00/00 Emask 0x409 (media error) <F>
[6000029.246466] ata1.00: status: { DRDY ERR }
[6000029.246488] ata1.00: error: { UNC }
[6000029.279571] ata1.00: configured for UDMA/133
[6000029.279610] ata1: EH complete
[6000039.259377] ata1.00: exception Emask 0x0 SAct 0x800 SErr 0x0 action 0x0
[6000039.259408] ata1.00: irq_stat 0x40000008
[6000039.259433] ata1.00: failed command: READ FPDMA QUEUED
[6000039.259462] ata1.00: cmd 60/00:58:80:92:b3/04:00:02:00:00/40 tag 11 ncq 524288 in
[6000039.259463]          res 41/40:00:f1:93:b3/00:04:02:00:00/00 Emask 0x409 (media error) <F>
[6000039.259544] ata1.00: status: { DRDY ERR }
[6000039.259565] ata1.00: error: { UNC }
[6000039.405830] ata1.00: configured for UDMA/133
[6000039.405868] ata1: EH complete
[6000049.475251] ata1.00: exception Emask 0x0 SAct 0x4000 SErr 0x0 action 0x0
[6000049.475282] ata1.00: irq_stat 0x40000008
[6000049.475306] ata1.00: failed command: READ FPDMA QUEUED
[6000049.475335] ata1.00: cmd 60/00:70:80:92:b3/04:00:02:00:00/40 tag 14 ncq 524288 in
[6000049.475336]          res 41/40:00:2c:94:b3/00:04:02:00:00/00 Emask 0x409 (media error) <F>
[6000049.475416] ata1.00: status: { DRDY ERR }
[6000049.475438] ata1.00: error: { UNC }
[6000049.508524] ata1.00: configured for UDMA/133
[6000049.508563] ata1: EH complete
[6000059.261045] ata1.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0
[6000059.261075] ata1.00: irq_stat 0x40000008
[6000059.261100] ata1.00: failed command: READ FPDMA QUEUED
[6000059.261128] ata1.00: cmd 60/00:88:80:92:b3/04:00:02:00:00/40 tag 17 ncq 524288 in
[6000059.261130]          res 41/40:00:d4:93:b3/00:04:02:00:00/00 Emask 0x409 (media error) <F>
[6000059.261210] ata1.00: status: { DRDY ERR }
[6000059.261232] ata1.00: error: { UNC }
[6000059.294301] ata1.00: configured for UDMA/133
[6000059.294337] ata1: EH complete
[6000068.978670] ata1.00: exception Emask 0x0 SAct 0x100000 SErr 0x0 action 0x0
[6000068.978700] ata1.00: irq_stat 0x40000008
[6000068.978726] ata1.00: failed command: READ FPDMA QUEUED
[6000068.978755] ata1.00: cmd 60/00:a0:80:92:b3/04:00:02:00:00/40 tag 20 ncq 524288 in
[6000068.978756]          res 41/40:00:33:94:b3/00:04:02:00:00/00 Emask 0x409 (media error) <F>
[6000068.980257] ata1.00: status: { DRDY ERR }
[6000068.980279] ata1.00: error: { UNC }
[6000069.112684] ata1.00: configured for UDMA/133
[6000069.112727] sd 0:0:0:0: [sda] Unhandled sense code
[6000069.112751] sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[6000069.112792] sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
[6000069.112836] Descriptor sense data with sense descriptors (in hex):
[6000069.112862]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[6000069.112904]         02 b3 94 33
[6000069.112929] sd 0:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
[6000069.112974] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 02 b3 92 80 00 04 00 00
[6000069.113015] end_request: I/O error, dev sda, sector 45323315
[6000069.113055] ata1: EH complete

Den betroffenen Sector (45323315) kann ich mittels hdparm erfolgreich auslesen.

Code:

root@server # hdparm --read-sector 45323315 /dev/sda

/dev/sda:
reading sector 45323315: succeeded
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000

Sollte ich mir Sorgen machen?

IP-Projects.de · Mar 1, 2015

Festplatte schnellstmöglich tauschen. Meinst sind das die ersten Anzeichen eines schleichenden Defekts.

GwenDragon · Mar 1, 2015

Hatte ich auch. Wenn auch erst bei ca. 30.000 h.
Lass sie tauschen.

ist das ein RAID?

d3p · Mar 1, 2015

GwenDragon said:
Hatte ich auch. Wenn auch erst bei ca. 30.000 h.
Lass sie tauschen.

ist das ein RAID?

Ja, ein SW-RAID.
Hab die Platte schon als fehlerhaft markiert, aus dem Verbund genommen und ein Ticket aufgemacht.

Danke euch!

Festplatte defekt? - end_request: I/O error, dev sda

d3p

Member

IP-Projects.de

Active Member

GwenDragon

Registered User

d3p

Member