Ata Bus Error Icrc Abrt
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site
Drdy Err Unc
About Us Learn more about Stack Overflow the company Business Learn more about what is drdy hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is options libata noacpi=1 a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The
Drdy Error Ubuntu Boot
best answers are voted up and rise to the top SATA drives or chipset throwing DRDY ERR and ICRC ABRT up vote 4 down vote favorite 2 I have an SD-VIA-1A2S PCI card with 2 sata ports (and one ATA-133 that isn't used). Two new Western Digital Caviar Green drives (WD10EARS 1TB) throw repeated errors in kern.log (removed date/time/host info for brevity): [ 7.376475] ata2.00: exception
Status Drdy Err Centos
Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 [ 7.376480] ata2.00: BMDMA stat 0x5 [ 7.376483] ata2: SError: { UnrecovData Proto TrStaTrns } [ 7.376489] ata2.00: cmd c8/00:40:20:00:00/00:00:00:00:00/e0 tag 0 dma 32768 in [ 7.376490] res 51/84:2f:20:00:00/00:00:00:00:00/e0 Emask 0x12 (ATA bus error) [ 7.376493] ata2.00: status: { DRDY ERR } [ 7.376495] ata2.00: error: { ICRC ABRT } [ 7.376504] ata2: hard resetting link I'm using Ubuntu 9.04 - 2.6.28-18-generic, though I have tried live cds of Ubuntu 9.10, Fedora 12 and OpenSUSE 11.2 - all running various 2.6.31 kernels - and all received the same error. Based on testing these drives and this card in two other machines and combos of connecting the drives directly to the motherboard or the add-in card, I'm relatively convinced that it's the VIA chipset that is the problem. Another computer that also has an onboard VIA SATA chipset (like the add-in card) produces the same errors when the drives are directly on that motherboard. I have been able to verify that the drives are perfectly good, and I tried everything I can think of in terms of swapping cables, psu isn't overloaded, etc. The error happens on boot once
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 ata1.00 failed command read dma > Hardware & Laptops [SOLVED] [HDD] hardware problem? FedoraForum Search User Name
Exception Emask 0x0 Sact 0x0 Serr 0x0 Action 0x0
Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Hardware & Laptops Help with failed command read dma ext your hardware, including laptop issues Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search http://superuser.com/questions/121391/sata-drives-or-chipset-throwing-drdy-err-and-icrc-abrt this Thread Display Modes #1 30th August 2014, 09:43 AM md7sum Offline Registered User Join Date: Aug 2014 Location: Oregon Posts: 4 [HDD] hardware problem? For some days now I get error messages while booting up fedora. As they appear in an irreproducible manner, I suspect my HDD to be faulty. Nonetheless, the "Lenovo Bootable Diagnostics ISO" does not show any http://forums.fedoraforum.org/showthread.php?t=300535 errors and I need to prove reliably that the HDD is not working in order to get a new HDD payed by the warranty. OCR of the screenshot showing the error messages: [126.798506] ata1.00: failed command: READ FPDMA QUEUED [126.800501] ata1.00: cmd 60/08:60:e0:6f:f8/00:00:35:00:00/40 tag 1Z ncq 4096 in [126.800501] res 41/84:08:e0:6f:f8/00:00:35:00:00/00 Emask 0x410 (ATA bus error) [126.804484] ata1.00: status: { DRDY ERR 1 [126.806355] ata1.00: error: { ICRC ABRT [127.279527] end_request: I/O error, deu sda, sector 905474016 [127.294777] ata1.00: exception Emask Ox0 SAct Ox7c0000 SErr Ox0 action 0x6 [127.296798] ata1.00: irq_stat Ox40::c008 [127.298796] ata1.00: failed command: READ FPDMA QUEUED L [127.300789] ata1.00: cad 60/08:b0:d8:6f:f8/00:00:35:00:00/40 tag 22 ncq 4096 in E [127.300789] res 41/84:08:d8:6f:f8/00:00:35:00:00/00 Enask 0)(410 (ATA bus error)
errorPCI bus errorLate completionUnknown error (timeout)Hotplug and power management exceptionsEH recovery actionsClearing error conditionResetReconfigure transport This chapter tries to identify what error/exception conditions exist for https://www.kernel.org/doc/htmldocs/libata/ataExceptions.html ATA/ATAPI devices and describe how they should be handled in http://unix.stackexchange.com/questions/205675/can-anyone-please-help-debug-these-ata-error-messages 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 drdy err 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 categoriesHSM violationATA/ATAPI device error (non-NCQ / non-CHECK CONDITION)ATAPI device CHECK CONDITIONATA device error (NCQ)ATA bus errorPCI bus failed command read errorLate completionUnknown error (timeout)Hotplug and power management exceptions 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. Examples 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 err
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Can anyone please help debug these ata error messages? up vote 1 down vote favorite my Centos 6 server has been playing recently in that it seems to freeze up and lose network access. I've been getting a load of ata5 error messages in the log and after some digging have determined that the drive is sda, the root filesystem. Another post with similar issues suggested changing the SATA cable, which i've done but the errors still persist. I've also set fsck to run at each boot up (as it's the root filesystem) although i'm not sure it's running as there's nothing appearing on screen during boot to suggest it's running (should there be?). I basically set the maximum mount count to 1 with tune2fs. Sometimes the system works fine, but i went away for a couple of days over the weekend and it was dead on my return. A simple hard reset brought it back again, but obviously I need to get to the bottom of it. Any help would be appreciated. May 26 14:05:21 centos kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) May 26 14:05:21 centos kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) May 26 14:05:21 centos kernel: ata7.00: ATA-7: SAMSUNG HD103UJ, 1AA01113, max UDMA7 May 26 14:05:21 centos kernel: ata7.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32) May 26 14:05:21 centos kernel: ata5.00: ATA-8: SanDisk SDSSDX120GG25, R211, max UDMA/133 May 26 14:05:21 centos kernel: ata5.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32) May 26 14:05:21 centos kernel: ata7.00: configured for UDMA/133 May 26 14:05:21 centos kernel: ata5.00: configured for UDMA/133 May 26 14:05:21 centos kernel: ata4: SATA link down (SStatus 0 SControl 300) May 26 14:05:21 centos kernel: scsi 4:0:0:0: Direct-Access ATA SanDisk SDSSDX12 R211 PQ: 0 ANSI: 5 May 26 14:05:21 centos kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) May 26 14:05:21 centos kernel: ata6.00: ATA-8: ST31000524AS, JC4B, max UDMA/133 May 26 14:05:21 centos kernel: ata6.00: 1953525168 sectors, multi 16: LBA48 NCQ (de