Ata2.00 Status Drdy Drq Error

Start 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 status: { drdy err } error: { unc } or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server

What Is Drdy

Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it drdy error ubuntu boot works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top SATA hdd errors up vote 0 down vote favorite I have one server with WDC WD3202ABYS ... There are 100 virtual

Status Drdy Err Centos

hosts. Server is working about 5 years and in this time period I have change 4 disks. All with same reason: sata error. The last one: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata2.00: BMDMA stat 0x5 ata2.00: cmd 35/00:60:57:7b:b6/00:01:06:00:00/e0 tag 0 dma 180224 out res 51/10:60:57:7b:b6/10:01:06:00:00/e0 Emask 0x81 (invalid argument) ata2.00: status: { DRDY ERR } ata2.00: error: { IDNF } ata2.00: configured for UDMA/133 sd 1:0:0:0: SCSI error: return code = 0x08000002 sdb: Current [descriptor]: sense ata1 00 status drdy key: Aborted Command Add. Sense: Recorded entity not found Descriptor sense data with sense descriptors (in hex): 72 0b 14 00 00 00 00 0c 00 0a 80 00 00 00 00 00 06 b6 7b 57 end_request: I/O error, dev sdb, sector 112622423 Buffer I/O error on device dm-8, logical block 14077747 lost page write due to I/O error on dm-8 Buffer I/O error on device dm-8, logical block 14077748 lost page write due to I/O error on dm-8 Buffer I/O error on device dm-8, logical block 14077749 lost page write due to I/O error on dm-8 Buffer I/O error on device dm-8, logical block 14077750 lost page write due to I/O error on dm-8 Buffer I/O error on device dm-8, logical block 14077751 lost page write due to I/O error on dm-8 Buffer I/O error on device dm-8, logical block 14077756 lost page write due to I/O error on dm-8 ata2: EH complete SCSI device sdb: 625142448 512-byte hdwr sectors (320073 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: drive cache: write back ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata2.00: BMDMA stat 0x5 ata2.00: cmd 35/00:90:17:30:b7/00:02:08:00:00/e0 tag 0 dma 335872 out res 51/10:90:17:30:b7/10:02:08:00:00/e0 Emask 0x81 (invalid argument) ata2.00: status: { DRDY ERR } ata2.00: error: { IDNF } ata2.00: configured for UDMA/133 sd 1:0:0:0: SCSI error: return code = 0x08000002 sdb: Current [descriptor]: sense key: Aborted Comman

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

Status Drdy Err Linux

Learn more about Stack Overflow the company Business Learn more about hiring developers

Status Drdy Err Error Abrt

or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and options libata noacpi=1 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 best answers are voted http://serverfault.com/questions/152855/sata-hdd-errors up and rise to the top DRDY ERR from HDD up vote 2 down vote favorite All of a sudden I started getting the DRDY ERR with my laptop running linux..some messages look like.. ata1:00: status: { DRDY ERR } ata1.00: error {UNC } ata1:00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1:00: BMDMA stat 0x25 ata1:00: failed command: READ DMA finally it drops me into http://superuser.com/questions/796423/drdy-err-from-hdd a command prompt asking me to enter a run level and after that INIT: no more processes left in this runlevel Suspecting a HDD crash, I took it out and used in another PC as an external USB HDD drive and I was able to mount & see all partitions and files within. So I assume Disc is OK. [EDIT/UPDATE] I'm also able to boot into the laptop from a USB pen drive with linux) and even able to see all the partitions on the disk and access them. Also took out the HDD and put it in a external casing and tried booting into the same laptop but got following different errors end_request: critical target error, dev sda, sector 32839936 EXT4_fs error: (device sda5): ext4_find_entry:935: inode #393217: comm init: reading directory lblock 0 INIT: No inittab file found Enter runlevel: So I guess, the HDD is accesible as a storage, but not bootable. The partitioning scheme on that HDD is as under if that'd help.. (GPT scheme) partition FileSystem size flags --------- ----------- ---- ----- /dev/sda1 unknown 2.00MB bios_grub /dev/sda2 ext2 128MB # was supposed to be common boot partition for chain loading /dev/sda3 swap 1.5GB /dev/sda4 ext4 8GB # Li

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: 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: https://ata.wiki.kernel.org/index.php/Libata_error_messages { DRDY } Prefix The prefix ata3.00: decodes as ata prefix, indicating this is a http://www.linux.org.ru/forum/general/8826435 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) state. exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Emask Error classification bitmask (AC_ERR_xxx in source code) SAct SATA SActive status drdy 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 number of retries Input taskfile The "cmd" line gives the ATA command (taskfile) sent to the device: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 This lists ATA registers in the following order: Command (separator) Feature NSect LBA L LBA M LBA H (separator) HOB Feature HOB NSect HOB LBA L HOB LBA M HOB status drdy err LBA H (separator) Device/Head tag NCQ tag number, or listed as zero if NCQ is not active/applicable. Output taskfile, error summary The next line contains a current dump of the ATA device's registers, along with an error summary: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) In order: Status (separator) Error NSect LBA L LBA M LBA H (separator) HOB Error HOB NSect HOB LBA L HOB LBA M HOB LBA H (separator) Device/Head Emask ATA command's internal error mask (AC_ERR_xxx in source code) (summary) An English summary of the error, such as timeout HSM violation media error See below for a full list. Error classes These are the possible values for the (summary) in each error message, above. host bus error Host<->chip bus error (i.e. PCI, if on PCI bus) ATA bus error chip<->device bus error timeout Controller failed to respond to an active ATA command. This could be any number of causes. Most often this is due to an unrelated interrupt subsystem bug (try booting with 'pci=nomsi' or 'acpi=off' or 'noapic'), which failed to deliver an interrupt when we were expecting one from the hardware. HSM violation Hardware failed to respond in an expected manner. "HSM" stands for Host State Machine, a software-based finite state machine required by ATA that expects certain hardware behaviors, based on the current ATA command and other hardware-state programming details. internal er

2 Вот такая вот зараза девочка моей мечты:02:0b.0 Mass storage controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01) [ 1.203295] ata2: SATA max UDMA/100 mmio m512@0xf7ff7800 tf 0xf7ff78c0 irq 23 [ 1.840029] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 1.875593] ata2.00: ATA-8: ST31500341AS, CC1G, max UDMA/133 [ 1.875598] ata2.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 1.931623] ata2.00: configured for UDMA/100 [ 91.816053] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x6 frozen [ 91.816061] ata2: SError: { 10B8B BadCRC } [ 91.816066] ata2.00: failed command: READ DMA EXT [ 91.816075] ata2.00: cmd 25/00:00:df:5e:1e/00:01:73:00:00/e0 tag 0 dma 131072 in [ 91.816081] ata2.00: status: { DRDY } [ 91.816094] ata2: hard resetting link [ 92.136033] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 92.227617] ata2.00: configured for UDMA/100 [ 92.227625] ata2.00: device reported invalid CHS sector 0 [ 92.227636] ata2: EH complete [ 92.879119] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 [ 92.879126] ata2.00: BMDMA2 stat 0x6d0009 [ 92.879130] ata2: SError: { 10B8B BadCRC } [ 92.879135] ata2.00: failed command: READ DMA EXT [ 92.879143] ata2.00: cmd 25/00:00:df:60:1e/00:01:73:00:00/e0 tag 0 dma 131072 in [ 92.879149] ata2.00: status: { DRDY ERR } [ 92.879170] ata2.00: error: { ABRT } [ 92.983634] ata2.00: configured for UDMA/100 [ 92.983649] ata2: EH complete [ 93.008075] ata2: drained 32768 bytes to clear DRQ. [ 93.045690] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x6 frozen [ 93.045699] ata2: SError: { 10B8B BadCRC } [ 93.045706] ata2.00: failed command: READ DMA EXT [ 93.045719] ata2.00: cmd 25/00:00:df:62:1e/00:01:73:00:00/e0 tag 0 dma 131072 in [ 93.045729] ata2.00: status: { Busy } [ 93.045734] ata2.00: error: { ICRC UNC IDNF ABRT } [ 93.045776] ata2: hard resetting link [ 93.364032] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 93.455623] ata2.00: configured for UDMA/100 [ 93.455638] ata2: EH complete *skip* [ 2924.507363] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 [ 2924.507370] ata2.00: BMDMA2 stat 0x6d0009 [ 2924.507375] ata2: SError: { 10B8B BadCRC } [ 2924.507380] ata2.00: failed command: READ DMA [ 2924.507389] ata2.00: cmd c8/00:00:00:6d:04/00:00:00:00:00/e0 tag 0 dma 131072 in [ 2924.507395] ata2.00: status: { DRDY ERR } [ 2924.507398] ata2.00: error: { ABRT } [ 2924.595626] ata2.00: configured for UDMA/33 [ 2924.595642] ata2: EH complete [ 2955.000055] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x6 frozen [ 2955.000063] ata2: