Drdy Error Media Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings drdy error ubuntu boot and policies of this site About Us Learn more about Stack Overflow
Drdy Error Centos
the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges
Drdy Err
Unanswered Ask Question _ Super 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
Drdy Err Abrt
works: Anybody can ask a question Anybody 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 drdy err unc 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1:00: BMDMA stat 0x25 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
Unanswered Index »Help & Support (Crunchbang 11 "Waldorf") »[resolved] DRDY ERR and UNC errors at boot, fsck says HDD OK though... Pages: 1 #1 2014-03-15 15:45:57 photonucleon Quantum Geek From: Hogwarts Registered: 2013-06-10 Posts: 952 status drdy err [resolved] DRDY ERR and UNC errors at boot, fsck says HDD OK though... Hey,I ata1 00 status drdy err recently got given a second-hand Dell XPS M1330 (a great improvement on my other laptop in terms of specs!), and I first thought drdy serv err I'd take advantage of the relatively high specs of the laptop to install Ubuntu GNOME, and use the GNOME 3 DE It worked fine, but I missed Openbox. Some time later, I installed Waldorf, wiping the entire http://superuser.com/questions/796423/drdy-err-from-hdd HDD with the 'Guided - Use Entire Disk' option in the installer. Upon reboot, several errors appeared (shown here from dmesg):[ 7.163074] ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 [ 7.163132] ata3.00: irq_stat 0x40000008 [ 7.163184] ata3.00: failed command: READ FPDMA QUEUED [ 7.163241] ata3.00: cmd 60/20:00:00:2a:44/00:00:1c:00:00/40 tag 0 ncq 16384 in [ 7.163242] res 41/40:00:09:2a:44/00:00:1c:00:00/40 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 http://serverfault.com/questions/152855/sata-hdd-errors 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 only takes a minute: Sign up Here's how it works: Anybody can ask drdy err 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 error. The last one: status drdy err 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, logical block 14077751 lost page write due to I/O error