Kernel Add. Sense Unrecovered Read Error - Auto Reallocate Failed
Contents |
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 hdparm read-sector developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _
Unhandled Sense Code Medium Error
Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how result: hostbyte=did_ok driverbyte=driver_sense it works: Anybody can 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 failed result 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 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
Add. Sense: Internal Target Failure
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 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 wro
and only cause some noise in your syslog. In most cases the disk will automatically reallocate one or two damaged sectors add. sense: logical unit not supported and you should start planning on buying a new disk while your data unrecovered read error linux is safe. However, sometimes the disk won't automatically reallocate these sectors and you'll have to do that manually
Cdb Read(10) 28 00
yourself. Luckily, this doesn't include 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: http://serverfault.com/questions/407007/what-do-these-disk-errors-in-syslog-mean [66774.973049] end_request: I/O error, dev sdb, 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 http://www.sj-vs.net/forcing-a-hard-disk-to-reallocate-bad-sectors/ 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 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. T
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 https://ubuntuforums.org/showthread.php?t=1720375 Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity http://andrew.daviel.org/linux-sata-recovery.html Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [SOLVED] Random freeze and "Unrecovered read error" in /var/log/messages Having an Issue add. sense With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 4 of 4 Thread: Random freeze and "Unrecovered read error" in /var/log/messages Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode April 3rd, 2011 #1 Naggobot unrecovered read error View Profile View Forum Posts Private Message Gee! These Aren't Roasted! Join Date Mar 2010 Beans 178 DistroUbuntu 12.04 Precise Pangolin Random freeze and "Unrecovered read error" in /var/log/messages System is Acer 5020 laptop with 32 bit Ubuntu 10.04 Lucid. I have following "smallish" problem. System freezes suddenly for a few seconds and after the freeze if I run following command to prompt Code: tail -n 100 /var/log/messages I can find a following possibly related error Code: .... Apr 3 08:18:09 acer5020-laptop kernel: [ 1383.202090] ata1.00: configured for UDMA/100 Apr 3 08:18:09 acer5020-laptop kernel: [ 1383.202113] ata1: EH complete Apr 3 08:18:13 acer5020-laptop kernel: [ 1387.568764] ata1.00: configured for UDMA/100 Apr 3 08:18:13 acer5020-laptop kernel: [ 1387.568786] ata1: EH complete Apr 3 08:18:17 acer5020-laptop kernel: [ 1391.888898] ata1.00: configured for UDMA/100 Apr 3 08:18:17 acer5020-laptop kernel: [ 1391.888919] ata1: EH complete Apr 3 08:18:22 acer5020-laptop kernel: [ 1396.232745] ata1.00: configured for UDMA/100 Apr 3 08:18:22 acer5020-laptop kernel: [ 1396.232768] ata1: EH complete Apr 3 08:18:26 acer5020-laptop kernel: [ 1400.620733] ata1.00: configured for UDMA/100 Apr 3 08:18:31 acer5020-laptop kernel: [ 1400.620755] ata1: EH complete Apr 3 08
I recall, the IDE drive with Reiser 3 filesystem failed gradually - I would get I/O errors on odd files, run fsck, clean up a bunch of errors, and repeat until it became obvious there was a hardware issue at which point I copied everything to ext3 on the new drive, keeping the old one online for some months until it started impacting the running system. If a file had no I/O errors and had passed fsck, it worked normally. Recently I started having problems with the new drive. I didn't read the logs properly at first, and thought the odd sda entries I'd seen in passing were something to do with inserting/unplugging a memory stick. I didn't initially get i/o errors, but I noticed that sometimes reading a "man" page that it was slow - the first page would appear quickly, but the colon at the bottom of the page indicating the page was fully parsed would take a while to appear. Finally, while unpacking a big zip file with a few thousand entries, I got solid errors trying to create directories. When I rebooted the machine to try to clear the errors, it was very slow to come up. Looking at the logs, it seemed that the SATA driver was getting errors and then re-initializing the drive each time, which took a while. The log had entries like: kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 kernel: ata3.00: irq_stat 0x40000000 kernel: ata3.00: cmd c8/00:08:99:90:aa/00:00:00:00:00/e7 tag 0 dma 4096 in kernel: res 51/40:00:99:90:aa/00:00:07:00:00/07 Emask 0x9 (media error) kernel: ata3.00: status: { DRDY ERR } kernel: ata3.00: error: { UNC } kernel: ata3.00: configured for UDMA/133 kernel: ata3: EH complete kernel: ata3.00: configured for UDMA/133 kernel: sd 2:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK kernel: sd 2:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor] kernel: Descriptor sense data with sense descriptors (in hex): kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 kernel: sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed kernel: end_request: I/O error, dev sda, sector 128618649 kernel: sd 2:0:0:0: