Error Auto Reallocation Failed

and only cause some noise in your syslog. In most cases the disk hdparm read-sector will automatically reallocate one or two damaged sectors and you should unhandled sense code medium error start planning on buying a new disk while your data is safe. However, sometimes the disk

Failed Result

won't automatically reallocate these sectors and you'll have to do that manually yourself. Luckily, this doesn't include any rocket science. A few days ago, one of

Add. Sense: Internal Target Failure

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 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 hostbyte=did_ok driverbyte=driver_sense 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 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 miserab

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

Add. Sense: Logical Unit Not Supported

of this site About Us Learn more about Stack Overflow the company Business sense key : illegal request [current] Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question cdb read(10) 28 00 _ 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 it works: Anybody can ask a http://www.sj-vs.net/forcing-a-hard-disk-to-reallocate-bad-sectors/ 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 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 http://serverfault.com/questions/407007/what-do-these-disk-errors-in-syslog-mean 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: [ 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

communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions http://askubuntu.com/questions/9606/how-to-interpret-these-errors-from-syslog 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 http://www.pclinuxos.com/forum/index.php?topic=107138.0 posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. add. sense: 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 rise to the top how to interpret these errors from syslog up vote 11 down vote favorite 1 My Ubuntu has been acting weird lately. Yesterday, it wouldn't error auto reallocation boot normally, so I had to do a 'recovery mode' boot. It said I had to do an fsck manually, which I did using a live CD. After this, I was already able to boot to the desktop but everything is so sluggish. Apps would turn gray for seconds. Sometimes other apps wont start at all. In other instances it it saying that the filesystem is in read-only mode. This is part of what I've been getting: Oct 26 21:23:56 kernel: [ 1900.960506] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed Oct 26 21:23:56 kernel: [ 1900.960533] end_request: I/O error, dev sda, sector 63206544 Oct 26 21:23:56 kernel: [ 1900.960541] Buffer I/O error on device sda1, logical block 7900562 Oct 26 21:24:00 kernel: [ 1904.146683] res 51/40:00:90:74:c4/00:00:00:00:00/03 Emask 0x9 (media error) Oct 26 21:24:00 kernel: [ 1904.146692] ata1.00: error: { UNC } Oct 26 21:24:03 kernel: [ 1907.351844] res 51/40:00:90:74:c4/00:00:00:00:00/03 Emask 0x9 (media error) Oct 26 21:24:03 kernel: [ 1907.3518

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 something which wasn't broken...... (Read 5117 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 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 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 [ 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: July 11, 2012, 06:43:55 AM » Are both OS's on the same drive? If PCLinuxOS is on it's own drive maybe you've accidentally nudged a cable.Have you checke