Ata1.00 Emask 0x9 Media Error
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 have Meta Discuss the sense key : medium error [current] workings and policies of this site About Us Learn more about Stack
Add. Sense: Unrecovered Read Error
Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users unhandled sense code medium error 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 result: hostbyte=did_ok driverbyte=driver_sense 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 to do a 'recovery mode' boot. It said I had to do an
Cdb Read(10) 28 00
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.482152] res 51/40:00:90:74:c4/00:00:00:00:00/03 Emask 0x9 (media error) Oct 26 21:24:06 kernel: [ 1910.482161] ata1.00: error: { UNC } Oct 26 21:24:09 kernel: [ 1913.604742] res 51/40:0
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 emask 0x409 (media error) Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter add. sense: internal target failure Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please
Add. Sense: Logical Unit Not Supported
read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Hardware [ubuntu] Failed hard drive or kernel bug? Emask 0x9 (media error) Having an Issue With Posting http://askubuntu.com/questions/9606/how-to-interpret-these-errors-from-syslog ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 2 of 2 Thread: Failed hard drive or kernel bug? Emask 0x9 (media error) Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode April 8th, 2009 #1 Endolith View https://ubuntuforums.org/showthread.php?t=1119741 Profile View Forum Posts Private Message Grande Half-n-Half Cinnamon Ubuntu Join Date Feb 2007 Location New York Beans 894 DistroUbuntu 9.10 Karmic Koala Failed hard drive or kernel bug? Emask 0x9 (media error) I bought a new Seagate hard drive two months ago, and I'm getting errors on it that screw up Ubuntu. I ran GNU ddrescue on it, and it only found 1 error (1024 bytes). I'm confused as to what that means. If this is just a bad block, wouldn't the hard drive automatically mark it "bad" and carry on? What else would cause a single kilobyte of error on a 160 GB drive? Code: % ddrescue --direct -r 7 -v /dev/sda sdaimage sdalog About to copy 160041 MBytes from /dev/sda to sdaimage Starting positions: infile = 0 B, outfile = 0 B Copy block size: 128 hard blocks Hard block size: 512 bytes Max_retries: 7 Direct: yes Sparse: no Split: yes Truncate: no Press Ctrl-C to interrupt Initial status (read from logfile) rescued: 160041 MB, errsize: 1024 B, errors: 1 Current status rescued: 160041 MB, errsize: 1024 B, current rate: 0 B/s ipos: 102334 MB, errors: 1, ave
hdd Issues related to hardware problems Post Reply Print view Search Advanced search 11 posts 1 2 Next dtoch Posts: 4 Joined: 2013/09/17 06:28:28 Contact: Contact dtoch Website Strange problem with hdd Quote Postby dtoch » 2013/09/17 07:20:03 Hello!I have a strange http://www.centos.org/forums/viewtopic.php?t=7577 problem with my server's hdd.One day I found following in dmesg:sd 0:0:0:0: [sda] Unhandled sense http://forums.fedoraforum.org/archive/index.php/t-169098.html codesd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSEsd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]Descriptor sense data with sense descriptors (in hex): 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 55 a5 da e8 sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failedsd 0:0:0:0: [sda] CDB: Read(10): 28 00 55 a5 add. sense: da d8 00 00 40 00ata1: EH completeata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0ata1.00: irq_stat 0x40000008ata1.00: failed command: READ FPDMA QUEUEData1.00: cmd 60/08:00:e8:da:a5/00:00:55:00:00/40 tag 0 ncq 4096 in res 41/40:08:e8:da:a5/00:00:55:00:00/00 Emask 0x409 (media error) ata1.00: status: { DRDY ERR }ata1.00: error: { UNC }ata1.00: configured for UDMA/133ata1: EH completeMy first guess was about dead HDD. HDD was replaced and two or three days everything goes fine. But then this messages was found again...Well, in a ata1.00 emask 0x9 few days I step-by-step changed both HDDs and motherboard. But problem is still here.About my hardware: its a two 2Gb Seagate (ST2000DM001-9YN164) in software RAID1 connetcted to Intel DH77EB motherboard.Have no idea what the h... with this server. May by some suggestions from community? May be some kernel issues? Top TrevorH Forum Moderator Posts: 16693 Joined: 2009/09/24 10:40:56 Location: Brighton, UK Strange problem with hdd Quote Postby TrevorH » 2013/09/17 08:36:45 sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failedMeans it found a sector that was bad and went to try to get a different one from its pool of spares and found that the pool was all used up. That shows that the drive is dying and has already used up its entire spare area. Best RMA it. Top dtoch Posts: 4 Joined: 2013/09/17 06:28:28 Contact: Contact dtoch Website Re: Strange problem with hdd Quote Postby dtoch » 2013/09/17 09:57:12 TrevorH wrote:Means it found a sector that was bad and went to try to get a different one from its pool of spares and found that the pool was all used up. That shows that the drive is dying and has already used up its entire spare area. Best RMA it.Well, yes it will the best. But hdd is new - about 420 power on hours. And as I wrote, it was changed two weeks ago. I
acpi and apic. The startup script has acpi=off and noapic in it. Recently when I was downloading a file the computer switched to screen saver and I got an error message saying input/output error. Now every time I try to copy the file or read the file I get the error posted below. How do I make sure that the hard disk has a problem and not something that can be fixed. If there are any bad sectors etc. I tried fsck but doing it on a logical volume is quite a problem. Any suggestions would be greatly appreciated. Thanks in advance, Thomas. Error Log: Oct 14 17:22:27 localhost kernel: sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB) Oct 14 17:22:27 localhost kernel: sd 0:0:0:0: [sda] Write Protect is off Oct 14 17:22:27 localhost kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 14 17:22:27 localhost kernel: sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB) Oct 14 17:22:27 localhost kernel: sd 0:0:0:0: [sda] Write Protect is off Oct 14 17:22:27 localhost kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 14 17:22:27 localhost kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Oct 14 17:22:27 localhost kernel: ata1.00: (BMDMA2 stat 0x686d0009) Oct 14 17:22:27 localhost kernel: ata1.00: cmd c8/00:08:69:41:b8/00:00:00:00:00/e7 tag 0 cdb 0x0 data 4096 in Oct 14 17:22:27 localhost kernel: res 51/40:03:6e:41:b8/00:00:00:00:00/e7 Emask 0x9 (media error) Oct 14 17:22:27 localhost kernel: ata1.00: configured for UDMA/100 Oct 14 17:22:27 localhost kernel: ata1: EH complete Oct 14 17:22:27 localhost kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Oct 14 17:22:27 localhost kernel: ata1.00: (BMDMA2 stat 0x686d0009) Oct 14 17:22:27 localhost kernel: ata1.00: cmd c8/00:08:69:41:b