Emask 0x9 Media Error Linux
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might status drdy err error unc have Meta Discuss the workings and policies of this site About
Drdy Error Ubuntu Boot
Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with ata1.00: status: { drdy } us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only
Status Drdy Err Error Abrt
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 how to interpret these errors from syslog up vote 11 down vote favorite 1 My Ubuntu has been acting weird lately. Yesterday, it wouldn't boot normally, so I had what is drdy to do a 'recovery mode' boot. It said I had to do an fsck manually, which I did using a live CD. After this, I was already able to boot to the desktop but everything is so sluggish. Apps would turn gray for seconds. Sometimes other apps wont start at all. In other instances it it saying that the filesystem is in read-only mode. This is part of what I've been getting: Oct 26 21:23:56 kernel: [ 1900.960506] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed Oct 26 21:23:56 kernel: [ 1900.960533] end_request: I/O error, dev sda, sector 63206544 Oct 26 21:23:56 kernel: [ 1900.960541] Buffer I/O error on device sda1, logical block 7900562 Oct 26 21:24:00 kernel: [ 1904.146683] res 51/40:00:90:74:c4/00:00:00:00:00/03 Emask 0x9 (media error) Oct 26 21:24:00 kernel: [ 1904.146692] ata1.00: error: { UNC } Oct 26 21:24:03 kernel: [ 1907.351844] res 51/40:00:90:74:c4/00:00:00:00:00/03 Emask 0x9 (media error) Oct 26 21:24:03 kernel: [ 1907.351853] ata1.00: error: { UNC } Oct 26 21:24:06 kernel: [ 1910.4821
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
Status Drdy Err Linux
Overflow the company Business Learn more about hiring developers or posting ads with us
Status Drdy Err Centos
Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and drdy err unc centos 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 up and rise to the top HDD Failure, http://askubuntu.com/questions/9606/how-to-interpret-these-errors-from-syslog SATA failure or both? up vote -1 down vote favorite After 3 years running a DELL T110 server with Linux Debian and ProxMox version 2.6.32 I started getting the following messages (Running dmesg shows tons of these messages): ata4.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x0 ata4.00: irq_stat 0x40000008 ata4.00: failed command: READ FPDMA QUEUED ata4.00: cmd 60/40:20:c0:39:29/00:00:cc:00:00/40 tag 4 ncq 32768 in res 41/40:40:c0:39:29/00:00:cc: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 http://serverfault.com/questions/407007/what-do-these-disk-errors-in-syslog-mean 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 or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it drdy err 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 8 down vote favorite 1 I just rebooted my monitoring server for the first time in a status drdy err 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 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