Ata bus error linux

Hello,
I have some problems with hard drive on my laptop. Sometimes everything freezes for few seconds (usually during start-up, but sometimes after I login) and I get some errors. After that, everything seems to be working fine.

Part of dmesg with errors:

[   10.019887] ata1.00: cmd 60/00:10:10:da:59/01:00:0f:00:00/40 tag 2 ncq 131072 in
                        res 41/84:00:f2:da:59/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   10.019968] ata1.00: status: { DRDY ERR }
[   10.019992] ata1.00: error: { ICRC ABRT }
[   10.020017] ata1: hard resetting link
[   10.339913] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   10.443163] ata1.00: configured for UDMA/133
[   10.443191] ata1: EH complete
[   10.516832] ata1.00: exception Emask 0x0 SAct 0x7000 SErr 0x0 action 0x6
[   10.516877] ata1.00: irq_stat 0x40000008
[   10.516902] ata1.00: failed command: READ FPDMA QUEUED
[   10.516935] ata1.00: cmd 60/e8:60:e8:16:3b/00:00:0f:00:00/40 tag 12 ncq 118784 in
                        res 41/84:e8:8c:17:3b/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   10.517017] ata1.00: status: { DRDY ERR }
[   10.517041] ata1.00: error: { ICRC ABRT }
[   10.517067] ata1: hard resetting link
[   10.836973] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   10.964972] ata1.00: configured for UDMA/133
[   10.965002] ata1: EH complete
[   10.984003] ata1: limiting SATA link speed to 3.0 Gbps
[   10.984015] ata1.00: exception Emask 0x0 SAct 0x60020000 SErr 0x0 action 0x6
[   10.984106] ata1.00: irq_stat 0x40000008
[   10.984157] ata1.00: failed command: READ FPDMA QUEUED
[   10.984225] ata1.00: cmd 60/20:e8:40:6e:b0/00:00:13:00:00/40 tag 29 ncq 16384 in
                        res 41/84:20:46:6e:b0/00:00:13:00:00/00 Emask 0x410 (ATA bus error) <F>
[   10.984397] ata1.00: status: { DRDY ERR }
[   10.984445] ata1.00: error: { ICRC ABRT }
[   10.984497] ata1: hard resetting link
[   11.304016] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   11.409308] ata1.00: configured for UDMA/133
[   11.409343] ata1: EH complete
[   11.441025] vboxpci: IOMMU not found (not registered)
[   11.543239] bbswitch: version 0.8
[   11.543246] bbswitch: Found integrated VGA device 0000:00:02.0: _SB_.PCI0.GFX0
[   11.543252] bbswitch: Found discrete VGA device 0000:03:00.0: _SB_.PCI0.RP05.PEGP
[   11.543262] ACPI Warning: _SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[   11.543355] bbswitch: detected an Optimus _DSM function
[   11.543372] pci 0000:03:00.0: enabling device (0006 -> 0007)
[   11.543434] bbswitch: Succesfully loaded. Discrete card 0000:03:00.0 is on
[   11.545169] bbswitch: disabling discrete graphics
[   11.545181] ACPI Warning: _SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[   13.327790] r8169 0000:01:00.0 enp1s0: link up
[   20.651344] ata1.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x6
[   20.651349] ata1.00: irq_stat 0x40000008
[   20.651353] ata1.00: failed command: READ FPDMA QUEUED
[   20.651359] ata1.00: cmd 60/08:c8:98:86:ae/00:00:10:00:00/40 tag 25 ncq 4096 in
                        res 41/84:08:98:86:ae/00:00:10:00:00/00 Emask 0x410 (ATA bus error) <F>
[   20.651361] ata1.00: status: { DRDY ERR }
[   20.651363] ata1.00: error: { ICRC ABRT }
[   20.651367] ata1: hard resetting link
[   20.971293] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   21.080441] ata1.00: configured for UDMA/133
[   21.080467] ata1: EH complete
[   21.121498] ata1.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6
[   21.121503] ata1.00: irq_stat 0x40000008
[   21.121507] ata1.00: failed command: READ FPDMA QUEUED
[   21.121513] ata1.00: cmd 60/00:e8:00:f4:69/01:00:0f:00:00/40 tag 29 ncq 131072 in
                        res 41/84:00:ee:f4:69/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   21.121515] ata1.00: status: { DRDY ERR }
[   21.121517] ata1.00: error: { ICRC ABRT }
[   21.121521] ata1: hard resetting link
[   21.441483] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   21.546775] ata1.00: configured for UDMA/133
[   21.546795] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[   21.546798] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[   21.546801] sd 0:0:0:0: [sda] ASC=0x47 ASCQ=0x0
[   21.546802] sd 0:0:0:0: [sda] CDB: 
[   21.546804] cdb[0]=0x28: 28 00 0f 69 f4 00 00 01 00 00
[   21.546812] blk_update_request: I/O error, dev sda, sector 258601984
[   21.546829] ata1: EH complete
[   21.606131] ata1.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x6
[   21.606139] ata1.00: irq_stat 0x40000008
[   21.606145] ata1.00: failed command: READ FPDMA QUEUED
[   21.606155] ata1.00: cmd 60/88:48:00:d8:36/00:00:0f:00:00/40 tag 9 ncq 69632 in
                        res 41/84:88:04:d8:36/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   21.606160] ata1.00: status: { DRDY ERR }
[   21.606163] ata1.00: error: { ICRC ABRT }
[   21.606170] ata1: hard resetting link
[   21.924963] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   22.035385] ata1.00: configured for UDMA/133
[   22.035408] ata1: EH complete
[   22.111984] ata1: limiting SATA link speed to 1.5 Gbps
[   22.111991] ata1.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x6
[   22.111994] ata1.00: irq_stat 0x40000008
[   22.111997] ata1.00: failed command: READ FPDMA QUEUED
[   22.112003] ata1.00: cmd 60/90:c0:48:39:32/00:00:0f:00:00/40 tag 24 ncq 73728 in
                        res 41/84:90:8a:39:32/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   22.112005] ata1.00: status: { DRDY ERR }
[   22.112007] ata1.00: error: { ICRC ABRT }
[   22.112011] ata1: hard resetting link
[   22.431783] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   22.535011] ata1.00: configured for UDMA/133
[   22.535038] ata1: EH complete
[   22.618877] ata1.00: exception Emask 0x0 SAct 0x1e SErr 0x0 action 0x6
[   22.618886] ata1.00: irq_stat 0x40000008
[   22.618891] ata1.00: failed command: READ FPDMA QUEUED
[   22.618901] ata1.00: cmd 60/00:08:08:2c:32/01:00:0f:00:00/40 tag 1 ncq 131072 in
                        res 41/84:00:70:2c:32/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   22.618906] ata1.00: status: { DRDY ERR }
[   22.618909] ata1.00: error: { ICRC ABRT }
[   22.618920] ata1: hard resetting link
[   22.938608] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   23.023643] ata1.00: configured for UDMA/133
[   23.023682] ata1: EH complete
[   53.428943] ata1.00: exception Emask 0x1 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
[   53.428953] ata1.00: irq_stat 0x40000008
[   53.428960] ata1.00: failed command: READ FPDMA QUEUED
[   53.428971] ata1.00: cmd 60/00:00:00:e8:31/01:00:10:00:00/40 tag 0 ncq 131072 in
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x5 (timeout)
[   53.428976] ata1.00: status: { DRDY }
[   53.428981] ata1.00: failed command: READ FPDMA QUEUED
[   53.428990] ata1.00: cmd 60/08:08:20:fe:e9/00:00:0f:00:00/40 tag 1 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.428994] ata1.00: status: { DRDY }
[   53.428998] ata1.00: failed command: READ FPDMA QUEUED
[   53.429006] ata1.00: cmd 60/08:10:28:fe:e9/00:00:0f:00:00/40 tag 2 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429010] ata1.00: status: { DRDY }
[   53.429014] ata1.00: failed command: READ FPDMA QUEUED
[   53.429022] ata1.00: cmd 60/08:18:30:fe:e9/00:00:0f:00:00/40 tag 3 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429026] ata1.00: status: { DRDY }
[   53.429029] ata1.00: failed command: READ FPDMA QUEUED
[   53.429037] ata1.00: cmd 60/08:20:38:fe:e9/00:00:0f:00:00/40 tag 4 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429042] ata1.00: status: { DRDY }
[   53.429045] ata1.00: failed command: READ FPDMA QUEUED
[   53.429053] ata1.00: cmd 60/08:28:40:fe:e9/00:00:0f:00:00/40 tag 5 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429057] ata1.00: status: { DRDY }
[   53.429061] ata1.00: failed command: READ FPDMA QUEUED
[   53.429069] ata1.00: cmd 60/08:30:48:fe:e9/00:00:0f:00:00/40 tag 6 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429073] ata1.00: status: { DRDY }
[   53.429076] ata1.00: failed command: READ FPDMA QUEUED
[   53.429084] ata1.00: cmd 60/08:38:50:fe:e9/00:00:0f:00:00/40 tag 7 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429089] ata1.00: status: { DRDY }
[   53.429092] ata1.00: failed command: READ FPDMA QUEUED
[   53.429100] ata1.00: cmd 60/08:40:58:fe:e9/00:00:0f:00:00/40 tag 8 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429104] ata1.00: status: { DRDY }
[   53.429108] ata1.00: failed command: READ FPDMA QUEUED
[   53.429116] ata1.00: cmd 60/08:48:60:fe:e9/00:00:0f:00:00/40 tag 9 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429120] ata1.00: status: { DRDY }
[   53.429124] ata1.00: failed command: READ FPDMA QUEUED
[   53.429132] ata1.00: cmd 60/08:50:68:fe:e9/00:00:0f:00:00/40 tag 10 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429136] ata1.00: status: { DRDY }
[   53.429139] ata1.00: failed command: READ FPDMA QUEUED
[   53.429148] ata1.00: cmd 60/08:58:70:fe:e9/00:00:0f:00:00/40 tag 11 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429152] ata1.00: status: { DRDY }
[   53.429155] ata1.00: failed command: READ FPDMA QUEUED
[   53.429163] ata1.00: cmd 60/08:60:78:fe:e9/00:00:0f:00:00/40 tag 12 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429168] ata1.00: status: { DRDY }
[   53.429171] ata1.00: failed command: READ FPDMA QUEUED
[   53.429179] ata1.00: cmd 60/08:68:80:fe:e9/00:00:0f:00:00/40 tag 13 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429183] ata1.00: status: { DRDY }
[   53.429187] ata1.00: failed command: READ FPDMA QUEUED
[   53.429195] ata1.00: cmd 60/08:70:18:e8:a9/00:00:16:00:00/40 tag 14 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429199] ata1.00: status: { DRDY }
[   53.429203] ata1.00: failed command: READ FPDMA QUEUED
[   53.429211] ata1.00: cmd 60/08:78:90:fe:e9/00:00:0f:00:00/40 tag 15 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429215] ata1.00: status: { DRDY }
[   53.429218] ata1.00: failed command: READ FPDMA QUEUED
[   53.429226] ata1.00: cmd 60/08:80:98:fe:e9/00:00:0f:00:00/40 tag 16 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429230] ata1.00: status: { DRDY }
[   53.429234] ata1.00: failed command: READ FPDMA QUEUED
[   53.429242] ata1.00: cmd 60/08:88:a0:fe:e9/00:00:0f:00:00/40 tag 17 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429246] ata1.00: status: { DRDY }
[   53.429250] ata1.00: failed command: READ FPDMA QUEUED
[   53.429258] ata1.00: cmd 60/08:90:a8:fe:e9/00:00:0f:00:00/40 tag 18 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429262] ata1.00: status: { DRDY }
[   53.429265] ata1.00: failed command: READ FPDMA QUEUED
[   53.429273] ata1.00: cmd 60/08:98:b0:fe:e9/00:00:0f:00:00/40 tag 19 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429277] ata1.00: status: { DRDY }
[   53.429281] ata1.00: failed command: READ FPDMA QUEUED
[   53.429289] ata1.00: cmd 60/08:a0:b8:fe:e9/00:00:0f:00:00/40 tag 20 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429293] ata1.00: status: { DRDY }
[   53.429297] ata1.00: failed command: READ FPDMA QUEUED
[   53.429305] ata1.00: cmd 60/08:a8:c0:fe:e9/00:00:0f:00:00/40 tag 21 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429309] ata1.00: status: { DRDY }
[   53.429312] ata1.00: failed command: READ FPDMA QUEUED
[   53.429320] ata1.00: cmd 60/08:b0:c8:fe:e9/00:00:0f:00:00/40 tag 22 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429325] ata1.00: status: { DRDY }
[   53.429328] ata1.00: failed command: READ FPDMA QUEUED
[   53.429336] ata1.00: cmd 60/08:b8:d0:fe:e9/00:00:0f:00:00/40 tag 23 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429340] ata1.00: status: { DRDY }
[   53.429344] ata1.00: failed command: READ FPDMA QUEUED
[   53.429352] ata1.00: cmd 60/08:c0:d8:fe:e9/00:00:0f:00:00/40 tag 24 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429356] ata1.00: status: { DRDY }
[   53.429360] ata1.00: failed command: READ FPDMA QUEUED
[   53.429367] ata1.00: cmd 60/08:c8:e0:fe:e9/00:00:0f:00:00/40 tag 25 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429372] ata1.00: status: { DRDY }
[   53.429375] ata1.00: failed command: READ FPDMA QUEUED
[   53.429383] ata1.00: cmd 60/08:d0:e8:fe:e9/00:00:0f:00:00/40 tag 26 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429387] ata1.00: status: { DRDY }
[   53.429391] ata1.00: failed command: READ FPDMA QUEUED
[   53.429399] ata1.00: cmd 60/08:d8:f0:fe:e9/00:00:0f:00:00/40 tag 27 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429403] ata1.00: status: { DRDY }
[   53.429407] ata1.00: failed command: READ FPDMA QUEUED
[   53.429414] ata1.00: cmd 60/08:e0:f8:fe:e9/00:00:0f:00:00/40 tag 28 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429419] ata1.00: status: { DRDY }
[   53.429422] ata1.00: failed command: READ FPDMA QUEUED
[   53.429430] ata1.00: cmd 60/08:e8:00:ff:e9/00:00:0f:00:00/40 tag 29 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429435] ata1.00: status: { DRDY }
[   53.429438] ata1.00: failed command: READ FPDMA QUEUED
[   53.429446] ata1.00: cmd 60/08:f0:88:fe:e9/00:00:0f:00:00/40 tag 30 ncq 4096 in
                        res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[   53.429450] ata1.00: status: { DRDY }
[   53.429458] ata1: hard resetting link
[   53.749173] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   53.836070] ata1.00: configured for UDMA/133
[   53.836079] ata1.00: device reported invalid CHS sector 0
[   53.836116] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[   53.836119] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[   53.836121] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[   53.836123] sd 0:0:0:0: [sda] CDB: 
[   53.836125] cdb[0]=0x28: 28 00 0f e9 fe 20 00 00 08 00
[   53.836133] blk_update_request: I/O error, dev sda, sector 266993184
[   53.836148] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[   53.836151] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[   53.836153] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[   53.836154] sd 0:0:0:0: [sda] CDB: 
[   53.836155] cdb[0]=0x28: 28 00 0f e9 fe 28 00 00 08 00
[   53.836162] blk_update_request: I/O error, dev sda, sector 266993192
[   53.836167] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[   53.836169] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[   53.836171] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[   53.836173] sd 0:0:0:0: [sda] CDB: 
[   53.836174] cdb[0]=0x28: 28 00 0f e9 fe 30 00 00 08 00
[   53.836180] blk_update_request: I/O error, dev sda, sector 266993200
[   53.836185] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[   53.836187] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[   53.836189] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[   53.836190] sd 0:0:0:0: [sda] CDB: 
[   53.836191] cdb[0]=0x28: 28 00 0f e9 fe 38 00 00 08 00
[   53.836198] blk_update_request: I/O error, dev sda, sector 266993208
[   53.836202] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[   53.836204] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[   53.836206] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[   53.836208] sd 0:0:0:0: [sda] CDB: 
[   53.836209] cdb[0]=0x28: 28 00 0f e9 fe 40 00 00 08 00
[   53.836215] blk_update_request: I/O error, dev sda, sector 266993216
[   53.836220] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[   53.836222] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[   53.836224] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[   53.836225] sd 0:0:0:0: [sda] CDB: 
[   53.836226] cdb[0]=0x28: 28 00 0f e9 fe 48 00 00 08 00
[   53.836232] blk_update_request: I/O error, dev sda, sector 266993224
[   53.836237] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[   53.836239] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[   53.836241] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[   53.836242] sd 0:0:0:0: [sda] CDB: 
[   53.836243] cdb[0]=0x28: 28 00 0f e9 fe 50 00 00 08 00
[   53.836249] blk_update_request: I/O error, dev sda, sector 266993232
[   53.836253] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[   53.836255] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[   53.836257] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[   53.836259] sd 0:0:0:0: [sda] CDB: 
[   53.836260] cdb[0]=0x28: 28 00 0f e9 fe 58 00 00 08 00
[   53.836266] blk_update_request: I/O error, dev sda, sector 266993240
[   53.836270] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[   53.836272] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[   53.836274] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[   53.836276] sd 0:0:0:0: [sda] CDB: 
[   53.836277] cdb[0]=0x28: 28 00 0f e9 fe 60 00 00 08 00
[   53.836283] blk_update_request: I/O error, dev sda, sector 266993248
[   53.836287] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[   53.836289] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[   53.836291] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[   53.836293] sd 0:0:0:0: [sda] CDB: 
[   53.836294] cdb[0]=0x28: 28 00 0f e9 fe 68 00 00 08 00
[   53.836300] blk_update_request: I/O error, dev sda, sector 266993256
[   53.836354] ata1: EH complete
[   53.922776] ata1.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x6
[   53.922827] ata1.00: irq_stat 0x40000008
[   53.922855] ata1.00: failed command: READ FPDMA QUEUED
[   53.922891] ata1.00: cmd 60/00:28:38:3f:04/01:00:10:00:00/40 tag 5 ncq 131072 in
                        res 41/84:00:5a:3f:04/00:01:10:00:00/00 Emask 0x410 (ATA bus error) <F>
[   53.922981] ata1.00: status: { DRDY ERR }
[   53.923007] ata1.00: error: { ICRC ABRT }
[   53.923037] ata1: hard resetting link
[   54.242882] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   54.357940] ata1.00: configured for UDMA/133
[   54.357967] ata1: EH complete
[   54.413337] ata1.00: limiting speed to UDMA/100:PIO4
[   54.413343] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6
[   54.413387] ata1.00: irq_stat 0x40000008
[   54.413412] ata1.00: failed command: READ FPDMA QUEUED
[   54.413445] ata1.00: cmd 60/20:40:c0:04:b1/00:00:16:00:00/40 tag 8 ncq 16384 in
                        res 41/84:20:d4:04:b1/00:00:16:00:00/00 Emask 0x410 (ATA bus error) <F>
[   54.413527] ata1.00: status: { DRDY ERR }
[   54.413551] ata1.00: error: { ICRC ABRT }
[   54.413578] ata1: hard resetting link
[   54.733264] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   54.835393] ata1.00: configured for UDMA/100
[   54.835419] ata1: EH complete
[   54.883575] ata1.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x6
[   54.883618] ata1.00: irq_stat 0x40000008
[   54.883643] ata1.00: failed command: READ FPDMA QUEUED
[   54.883675] ata1.00: cmd 60/08:18:e0:04:b1/00:00:16:00:00/40 tag 3 ncq 4096 in
                        res 41/84:08:e4:04:b1/00:00:16:00:00/00 Emask 0x410 (ATA bus error) <F>
[   54.883756] ata1.00: status: { DRDY ERR }
[   54.883779] ata1.00: error: { ICRC ABRT }
[   54.883805] ata1: hard resetting link
[   55.203636] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   55.301754] ata1.00: configured for UDMA/100
[   55.301780] ata1: EH complete
[   55.357428] ata1.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6
[   55.357474] ata1.00: irq_stat 0x40000008
[   55.357500] ata1.00: failed command: READ FPDMA QUEUED
[   55.357532] ata1.00: cmd 60/f0:90:e0:34:a5/00:00:0e:00:00/40 tag 18 ncq 122880 in
                        res 41/84:f0:ea:34:a5/00:00:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[   55.357613] ata1.00: status: { DRDY ERR }
[   55.357636] ata1.00: error: { ICRC ABRT }
[   55.357661] ata1: hard resetting link
[   55.677344] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   55.779200] ata1.00: configured for UDMA/100
[   55.779228] ata1: EH complete
[   55.954538] ata1.00: exception Emask 0x0 SAct 0xc0000 SErr 0x0 action 0x6
[   55.954585] ata1.00: irq_stat 0x40000008
[   55.954610] ata1.00: failed command: READ FPDMA QUEUED
[   55.954643] ata1.00: cmd 60/00:90:00:eb:a4/01:00:0e:00:00/40 tag 18 ncq 131072 in
                        res 41/84:00:10:eb:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[   55.954725] ata1.00: status: { DRDY ERR }
[   55.954748] ata1.00: error: { ICRC ABRT }
[   55.954774] ata1: hard resetting link
[   56.274496] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   56.367864] ata1.00: configured for UDMA/100
[   56.367921] ata1: EH complete
[   56.448401] ata1.00: limiting speed to UDMA/33:PIO4
[   56.448412] ata1.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x6
[   56.448483] ata1.00: irq_stat 0x40000008
[   56.448524] ata1.00: failed command: READ FPDMA QUEUED
[   56.448578] ata1.00: cmd 60/00:10:58:ec:a4/01:00:0e:00:00/40 tag 2 ncq 131072 in
                        res 41/84:00:fe:ec:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[   56.448715] ata1.00: status: { DRDY ERR }
