Ata 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 About Us Learn more about Stack Overflow the company Business Learn more drdy err unc about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask what is drdy Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: options libata noacpi=1 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 SATA drives or chipset throwing DRDY ERR and ICRC ABRT up vote 4 down drdy error ubuntu boot 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 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
Status Drdy Err Centos
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 or twice, after using fdisk on the drive once or twice, and constantly when attempting to sync a new mdadm raid 1 array created on the two drives. Any thoughts on where to go from here - driver/kernel wise? I'm completely open to buying a new PCI add-in card if someone can recommend one with 2 internal sata ports that works well in Debian/Ubuntu. Thanks! linux hard-drive drivers sata chipset share|improve this ques
Overview All libata error messages produced by the kernel use a standard format: ata3.00: exception Emask 0x0 SAct 0x0 SErr
Ata Status 51 Error 40
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 icrc abrt at lba Emask 0x4 (timeout) ata3.00: status: { DRDY } Prefix The prefix ata3.00: decodes as ata prefix, indicating this ata bus error 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 http://superuser.com/questions/121391/sata-drives-or-chipset-throwing-drdy-err-and-icrc-abrt 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
Please help today!Produce and hosting N4F does cost money, please consider a small donation to our project so that we can stay offering you the best.We really do need your support! "READ_DMA" http://www.nas4free.org/forums/viewtopic.php?t=5306 and "CAM status" errors: desperate for fix! Filesystems(UFS, EXT2, FAT, NTFS, ZFS), mount points, partitions Forum rules • NAS4Free Official Site • Set-Up Guide • FAQs • Forum Rules Post Reply Print view 5 posts • Page 1 of 1 fomoco NewUser Posts: 11 Joined: 25 Jun 2012 22:53 Status: Offline "READ_DMA" and "CAM status" errors: desperate for fix! Quote Post #1 by fomoco » 25 Oct drdy err 2013 02:26 After a massive ordeal, and loss of a significant amount of data http://www.forums.nas4free.org/viewtopic.php?f=68&t=5183, I have begun to rebuild my NAS.I'll be buggered if the same error isn't flooding my log.Please keep in mind that the new system has all new components, including new disks that have been wiped as per the process in the FAQ, all the cabling has been replaced, fresh install (embedded, 9.1.0.1 847). ata error icrc No modifications to the default config, other than adding and configuring the disks (even gone so far as to reboot after every single step during the build). The error stays with the ada assignment, even if the physical disks are swapped. It has been at ada4 on both controllers. The problem prevents me from building a software RAID 5 (my preference) as it takes the disk offline due to "error". I can build a ZFS pool with the disk included, but this is what the log looks like: Code: Select allOct 24 18:03:34 freenas kernel: (ada4:ata6:0:1:0): Retrying command
Oct 24 18:03:34 freenas kernel: (ada4:ata6:0:1:0): RES: 51 84 cc 0b 58 00 00 00 00 80 00
Oct 24 18:03:34 freenas kernel: (ada4:ata6:0:1:0): ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT )
Oct 24 18:03:34 freenas kernel: (ada4:ata6:0:1:0): CAM status: ATA Status Error
Oct 24 18:03:34 freenas kernel: (ada4:ata6:0:1:0): READ_DMA. ACB: c8 00 cc 0b 58 40 00 00 00 00 80 00
Oct 24 18:03:18 freenas kernel: (ada4:ata6:0:1:0): Retrying command
Oct 24 18:03:18 freenas kernel: (ada4:ata6:0:1:0): RES: 51 84 e1 c3 57 00 00 00 00 80 00
Oct 24 18:03:18 freenas kernel: (ada4:ata6:0:1:0): ATA status: 51 (DRDY SERV