Add. Sense Unrecovered 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 Learn more about Stack Overflow hdparm read-sector the company Business Learn more about hiring developers or posting ads with us Unix
Unhandled Sense Code Medium Error
& Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for
Add. Sense: Internal Target Failure
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 Anybody can answer The best answers are voted up and
Add. Sense: Logical Unit Not Supported
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 kernel: [10893.039180] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 4 20:54:04 failed result 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:54:04 mediaserver kernel: [10893.180389] sd 3:0:1:0: [sdc] Nov 4 20:54:04 mediaserver kernel: [10893.180393] Add. Sense: Unrecovered read error - auto reallocate failed Nov 4 20:54:04 mediaserver kernel: [10893.180396] sd 3:0:1:0: [sdc
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 hostbyte=did_ok driverbyte=driver_sense planning on buying a new disk while your data is safe. However, sometimes sense key : illegal request [current] the disk won't automatically reallocate these sectors and you'll have to do that manually yourself. Luckily, this doesn't include any cdb read(10) 28 00 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, sector 1261069669 http://unix.stackexchange.com/questions/99553/does-a-bad-sector-indicate-a-failing-disk 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 : Medium http://www.sj-vs.net/forcing-a-hard-disk-to-reallocate-bad-sectors/ 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 dynamically relocate the damaged sectors. Tha
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 http://www.centos.org/forums/viewtopic.php?t=7577 Contact: Contact dtoch Website Strange problem with hdd Quote Postby dtoch » 2013/09/17 07:20:03 Hello!I have a strange problem with my server's hdd.One day 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 add. sense 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 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: add. sense unrecovered 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 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: 16688 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