Read Error Auto Reallocate Failed
Contents |
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 hdparm read-sector Learn more about Stack Overflow the company Business Learn more about hiring developers unrecovered read error auto reallocate failed ubuntu or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange unhandled sense code medium error is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question
Tag#0 Failed Result: Hostbyte=did_ok Driverbyte=driver_sense
Anybody can answer The best answers are voted up and rise to the top Does a bad sector indicate a failing disk? up vote 7 down vote favorite 5 My Ubuntu 13.10 system has been performing very poorly over the last day or so. Looking at the kernel logs, it appears that the <1yr old 3TB SATA disk is having issues with a particular sector: Nov 4 20:54:04 mediaserver add. sense: internal target failure kernel: [10893.039180] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 4 20:54:04 mediaserver kernel: [10893.039187] ata4.01: BMDMA stat 0x65 Nov 4 20:54:04 mediaserver kernel: [10893.039193] ata4.01: failed command: READ DMA EXT Nov 4 20:54:04 mediaserver kernel: [10893.039202] ata4.01: cmd 25/00:08:f8:3f:83/00:00:af:00:00/f0 tag 0 dma 4096 in Nov 4 20:54:04 mediaserver kernel: [10893.039202] res 51/40:00:f8:3f:83/40:00:af:00:00/10 Emask 0x9 (media error) Nov 4 20:54:04 mediaserver kernel: [10893.039207] ata4.01: status: { DRDY ERR } Nov 4 20:54:04 mediaserver kernel: [10893.039211] ata4.01: error: { UNC } Nov 4 20:54:04 mediaserver kernel: [10893.148527] ata4.00: configured for UDMA/133 Nov 4 20:54:04 mediaserver kernel: [10893.180322] ata4.01: configured for UDMA/133 Nov 4 20:54:04 mediaserver kernel: [10893.180345] sd 3:0:1:0: [sdc] Unhandled sense code Nov 4 20:54:04 mediaserver kernel: [10893.180349] sd 3:0:1:0: [sdc] Nov 4 20:54:04 mediaserver kernel: [10893.180353] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Nov 4 20:54:04 mediaserver kernel: [10893.180356] sd 3:0:1:0: [sdc] Nov 4 20:54:04 mediaserver kernel: [10893.180359] Sense Key : Medium Error [current] [descriptor] Nov 4 20:54:04 mediaserver kernel: [10893.180371] Descriptor sense data with sense descriptors (in hex): Nov 4 20:54:04 mediaserver kernel: [10893.180373] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 4 20:54:04 mediaserver kernel: [10893.180384] af 83 3f f8 Nov 4 20:
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 sense key : hardware error [current] Learn more about Stack Overflow the company Business Learn more about hiring developers or
Add. Sense: Logical Unit Not Supported
posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and
Cdb Read(10) 28 00
answer site for system and network administrators. 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 http://unix.stackexchange.com/questions/99553/does-a-bad-sector-indicate-a-failing-disk 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 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 http://serverfault.com/questions/407007/what-do-these-disk-errors-in-syslog-mean 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 Error [current] [descriptor] Jul 11 23:52:30 monit kernel: [ 25.552490] Descriptor sense data with sense descriptors (in hex): Jul 11 23:52:30 monit kernel: [ 25.552498] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Jul 11 23:52:30 monit kernel: [ 25.552529] 00 35 68 41 Jul 11 23:52:30 monit kernel: [ 25.552543] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed Jul 11
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 http://www.centos.org/forums/viewtopic.php?t=7577 dtoch » 2013/09/17 07:20:03 Hello!I have a strange problem with my server's hdd.One day http://forums.fedoraforum.org/showthread.php?t=222327 I found following in dmesg:sd 0:0:0:0: [sda] Unhandled sense 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 read error - auto reallocate failedsd 0:0:0:0: [sda] CDB: Read(10): 28 00 55 a5 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 read error auto dead HDD. HDD was replaced and two or three days everything goes fine. But then this messages was found again...Well, in a 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: 16948 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 s
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Hardware & Laptops HDD errors - unrecovered read error - auto reallocate failed FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Hardware & Laptops Help with your hardware, including laptop issues Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 24th May 2009, 03:56 PM kajencik Offline Registered User Join Date: Dec 2008 Age: 31 Posts: 3 HDD errors - unrecovered read error - auto reallocate failed I'm running Fedora 10 and keep getting this error: Code: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata4.00: irq_stat 0x40000008 ata4.00: cmd 60/08:00:81:12:9c/00:00:2e:00:00/40 tag 0 ncq 4096 in res 41/40:00:84:12:9c/76:00:2e:00:00/40 Emask 0x409 (media error)