Ata3.00 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
Drdy Err Unc
and policies of this site About Us Learn more about Stack Overflow options libata noacpi=1 the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users
What Is Drdy
Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how drdy error ubuntu boot it works: Anybody can ask a question Anybody can answer The 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 status drdy err centos (WD10EARS 1TB) throw repeated errors in kern.log (removed date/time/host info for brevity): [ 7.376475] ata2.00: exception 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
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and
Exception Emask 0x0 Sact 0x0 Serr 0x0 Action 0x0
policies of this site About Us Learn more about Stack Overflow the ata bus error company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges
Ata1.00 Failed Command Read Dma
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 http://superuser.com/questions/121391/sata-drives-or-chipset-throwing-drdy-err-and-icrc-abrt 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 http://unix.stackexchange.com/questions/205675/can-anyone-please-help-debug-these-ata-error-messages 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
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 https://ata.wiki.kernel.org/index.php/Libata_error_messages 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 Emask 0x4 (timeout) ata3.00: status: { DRDY } Prefix The prefix ata3.00: decodes as ata prefix, indicating this is a libata port or device http://forums.fedoraforum.org/showthread.php?t=300535 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 drdy err (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
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 > Hardware & Laptops [SOLVED] [HDD] hardware problem? FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Hardware & Laptops Help with 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 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 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)