Ata3 Bus Error
Contents |
9th, 2009, 07:25 AMHi all I ata bus error ubuntu have problem with my System the log always spam emask 0x10 (ata bus error) with these messages : .......... 68489.756311] ata3.00: status: { DRDY ERR } [68489.756314] ata3.00: exception emask 0x0 sact 0x0 serr 0x0 action 0x0 error: { UNC } [68489.951583] ata3.00: configured for UDMA/133 [68489.951604] ata3: EH complete [68492.671124] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 failed command identify packet device [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: { UNC } [68492.899657] ata3.00: configured for UDMA/133 [68492.899678] ata3: EH complete [68495.610841] ata3.00: exception Emask 0x0
Write Fpdma Queued Ata Bus Error
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 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: [sd
Edit Invalid Medium Unassigned Edit You need to log in to change this bug's
Ata1.00: Failed Command: Read Fpdma Queued
status. Affecting: linux (Ubuntu) Filed here by: Leoaloha When: 2014-10-24 status drdy Completed: 2014-10-28 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux device reported invalid chs sector 0 nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Medium Assigned to Nobody Me Comment https://ubuntuforums.org/archive/index.php/t-1034762.html on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Maybe related to long lasting bug #550559. Consistent ATAbus error resulting in crashed disk. changed three different SATA cables. change three different physical disks. Three other https://bugs.launchpad.net/bugs/1385034 disks in system OK. Have SSD /dev/sda with operating system on it. Crashing disk always /home /tmp /var and swap on it. Three different ports used. always; ata3: exception Emask 0x10 SAct 0x0 SErr 0x10202 action 0xe frozen ata3: irq_stat 0x00400000, PHY RDY changed ata3: SError: { RecovComm Persist PHYRdyChg } ata3: hard resetting link ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) ata3.00: supports DRM functions and may not be fully accessible ata3.00: supports DRM functions and may not be fully accessible ata3.00: configured for UDMA/133 ata3: EH complete ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: leoaloha 2776 F.... pulseaudio /dev/snd/controlC2: leoaloha 2776 F.... pulseaudio /dev/snd/controlC0: leoaloha 2776 F.... pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Oct 23 18:27:10 2014 HibernationDevice: RESUME=UUID=deb735eb-e665-4f99-bcb3-b156a53694a0 InstallationDate: Installed on 2014-09-19 (3
Overview All libata error messages produced by the kernel use a standard format: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata3.00: https://ata.wiki.kernel.org/index.php/Libata_error_messages 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 Emask 0x4 (timeout) ata3.00: status: { DRDY } Prefix The prefix ata3.00: decodes as ata prefix, indicating 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 The exception line gives an overview of the EH (Error Handler) bus error 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