Linux Add. Sense Unrecovered Read Error - Auto Reallocate Failed

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

Hdparm Read-sector

planning on buying a new disk while your data is safe. However, unhandled sense code medium error sometimes the disk won't automatically reallocate these sectors and you'll have to do that manually yourself. Luckily, this doesn't include unrecovered read error auto reallocate failed ubuntu any rocket science. A few 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,

Failed Result

sector 1261069669 Jan 29 18:19:54 dragon 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

Add. Sense: Internal Target Failure

: Medium Error [current] [descriptor] Jan 29 18:20:11 dragon 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 dy

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 add. sense: logical unit not supported » 2013/09/17 07:20:03 Hello!I have a strange problem with my server's hdd.One day I found

Cdb Read(10) 28 00

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] tag#0 failed result: hostbyte=did_ok driverbyte=driver_sense [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 http://www.sj-vs.net/forcing-a-hard-disk-to-reallocate-bad-sectors/ - 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 dead HDD. HDD http://www.centos.org/forums/viewtopic.php?t=7577 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: 16877 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 an

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 http://forums.fedoraforum.org/showthread.php?t=222327 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 add. sense 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) ata4.00: status: { DRDY ERR } ata4.00: error: { UNC } ata4.00: configured for UDMA/133 sd 3:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK sd 3:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor] unrecovered read error Descriptor sense data with sense descriptors (in hex): 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 2e 9c 12 84 sd 3:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed end_request: I/O error, dev sda, sector 781980292 ata4: EH complete sd 3:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) sd 3:0:0:0: [sda] Write Protect is off sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO It show only one sector again and again, and also on the second HDD there is a very similar problem that one sector cannot be read, I'm not sure how serious this is, the HDD's were bought at the same time, they are same brand and type. According to smart diagnostics. One drive has 1 pending sector and no offline uncorectable or realocated, the other one has 12 pending and 11 offline uncorrectable They are both WDC WD5000AAKS-00A7B0 - 500GB capacity. Do you think this means I have to replace them (fortunatelly they are still under warrany)? It would be really a pain in the neck, because i really don't have spare 1TB drive to backup my data IMHO the problem would be solved by reallocating the sectors manually somehow...? I think I did that in the past, but I'm not sure how... I've searched the internet a lot but