Linux Ata Host Bus Error
Contents |
Overview All libata error messages produced by the kernel use a standard format: ata3.00: exception Emask 0x0 SAct 0x0 sata error register SErr 0x0 action 0x2 frozen ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 res 40/00:00:01:4f:c2/00:00:00:00:00/00
Ata Bus Error
Emask 0x4 (timeout) ata3.00: status: { DRDY } Prefix The prefix ata3.00: decodes as ata prefix, indicating hsm violation ubuntu this is a libata port or device message 3 port number, counting from one (1) 00 device number, usually zero unless Port Multiplier or PATA master/slave is involved Exception line
Options Libata Noacpi=1
The exception line gives an overview of the EH (Error Handler) state. exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Emask Error classification bitmask (AC_ERR_xxx in source code) SAct SATA SActive register SErr SATA SError register action ATA_EH_xxx actions, like revalidate, softreset, hardreset (see include/linux/libata.h) frozen if present, indicates the port was frozen for EH t
9th, 2009, 07:25 AMHi all I have problem with my System the log always spam with these messages : .......... 68489.756311]
Exception Emask 0x0 Sact 0x0 Serr 0x0 Action 0x0
ata3.00: status: { DRDY ERR } [68489.756314] ata3.00: error: { UNC } [68489.951583]
Icrc Abrt
ata3.00: configured for UDMA/133 [68489.951604] ata3: EH complete [68492.671124] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 "ata1.00: status: { drdy }" [68492.671133] ata3.00: BMDMA stat 0x24 [68492.671140] ata3.00: cmd c8/00:08:55:e8:8d/00:00:00:00:00/e2 tag 0 dma 4096 in [68492.671142] res 51/40:00:56:e8:8d/00:00:00:00:00/02 Emask 0x9 (media error) [68492.671145] ata3.00: status: { DRDY ERR } [68492.671148] ata3.00: error: https://ata.wiki.kernel.org/index.php/Libata_error_messages { UNC } [68492.899657] ata3.00: configured for UDMA/133 [68492.899678] ata3: EH complete [68495.610841] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [68495.610851] ata3.00: BMDMA stat 0x24 [68495.610857] ata3.00: cmd c8/00:08:55:e8:8d/00:00:00:00:00/e2 tag 0 dma 4096 in [68495.610859] res 51/40:00:56:e8:8d/00:00:00:00:00/02 Emask 0x9 (media error) [68495.610863] ata3.00: status: { DRDY ERR } [68495.610865] ata3.00: error: { UNC } [68495.799599] ata3.00: configured for UDMA/133 [68495.799620] sd https://ubuntuforums.org/archive/index.php/t-1034762.html 2:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [68495.799626] sd 2:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor] [68495.799631] Descriptor sense data with sense descriptors (in hex): [68495.799633] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 [68495.799643] 02 8d e8 56 [68495.799647] sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed [68495.799653] end_request: I/O error, dev sda, sector 42854486 [68495.799675] ata3: EH complete [68495.800096] sd 2:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB) [68495.817023] sd 2:0:0:0: [sda] Write Protect is off [68495.817030] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 [68495.819042] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [68495.826120] sd 2:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB) ..... I Have just replace the Hard Drive but the messages are still spaming my system. Any one could please help me ? I also attach the log from dmesg command output. Thank You U'm using Ubuntu 8.10 II Proc 3.1 Ghz Hard Drive 320 GB Mem 2 GB It's Kernel bug on ata acpi Put "options libata noacpi=1" on /etc/modprobe.d/options solved t
Technology - unRAID Server Community » Legacy Support (unRAID 5 and Older) » General Support (V5 and Older) » http://lime-technology.com/forum/index.php?topic=33937.0 [SOLVED] Errors in syslog - host bus errors with Gigabyte GA-X58A-UD3R_rev2 « previous next » Send this topic Print Pages: [1] 2 Go Down Author Topic: [SOLVED] Errors in syslog http://www.centos.org/forums/viewtopic.php?t=24578 - host bus errors with Gigabyte GA-X58A-UD3R_rev2 (Read 3010 times) Switchblade Hero Member Posts: 747 [SOLVED] Errors in syslog - host bus errors with Gigabyte GA-X58A-UD3R_rev2 « on: June bus error 27, 2014, 05:55:23 PM » My rig was running great with no errors for months. A couple of weeks ago I started seeing errors on my console, cache drive errors. you can read all about that thread here,http://lime-technology.com/forum/index.php?topic=33856.new;topicseen#new I never did get anyone to confirm if the cache drive was the issue, but no more CRC errors status: { drdy and the system seems very happy - well except... So I replaced my cache drive, ran preclear, and now have a working cache drive again. I have confirmed I have no SMART errors on any of my drives and unraid shows no errors on the webgui. No errors on the console either. Ran a parity check, zero errors. However, there are some errors in the syslog that concern me.I built this new server several months ago and have had no issues (other than the cache drive mentioned above) and I have not changed the BIOS settings, drives or anything else. I went back and confirmed that the errors did not exist with my old mb setup, good to have backups of my flash drive with syslogs. . This makes me think if I perhaps have a BIOS settings incorrect re the hard drive controllers. This mb has 3 of them. If it is a cable, it would be good to know which drive/cable is having the issue. In the syslog, it refers to ata15
Assistance Issues related to hardware problems Post Reply Print view Search Advanced search 3 posts • Page 1 of 1 herders Posts: 20 Joined: 2007/01/07 16:11:15 ATA messages - Assistance Quote Postby herders » 2011/10/18 21:40:35 Hi All,I am getting a list of errors, dealing with ATA, as below.I can log into the machine no problem, my users are able to browse the server through SAMBA, can view all the files but they are all unavailable. Checked the SElinux settings and found they were in incorrect, reset the proper settings and fixed file permissions.Not sure where to go from here...Any suggestions.ThanksJackCode: Select allata4.00: irq_stat 0x03020002, device error via SDB FIS
ata4: SError: { 10B8B BadCRC }
ata4.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 4096 in
res 41/84:08:00:00:00/00:00:00:00:00/00 Emask 0x410 (ATA bus error)
ata4.00: status: { DRDY ERR }
ata4.00: error: { ICRC ABRT }
ata4: hard resetting link
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata4.00: configured for UDMA/100
ata4: EH complete
ata4: limiting SATA link speed to 1.5 Gbps
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x280000 action 0x6
ata4.00: irq_stat 0x03020002, device error via SDB FIS
ata4: SError: { 10B8B BadCRC }
ata4.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 4096 in
res 41/84:08:00:00:00/00:00:00:00:00/00 Emask 0x410 (ATA bus error)
ata4.00: status: { DRDY ERR }
ata4.00: error: { ICRC ABRT }
ata4: hard resetting link
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 10)
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata4.00: revalidation failed (errno=-5)
ata4: failed to recover some devices, retrying in 5 secs
ata4: hard resetting link
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 10)
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata4.00: revalidation failed (errno=-5)
ata4: failed to recover some devices, retrying in 5 secs
ata4: hard resetting link
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 10)
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata4.00: revalidation failed (errno=-5)
ata4.00: disabled
ata4: hard resetting link
ata4: SATA link up 1.5