End_request Critical Target Error
Contents |
2009-06-15 Posts: 3,578 [SOLVED] badblocks ext4 Overview of issue.On boot when a filesystem is being fsck, errors appear:[ 21.638174] sd 2:0:0:0: [sdc] end_request critical medium error dev sdb sector Unhandled sense code [ 21.638180] sd 2:0:0:0: [sdc] Result: hostbyte=0x10 driverbyte=0x08 how to end a request letter [ 21.638186] sd 2:0:0:0: [sdc] Sense Key : 0x3 [current] [ 21.638192] sd 2:0:0:0: [sdc] ASC=0x11 how to end a request email ASCQ=0x0 [ 21.638197] sd 2:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 05 c0 00 67 00 00 40 00 [ 21.638210] end_request: critical target error, dev sdc, sector express end request 96469095 [ 21.638289] Buffer I/O error on device sdc1, logical block 96469032 [ 21.638351] Buffer I/O error on device sdc1, logical block 96469033 [ 21.638410] Buffer I/O error on device sdc1, logical block 96469034 [ 21.638468] Buffer I/O error on device sdc1, logical block 96469035 [ 21.638525] Buffer I/O error on device sdc1, logical block
How To End A Request For A Letter Of Recommendation
96469036 [ 21.638581] Buffer I/O error on device sdc1, logical block 96469037 [ 21.638639] Buffer I/O error on device sdc1, logical block 96469038 [ 21.638696] Buffer I/O error on device sdc1, logical block 96469039 [ 21.638762] Buffer I/O error on device sdc1, logical block 96469040 [ 21.638820] Buffer I/O error on device sdc1, logical block 96469041 [ 23.551857] sd 2:0:0:0: [sdc] Unhandled sense code [ 23.551863] sd 2:0:0:0: [sdc] Result: hostbyte=0x10 driverbyte=0x08 [ 23.551868] sd 2:0:0:0: [sdc] Sense Key : 0x3 [current] [ 23.551874] sd 2:0:0:0: [sdc] ASC=0x11 ASCQ=0x0 [ 23.551878] sd 2:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 05 c0 00 a7 00 00 80 00 [ 23.551890] end_request: critical target error, dev sdc, sector 96469159 [ 24.591795] sd 2:0:0:0: [sdc] Unhandled sense code [ 24.591801] sd 2:0:0:0: [sdc] Result: hostbyte=0x10 driverbyte=0x08 [ 24.591806] sd 2:0:0:0: [sdc] Sense Key : 0x3 [current] [ 24.591811] sd 2:0:0:0: [sdc] ASC=0x11 ASCQ=0x0 [ 24.591816] sd 2:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 05 c0 00
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
107.9 The End Request A Song
company Business Learn more about hiring developers or posting ads with us Server Fault node request on end Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join blk_update_request: critical target error, dev , sector 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 Identifying failed hard drive in RAID https://bbs.archlinux.org/viewtopic.php?id=129916 up vote 3 down vote favorite I have a server which is running customized version of Debian. It is attached a sun storage raid. It has very limited tools and installing new tools is not allowed. :( This message I see in dmesg: end_request: critical target error, dev sda, sector 556782970 sd 0:0:0:0: [sda] Unhandled sense code sd 0:0:0:0: [sda] Result: hostbyte=0x10 driverbyte=0x08 sd 0:0:0:0: [sda] Sense Key : 0x4 [current] sd 0:0:0:0: [sda] http://serverfault.com/questions/590860/identifying-failed-hard-drive-in-raid ASC=0x44 ASCQ=0x0 sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 21 2f d5 7a 00 00 08 00 end_request: critical target error, dev sda, sector 556782970 So it seems there is badblock in sector 556782970, but I don't know which hard drive it belongs to so that I can get it replaced. arcconf getlogs command does not reveal any issues with drives. I did arcconf task start 1 logicaldrive 0 verify_fix but this didn't help. I did an e2fsck check. It attempts to fix some inodes but above issue remained. (I assume since its physical issue). more info: http://pastebin.com/cJ2bUywj Tools not available :( smartctl badblocks raid storage hard-drive sun share|improve this question edited Apr 23 '14 at 18:31 jkt123 1134 asked Apr 23 '14 at 17:32 p0werf00l 183 add a comment| 3 Answers 3 active oldest votes up vote 1 down vote accepted If you actually use arcconf you can see physical drive status like this: arcconf getconfig 1 PD Look for drives with Failed state to identify drives that have been marked as failed. For your reference the output would look something like this: Device #6 Device is a Hard drive State : Failed Block Size : Unknown Supported : Yes Reported Channel,Device(T:L) : 0,15(15:0) Vendor : *MISSING* Model : Firmware : Total Size : 0 MB Write Ca
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 you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow http://askubuntu.com/questions/105030/what-is-happening-i-o-error-dev-sda-sector-545868115 the company Business Learn more about hiring developers or 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. 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 What is happening? I/O error, dev how to sda, sector 545868115 up vote 10 down vote favorite 2 Since a few days ago, my computer freezes whenever I sync my HDD with an external USB3 drive. When the keyboard gets temporarily a bit responsive I am able to switch to another terminal (Ctrl+Alt+F2) and I see the following image repeating continuously. I am on Ubuntu 11 using LuckyBackup. What is going on? Is my hdd defective? Is it the external one? Something else? how to end Many thanks! external-hdd sync share|improve this question edited Feb 20 '12 at 14:01 James♦ 31k43133224 asked Feb 17 '12 at 11:44 Pomario 79831223 I'd bet that your hard disk is failing. Use the Disk Utility to verity it's smart status. –Javier Rivera Feb 17 '12 at 11:53 3 @JavierRivera Can you include a answer with instructions on how to do that? Leaving a half-answer as a comment can often cause more harm than good. Thanks. :) –James♦ Feb 17 '12 at 12:49 add a comment| 2 Answers 2 active oldest votes up vote 9 down vote accepted You need to check and see if your disks are indeed failing. There are command line tools for monitoring SMART data (which is data that the hd reports about it's own health). sudo apt-get install smartmontools gsmartcontrol Gsmartcontrol is a gui version of the same tool, and is very easy to use. Select the disk and run a short or long test in addition to viewing any errors the hd is reporting. To run via the the command line, do the following sudo smartctl -i /dev/sda Make sure SMART is turned on. If not, sudo smartctl -s on /dev/sda Finally, run sudo smartctl -a /dev/sda or if it's a serial ata drive. sudo smartctl -a -d ata /dev/sda See this li