[   56.448753] ata1.00: error: { ICRC ABRT }
[   56.448798] ata1: hard resetting link
[   56.768215] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   56.856253] ata1.00: configured for UDMA/33
[   56.856297] ata1: EH complete
[   56.898690] ata1.00: exception Emask 0x0 SAct 0x60 SErr 0x0 action 0x6
[   56.898770] ata1.00: irq_stat 0x40000008
[   56.898816] ata1.00: failed command: READ FPDMA QUEUED
[   56.898876] ata1.00: cmd 60/00:30:c8:ee:a4/01:00:0e:00:00/40 tag 6 ncq 131072 in
                        res 41/84:00:e8:ee:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[   56.899029] ata1.00: status: { DRDY ERR }
[   56.899072] ata1.00: error: { ICRC ABRT }
[   56.899121] ata1: hard resetting link
[   57.218560] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   57.311513] ata1.00: configured for UDMA/33
[   57.311542] ata1: EH complete
[   57.355664] ata1.00: exception Emask 0x0 SAct 0x500 SErr 0x0 action 0x6
[   57.355754] ata1.00: irq_stat 0x40000008
[   57.355806] ata1.00: failed command: READ FPDMA QUEUED
[   57.355873] ata1.00: cmd 60/58:50:00:ec:a4/00:00:0e:00:00/40 tag 10 ncq 45056 in
                        res 41/84:58:1a:ec:a4/00:00:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[   57.356044] ata1.00: status: { DRDY ERR }
[   57.356091] ata1.00: error: { ICRC ABRT }
[   57.356145] ata1: hard resetting link
[   57.675608] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   57.766781] ata1.00: configured for UDMA/33
[   57.766816] ata1: EH complete
[   57.806077] ata1.00: exception Emask 0x0 SAct 0x3000 SErr 0x0 action 0x6
[   57.806134] ata1.00: irq_stat 0x40000008
[   57.806164] ata1.00: failed command: READ FPDMA QUEUED
[   57.806203] ata1.00: cmd 60/00:68:70:24:a5/01:00:0e:00:00/40 tag 13 ncq 131072 in
                        res 41/84:00:f2:24:a5/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[   57.806302] ata1.00: status: { DRDY ERR }
[   57.806330] ata1.00: error: { ICRC ABRT }
[   57.806362] ata1: hard resetting link
[   58.125961] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   58.211103] ata1.00: configured for UDMA/33
[   58.211156] ata1: EH complete
[   58.249769] ata1.00: exception Emask 0x0 SAct 0x18000 SErr 0x0 action 0x6
[   58.249854] ata1.00: irq_stat 0x40000008
[   58.249901] ata1.00: failed command: READ FPDMA QUEUED
[   58.249962] ata1.00: cmd 60/00:80:20:27:a5/01:00:0e:00:00/40 tag 16 ncq 131072 in
                        res 41/84:00:a2:27:a5/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[   58.255626] ata1.00: status: { DRDY ERR }
[   58.258790] ata1.00: error: { ICRC ABRT }
[   58.261924] ata1: hard resetting link
[   58.579657] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   58.666164] ata1.00: configured for UDMA/33
[   58.666199] ata1: EH complete
[   58.716707] ata1.00: exception Emask 0x0 SAct 0x4000000 SErr 0x0 action 0x6
[   58.718539] ata1.00: irq_stat 0x40000008
[   58.720328] ata1.00: failed command: READ FPDMA QUEUED
[   58.722121] ata1.00: cmd 60/00:d0:68:92:5c/01:00:0f:00:00/40 tag 26 ncq 131072 in
                        res 41/84:00:76:92:5c/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   58.725736] ata1.00: status: { DRDY ERR }
[   58.727553] ata1.00: error: { ICRC ABRT }
[   58.728965] ata1: hard resetting link
[   59.046670] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   59.132488] ata1.00: configured for UDMA/33
[   59.132515] ata1: EH complete
[   59.180459] ata1.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6
[   59.181979] ata1.00: irq_stat 0x40000008
[   59.182990] ata1.00: failed command: READ FPDMA QUEUED
[   59.183943] ata1.00: cmd 60/f8:e8:68:93:5c/00:00:0f:00:00/40 tag 29 ncq 126976 in
                        res 41/84:f8:6a:93:5c/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   59.185831] ata1.00: status: { DRDY ERR }
[   59.186778] ata1.00: error: { ICRC ABRT }
[   59.187715] ata1: hard resetting link
[   59.507035] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   59.610051] ata1.00: configured for UDMA/33
[   59.610080] ata1: EH complete
[   59.661766] ata1.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x6
[   59.663154] ata1.00: irq_stat 0x40000008
[   59.664089] ata1.00: failed command: READ FPDMA QUEUED
[   59.665027] ata1.00: cmd 60/98:38:60:94:5c/00:00:0f:00:00/40 tag 7 ncq 77824 in
                        res 41/84:98:64:94:5c/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   59.666916] ata1.00: status: { DRDY ERR }
[   59.669774] ata1.00: error: { ICRC ABRT }
[   59.672954] ata1: hard resetting link
[   59.990695] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   60.087554] ata1.00: configured for UDMA/33
[   60.087600] ata1: EH complete
[   60.217903] ata1.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x6
[   60.219413] ata1.00: irq_stat 0x40000008
[   60.220456] ata1.00: failed command: READ FPDMA QUEUED
[   60.221440] ata1.00: cmd 60/20:38:00:1b:3e/00:00:0f:00:00/40 tag 7 ncq 16384 in
                        res 41/84:20:18:1b:3e/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   60.223332] ata1.00: status: { DRDY ERR }
[   60.224269] ata1.00: error: { ICRC ABRT }
[   60.225206] ata1: hard resetting link
[   60.544531] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   60.653686] ata1.00: configured for UDMA/33
[   60.653713] ata1: EH complete
[   60.701540] ata1.00: exception Emask 0x0 SAct 0x400 SErr 0x0 action 0x6
[   60.703016] ata1.00: irq_stat 0x40000008
[   60.704106] ata1.00: failed command: READ FPDMA QUEUED
[   60.705056] ata1.00: cmd 60/88:50:78:1b:3e/00:00:0f:00:00/40 tag 10 ncq 69632 in
                        res 41/84:88:78:1b:3e/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   60.706949] ata1.00: status: { DRDY ERR }
[   60.707884] ata1.00: error: { ICRC ABRT }
[   60.708824] ata1: hard resetting link
[   61.028237] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   61.142293] ata1.00: configured for UDMA/33
[   61.142319] ata1: EH complete
[   61.195399] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6
[   61.197750] ata1.00: irq_stat 0x40000008
[   61.200089] ata1.00: failed command: READ FPDMA QUEUED
[   61.201690] ata1.00: cmd 60/20:78:10:39:38/00:00:0f:00:00/40 tag 15 ncq 16384 in
                        res 41/84:20:14:39:38/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   61.204897] ata1.00: status: { DRDY ERR }
[   61.206484] ata1.00: error: { ICRC ABRT }
[   61.208071] ata1: hard resetting link
[   61.525313] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   61.630818] ata1.00: configured for UDMA/33
[   61.630845] ata1: EH complete
[   61.675724] ata1.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6
[   61.677345] ata1.00: irq_stat 0x40000008
[   61.678943] ata1.00: failed command: READ FPDMA QUEUED
[   61.680539] ata1.00: cmd 60/50:90:30:39:38/00:00:0f:00:00/40 tag 18 ncq 40960 in
                        res 41/84:50:70:39:38/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   61.683756] ata1.00: status: { DRDY ERR }
[   61.685369] ata1.00: error: { ICRC ABRT }
[   61.686586] ata1: hard resetting link
[   62.005676] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   62.108289] ata1.00: configured for UDMA/33
[   62.108316] ata1: EH complete
[   62.162783] ata1.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x6
[   62.164411] ata1.00: irq_stat 0x40000008
[   62.166015] ata1.00: failed command: READ FPDMA QUEUED
[   62.167617] ata1.00: cmd 60/20:b0:d8:c3:3d/00:00:0f:00:00/40 tag 22 ncq 16384 in
                        res 41/84:20:d8:c3:3d/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[   62.170837] ata1.00: status: { DRDY ERR }
[   62.172433] ata1.00: error: { ICRC ABRT }
[   62.173698] ata1: hard resetting link
[   62.492749] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   62.607944] ata1.00: configured for UDMA/33
[   62.607974] ata1: EH complete

Output of smartctl -a /dev/sda

smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Laptop SSHD
Device Model:     ST1000LM014-SSHD-8GB
Serial Number:    W3829AM6
LU WWN Device Id: 5 000c50 07be01372
Firmware Version: LVD3
User Capacity:    1,000,204,886,016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Sun May 10 11:12:02 2015 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
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(  150) seconds.
Offline data collection
capabilities: 			 (0x73) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No 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: 	 ( 198) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x1081)	SCT Status 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       -       158141600
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       429
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   073   060   030    Pre-fail  Always       -       4319585187
  9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       1864
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       437
184 End-to-End_Error        0x0032   089   089   099    Old_age   Always   FAILING_NOW 11
187 Reported_Uncorrect      0x0032   098   098   000    Old_age   Always       -       2
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   069   052   045    Old_age   Always       -       31 (Min/Max 25/31)
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       -       50
193 Load_Cycle_Count        0x0032   097   097   000    Old_age   Always       -       6179
194 Temperature_Celsius     0x0022   031   048   000    Old_age   Always       -       31 (0 19 0 0 0)
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
254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 13 (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 13 occurred at disk power-on lifetime: 1779 hours (74 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 10 ff ff ff 4f 00      09:58:41.053  READ FPDMA QUEUED
  60 00 b0 ff ff ff 4f 00      09:58:41.053  READ FPDMA QUEUED
  60 00 30 ff ff ff 4f 00      09:58:41.053  READ FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      09:58:40.403  FLUSH CACHE EXT
  61 00 08 ff ff ff 4f 00      09:58:40.403  WRITE FPDMA QUEUED

Error 12 occurred at disk power-on lifetime: 1722 hours (71 days + 18 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 00 ff ff ff 4f 00      00:01:28.048  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      00:01:28.048  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:01:28.047  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      00:01:28.047  READ FPDMA QUEUED
  60 00 30 50 3a c5 4e 00      00:01:28.045  READ FPDMA QUEUED

Error 11 occurred at disk power-on lifetime: 1537 hours (64 days + 1 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 00 ff ff ff 4f 00      00:00:35.199  READ FPDMA QUEUED
  60 00 20 ff ff ff 4f 00      00:00:35.198  READ FPDMA QUEUED
  60 00 08 10 10 2b 4f 00      00:00:35.188  READ FPDMA QUEUED
  60 00 e0 20 e0 78 4f 00      00:00:35.187  READ FPDMA QUEUED
  60 00 90 68 e1 78 4f 00      00:00:35.185  READ FPDMA QUEUED

Error 10 occurred at disk power-on lifetime: 1525 hours (63 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 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 a0 ff ff ff 4f 00      00:00:15.374  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:15.373  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:15.373  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00      00:00:15.370  READ FPDMA QUEUED
  60 00 68 ff ff ff 4f 00      00:00:15.370  READ FPDMA QUEUED

Error 9 occurred at disk power-on lifetime: 1525 hours (63 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 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 e0 9e 31 4f 00      00:00:15.146  READ FPDMA QUEUED
  60 00 a8 ff ff ff 4f 00      00:00:15.073  READ FPDMA QUEUED
  60 00 18 ff ff ff 4f 00      00:00:15.072  READ FPDMA QUEUED
  60 00 98 ff ff ff 4f 00      00:00:15.072  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      00:00:15.068  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.

Is this software bug or hard drive failure? Thanks in advance.

Накрывается жесткий диск?

Заметил в messages такие сообщения:

Это жесткий диск или контроллер глючит?

Это кабель «от ветра» колышет. Или переткни или поставь другой

Словил такое один раз:

После этого пришлось перезагружаться reset-ом.

Ты кабель-то проверил, как тебе выше советовали 😕

Кабель перевоткнул. Можно конечно попробовать заменить.

Стоит попробовать. У меня так же было. Эти SATA-кабели слишком ненадёжны.

Кабель поменял. Вроде ошибок пока нет. Спасибо, потестирую.

такое началось опять. Видимо проблема не в кабеле 🙁

Данные S.M.A.R.T. в студию.

Показатели нормальные. Диск довольно старый. Неплохо бы погонять его на другом компьютере. Если проблем не будет, то, как уже сказали выше, это может быть контроллер.

У меня подобная ситуация:

Жесткий: WD1000EADS, 20 сентября купленный и отформатированный в ext3

Контроллер: вспомогательный Promise (вроде) sata378 (2 родных интеловских заняты другими жесткими).

dmesg выхлоп совпадает с твоим. Но был еще симптом: cat /dev/sdc вызывал такие ошибки буквально через несколько секунд после запуска — в начале диска проблема.

4 раза запускал fsck.ext3 -c (с проверкой на бэды). Всегда были помечены одни и теже сектора. Сейчас на жестком 15 гигов свободно, перевел в RO, буду смотреть.

smartctl -a /dev/sdc:

С сегодняшнего дня проблемы усилились. На компьютере, где он стоял загрузочным с него больше не загрузиться (почти :)). Подключил к другому компьютеру — без проблем читаю данные. Мистика. Грешу на контроллер.

Источник

Chapter 7. ATA errors and exceptions

Table of Contents

This chapter tries to identify what error/exception conditions exist for ATA/ATAPI devices and describe how they should be handled in implementation-neutral way.

The term ‘error’ is used to describe conditions where either an explicit error condition is reported from device or a command has timed out.

The term ‘exception’ is either used to describe exceptional conditions which are not errors (say, power or hotplug events), or to describe both errors and non-error exceptional conditions. Where explicit distinction between error and exception is necessary, the term ‘non-error exception’ is used.

Exception categories

Exceptions are described primarily with respect to legacy taskfile + bus master IDE interface. If a controller provides other better mechanism for error reporting, mapping those into categories described below shouldn’t be difficult.

In the following sections, two recovery actions — reset and reconfiguring transport — are mentioned. These are described further in the section called “EH recovery actions”.

HSM violation

This error is indicated when STATUS value doesn’t match HSM requirement during issuing or execution any ATA/ATAPI command.

ATA_STATUS doesn’t contain !BSY && DRDY && !DRQ while trying to issue a command.

!BSY && !DRQ during PIO data transfer.

DRQ on command completion.

!BSY && ERR after CDB transfer starts but before the last byte of CDB is transferred. ATA/ATAPI standard states that «The device shall not terminate the PACKET command with an error before the last byte of the command packet has been written» in the error outputs description of PACKET command and the state diagram doesn’t include such transitions.

In these cases, HSM is violated and not much information regarding the error can be acquired from STATUS or ERROR register. IOW, this error can be anything — driver bug, faulty device, controller and/or cable.

As HSM is violated, reset is necessary to restore known state. Reconfiguring transport for lower speed might be helpful too as transmission errors sometimes cause this kind of errors.

ATA/ATAPI device error (non-NCQ / non-CHECK CONDITION)

These are errors detected and reported by ATA/ATAPI devices indicating device problems. For this type of errors, STATUS and ERROR register values are valid and describe error condition. Note that some of ATA bus errors are detected by ATA/ATAPI devices and reported using the same mechanism as device errors. Those cases are described later in this section.

For ATA commands, this type of errors are indicated by !BSY && ERR during command execution and on completion.

For ATAPI commands,

!BSY && ERR && ABRT right after issuing PACKET indicates that PACKET command is not supported and falls in this category.

!BSY && ERR(==CHK) && !ABRT after the last byte of CDB is transferred indicates CHECK CONDITION and doesn’t fall in this category.

!BSY && ERR(==CHK) && ABRT after the last byte of CDB is transferred *probably* indicates CHECK CONDITION and doesn’t fall in this category.

Of errors detected as above, the following are not ATA/ATAPI device errors but ATA bus errors and should be handled according to the section called “ATA bus error”.

This is indicated by ICRC bit in the ERROR register and means that corruption occurred during data transfer. Up to ATA/ATAPI-7, the standard specifies that this bit is only applicable to UDMA transfers but ATA/ATAPI-8 draft revision 1f says that the bit may be applicable to multiword DMA and PIO.

ABRT error during data transfer or on completion

Up to ATA/ATAPI-7, the standard specifies that ABRT could be set on ICRC errors and on cases where a device is not able to complete a command. Combined with the fact that MWDMA and PIO transfer errors aren’t allowed to use ICRC bit up to ATA/ATAPI-7, it seems to imply that ABRT bit alone could indicate transfer errors.

However, ATA/ATAPI-8 draft revision 1f removes the part that ICRC errors can turn on ABRT. So, this is kind of gray area. Some heuristics are needed here.

ATA/ATAPI device errors can be further categorized as follows.

This is indicated by UNC bit in the ERROR register. ATA devices reports UNC error only after certain number of retries cannot recover the data, so there’s nothing much else to do other than notifying upper layer.

READ and WRITE commands report CHS or LBA of the first failed sector but ATA/ATAPI standard specifies that the amount of transferred data on error completion is indeterminate, so we cannot assume that sectors preceding the failed sector have been transferred and thus cannot complete those sectors successfully as SCSI does.

Media changed / media change requested error

This is indicated by IDNF bit in the ERROR register. Report to upper layer.

This can be invalid command or parameter indicated by ABRT ERROR bit or some other error condition. Note that ABRT bit can indicate a lot of things including ICRC and Address errors. Heuristics needed.

Depending on commands, not all STATUS/ERROR bits are applicable. These non-applicable bits are marked with «na» in the output descriptions but up to ATA/ATAPI-7 no definition of «na» can be found. However, ATA/ATAPI-8 draft revision 1f describes «N/A» as follows.

A keyword the indicates a field has no defined value in this standard and should not be checked by the host or device. N/A fields should be cleared to zero.

So, it seems reasonable to assume that «na» bits are cleared to zero by devices and thus need no explicit masking.

ATAPI device CHECK CONDITION

ATAPI device CHECK CONDITION error is indicated by set CHK bit (ERR bit) in the STATUS register after the last byte of CDB is transferred for a PACKET command. For this kind of errors, sense data should be acquired to gather information regarding the errors. REQUEST SENSE packet command should be used to acquire sense data.

Once sense data is acquired, this type of errors can be handled similarly to other SCSI errors. Note that sense data may indicate ATA bus error (e.g. Sense Key 04h HARDWARE ERROR && ASC/ASCQ 47h/00h SCSI PARITY ERROR). In such cases, the error should be considered as an ATA bus error and handled according to the section called “ATA bus error”.

ATA device error (NCQ)

NCQ command error is indicated by cleared BSY and set ERR bit during NCQ command phase (one or more NCQ commands outstanding). Although STATUS and ERROR registers will contain valid values describing the error, READ LOG EXT is required to clear the error condition, determine which command has failed and acquire more information.

READ LOG EXT Log Page 10h reports which tag has failed and taskfile register values describing the error. With this information the failed command can be handled as a normal ATA command error as in the section called “ATA/ATAPI device error (non-NCQ / non-CHECK CONDITION)” and all other in-flight commands must be retried. Note that this retry should not be counted — it’s likely that commands retried this way would have completed normally if it were not for the failed command.

Note that ATA bus errors can be reported as ATA device NCQ errors. This should be handled as described in the section called “ATA bus error”.

If READ LOG EXT Log Page 10h fails or reports NQ, we’re thoroughly screwed. This condition should be treated according to the section called “HSM violation”.

ATA bus error

ATA bus error means that data corruption occurred during transmission over ATA bus (SATA or PATA). This type of errors can be indicated by

Controller-specific error completion with error information indicating transmission error.

On some controllers, command timeout. In this case, there may be a mechanism to determine that the timeout is due to transmission error.

Unknown/random errors, timeouts and all sorts of weirdities.

As described above, transmission errors can cause wide variety of symptoms ranging from device ICRC error to random device lockup, and, for many cases, there is no way to tell if an error condition is due to transmission error or not; therefore, it’s necessary to employ some kind of heuristic when dealing with errors and timeouts. For example, encountering repetitive ABRT errors for known supported command is likely to indicate ATA bus error.

Once it’s determined that ATA bus errors have possibly occurred, lowering ATA bus transmission speed is one of actions which may alleviate the problem. See the section called “Reconfigure transport” for more information.

PCI bus error

Data corruption or other failures during transmission over PCI (or other system bus). For standard BMDMA, this is indicated by Error bit in the BMDMA Status register. This type of errors must be logged as it indicates something is very wrong with the system. Resetting host controller is recommended.

Late completion

This occurs when timeout occurs and the timeout handler finds out that the timed out command has completed successfully or with error. This is usually caused by lost interrupts. This type of errors must be logged. Resetting host controller is recommended.

Unknown error (timeout)

This is when timeout occurs and the command is still processing or the host and device are in unknown state. When this occurs, HSM could be in any valid or invalid state. To bring the device to known state and make it forget about the timed out command, resetting is necessary. The timed out command may be retried.

Timeouts can also be caused by transmission errors. Refer to the section called “ATA bus error” for more details.

Источник

Arch Linux

You are not logged in.

#1 2015-05-10 09:35:13

ATA bus error

Hello,
I have some problems with hard drive on my laptop. Sometimes everything freezes for few seconds (usually during start-up, but sometimes after I login) and I get some errors. After that, everything seems to be working fine.

Part of dmesg with errors:

Output of smartctl -a /dev/sda

Is this software bug or hard drive failure? Thanks in advance.

#2 2015-05-10 16:16:12

Re: ATA bus error

Those seek errors and raw read error rates are astronomical. This is a hard drive failure.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#3 2015-05-10 20:02:41

Re: ATA bus error

Those seek errors and raw read error rates are astronomical. This is a hard drive failure.

Not necessarily, this is a Seagate hard drive. AFAIK Seek Error Rate and Raw Read Error Rate are 48bit values where the lower 24bit encode the total number of sectors read/saught (which overflows to zero) and the upper 24bit encode the acutal errors.

should display OP’s data in a usuable format.

In fact, I turned my recently purchased laptop in for a hard disk replacement of almost the same type as OP (ST500LM000-SSHD-8GB) twice, but all three drives of this type I had provided SMART values which were more of an oracle rather than data useful for monitoring purposes. Forums are full with people unsure about what to do with this kind of drives. If you google for the End-to-End errors with Seagate drives (here marked as FAILING!), you’ll find people reporting that Seagate’s own tools do not report any errors despite the attribute in question being reported by monitoring tools just as bad. Seagate is the horror. So, I’d say that it is rather uncertain whether the SMART values are connected to the actual drive failing or a faulty cable.

OP, did you see these errors from the beginning or after a certain time, or perhaps after a kernel upgrade? Did you check the drive’s cable? What was the situation before these errors showed up (maybe under Windows?)

#4 2015-05-10 22:35:45

Re: ATA bus error

I’d never heard that; So much for trusting the instrumentation. I’ll watch this thread and see how it plays out.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#5 2015-05-10 22:39:49

Re: ATA bus error

Okay, point of reference. I too have a Seagate drive, but I don’t see the issue 😕

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#6 2015-05-11 06:06:31

Re: ATA bus error

Here’s mine, it looks like all the drives I had before from the same model line looked like:

You can tell that my Seek Error Rate (although not Raw Reads) is worrying even according to the interpretation I gave (likewise, the Reallocated Event Count), but the service people (Lenovo Service, it’s a TP) refuse to exchange the drive a third time since short and long SMART test routines do not error out. As I said, I do not have verified information and do not know anybody who does know how to read these SMART values correctly. I gave up and am just waiting for the drive to fail.

Last edited by jsoy9pQbYVNu5nfU (2015-05-11 06:07:13)

#7 2015-05-11 10:24:56

Re: ATA bus error

Thanks for your answers.

Not necessarily, this is a Seagate hard drive. AFAIK Seek Error Rate and Raw Read Error Rate are 48bit values where the lower 24bit encode the total number of sectors read/saught (which overflows to zero) and the upper 24bit encode the acutal errors.

should display OP’s data in a usuable format.

In fact, I turned my recently purchased laptop in for a hard disk replacement of almost the same type as OP (ST500LM000-SSHD-8GB) twice, but all three drives of this type I had provided SMART values which were more of an oracle rather than data useful for monitoring purposes. Forums are full with people unsure about what to do with this kind of drives. If you google for the End-to-End errors with Seagate drives (here marked as FAILING!), you’ll find people reporting that Seagate’s own tools do not report any errors despite the attribute in question being reported by monitoring tools just as bad. Seagate is the horror. So, I’d say that it is rather uncertain whether the SMART values are connected to the actual drive failing or a faulty cable.

OP, did you see these errors from the beginning or after a certain time, or perhaps after a kernel upgrade? Did you check the drive’s cable? What was the situation before these errors showed up (maybe under Windows?)

smartctl -v 1,hex48 -v 7,hex48 -a /dev/sda

These errors just appeared, not after upgrade and I didn’t get them in the beginning. The situation before errors — everything worked exactly the same, I see no difference in performance, except that few seconds long freeze that sometimes happen. Can’t tell about Windows, I have it pre-installed but never used it so I can’t compare. I didn’t check the cable, and I’d rather not do that — I don’t want to mess with hardware, if I do something wrong I lose the warranty. If something is wrong then I’d rather have it checked and fixed by someone who knows how to do that (and for free, because I still have the warranty).

Источник

Сразу после загрузки, при любой, даже незначительной нагрузке на диск, начинают сыпаться сообщения в dmesg:

ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x780100 action 0x2
ata5.00: irq_stat 0x08000000
ata5: SError: { UnrecovData 10B8B Dispar BadCRC Handshk }
ata5.00: cmd c8/00:28:df:31:aa/00:00:00:00:00/ee tag 0 dma 20480 in
         res 50/00:00:96:77:a5/00:00:00:00:00/ee Emask 0x10 (ATA bus error)
ata5.00: status: { DRDY }
ata5: hard resetting link
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: configured for UDMA/133
ata5: EH complete
sd 4:0:0:0: [sdd] 625142448 512-byte hardware sectors (320073 MB)
sd 4:0:0:0: [sdd] Write Protect is off
sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x780100 action 0x2
ata5.00: irq_stat 0x08000000
ata5: SError: { UnrecovData 10B8B Dispar BadCRC Handshk }
ata5.00: cmd c8/00:00:47:42:b0/00:00:00:00:00/ee tag 0 dma 131072 in
         res 50/00:00:56:99:3a/00:00:00:00:00/ee Emask 0x10 (ATA bus error)
ata5.00: status: { DRDY }
ata5: hard resetting link
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: configured for UDMA/133
ata5: EH complete
sd 4:0:0:0: [sdd] 625142448 512-byte hardware sectors (320073 MB)
sd 4:0:0:0: [sdd] Write Protect is off
sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x780100 action 0x2
ata5.00: irq_stat 0x08000000
ata5: SError: { UnrecovData 10B8B Dispar BadCRC Handshk }
ata5.00: cmd 25/00:c0:af:47:86/00:01:0e:00:00/e0 tag 0 dma 229376 in
         res 50/00:00:7e:4f:aa/00:00:00:00:00/ee Emask 0x10 (ATA bus error)
ata5.00: status: { DRDY }
ata5: hard resetting link
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: configured for UDMA/133
ata5: EH complete
sd 4:0:0:0: [sdd] 625142448 512-byte hardware sectors (320073 MB)
sd 4:0:0:0: [sdd] Write Protect is off
sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
ata5: limiting SATA link speed to 1.5 Gbps
ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x780100 action 0x6
ata5.00: irq_stat 0x08000000
ata5: SError: { UnrecovData 10B8B Dispar BadCRC Handshk }
ata5.00: cmd c8/00:00:7f:4f:aa/00:00:00:00:00/ee tag 0 dma 131072 in
         res 50/00:00:fe:fa:c0/00:00:00:00:00/ee Emask 0x10 (ATA bus error)
ata5.00: status: { DRDY }
ata5: hard resetting link
ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata5.00: configured for UDMA/133
ata5: EH complete
sd 4:0:0:0: [sdd] 625142448 512-byte hardware sectors (320073 MB)
sd 4:0:0:0: [sdd] Write Protect is off
sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

Ядро 2.6.24, диск — Seagate ST3320620AS, контроллер «JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 03)».
Подозрение, что началось после обновления ядра с 2.6.23.
У кого-нибудь ещё такое встречалось?
Попробую заменить SATA кабель, но вроде бы раньше работало нормально, и никто вообще не трогал его…

Arch Linux

You are not logged in.

#1 2015-05-10 09:35:13

ATA bus error

Hello,
I have some problems with hard drive on my laptop. Sometimes everything freezes for few seconds (usually during start-up, but sometimes after I login) and I get some errors. After that, everything seems to be working fine.

Part of dmesg with errors:

Is this software bug or hard drive failure? Thanks in advance.

#2 2015-05-10 16:16:12

Re: ATA bus error

Those seek errors and raw read error rates are astronomical. This is a hard drive failure.

#3 2015-05-10 20:02:41

Re: ATA bus error

Those seek errors and raw read error rates are astronomical. This is a hard drive failure.

Not necessarily, this is a Seagate hard drive. AFAIK Seek Error Rate and Raw Read Error Rate are 48bit values where the lower 24bit encode the total number of sectors read/saught (which overflows to zero) and the upper 24bit encode the acutal errors.

should display OP’s data in a usuable format.

In fact, I turned my recently purchased laptop in for a hard disk replacement of almost the same type as OP (ST500LM000-SSHD-8GB) twice, but all three drives of this type I had provided SMART values which were more of an oracle rather than data useful for monitoring purposes. Forums are full with people unsure about what to do with this kind of drives. If you google for the End-to-End errors with Seagate drives (here marked as FAILING!), you’ll find people reporting that Seagate’s own tools do not report any errors despite the attribute in question being reported by monitoring tools just as bad. Seagate is the horror. So, I’d say that it is rather uncertain whether the SMART values are connected to the actual drive failing or a faulty cable.

OP, did you see these errors from the beginning or after a certain time, or perhaps after a kernel upgrade? Did you check the drive’s cable? What was the situation before these errors showed up (maybe under Windows?)

#4 2015-05-10 22:35:45

Re: ATA bus error

I’d never heard that; So much for trusting the instrumentation. I’ll watch this thread and see how it plays out.

#5 2015-05-10 22:39:49

Re: ATA bus error

Okay, point of reference. I too have a Seagate drive, but I don’t see the issue 😕

#6 2015-05-11 06:06:31

Re: ATA bus error

Here’s mine, it looks like all the drives I had before from the same model line looked like:

You can tell that my Seek Error Rate (although not Raw Reads) is worrying even according to the interpretation I gave (likewise, the Reallocated Event Count), but the service people (Lenovo Service, it’s a TP) refuse to exchange the drive a third time since short and long SMART test routines do not error out. As I said, I do not have verified information and do not know anybody who does know how to read these SMART values correctly. I gave up and am just waiting for the drive to fail.

Last edited by 2ion (2015-05-11 06:07:13)

#7 2015-05-11 10:24:56

Re: ATA bus error

Thanks for your answers.

Not necessarily, this is a Seagate hard drive. AFAIK Seek Error Rate and Raw Read Error Rate are 48bit values where the lower 24bit encode the total number of sectors read/saught (which overflows to zero) and the upper 24bit encode the acutal errors.

should display OP’s data in a usuable format.

In fact, I turned my recently purchased laptop in for a hard disk replacement of almost the same type as OP (ST500LM000-SSHD-8GB) twice, but all three drives of this type I had provided SMART values which were more of an oracle rather than data useful for monitoring purposes. Forums are full with people unsure about what to do with this kind of drives. If you google for the End-to-End errors with Seagate drives (here marked as FAILING!), you’ll find people reporting that Seagate’s own tools do not report any errors despite the attribute in question being reported by monitoring tools just as bad. Seagate is the horror. So, I’d say that it is rather uncertain whether the SMART values are connected to the actual drive failing or a faulty cable.

OP, did you see these errors from the beginning or after a certain time, or perhaps after a kernel upgrade? Did you check the drive’s cable? What was the situation before these errors showed up (maybe under Windows?)

Источник

Накрывается жесткий диск?

Заметил в messages такие сообщения:

Это жесткий диск или контроллер глючит?

Это кабель «от ветра» колышет. Или переткни или поставь другой

Словил такое один раз:

После этого пришлось перезагружаться reset-ом.

Ты кабель-то проверил, как тебе выше советовали 😕

Кабель перевоткнул. Можно конечно попробовать заменить.

Стоит попробовать. У меня так же было. Эти SATA-кабели слишком ненадёжны.

Кабель поменял. Вроде ошибок пока нет. Спасибо, потестирую.

такое началось опять. Видимо проблема не в кабеле 🙁

Данные S.M.A.R.T. в студию.

Показатели нормальные. Диск довольно старый. Неплохо бы погонять его на другом компьютере. Если проблем не будет, то, как уже сказали выше, это может быть контроллер.

У меня подобная ситуация:

Жесткий: WD1000EADS, 20 сентября купленный и отформатированный в ext3

Контроллер: вспомогательный Promise (вроде) sata378 (2 родных интеловских заняты другими жесткими).

Источник

Проблемы с жестким диском SATA

Уже пару месяцев время от времени наблюдаю такие сообщения на текстовую консоль и в syslog :

При этом комп подвисает, иногда наглухо, приходится ресетить. Естественно, в ext3 при этом появляются пробелмы, они лечатся fsck, который никаких бэдов на диске не находит.

Что это может быть? Контроллер на материнке? На самом диске? Какие-то проблемы в ОС/драйверах, которые это провоцируют?

система Debian 6.0.3, ядро 2.6.32-5-686

Проверь кабельки, жельтенькие или красненькие. вдруг кто-то пытался их перерезать ну и быстренько переноси свою помойку на другой винт.

В моем случае это как раз эти кабельки болтались, винт был в норме.

Бери-ка кабелёчки только с металлич. зажимочками, чтобы не болталися.

Контроллер на материнке? На самом диске? Какие-то проблемы в ОС/драйверах, которые это провоцируют?

А вот все вышеперечисленное!

Контроллер на материнке может сдохнуть. Могут микротрещины на маме быть.

Проблемы в драйверах могут быть. И проверить можно только методом проб и ошибок с заменой либо гугленьем с версией ядра и версией контроллера.

fsck, который никаких бэдов на диске не находит.

Загляните в его SMART. Убедитесь в том, что шлейфы целы.

кабельки питания? кабель данных SATA один и он красный. бекап в процессе 🙂

Увы, гугление с версией ядра и номерами ошибок ничего не дало, с контроллером попробую.

Метод проб и ошибок это хорошо, но у меня нет под рукой другой материнки/другого компа, другой диск есть, но он IDE и еще более старый и подозрительный 🙂

Других поводов менять диск нет, места пока хватает, и не хочется выкидывать деньги просто так. Тогда уж проще надежнее сразу новый комп покупать и ставить на него ОС заново, перенося только данные.

Источник

Arch Linux

You are not logged in.

#1 2019-03-24 09:22:05

exception Emask 0x50 ATA bus errors on fresh Arch install (unusable)

I have installed Arch Linux on my main desktop computer yesterday. Until then, I was using debian stable for about two years on it. I had no issues.

The install part went smoothly. I chose XFCE DE with full disk encryption.

After a while however, the machine froze completely. After a few tests I was able to describe the following behavior:

1. Whenever some network activity is triggered, such as downloading a file or even opening Firefox, the kernel starts throwing all kind of errors relating to ATA errors, and the computer starts to slow down. It seems to be constantly resetting the SATA link, eventually it results in a complete freeze or a remount in read-only mode (see kernel messages below)
2. This does not seem to happen when I am writing files unto the disk without network activity.
3. SMART test are OK for this disk (very recent, used debian stable on it for 4-5 months without problems).
4. This does not happen when I boot the disk from a USB-SATA adapter (disk currently connected to USB port and running fine now).
5. Changing SATA cables did not solve the problem.
6. Using the same SATA cables with debian stable on an encrypted SSD does not cause these errors, it only happens in Arch Linux (so apparently no hardware failure on the PC side)
7. Replacing the current kernel with the lts version did not solve the problem

I am completely lost at this point. I have no idea how to solve this problem and where to start from. Again, hardware does not seem to be the problem here: I have no issues using another disk with debian stable, and I have no issues when connecting the Arch disk with a USB-SATA adapter. Any suggestion welcome.

My hardware specs are as follows:

CPU i7-4790
Motherboard Gigabyte Z87M-D3H
GPU Radeon R9 270X
SSD Samsung 860EVO 1TB

The kernel messages that I receive:

[ 69.004732] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 69.006641] ata1.00: supports DRM functions and may not be fully accessible
[ 69.010168] ata1.00: supports DRM functions and may not be fully accessible
[ 69.012999] ata1.00: configured for UDMA/133
[ 69.013053] ata1.00: Enabling discard_zeroes_data
[ 74.394764] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 74.396686] ata1.00: supports DRM functions and may not be fully accessible
[ 74.400156] ata1.00: supports DRM functions and may not be fully accessible
[ 74.403093] ata1.00: configured for UDMA/133
[ 74.403159] ata1.00: Enabling discard_zeroes_data
[ 76.614785] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 76.616652] ata1.00: supports DRM functions and may not be fully accessible
[ 76.619944] ata1.00: supports DRM functions and may not be fully accessible
[ 76.622687] ata1.00: configured for UDMA/133
[ 76.622750] ata1.00: Enabling discard_zeroes_data
[ 80.975983] ata1: limiting SATA link speed to 3.0 Gbps
[ 81.704763] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 81.706738] ata1.00: supports DRM functions and may not be fully accessible
[ 81.710280] ata1.00: supports DRM functions and may not be fully accessible
[ 81.713071] ata1.00: configured for UDMA/133
[ 81.713142] ata1.00: Enabling discard_zeroes_data
[ 83.344778] ata1: SATA link down (SStatus 0 SControl 320)
[ 88.756472] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 88.758370] ata1.00: supports DRM functions and may not be fully accessible
[ 88.761694] ata1.00: supports DRM functions and may not be fully accessible
[ 88.764534] ata1.00: configured for UDMA/133
[ 88.764637] ata1.00: Enabling discard_zeroes_data
[ 89.664779] ata1.00: exception Emask 0x50 SAct 0xff0 SErr 0x4890800 action 0xe frozen
[ 89.664785] ata1.00: irq_stat 0x08400040, interface fatal error, connection status changed
[ 89.664788] ata1: SError: < HostInt PHYRdyChg 10B8B LinkSeq DevExch >
[ 89.664792] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664799] ata1.00: cmd 61/40:20:80:ea:45/05:00:10:00:00/40 tag 4 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664802] ata1.00: status: < DRDY >
[ 89.664805] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664812] ata1.00: cmd 61/40:28:c0:ef:45/00:00:10:00:00/40 tag 5 ncq dma 32768 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664815] ata1.00: status: < DRDY >
[ 89.664817] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664824] ata1.00: cmd 61/40:30:00:f0:45/05:00:10:00:00/40 tag 6 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664826] ata1.00: status: < DRDY >
[ 89.664829] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664835] ata1.00: cmd 61/40:38:40:f5:45/05:00:10:00:00/40 tag 7 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664838] ata1.00: status: < DRDY >
[ 89.664840] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664847] ata1.00: cmd 61/40:40:80:fa:45/05:00:10:00:00/40 tag 8 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664849] ata1.00: status: < DRDY >
[ 89.664852] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664858] ata1.00: cmd 61/40:48:c0:ff:45/00:00:10:00:00/40 tag 9 ncq dma 32768 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664861] ata1.00: status: < DRDY >
[ 89.664863] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664870] ata1.00: cmd 61/40:50:00:00:46/05:00:10:00:00/40 tag 10 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664873] ata1.00: status: < DRDY >
[ 89.664875] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664881] ata1.00: cmd 61/40:58:40:05:46/05:00:10:00:00/40 tag 11 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664884] ata1.00: status: < DRDY >
[ 89.664888] ata1: hard resetting link
[ 90.404756] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 90.406630] ata1.00: supports DRM functions and may not be fully accessible
[ 90.410001] ata1.00: supports DRM functions and may not be fully accessible
[ 90.412862] ata1.00: configured for UDMA/133
[ 90.412884] ata1: EH complete
[ 90.412960] ata1.00: Enabling discard_zeroes_data
[ 90.744760] ata1.00: exception Emask 0x50 SAct 0x60000001 SErr 0x4890800 action 0xe frozen
[ 90.744766] ata1.00: irq_stat 0x08400040, interface fatal error, connection status changed
[ 90.744769] ata1: SError: < HostInt PHYRdyChg 10B8B LinkSeq DevExch >
[ 90.744773] ata1.00: failed command: WRITE FPDMA QUEUED
[ 90.744780] ata1.00: cmd 61/40:00:00:50:47/05:00:10:00:00/40 tag 0 ncq dma 688128 out
res 40/00:f0:c0:4f:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 90.744784] ata1.00: status: < DRDY >
[ 90.744787] ata1.00: failed command: WRITE FPDMA QUEUED
[ 90.744793] ata1.00: cmd 61/40:e8:80:4a:47/05:00:10:00:00/40 tag 29 ncq dma 688128 out
res 40/00:f0:c0:4f:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 90.744796] ata1.00: status: < DRDY >
[ 90.744799] ata1.00: failed command: WRITE FPDMA QUEUED
[ 90.744805] ata1.00: cmd 61/40:f0:c0:4f:47/00:00:10:00:00/40 tag 30 ncq dma 32768 out
res 40/00:f0:c0:4f:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 90.744808] ata1.00: status: < DRDY >
[ 90.744812] ata1: hard resetting link
[ 91.664775] ata1: SATA link down (SStatus 0 SControl 320)
[ 96.734748] ata1: hard resetting link
[ 97.066816] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 97.068830] ata1.00: supports DRM functions and may not be fully accessible
[ 97.072430] ata1.00: supports DRM functions and may not be fully accessible
[ 97.075377] ata1.00: configured for UDMA/133
[ 97.075401] ata1: EH complete
[ 97.075559] ata1.00: Enabling discard_zeroes_data
[ 97.154789] ata1: limiting SATA link speed to 1.5 Gbps
[ 97.154795] ata1.00: exception Emask 0x50 SAct 0x400ffa04 SErr 0x4890800 action 0xe frozen
[ 97.154802] ata1.00: irq_stat 0x08400040, interface fatal error, connection status changed
[ 97.154808] ata1: SError: < HostInt PHYRdyChg 10B8B LinkSeq DevExch >
[ 97.154815] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154828] ata1.00: cmd 61/40:10:80:4a:47/05:00:10:00:00/40 tag 2 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154834] ata1.00: status: < DRDY >
[ 97.154838] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154851] ata1.00: cmd 61/40:48:40:55:47/05:00:10:00:00/40 tag 9 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154856] ata1.00: status: < DRDY >
[ 97.154860] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154872] ata1.00: cmd 61/d0:58:80:5a:47/03:00:10:00:00/40 tag 11 ncq dma 499712 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154877] ata1.00: status: < DRDY >
[ 97.154881] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154893] ata1.00: cmd 61/40:60:00:90:47/05:00:10:00:00/40 tag 12 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154898] ata1.00: status: < DRDY >
[ 97.154902] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154913] ata1.00: cmd 61/40:68:40:95:47/05:00:10:00:00/40 tag 13 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154918] ata1.00: status: < DRDY >
[ 97.154922] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154934] ata1.00: cmd 61/40:70:80:9a:47/05:00:10:00:00/40 tag 14 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154939] ata1.00: status: < DRDY >
[ 97.154943] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154955] ata1.00: cmd 61/40:78:c0:9f:47/00:00:10:00:00/40 tag 15 ncq dma 32768 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154960] ata1.00: status: < DRDY >
[ 97.154964] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154976] ata1.00: cmd 61/40:80:40:a5:47/05:00:10:00:00/40 tag 16 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154980] ata1.00: status: < DRDY >
[ 97.154985] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154996] ata1.00: cmd 61/40:88:80:aa:47/05:00:10:00:00/40 tag 17 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.155001] ata1.00: status: < DRDY >
[ 97.155005] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.155017] ata1.00: cmd 61/40:90:00:50:47/05:00:10:00:00/40 tag 18 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.155022] ata1.00: status: < DRDY >
[ 97.155026] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.155038] ata1.00: cmd 61/40:98:c0:4f:47/00:00:10:00:00/40 tag 19 ncq dma 32768 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.155043] ata1.00: status: < DRDY >
[ 97.155047] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.155059] ata1.00: cmd 61/40:f0:00:a0:47/05:00:10:00:00/40 tag 30 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.155064] ata1.00: status: < DRDY >
[ 97.155070] ata1: hard resetting link
[ 97.884756] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 97.886638] ata1.00: supports DRM functions and may not be fully accessible
[ 97.890135] ata1.00: supports DRM functions and may not be fully accessible
[ 97.892980] ata1.00: configured for UDMA/133
[ 97.893026] ata1: EH complete
[ 97.893086] ata1.00: Enabling discard_zeroes_data
[ 105.474760] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 105.476697] ata1.00: supports DRM functions and may not be fully accessible
[ 105.480206] ata1.00: supports DRM functions and may not be fully accessible
[ 105.483163] ata1.00: configured for UDMA/133
[ 105.483220] ata1.00: Enabling discard_zeroes_data
[ 106.884761] ata1: SATA link down (SStatus 0 SControl 310)

Источник

Chapter 7. ATA errors and exceptions

This chapter tries to identify what error/exception conditions exist for ATA/ATAPI devices and describe how they should be handled in implementation-neutral way.

The term ‘error’ is used to describe conditions where either an explicit error condition is reported from device or a command has timed out.

The term ‘exception’ is either used to describe exceptional conditions which are not errors (say, power or hotplug events), or to describe both errors and non-error exceptional conditions. Where explicit distinction between error and exception is necessary, the term ‘non-error exception’ is used.

Exception categories

Exceptions are described primarily with respect to legacy taskfile + bus master IDE interface. If a controller provides other better mechanism for error reporting, mapping those into categories described below shouldn’t be difficult.

HSM violation

This error is indicated when STATUS value doesn’t match HSM requirement during issuing or execution any ATA/ATAPI command.

DRQ on command completion.

!BSY && ERR after CDB transfer starts but before the last byte of CDB is transferred. ATA/ATAPI standard states that «The device shall not terminate the PACKET command with an error before the last byte of the command packet has been written» in the error outputs description of PACKET command and the state diagram doesn’t include such transitions.

As HSM is violated, reset is necessary to restore known state. Reconfiguring transport for lower speed might be helpful too as transmission errors sometimes cause this kind of errors.

ATA/ATAPI device error (non-NCQ / non-CHECK CONDITION)

