Hard Drive Error Icrc
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
Drdy Err Unc
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 options libata noacpi=1 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 SATA drives or chipset throwing DRDY ERR and ICRC ABRT
Status Drdy Err Centos
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 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
Drdy Error Ubuntu Boot
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 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 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 ata4.00: status: { drdy err } > Fedora 23/24 > Hardware & Laptops [SOLVED] [HDD] hardware problem? FedoraForum
Exception Emask 0x0 Sact 0x0 Serr 0x0 Action 0x0
Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search ata1.00 failed command read dma 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 http://superuser.com/questions/121391/sata-drives-or-chipset-throwing-drdy-err-and-icrc-abrt 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. http://forums.fedoraforum.org/showthread.php?t=300535 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)
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 https://forums.opensuse.org/showthread.php/389674-Hard-disk-failure-SMART-and-smartmontools 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) drdy err 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
Help Here Hardware Hard disk failure? SMART and smartmontools Welcome! If this is your first visit, be sure to check out the FAQ. You will have to register before you can post in the forums. (Be aware the forums do not accept user names with a dash "-") Also, logging in lets you avoid the CAPTCHA verification when searching . Select Articles, Forum, or Blog. Posting in the Forums implies acceptance of the Terms and Conditions. Results 1 to 4 of 4 Thread: Hard disk failure? SMART and smartmontools Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 12-Jul-2008,10:22 #1 gilap View Profile View Forum Posts View Blog Entries View Articles Explorer Penguin Join Date Jun 2008 Location Morecambe Bay Posts 103 Hard disk failure? SMART and smartmontools I have a brand new Hitachi drive (250 gb and only 3 days old). I have installed a dual boot system with XP and Suse 10.3. I am also a noob, so please bear with me... I keep getting SMART error messages when I'm in Suse. The Hitachi diagnostic tool tells me the disk is fine and smartmontools says "PASSED" after running this command "smartctl -H /dev/sda" I have also run a couple of short and long selftests and no errors show up. # smartctl -l selftest /dev/sda smartctl version 5.37 [i686-suse-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is smartmontools Home Page (last updated $Date: 2008/06/16 17:31:16 $) === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 43 - # 2 Short offline Completed without error 00% 41 - # 3 Extended offline Aborted by host 90% 37 - # 4 Extended offline Completed without error 00% 36 - # 5 Short offline Completed without error 00% 34 - Yet the smart log throws out the following Error 68 occurred at disk power-on lifetime: 43 hours (1 days + 19 hours) When the command that caused the error occurred, the device was active or idle . After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 29 36 ba e8 Error: ICRC, ABRT at LBA = 0x08ba3629 = 146421289 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 a0 8a 32 ba e0 00 03:23:54.100 READ DMA EXT 27 00 00 00 00 00 e0 00 03:23:54.100 READ NATIVE MAX ADDRE