• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

[gelöst] Festplattencontrollerfehler im dmesg

Hallo,

habe ein paar komische Meldungen im dmesg:

Code:
[ 6662.131158] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x400000 action 0x6 frozen
[ 6662.131162] ata1.00: irq_stat 0x08000000, interface fatal error
[ 6662.131166] ata1: SError: { Handshk }
[ 6662.131171] ata1.00: failed command: WRITE FPDMA QUEUED
[ 6662.131176] ata1.00: cmd 61/00:00:88:b5:72/04:00:00:00:00/40 tag 0 ncq 524288 out
[ 6662.131178]          res 50/00:00:88:b5:72/00:04:00:00:00/40 Emask 0x10 (ATA bus error)
[ 6662.131180] ata1.00: status: { DRDY }
[ 6662.131187] ata1: hard resetting link
[ 6662.436090] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 6662.439517] ata1.00: configured for UDMA/133
[ 6662.439643] ata1: EH complete
[ 9169.152673] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x400000 action 0x6 frozen
[ 9169.152678] ata1.00: irq_stat 0x08000000, interface fatal error
[ 9169.152681] ata1: SError: { Handshk }
[ 9169.152685] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9169.152691] ata1.00: cmd 61/00:00:88:01:5d/04:00:01:00:00/40 tag 0 ncq 524288 out
[ 9169.152692]          res 50/00:00:88:01:5d/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9169.152695] ata1.00: status: { DRDY }
[ 9169.152701] ata1: hard resetting link
[ 9169.459051] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 9169.462412] ata1.00: configured for UDMA/133
[ 9169.462534] ata1: EH complete
[ 9172.088626] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x400000 action 0x6 frozen
[ 9172.088631] ata1.00: irq_stat 0x08000000, interface fatal error
[ 9172.088635] ata1: SError: { Handshk }
[ 9172.088639] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.088645] ata1.00: cmd 61/00:00:88:5d:74/04:00:01:00:00/40 tag 0 ncq 524288 out
[ 9172.088646]          res 50/00:00:88:5d:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.088649] ata1.00: status: { DRDY }
[ 9172.088655] ata1: hard resetting link
[ 9172.396049] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 9172.399471] ata1.00: configured for UDMA/133
[ 9172.399598] ata1: EH complete
[ 9172.514186] ata1.00: exception Emask 0x10 SAct 0x1ff00fff SErr 0x400000 action 0x6 frozen
[ 9172.514191] ata1.00: irq_stat 0x08000000, interface fatal error
[ 9172.514195] ata1: SError: { Handshk }
[ 9172.514199] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514205] ata1.00: cmd 61/00:00:88:d1:74/04:00:01:00:00/40 tag 0 ncq 524288 out
[ 9172.514206]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514208] ata1.00: status: { DRDY }
[ 9172.514211] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514216] ata1.00: cmd 61/00:08:88:d5:74/04:00:01:00:00/40 tag 1 ncq 524288 out
[ 9172.514217]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514219] ata1.00: status: { DRDY }
[ 9172.514221] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514226] ata1.00: cmd 61/00:10:88:d9:74/04:00:01:00:00/40 tag 2 ncq 524288 out
[ 9172.514227]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514230] ata1.00: status: { DRDY }
[ 9172.514232] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514237] ata1.00: cmd 61/00:18:88:dd:74/04:00:01:00:00/40 tag 3 ncq 524288 out
[ 9172.514238]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514240] ata1.00: status: { DRDY }
[ 9172.514242] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514247] ata1.00: cmd 61/00:20:88:e1:74/04:00:01:00:00/40 tag 4 ncq 524288 out
[ 9172.514248]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514250] ata1.00: status: { DRDY }
[ 9172.514252] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514258] ata1.00: cmd 61/00:28:88:e5:74/04:00:01:00:00/40 tag 5 ncq 524288 out
[ 9172.514259]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514261] ata1.00: status: { DRDY }
[ 9172.514263] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514268] ata1.00: cmd 61/00:30:88:e9:74/04:00:01:00:00/40 tag 6 ncq 524288 out
[ 9172.514269]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514271] ata1.00: status: { DRDY }
[ 9172.514273] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514278] ata1.00: cmd 61/00:38:88:ed:74/04:00:01:00:00/40 tag 7 ncq 524288 out
[ 9172.514279]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514282] ata1.00: status: { DRDY }
[ 9172.514284] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514288] ata1.00: cmd 61/00:40:88:f1:74/04:00:01:00:00/40 tag 8 ncq 524288 out
[ 9172.514289]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514292] ata1.00: status: { DRDY }
[ 9172.514294] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514299] ata1.00: cmd 61/00:48:88:f5:74/04:00:01:00:00/40 tag 9 ncq 524288 out
[ 9172.514300]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514302] ata1.00: status: { DRDY }
[ 9172.514304] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514309] ata1.00: cmd 61/00:50:88:f9:74/04:00:01:00:00/40 tag 10 ncq 524288 out
[ 9172.514310]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514313] ata1.00: status: { DRDY }
[ 9172.514315] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514320] ata1.00: cmd 61/00:58:88:fd:74/04:00:01:00:00/40 tag 11 ncq 524288 out
[ 9172.514321]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514323] ata1.00: status: { DRDY }
[ 9172.514325] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514330] ata1.00: cmd 61/00:a0:88:ad:74/04:00:01:00:00/40 tag 20 ncq 524288 out
[ 9172.514331]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514334] ata1.00: status: { DRDY }
[ 9172.514336] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514341] ata1.00: cmd 61/00:a8:88:b1:74/04:00:01:00:00/40 tag 21 ncq 524288 out
[ 9172.514342]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514344] ata1.00: status: { DRDY }
[ 9172.514346] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514351] ata1.00: cmd 61/00:b0:88:b5:74/04:00:01:00:00/40 tag 22 ncq 524288 out
[ 9172.514352]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514355] ata1.00: status: { DRDY }
[ 9172.514357] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514362] ata1.00: cmd 61/00:b8:88:b9:74/04:00:01:00:00/40 tag 23 ncq 524288 out
[ 9172.514363]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514365] ata1.00: status: { DRDY }
[ 9172.514367] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514372] ata1.00: cmd 61/00:c0:88:bd:74/04:00:01:00:00/40 tag 24 ncq 524288 out
[ 9172.514373]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514375] ata1.00: status: { DRDY }
[ 9172.514377] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514382] ata1.00: cmd 61/00:c8:88:c1:74/04:00:01:00:00/40 tag 25 ncq 524288 out
[ 9172.514383]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514386] ata1.00: status: { DRDY }
[ 9172.514388] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514393] ata1.00: cmd 61/00:d0:88:c5:74/04:00:01:00:00/40 tag 26 ncq 524288 out
[ 9172.514394]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514396] ata1.00: status: { DRDY }
[ 9172.514398] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514403] ata1.00: cmd 61/00:d8:88:c9:74/04:00:01:00:00/40 tag 27 ncq 524288 out
[ 9172.514405]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514407] ata1.00: status: { DRDY }
[ 9172.514409] ata1.00: failed command: WRITE FPDMA QUEUED
[ 9172.514414] ata1.00: cmd 61/00:e0:88:cd:74/04:00:01:00:00/40 tag 28 ncq 524288 out
[ 9172.514415]          res 50/00:00:88:fd:74/00:04:01:00:00/40 Emask 0x10 (ATA bus error)
[ 9172.514417] ata1.00: status: { DRDY }
[ 9172.514424] ata1: hard resetting link
[ 9172.819040] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 9172.822479] ata1.00: configured for UDMA/133
[ 9172.822627] ata1: EH complete
[14053.713202] ata1.00: exception Emask 0x10 SAct 0x19 SErr 0x400000 action 0x6 frozen
[14053.713207] ata1.00: irq_stat 0x08000000, interface fatal error
[14053.713211] ata1: SError: { Handshk }
[14053.713215] ata1.00: failed command: WRITE FPDMA QUEUED
[14053.713221] ata1.00: cmd 61/08:00:58:fe:87/00:00:27:00:00/40 tag 0 ncq 4096 out
[14053.713222]          res 50/00:08:58:fe:87/00:00:27:00:00/40 Emask 0x10 (ATA bus error)
[14053.713225] ata1.00: status: { DRDY }
[14053.713227] ata1.00: failed command: WRITE FPDMA QUEUED
[14053.713232] ata1.00: cmd 61/08:18:48:fe:87/00:00:27:00:00/40 tag 3 ncq 4096 out
[14053.713233]          res 50/00:08:58:fe:87/00:00:27:00:00/40 Emask 0x10 (ATA bus error)
[14053.713235] ata1.00: status: { DRDY }
[14053.713237] ata1.00: failed command: WRITE FPDMA QUEUED
[14053.713242] ata1.00: cmd 61/08:20:50:fe:87/00:00:27:00:00/40 tag 4 ncq 4096 out
[14053.713243]          res 50/00:08:58:fe:87/00:00:27:00:00/40 Emask 0x10 (ATA bus error)
[14053.713246] ata1.00: status: { DRDY }
[14053.713252] ata1: hard resetting link
[14054.018103] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[14054.022611] ata1.00: configured for UDMA/133
[14054.022963] ata1: EH complete
[23765.115794] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x400000 action 0x6 frozen
[23765.115798] ata1.00: irq_stat 0x08000000, interface fatal error
[23765.115802] ata1: SError: { Handshk }
[23765.115806] ata1.00: failed command: WRITE FPDMA QUEUED
[23765.115812] ata1.00: cmd 61/00:00:88:31:30/04:00:2d:00:00/40 tag 0 ncq 524288 out
[23765.115813]          res 50/00:00:88:31:30/00:04:2d:00:00/40 Emask 0x10 (ATA bus error)
[23765.115816] ata1.00: status: { DRDY }
[23765.115822] ata1: hard resetting link
[23765.420050] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[23765.423388] ata1.00: configured for UDMA/133
[23765.423508] ata1: EH complete
[23917.201819] ata1.00: exception Emask 0x10 SAct 0x3c SErr 0x400000 action 0x6 frozen
[23917.201824] ata1.00: irq_stat 0x08000000, interface fatal error
[23917.201828] ata1: SError: { Handshk }
[23917.201832] ata1.00: failed command: WRITE FPDMA QUEUED
[23917.201838] ata1.00: cmd 61/00:10:88:8d:61/04:00:2d:00:00/40 tag 2 ncq 524288 out
[23917.201839]          res 50/00:00:88:69:61/00:04:2d:00:00/40 Emask 0x10 (ATA bus error)
[23917.201842] ata1.00: status: { DRDY }
[23917.201844] ata1.00: failed command: WRITE FPDMA QUEUED
[23917.201849] ata1.00: cmd 61/00:18:88:65:61/04:00:2d:00:00/40 tag 3 ncq 524288 out
[23917.201850]          res 50/00:00:88:69:61/00:04:2d:00:00/40 Emask 0x10 (ATA bus error)
[23917.201852] ata1.00: status: { DRDY }
[23917.201854] ata1.00: failed command: WRITE FPDMA QUEUED
[23917.201859] ata1.00: cmd 61/00:20:88:91:61/04:00:2d:00:00/40 tag 4 ncq 524288 out
[23917.201860]          res 50/00:00:88:69:61/00:04:2d:00:00/40 Emask 0x10 (ATA bus error)
[23917.201863] ata1.00: status: { DRDY }
[23917.201865] ata1.00: failed command: WRITE FPDMA QUEUED
[23917.201869] ata1.00: cmd 61/00:28:88:69:61/04:00:2d:00:00/40 tag 5 ncq 524288 out
[23917.201870]          res 50/00:00:88:69:61/00:04:2d:00:00/40 Emask 0x10 (ATA bus error)
[23917.201873] ata1.00: status: { DRDY }
[23917.201879] ata1: hard resetting link
[23917.508136] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[23917.511481] ata1.00: configured for UDMA/133
[23917.511611] ata1: EH complete

aber bei smartctl -x sieht alles gut aus:

Code:
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.1.9-1.4-desktop] (SUSE RPM)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar 7K3000
Device Model:     Hitachi HDS723030ALA640
Serial Number:    MK0311ABCDFGHI
LU WWN Device Id: 5 000cca 225c0d045
Firmware Version: MKAOA3B0
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sun Apr 15 19:02:18 2012 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:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        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:                (29034) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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.
SCT capabilities:              (0x003d) 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     PO-R--   100   100   016    -    0
  2 Throughput_Performance  P-S---   134   134   054    -    87
  3 Spin_Up_Time            POS---   132   132   024    -    614 (Average 558)
  4 Start_Stop_Count        -O--C-   100   100   000    -    64
  5 Reallocated_Sector_Ct   PO--CK   100   100   005    -    0
  7 Seek_Error_Rate         PO-R--   100   100   067    -    0
  8 Seek_Time_Performance   P-S---   133   133   020    -    27
  9 Power_On_Hours          -O--C-   099   099   000    -    11440
 10 Spin_Retry_Count        PO--C-   100   100   060    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    62
192 Power-Off_Retract_Count -O--CK   100   100   000    -    66
193 Load_Cycle_Count        -O--C-   100   100   000    -    66
194 Temperature_Celsius     -O----   166   166   000    -    36 (Min/Max 19/48)
196 Reallocated_Event_Count -O--CK   100   100   000    -    0
197 Current_Pending_Sector  -O---K   100   100   000    -    0
198 Offline_Uncorrectable   ---R--   100   100   000    -    0
199 UDMA_CRC_Error_Count    -O-R--   200   200   000    -    156
                            ||||||_ 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]
