Home > status drdy > linux ata1 error

Linux Ata1 Error

Contents

1 #1 2013-05-18 23:14:08 gay Member Registered: 2012-12-16 Posts: 73 Harddisk problem: ata1.00: end_request: I/O error, dev sda, sector ... I got errors like the end_request: i/o error, dev sda, sector following:ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata1.00: ata3.00 status drdy err irq_stat 0x40000008 ata1.00: failed command: READ FPDMA QUEUED ata1.00: cmd 60/08:00:68:33:32/00:00:31:00:00/40 tag 0 ncq 4096 in res status drdy err linux 41/40:00:68:33:32/00:00:31:00:00/40 Emask 0x409 (media error) ata1.00: status: { DRDY ERR } ata1.00: error: { UNC } ata1.00: end_request: I/O error, dev sda, sector 825373544Also: my filesystem was drdy error ubuntu boot inconsitent; i.e. reading specific ordinary files (for instance ~/.config/dconf/user) resulted in an I/O error. So I ran xfs_repair from a livesystem ... it seemed to work; xfs_check checked out without errors. After rebooting into the installed system, however, I keep getting error messages like the one shown above. The cmd and res lines as well as

Ata1.00 Status Drdy

sectors are different. Running xfs_repair (with and without -n; without, it doesnt actually do anything except for resetting the superclock, that's what it says) from the livesystem a large number of times always produces the above error giving the sector as 472904080.I cannot run xfs_check and/or xfs_repair from the installed system because it won't unmount /.Also I cannot find any problems with how the harddisk is connected etc. (it is screwed into the laptop; I checked that it is not loose or something).The problem seems similar to this one https://bbs.archlinux.org/viewtopic.php?id=135872 ... which was a hardware problem.As I understand the error message it says it couldn't read sector 825373544 (and several others) on the harddisk (sda). Is that right? If so, what does this mean? ... or what could it possibly mean? (That that disk is broken and I have to get the vendor to give me a new one? That some other hardware could be broken? Or could it still be a software problem ... if so

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

Ata1.00 Failed Command Read Dma

site About Us Learn more about Stack Overflow the company Business Learn what is drdy more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super status drdy err centos User is a question and 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 https://bbs.archlinux.org/viewtopic.php?id=163597 can answer The best answers are voted 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 http://superuser.com/questions/796423/drdy-err-from-hdd ata1:00: failed command: READ DMA finally it drops me into 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 e

Help Here Install/Boot/Login [SOLVED] ata1: SRST failed (errno=-16), boot extremely slow, BIOS disappears Welcome! If this is your first visit, be sure to check out the FAQ. https://forums.opensuse.org/showthread.php/454214-SOLVED-ata1-SRST-failed-(errno-16)-boot-extremely-slow-BIOS-disappears 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 7 of 7 Thread: [SOLVED] status drdy ata1: SRST failed (errno=-16), boot extremely slow, BIOS disappears Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 15-Feb-2011,22:46 #1 NonZ View Profile View Forum Posts View Blog Entries View Articles Student Penguin Join Date Feb 2011 Location U.S., Canada Posts 50 [SOLVED] ata1: SRST failed (errno=-16), boot extremely slow, BIOS status drdy err disappears I didn't ask for assistance with this problem, but I want to post it anyway, for the benefit of others who encounter the same problem. In fact, I'm wondering whether we should advise forum members, as a general rule, to post problem solutions. A few days ago, I replaced both the harddrive and the monitor in my 11-year-old AMD desktop. I then installed OpenSuSE 11.2 with Gnome 2.28.2 on the new harddrive. The installation went spectacularly well, and the images on my new monitor are glorious. There was only one problem: Booting was extremely slow. Simply for BIOS to detect the presence of my harddrive would take over a minute. Grub would take another half minute to load, then issue several "ata1: SRST failed" complaints. I applied google to the message and found other people having extremely slow boots, but no one finding solutions. Some people blamed the video card, some blamed memory overload, and some blamed Western Digital. I opened the box, looked at the new harddrive, and recalled my installation. The drive was one I had used briefly se

 

Related content

ata2.00 status drdy drq error

Ata Status Drdy Drq Error table id toc tbody tr td div id toctitle Contents div ul li a href What Is Drdy a li li a href Status Drdy Err Centos a li li a href Status Drdy Err Linux a li li a href Status Drdy Err Error Abrt a li ul td tr tbody table p 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 relatedl more about Stack Overflow the company Business Learn more