Emask Media Error
Contents |
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support status drdy err error unc AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu
Drdy Error Ubuntu Boot
PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search status drdy err error abrt Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Hardware [ubuntu] Hard Drive Error : ata3.00: status: { DRDY ERR } Having an Issue With Posting ? Do you want to help us debug ata1.00: status: { drdy } the posting issues ? < is the place to report it, thanks ! Page 1 of 3 123 Last Jump to page: Results 1 to 10 of 29 Thread: Hard Drive Error : ata3.00: status: { DRDY ERR } Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode January 9th, 2009 #1 hobong View Profile View Forum
What Is Drdy
Posts Private Message Spilled the Beans Join Date Mar 2007 Beans 12 [ SOLVED ] Hard Drive Error : ata3.00: status: { DRDY ERR } Hi all I have problem with my System the log always spam with these messages : Code: .......... 68489.756311] ata3.00: status: { DRDY ERR } [68489.756314] ata3.00: error: { UNC } [68489.951583] ata3.00: configured for UDMA/133 [68489.951604] ata3: EH complete [68492.671124] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [68492.671133] ata3.00: BMDMA stat 0x24 [68492.671140] ata3.00: cmd c8/00:08:55:e8:8d/00:00:00:00:00/e2 tag 0 dma 4096 in [68492.671142] res 51/40:00:56:e8:8d/00:00:00:00:00/02 Emask 0x9 (media error) [68492.671145] ata3.00: status: { DRDY ERR } [68492.671148] ata3.00: error: { UNC } [68492.899657] ata3.00: configured for UDMA/133 [68492.899678] ata3: EH complete [68495.610841] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [68495.610851] ata3.00: BMDMA stat 0x24 [68495.610857] ata3.00: cmd c8/00:08:55:e8:8d/00:00:00:00:00/e2 tag 0 dma 4096 in [68495.610859] res 51/40:00:56:e8:8d/00:00:00:00:00/02 Emask 0x9 (media error) [68495.610863] ata3.00: status: { DRDY ERR } [68495.610865] ata3.00: error: { UNC } [68495.799599] ata3.00: configured for UDMA/133 [68495.799620] sd 2:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [68495.799626] sd 2:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor] [68495.799631] Descriptor sense data with sense descriptors (in hex): [68495.799633] 72 03 11 04 00
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 status drdy err centos about Stack Overflow the company Business Learn more about hiring developers or posting ads drdy err unc centos with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question
Sense Key : Medium Error [current] [descriptor]
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 https://ubuntuforums.org/showthread.php?t=1034762 best answers are voted up and rise to the top I/O error but no bad block is reported in syslog up vote 2 down vote favorite 1 I got errors like this in my syslog, but there's no bad block or sector defined in kernel report, I can't just replace the HDD right now and I prefer to reallocate the bad blocks for now, so I need the number of bad http://unix.stackexchange.com/questions/48660/i-o-error-but-no-bad-block-is-reported-in-syslog sectors. Any suggestion on how to find the number of sectors as fast as possible? In other server that I have, kernel always reports sector number but on this server no sector reported. res 41/40:08:a0:11:76/00:00:53:00:00/00 Emask 0x409 (media 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 http://serverfault.com/questions/407007/what-do-these-disk-errors-in-syslog-mean Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users https://ata.wiki.kernel.org/index.php/Libata_error_messages Badges Unanswered Ask Question _ Server 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 works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top What do these disk errors in syslog mean? up vote drdy err 8 down vote favorite 1 I just rebooted my monitoring server for the first time in a while, and the following starting filling the screen: Jul 11 23:52:30 monit kernel: [ 25.255908] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jul 11 23:52:30 monit kernel: [ 25.256170] ata1.00: BMDMA stat 0x24 Jul 11 23:52:30 monit kernel: [ 25.256278] ata1.00: failed command: READ DMA Jul 11 23:52:30 monit kernel: [ 25.256410] ata1.00: cmd c8/00:c0:20:68:35/00:00:00:00:00/e0 tag status drdy err 0 dma 98304 in Jul 11 23:52:30 monit kernel: [ 25.256416] res 51/40:9f:41:68:35/00:00:00:00:00/e0 Emask 0x9 (media error) Jul 11 23:52:30 monit kernel: [ 25.256809] ata1.00: status: { DRDY ERR } Jul 11 23:52:30 monit kernel: [ 25.256933] ata1.00: error: { UNC } Jul 11 23:52:30 monit kernel: [ 25.304388] ata1.00: configured for UDMA/66 Jul 11 23:52:30 monit kernel: [ 25.304430] ata1: EH complete . . . Jul 11 23:52:30 monit kernel: [ 25.552451] sd 0:0:0:0: [sda] Unhandled sense code Jul 11 23:52:30 monit kernel: [ 25.552462] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Jul 11 23:52:30 monit kernel: [ 25.552475] sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor] Jul 11 23:52:30 monit kernel: [ 25.552490] Descriptor sense data with sense descriptors (in hex): Jul 11 23:52:30 monit kernel: [ 25.552498] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Jul 11 23:52:30 monit kernel: [ 25.552529] 00 35 68 41 Jul 11 23:52:30 monit kernel: [ 25.552543] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed Jul 11 23:52:30 monit kernel: [ 25.552559] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 35 68 20 00 00 c0 00 Jul 11 23:52:30 monit kernel: [ 25.552587] end_request: I/O error, dev sda, sector 3500097 Jul 11 23:52:30 monit kernel: [ 25.556607] ata1: EH complete I alre
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: { DRDY } Prefix The prefix ata3.00: decodes as ata prefix, indicating this 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 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