GP/S  Log at address 0x00 has    1 sectors [Log Directory]
SMART Log at address 0x01 has    1 sectors [Summary SMART error log]
GP    Log at address 0x03 has    1 sectors [Ext. Comprehensive SMART error log]
GP    Log at address 0x04 has    7 sectors [Device Statistics log]
SMART Log at address 0x06 has    1 sectors [SMART self-test log]
GP    Log at address 0x07 has    1 sectors [Extended self-test log]
GP    Log at address 0x08 has    1 sectors [Power Conditions log]
SMART Log at address 0x09 has    1 sectors [Selective self-test log]
GP    Log at address 0x10 has    1 sectors [NCQ Command Error log]
GP    Log at address 0x11 has    1 sectors [SATA Phy Event Counters]
GP    Log at address 0x20 has    1 sectors [Streaming performance log]
GP    Log at address 0x21 has    1 sectors [Write stream error log]
GP    Log at address 0x22 has    1 sectors [Read stream error log]
GP/S  Log at address 0x80 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x81 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x82 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x83 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x84 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x85 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x86 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x87 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x88 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x89 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8a has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8b has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8c has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8d has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8e has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8f has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x90 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x91 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x92 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x93 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x94 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x95 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x96 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x97 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x98 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x99 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9a has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9b has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9c has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9d has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9e has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9f has   16 sectors [Host vendor specific log]
GP/S  Log at address 0xe0 has    1 sectors [SCT Command/Status]
GP/S  Log at address 0xe1 has    1 sectors [SCT Data Transfer]

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
Device Error Count: 156 (device log contains only the most recent 4 errors)
        CR     = Command Register
        FEATR  = Features Register
        COUNT  = Count (was: Sector Count) Register
        LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
        LH     = LBA High (was: Cylinder High) Register    ]   LBA
        LM     = LBA Mid (was: Cylinder Low) Register      ] Register
        LL     = LBA Low (was: Sector Number) Register     ]
        DV     = Device (was: Device/Head) Register
        DC     = Device Control Register
        ER     = Error register
        ST     = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 156 [3] occurred at disk power-on lifetime: 11440 hours (476 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
  -- -- -- == -- == == == -- -- -- -- --
  84 -- 51 00 d0 00 00 2d 61 90 b8 0d 00  Error: ICRC, ABRT at LBA = 0x2d6190b8 = 761368760

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 04 00 00 d0 00 00 2d 61 90 b8 4d ff  1d+01:02:50.868  WRITE FPDMA QUEUED
  61 04 00 00 28 00 00 2d 61 69 88 40 00  1d+01:02:50.863  WRITE FPDMA QUEUED
  61 04 00 00 20 00 00 2d 61 91 88 40 00  1d+01:02:50.863  WRITE FPDMA QUEUED
  61 04 00 00 10 00 00 2d 61 8d 88 40 00  1d+01:02:50.854  WRITE FPDMA QUEUED
  61 04 00 00 08 00 00 2d 61 61 88 40 00  1d+01:02:50.851  WRITE FPDMA QUEUED

Error 155 [2] occurred at disk power-on lifetime: 11440 hours (476 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
  -- -- -- == -- == == == -- -- -- -- --
  84 -- 51 04 00 00 00 2d 30 31 88 0d 00  Error: ICRC, ABRT at LBA = 0x2d303188 = 758133128

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 04 00 00 c0 00 00 2d 30 34 c7 4d ff  1d+01:00:19.728  WRITE FPDMA QUEUED
  61 04 00 00 00 00 00 2d 30 31 88 40 00  1d+01:00:19.725  WRITE FPDMA QUEUED
  61 04 00 00 00 00 00 2d 30 2d 88 40 00  1d+01:00:19.719  WRITE FPDMA QUEUED
  61 04 00 00 00 00 00 2d 30 29 88 40 00  1d+01:00:19.713  WRITE FPDMA QUEUED
  61 04 00 00 00 00 00 2d 30 25 88 40 00  1d+01:00:19.707  WRITE FPDMA QUEUED

Error 154 [1] occurred at disk power-on lifetime: 11440 hours (476 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
  -- -- -- == -- == == == -- -- -- -- --
  84 -- 51 00 c0 00 00 2d 30 34 c8 0d 00  Error: ICRC, ABRT at LBA = 0x2d3034c8 = 758133960

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 04 00 00 c0 00 00 2d 30 34 c7 4d ff  1d+01:00:19.728  WRITE FPDMA QUEUED
  61 04 00 00 00 00 00 2d 30 31 88 40 00  1d+01:00:19.725  WRITE FPDMA QUEUED
  61 04 00 00 00 00 00 2d 30 2d 88 40 00  1d+01:00:19.719  WRITE FPDMA QUEUED
  61 04 00 00 00 00 00 2d 30 29 88 40 00  1d+01:00:19.713  WRITE FPDMA QUEUED
  61 04 00 00 00 00 00 2d 30 25 88 40 00  1d+01:00:19.707  WRITE FPDMA QUEUED

Error 153 [0] occurred at disk power-on lifetime: 11437 hours (476 days + 13 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
  -- -- -- == -- == == == -- -- -- -- --
  84 -- 51 00 08 00 00 27 87 fe 48 07 00  Error: ICRC, ABRT at LBA = 0x2787fe48 = 663223880

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 08 00 00 00 00 27 87 fe 50 47 ff     22:19:28.717  WRITE FPDMA QUEUED
  61 00 08 00 00 00 00 27 87 fe 58 40 00     22:19:28.716  WRITE FPDMA QUEUED
  61 00 08 00 20 00 00 27 87 fe 50 40 00     22:19:28.716  WRITE FPDMA QUEUED
  61 00 08 00 18 00 00 27 87 fe 48 40 00     22:19:28.716  WRITE FPDMA QUEUED
  61 00 08 00 10 00 00 27 87 fe 40 40 00     22:19:28.716  WRITE FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     11414         -
# 2  Extended offline    Completed without error       00%     10599         -

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):       256 (0x0100)
SCT Support Level:                   1
Device State:                        SMART Off-line Data Collection executing in background (4)
Current Temperature:                    36 Celsius
Power Cycle Min/Max Temperature:     31/38 Celsius
Lifetime    Min/Max Temperature:     19/48 Celsius
Under/Over Temperature Limit Count:   0/0
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:           -40/70 Celsius
Temperature History Size (Index):    128 (125)

Index    Estimated Time   Temperature Celsius
 126    2012-04-15 16:55    33  **************
 127    2012-04-15 16:56    33  **************
   0    2012-04-15 16:57    34  ***************
 ...    ..( 15 skipped).    ..  ***************
  16    2012-04-15 17:13    34  ***************
  17    2012-04-15 17:14    35  ****************
  18    2012-04-15 17:15    34  ***************
 ...    ..(  5 skipped).    ..  ***************
  24    2012-04-15 17:21    34  ***************
  25    2012-04-15 17:22    35  ****************
  26    2012-04-15 17:23    34  ***************
  27    2012-04-15 17:24    34  ***************
  28    2012-04-15 17:25    35  ****************
  29    2012-04-15 17:26    34  ***************
  30    2012-04-15 17:27    34  ***************
  31    2012-04-15 17:28    35  ****************
  32    2012-04-15 17:29    34  ***************
  33    2012-04-15 17:30    35  ****************
  34    2012-04-15 17:31    35  ****************
  35    2012-04-15 17:32    34  ***************
  36    2012-04-15 17:33    34  ***************
  37    2012-04-15 17:34    35  ****************
  38    2012-04-15 17:35    34  ***************
  39    2012-04-15 17:36    34  ***************
  40    2012-04-15 17:37    35  ****************
  41    2012-04-15 17:38    34  ***************
  42    2012-04-15 17:39    35  ****************
 ...    ..( 56 skipped).    ..  ****************
  99    2012-04-15 18:36    35  ****************
 100    2012-04-15 18:37    36  *****************
 101    2012-04-15 18:38    35  ****************
 ...    ..(  2 skipped).    ..  ****************
 104    2012-04-15 18:41    35  ****************
 105    2012-04-15 18:42    36  *****************
 106    2012-04-15 18:43    35  ****************
 ...    ..(  6 skipped).    ..  ****************
 113    2012-04-15 18:50    35  ****************
 114    2012-04-15 18:51    36  *****************
 115    2012-04-15 18:52    35  ****************
 116    2012-04-15 18:53    35  ****************
 117    2012-04-15 18:54    35  ****************
 118    2012-04-15 18:55    36  *****************
 ...    ..(  6 skipped).    ..  *****************
 125    2012-04-15 19:02    36  *****************

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            1  Command failed due to ICRC error
0x0002  2           12  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2           12  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
0x0009  2           31  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2           26  Device-to-host register FISes sent due to a COMRESET
0x000b  2           12  CRC errors within host-to-device FIS
0x000d  2            1  Non-CRC errors within host-to-device FIS

Was für Ursachen können diese Fehlemeldungen haben? Was mich noch wundert ist diese UDMA133 Meldung: Der IDE Controller ist nämlich deaktiviert und es sind keine Geräte angeschlossen. Kann man diese "SCT Error Recovery Control" aktivieren und bringt das was?

Danke und Gruß
schnurzelat
 

RME

Advanced Hacker
Hallo,

Code:
[ 6662.131158] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x400000 action 0x6 frozen
[ 6662.131162] ata1.00: irq_stat 0x08000000, interface fatal error
[ 6662.131166] ata1: SError: { Handshk }
>>> http://lime-technology.com/wiki/index.php/The_Analysis_of_Drive_Issues

Drive interface issue #3
An example:
Code:
   ata2.00: exception Emask 0x10 SAct 0x7ff4f SErr 0x400100 action 0x6 frozen
   ata2.00: irq_stat 0x08000000, interface fatal error
   ata2: SError: { UnrecovData Handshk }
From an expert:
"This is transmission error. Most common causes are power related or
unreliable connection especially if backplanes are involved. Is the
problem still reproducible? If so, can you please try to move it to
different power connector and SATA port and see what changes?"
--
tejun
>>> Kabel überprüfen, evtl. austauschen, umstecken, etc.

Gruss,
Roland
 
Oben