Error Auto Reallocate Failed
Contents |
and only cause some noise in your syslog. In most cases the disk will automatically reallocate one or two damaged sectors and you should start planning on buying
Hdparm Read-sector
a new disk while your data is safe. However, sometimes the disk won't unhandled sense code medium error automatically reallocate these sectors and you'll have to do that manually yourself. Luckily, this doesn't include any rocket science. A few
Failed Result
days ago, one of my disks reported some problems in my syslog while rebuilding a RAID5-array: Jan 29 18:19:54 dragon kernel: [66774.973049] end_request: I/O error, dev sdb, sector 1261069669 Jan 29 18:19:54 dragon add. sense: internal target failure kernel: [66774.973054] raid5:md3: read error not correctable (sector 405431640 on sdb6). Jan 29 18:19:54 dragon kernel: [66774.973059] raid5: Disk failure on sdb6, disabling device. Jan 29 18:20:11 dragon kernel: [66792.180513] sd 3:0:0:0: [sdb] Unhandled sense code Jan 29 18:20:11 dragon kernel: [66792.180516] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Jan 29 18:20:11 dragon kernel: [66792.180521] sd 3:0:0:0: [sdb] Sense Key : Medium Error [current] [descriptor] Jan 29 18:20:11 dragon hostbyte=did_ok driverbyte=driver_sense kernel: [66792.180547] sd 3:0:0:0: [sdb] Add. Sense: Unrecovered read error - auto reallocate failed Jan 29 18:20:11 dragon kernel: [66792.180553] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 4b 2a 6c 4c 00 00 c0 00 Jan 29 18:20:11 dragon kernel: [66792.180564] end_request: I/O error, dev sdb, sector 1261071601 Modern hard disk drives are equipped with a small amount of spare sectors to reallocate damaged sectors. However, a sector only gets relocated when a write operation fails. A failing read operation will, in most cases, only throw an I/O error. In the unlikely event a second read does succeed, some disks perform a auto-reallocation and data is preserved. In my case, the second read failed miserably ("Unrecovered read error - auto reallocate failed"). The read errors were caused by a sync of a new RAID5 array, which was initially running in degraded mode (on /dev/sdb and /dev/sdc, with /dev/sdd missing). Obviously, mdadm kicked sdb out of the already degraded RAID5-array, leaving nothing but sdc. That's not something to be very happy about… The only solution to this problem, was to force sdb to dynamically relocate the damaged sectors. That way, mdadm wouldn't encounter the read errors and the initial sync of the
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
Add. Sense: Logical Unit Not Supported
ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is sense key : illegal request [current] 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
Cdb Read(10) 28 00
ask a question Anybody can answer The best answers are voted up 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 http://www.sj-vs.net/forcing-a-hard-disk-to-reallocate-bad-sectors/ 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 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: http://serverfault.com/questions/407007/what-do-these-disk-errors-in-syslog-mean [ 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 23:52:30 monit kernel: [ 25.552559] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 35 68 20 00 00 c0 00 Jul 11 23:52:30 monit kernel: [ 25.552587] end_request: I/O error, dev sda, sector 3500097 Jul 11 23:52:30 monit kernel: [ 25.556607] ata1: EH complete I already know I need to replace the HDD (Cost of Data > Cost of HDD), but I want to know for my own knowledge what's actually wrong with it. Yes, our monitoring server has no RAID, just one HDD... Don't look at me... hard-drive ubuntu-
Help » General » SOLVED - After trying to fix something which wasn't broken...... « previous next » Print Pages: [1] 2 Go Down Author Topic: SOLVED - After trying to fix http://www.pclinuxos.com/forum/index.php?topic=107138.0 something which wasn't broken...... (Read 5115 times) maurice Hero Member Posts: 1868 SOLVED - After trying to fix something which wasn't broken...... « on: July 11, 2012, 06:19:37 AM » My machine was runnjng a http://forums.fedoraforum.org/showthread.php?t=222327 bit slowly on memory intensive stuff like Google Earth so I opened it up and reset the memory cards and checked a few other connections. When I put it back together I found I couldn't add. sense: get into my Pclos (updated). I could get into XP and Solusos but not Pclos.I entered dmesg |tail from Solusos and got the following -felix maurice # dmesg | tail[ 238.598673] Descriptor sense data with sense descriptors (in hex):[ 238.598676] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 238.598689] 25 18 b0 00 [ error auto reallocate 238.598694] sd 3:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed[ 238.598701] sd 3:0:0:0: [sda] CDB: Read(10): 28 00 25 18 af 30 00 00 f0 00[ 238.598718] end_request: I/O error, dev sda, sector 622374912[ 238.598729] JBD2: Failed to read block at offset 769[ 238.598737] ata4: EH complete[ 238.598748] JBD2: recovery failed[ 238.598752] EXT4-fs (sda3): error loading journalHave I fried it? Can someone kindly make sense of this to me please?Thank youMaurice « Last Edit: July 11, 2012, 07:24:05 AM by Maurice » Logged Minime64kde (3 copies), PcLinuxos64kde, on two separate hard drives on custom built Desktop-- Intel 4 core Haswell cpu 3.40. Asrock H831M-DGS mb. UEFI.Hitachi sata 250gb. WDC sata 70gb. 8gb ram. Lenovo 22" flat screen monitor bicol_willem Guest Re: After trying to fix something which wasn't broken...... « Reply #1 on: July 11, 2012, 06:38:33 AM » I would first fire up my PMagic LiveCD and do a file system check. Then try again.A remaster with Gparted on it could be used as well of course. « Last Edit: July 11, 2012, 06:40:07 AM by bicol_willem » Logged menotu PCLinuxOS Tester Super Villain Posts: 16095 "It Is What It Is" (Allan Karlsson) Re: After trying to fix something which wasn't broken...... « Reply #2 on:
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)