These are errors detected and reported by ATA/ATAPI devices indicating device problems. For this type of errors, STATUS and ERROR register values are valid and describe error condition. Note that some of ATA bus errors are detected by ATA/ATAPI devices and reported using the same mechanism as device errors. Those cases are described later in this section.

For ATAPI commands,

!BSY && ERR && ABRT right after issuing PACKET indicates that PACKET command is not supported and falls in this category.

!BSY && ERR(==CHK) && ABRT after the last byte of CDB is transferred *probably* indicates CHECK CONDITION and doesn’t fall in this category.

Of errors detected as above, the following are not ATA/ATAPI device errors but ATA bus errors and should be handled according to the section called “ATA bus error”.

This is indicated by ICRC bit in the ERROR register and means that corruption occurred during data transfer. Up to ATA/ATAPI-7, the standard specifies that this bit is only applicable to UDMA transfers but ATA/ATAPI-8 draft revision 1f says that the bit may be applicable to multiword DMA and PIO.

ABRT error during data transfer or on completion

Up to ATA/ATAPI-7, the standard specifies that ABRT could be set on ICRC errors and on cases where a device is not able to complete a command. Combined with the fact that MWDMA and PIO transfer errors aren’t allowed to use ICRC bit up to ATA/ATAPI-7, it seems to imply that ABRT bit alone could indicate transfer errors.

