Ata1.00 Status Drdy Err Error Unc
Contents |
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code
Drdy Err Unc
of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu what is drdy IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu
Status Drdy Err Linux
PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours status drdy err centos Support General Help [SOLVED] ata1.01: status: {DRDY ERR} Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 12 Thread: ata1.01: status: {DRDY ERR} Thread drdy error ubuntu boot Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode August 28th, 2009 #1 rootless View Profile View Forum Posts Private Message Just Give Me the Beans! Join Date Jul 2008 Location New York City Beans 67 DistroUbuntu 12.04 Precise Pangolin ata1.01: status: {DRDY ERR} Hey, Ubuntu works fine until I startx, at which point, my desktop launches, but my system monitor reads 100% processor usage. If I click on anything, the system becomes unresponsive. When I start gnome, if I go back down to the cli, I can see the following errors being thrown. Code: [various changing numbers] ata1.01: status: {DRDY ERR} [various changing numbers] ata1.01 ERROR: {unc} [various changing numbers] ata1.01 exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [various changing numbers] ata1.01 cmd c8/00:08:5f:99:e5/00:00:00:00:00/f0 tag 0 dma 4069 in Can anyone help me with this? Any advice at all would be good, even if it's not a solution. Adv Reply
#1 2012-08-23 14:42:19 68flag Member Registered: 2012-08-23 Posts: 4 DRDY ERR I/O Errors only occur with KDE. HDD or kernel related? This isn't too urgent
Drdy Err Abrt
since I'm not having this problem anymore, but I would like to ata1.00 failed command read dma know what caused it in the first place.A few months ago, I think it was in May, when
Options Libata Noacpi=1
I was booting into KDE, the desktop wouldnt load. After logging in it goes to a black screen with a cursor. I check my tty consoles and they are all https://ubuntuforums.org/showthread.php?t=1252285 spammed with DRDY and I/O errors.Today my log files don't go back to that time, but I apparantly wrote them down:[timestamp] ata1.00: irq_stat 0x40000001[timestamp] ata1: SError: { CommWake }[timestamp] ata1.00: failed command: READ FPDMA QUEUED[timestamp] ata1.00: cmd 60/08:00:79:c5:e9/00:00:38:00:00/40 tag 0 ncq 4096 in[timestamp] res 41/40:08:7c:c5:e9/00:00:38:00:00/60 Emast 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 http://serverfault.com/questions/152855/sata-hdd-errors and policies of this site About Us Learn more about Stack Overflow http://askubuntu.com/questions/321277/how-do-i-recover-from-a-read-dma-bootup-error 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 only takes a minute: Sign up Here's how it works: drdy err 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 hosts. Server is working about 5 years and in this time period I have change 4 disks. All with same reason: sata status drdy err 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 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, l
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 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 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 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 do I recover from a read DMA bootup error? up vote 4 down vote favorite 3 I am running 12.04 LTS, and almost every time I shut down my system, my root fails to mount on the next bootup, usually after an update. In this particular case, I can see my filesystem when running on live CD, but every time I boot, I see the following sequence of messages cycle in an endless loop (process IDs removed): ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: BMDMA stat 0x24 ata1.00: failed command: READ DMA ata1.00: cmd c8/00:08:b0:f7:46/00:00:00:00:00/e0 res 51/40:08:b0:f7:46/40:02:02:00:00/e0 Emask 0x9 (media error) ata1.00: status:{DRDY ERR} ata1.00:error:{UNC} end_request: I/O error, dev sda, sector 4650928 I boot off of a relatively new 60GB solid state disk drive, and in the past when I have run into this issue, I use fsck to detect and fix errors. But fsck runs clean on my partition, so i am uncertain how to approach the problem. 12.04 boot share|improve this question asked Jul 17 '13 at 20:46 txmystic 113239 possible duplicate of how to interpret these errors from syslog –Eliah Kagan Sep 9 '14 at 21:55 add a comment| 3 Answers 3 active oldest votes up vote 3 down vote accepted There was an Input Output error at your Hard Disk sda part, at sector 4650928. You can boot from Ubuntu Live cd/dvd/usb, start Disks Utility, try to see the SMART data and test your sda disk. Possible duplicate share|improve this answer answered Jul 17 '13 at 22:20 ubuntu_tr 64536 Disk utility claims the disk is healthy, although i am suspicious. The extended self-assessment (which should take "10s of minutes") finished in less than two with no errors. An attempted read-only benchmark failed on the firs