However, ATA/ATAPI-8 draft revision 1f removes the part that ICRC errors can turn on ABRT. So, this is kind of gray area. Some heuristics are needed here.

ATA/ATAPI device errors can be further categorized as follows.

This is indicated by UNC bit in the ERROR register. ATA devices reports UNC error only after certain number of retries cannot recover the data, so there’s nothing much else to do other than notifying upper layer.

READ and WRITE commands report CHS or LBA of the first failed sector but ATA/ATAPI standard specifies that the amount of transferred data on error completion is indeterminate, so we cannot assume that sectors preceding the failed sector have been transferred and thus cannot complete those sectors successfully as SCSI does.

Media changed / media change requested error

This is indicated by IDNF bit in the ERROR register. Report to upper layer.

This can be invalid command or parameter indicated by ABRT ERROR bit or some other error condition. Note that ABRT bit can indicate a lot of things including ICRC and Address errors. Heuristics needed.

Depending on commands, not all STATUS/ERROR bits are applicable. These non-applicable bits are marked with «na» in the output descriptions but up to ATA/ATAPI-7 no definition of «na» can be found. However, ATA/ATAPI-8 draft revision 1f describes «N/A» as follows.

A keyword the indicates a field has no defined value in this standard and should not be checked by the host or device. N/A fields should be cleared to zero.

So, it seems reasonable to assume that «na» bits are cleared to zero by devices and thus need no explicit masking.

ATAPI device CHECK CONDITION

ATAPI device CHECK CONDITION error is indicated by set CHK bit (ERR bit) in the STATUS register after the last byte of CDB is transferred for a PACKET command. For this kind of errors, sense data should be acquired to gather information regarding the errors. REQUEST SENSE packet command should be used to acquire sense data.

Once sense data is acquired, this type of errors can be handled similarly to other SCSI errors. Note that sense data may indicate ATA bus error (e.g. Sense Key 04h HARDWARE ERROR && ASC/ASCQ 47h/00h SCSI PARITY ERROR). In such cases, the error should be considered as an ATA bus error and handled according to the section called “ATA bus error”.

ATA device error (NCQ)

NCQ command error is indicated by cleared BSY and set ERR bit during NCQ command phase (one or more NCQ commands outstanding). Although STATUS and ERROR registers will contain valid values describing the error, READ LOG EXT is required to clear the error condition, determine which command has failed and acquire more information.

Note that ATA bus errors can be reported as ATA device NCQ errors. This should be handled as described in the section called “ATA bus error”.

If READ LOG EXT Log Page 10h fails or reports NQ, we’re thoroughly screwed. This condition should be treated according to the section called “HSM violation”.

ATA bus error

ATA bus error means that data corruption occurred during transmission over ATA bus (SATA or PATA). This type of errors can be indicated by

Controller-specific error completion with error information indicating transmission error.

On some controllers, command timeout. In this case, there may be a mechanism to determine that the timeout is due to transmission error.

Unknown/random errors, timeouts and all sorts of weirdities.

As described above, transmission errors can cause wide variety of symptoms ranging from device ICRC error to random device lockup, and, for many cases, there is no way to tell if an error condition is due to transmission error or not; therefore, it’s necessary to employ some kind of heuristic when dealing with errors and timeouts. For example, encountering repetitive ABRT errors for known supported command is likely to indicate ATA bus error.

Once it’s determined that ATA bus errors have possibly occurred, lowering ATA bus transmission speed is one of actions which may alleviate the problem. See the section called “Reconfigure transport” for more information.

PCI bus error

Data corruption or other failures during transmission over PCI (or other system bus). For standard BMDMA, this is indicated by Error bit in the BMDMA Status register. This type of errors must be logged as it indicates something is very wrong with the system. Resetting host controller is recommended.

Late completion

This occurs when timeout occurs and the timeout handler finds out that the timed out command has completed successfully or with error. This is usually caused by lost interrupts. This type of errors must be logged. Resetting host controller is recommended.

Unknown error (timeout)

This is when timeout occurs and the command is still processing or the host and device are in unknown state. When this occurs, HSM could be in any valid or invalid state. To bring the device to known state and make it forget about the timed out command, resetting is necessary. The timed out command may be retried.

Timeouts can also be caused by transmission errors. Refer to the section called “ATA bus error” for more details.

Источник

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх

=== START OF INFORMATION SECTION ===

Model Family:     SAMSUNG SpinPoint P80 SD series

Device Model:     SAMSUNG HD160JJ

Serial Number:    S08HJ10YB33273

Firmware Version: ZM100-33

User Capacity:    160,041,885,696 bytes

Device is:        In smartctl database [for details use: -P show]

ATA Version is:   7

ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 4a

Local Time is:    Mon Aug 17 11:43:51 2009 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:                 (3654) 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:        (  60) minutes.

SCT capabilities:              (0x003f) SCT Status 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate     0x000f   100   100   051    Pre-fail  Always       —       1

  3 Spin_Up_Time            0x0007   100   100   025    Pre-fail  Always       —       6208

  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       —       520

  5 Reallocated_Sector_Ct   0x0033   253   253   010    Pre-fail  Always       —       0

  7 Seek_Error_Rate         0x000f   253   253   051    Pre-fail  Always       —       0

  8 Seek_Time_Performance   0x0025   253   253   015    Pre-fail  Offline      —       0

  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       —       30817

 10 Spin_Retry_Count        0x0033   253   253   051    Pre-fail  Always       —       0

 11 Calibration_Retry_Count 0x0012   253   002   000    Old_age   Always       —       0

 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       —       388

190 Airflow_Temperature_Cel 0x0022   100   058   000    Old_age   Always       —       46

194 Temperature_Celsius     0x0022   100   058   000    Old_age   Always       —       46

195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       —       67415327

196 Reallocated_Event_Count 0x0032   253   253   000    Old_age   Always       —       0

197 Current_Pending_Sector  0x0012   253   253   000    Old_age   Always       —       0

198 Offline_Uncorrectable   0x0030   253   253   000    Old_age   Offline      —       0

199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       —       1723

200 Multi_Zone_Error_Rate   0x000a   100   100   000    Old_age   Always       —       0

201 Soft_Read_Error_Rate    0x000a   100   100   000    Old_age   Always       —       0

202 TA_Increase_Count       0x0032   253   253   000    Old_age   Always       —       0

SMART Error Log Version: 1

ATA Error Count: 1707 (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 1707 occurred at disk power-on lifetime: 30794 hours (1283 days + 2 hours)

  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  — — — — — — —

  84 51 80 cd 74 1d e5  Error: ICRC, ABRT 128 sectors at LBA = 0x051d74cd = 85816525

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  — — — — — — — —  —————-  ———————

  c8 00 80 cd 74 1d e5 00   4d+18:27:26.625  READ DMA

  c8 00 38 95 74 1d e5 00   4d+18:27:26.625  READ DMA

  c8 00 00 cd 70 1d e5 00   4d+18:27:26.625  READ DMA

  c8 00 48 4d 76 1d e5 00   4d+18:27:26.625  READ DMA

  c8 00 58 f5 75 1d e5 00   4d+18:27:26.563  READ DMA

Error 1706 occurred at disk power-on lifetime: 30794 hours (1283 days + 2 hours)

  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  — — — — — — —

  84 51 58 f5 75 1d e5  Error: ICRC, ABRT 88 sectors at LBA = 0x051d75f5 = 85816821

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  — — — — — — — —  —————-  ———————

  c8 00 58 f5 75 1d e5 00   4d+18:27:25.625  READ DMA

  c8 00 48 05 ea 1d e5 00   4d+18:27:25.625  READ DMA

  c8 00 10 ed e9 1d e5 00   4d+18:27:25.625  READ DMA

  c8 00 08 dd ea 1d e5 00   4d+18:27:25.625  READ DMA

  c8 00 08 cd ea 1d e5 00   4d+18:27:25.625  READ DMA

Error 1705 occurred at disk power-on lifetime: 30794 hours (1283 days + 2 hours)

  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  — — — — — — —

  84 51 70 de be 3b e7  Error: ICRC, ABRT 112 sectors at LBA = 0x073bbede = 121355998

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  — — — — — — — —  —————-  ———————

  c8 00 70 de be 3b e7 00   4d+18:23:10.625  READ DMA

  c8 00 90 4e be 3b e7 00   4d+18:23:10.625  READ DMA

  c8 00 40 e6 72 3b e7 00   4d+18:23:10.625  READ DMA

  c8 00 08 de 72 3b e7 00   4d+18:23:10.625  READ DMA

  c8 00 10 06 e1 3a e7 00   4d+18:23:10.313  READ DMA

Error 1704 occurred at disk power-on lifetime: 30794 hours (1283 days + 2 hours)

  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  — — — — — — —

  84 51 80 4d d5 f7 e5  Error: ICRC, ABRT 128 sectors at LBA = 0x05f7d54d = 100128077

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  — — — — — — — —  —————-  ———————

  c8 00 80 4d d5 f7 e5 00   4d+18:12:22.250  READ DMA

  c8 00 80 4d d4 f7 e5 00   4d+18:12:22.188  READ DMA

  ca 00 28 5e c3 4d e6 00   4d+18:12:21.063  WRITE DMA

  ca 00 f8 e6 fb 3d e7 00   4d+18:12:20.438  WRITE DMA

  ca 00 08 de fb 3d e7 00   4d+18:12:20.438  WRITE DMA

Error 1703 occurred at disk power-on lifetime: 30794 hours (1283 days + 2 hours)

  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  — — — — — — —

  84 51 18 46 80 3b e7  Error: ICRC, ABRT 24 sectors at LBA = 0x073b8046 = 121339974

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  — — — — — — — —  —————-  ———————

  c8 00 18 46 80 3b e7 00   4d+18:11:59.250  READ DMA

  c8 00 30 ae 6a 3b e7 00   4d+18:11:59.188  READ DMA

  c8 00 08 7e 6a 3b e7 00   4d+18:11:59.188  READ DMA

  c8 00 38 ee 69 3b e7 00   4d+18:11:59.188  READ DMA

  c8 00 10 de 69 3b e7 00   4d+18:11:59.125  READ DMA

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%     30805         —

# 2  Short offline       Completed without error       00%     30804         —

# 3  Extended offline    Completed without error       00%     26054         —

# 4  Extended offline    Interrupted (host reset)      60%     26052         —

SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1

SMART Selective self-test log data structure revision number 0

Warning: ATA Specification requires 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.

# smartctl -a /dev/sdb

smartctl version 5.38 [x86_64-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen

Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===

Model Family:     SAMSUNG SpinPoint P80 SD series

Device Model:     SAMSUNG HD160JJ

Serial Number:    S08HJ10YB33277

Firmware Version: ZM100-33

User Capacity:    160,041,885,696 bytes

Device is:        In smartctl database [for details use: -P show]

ATA Version is:   7

ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 4a

Local Time is:    Mon Aug 17 11:44:29 2009 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:                 (3561) 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:        (  59) minutes.

SCT capabilities:              (0x003f) SCT Status 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate     0x000f   100   100   051    Pre-fail  Always       —       0

  3 Spin_Up_Time            0x0007   100   100   025    Pre-fail  Always       —       6144

  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       —       524

  5 Reallocated_Sector_Ct   0x0033   253   253   010    Pre-fail  Always       —       0

  7 Seek_Error_Rate         0x000f   253   253   051    Pre-fail  Always       —       0

  8 Seek_Time_Performance   0x0025   253   253   015    Pre-fail  Offline      —       0

  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       —       30817

 10 Spin_Retry_Count        0x0033   253   253   051    Pre-fail  Always       —       0

 11 Calibration_Retry_Count 0x0012   253   002   000    Old_age   Always       —       0

 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       —       386

190 Airflow_Temperature_Cel 0x0022   094   055   000    Old_age   Always       —       48

194 Temperature_Celsius     0x0022   094   055   000    Old_age   Always       —       48

195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       —       58540580

196 Reallocated_Event_Count 0x0032   253   253   000    Old_age   Always       —       0

197 Current_Pending_Sector  0x0012   253   253   000    Old_age   Always       —       0

198 Offline_Uncorrectable   0x0030   253   253   000    Old_age   Offline      —       0

199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       —       1

200 Multi_Zone_Error_Rate   0x000a   100   100   000    Old_age   Always       —       0

201 Soft_Read_Error_Rate    0x000a   100   100   000    Old_age   Always       —       0

202 TA_Increase_Count       0x0032   100   100   000    Old_age   Always       —       262

SMART Error Log Version: 1

ATA Error Count: 357 (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 357 occurred at disk power-on lifetime: 27619 hours (1150 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

  — — — — — — —

  84 51 08 35 c3 57 e4  Error: ICRC, ABRT at LBA = 0x0457c335 = 72860469

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  — — — — — — — —  —————-  ———————

  ca 00 08 35 c3 57 e4 00      04:55:42.000  WRITE DMA

  ec 00 00 00 00 00 a0 00      04:55:41.938  IDENTIFY DEVICE

  ef 03 42 00 00 00 a0 00      04:55:41.938  SET FEATURES [Set transfer mode]

  ec 00 00 00 00 00 a0 00      04:55:41.938  IDENTIFY DEVICE

  00 00 01 01 00 00 a0 00      04:55:41.563  NOP [Abort queued commands]

Error 356 occurred at disk power-on lifetime: 27619 hours (1150 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

  — — — — — — —

  84 51 28 de e8 e3 e6  Error: ICRC, ABRT at LBA = 0x06e3e8de = 115599582

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  — — — — — — — —  —————-  ———————

  ca 00 28 de e8 e3 e6 00      04:55:41.500  WRITE DMA

  ec 00 00 00 00 00 a0 00      04:55:41.500  IDENTIFY DEVICE

  ef 03 42 00 00 00 a0 00      04:55:41.500  SET FEATURES [Set transfer mode]

  ec 00 00 00 00 00 a0 00      04:55:41.500  IDENTIFY DEVICE

  00 00 01 01 00 00 a0 00      04:55:41.125  NOP [Abort queued commands]

Error 355 occurred at disk power-on lifetime: 27619 hours (1150 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

  — — — — — — —

  84 51 28 de e8 e3 e6  Error: ICRC, ABRT at LBA = 0x06e3e8de = 115599582

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  — — — — — — — —  —————-  ———————

  ca 00 28 de e8 e3 e6 00      04:55:41.063  WRITE DMA

  ec 00 00 00 00 00 a0 00      04:55:41.063  IDENTIFY DEVICE

  ef 03 42 00 00 00 a0 00      04:55:41.063  SET FEATURES [Set transfer mode]

  ec 00 00 00 00 00 a0 00      04:55:41.063  IDENTIFY DEVICE

  00 00 01 01 00 00 a0 00      04:55:40.688  NOP [Abort queued commands]

Error 354 occurred at disk power-on lifetime: 27619 hours (1150 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

  — — — — — — —

  84 51 28 de e8 e3 e6  Error: ICRC, ABRT at LBA = 0x06e3e8de = 115599582

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  — — — — — — — —  —————-  ———————

  ca 00 28 de e8 e3 e6 00      04:55:40.625  WRITE DMA

  ec 00 00 00 00 00 a0 00      04:55:40.625  IDENTIFY DEVICE

  ef 03 42 00 00 00 a0 00      04:55:40.625  SET FEATURES [Set transfer mode]

  ec 00 00 00 00 00 a0 00      04:55:40.563  IDENTIFY DEVICE

  00 00 01 01 00 00 a0 00      04:55:40.250  NOP [Abort queued commands]

Error 353 occurred at disk power-on lifetime: 27619 hours (1150 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

  — — — — — — —

  84 51 28 de e8 e3 e6  Error: ICRC, ABRT at LBA = 0x06e3e8de = 115599582

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  — — — — — — — —  —————-  ———————

  ca 00 28 de e8 e3 e6 00      04:55:34.813  WRITE DMA

  ec 00 00 00 00 00 a0 00      04:55:34.750  IDENTIFY DEVICE

  ef 03 42 00 00 00 a0 00      04:55:34.750  SET FEATURES [Set transfer mode]

  ec 00 00 00 00 00 a0 00      04:55:34.750  IDENTIFY DEVICE

  00 00 01 01 00 00 a0 00      04:55:34.375  NOP [Abort queued commands]

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%     30806         —

# 2  Short offline       Completed without error       00%     30805         —

# 3  Extended offline    Completed without error       00%     26051         —

# 4  Extended offline    Interrupted (host reset)      60%     26049         —

SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1

SMART Selective self-test log data structure revision number 0

Warning: ATA Specification requires 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.