Error On Device Sdc1
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 buffer i o error on device sdc1 logical block Learn more about Stack Overflow the company Business Learn more about hiring developers
Buffer I/o Error On Device Sda1
or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and
Buffer I/o Error On Device Sdb1
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 question Anybody can answer The best answers are voted up
Buffer I/o Error On Device Sdc
and rise to the top Buffer I/O error on device (sata drive) up vote 2 down vote favorite 2 I keep getting these messages in one of my servers kernel logs (which is responsible for file operations). I wonder if anybody knows how serious are these issues. I cannot use smartmontools because the disks are handled by a 3ware card which has it's own (very limited tw_cli utility). buffer i/o error on device sdb logical block 0 [2522065.275739] sd 0:0:1:0: [sdg] CDB: [2522065.275741] Read(10): 28 00 2e 90 97 f8 00 00 08 00 [2522065.275750] end_request: I/O error, dev sdg, sector 781228024 [2522065.281091] Buffer I/O error on device sdg, logical block 97653503 [2522065.287157] sd 0:0:1:0: [sdg] Device not ready [2522065.287163] sd 0:0:1:0: [sdg] [2522065.287166] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [2522065.287168] sd 0:0:1:0: [sdg] [2522065.287170] Sense Key : Not Ready [current] [2522065.287174] sd 0:0:1:0: [sdg] [2522065.287176] Add. Sense: Logical unit not ready, cause not reportable [2522065.287179] sd 0:0:1:0: [sdg] CDB: [2522065.287181] Read(10): 28 00 00 00 00 00 00 00 20 00 [2522065.287190] end_request: I/O error, dev sdg, sector 0 [2522065.291147] Buffer I/O error on device sdg, logical block 0 [2522065.291147] Buffer I/O error on device sdg, logical block 1 [2522065.291147] Buffer I/O error on device sdg, logical block 2 [2522065.308465] sd 0:0:1:0: [sdg] Device not ready [2522065.308465] sd 0:0:1:0: [sdg] [2522065.308465] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [2522065.308465] sd 0:0:1:0: [sdg] [2522065.308465] Sense Key : Not Ready [current] [2522065.308465] sd 0:0:1:0: [sdg] [2522065.308465] Add. Sense: Logical unit not ready, cause not reportable [2522065.308465] sd 0:0:1:0: [sdg] CDB: [2522065.308465] Read(10): 28 00 00 00 00 00 00 00 08 00 [2522065.308465] end_request: I/O error, dev sdg, sector 0 Thanks! linux hard-drive share|improve this question aske
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower ext4 fs error device sda1 by Red Hat Cloud Computing Back Red Hat CloudForms Red Hat ext3 fs error device sdb1 OpenStack Platform Red Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container Platform Red buffer io error on device sda1 Hat OpenShift Online Red Hat OpenShift Dedicated Storage Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application http://serverfault.com/questions/613249/buffer-i-o-error-on-device-sata-drive Platform Red Hat JBoss Data Grid Red Hat JBoss Web Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back https://access.redhat.com/solutions/18746 Red Hat Mobile Application Platform Services Back Consulting Technical Account Management Training & Certifications Red Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities
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 http://askubuntu.com/questions/550840/buffer-i-o-errors more about Stack Overflow the company Business Learn more about hiring developers or posting https://ubuntuforums.org/archive/index.php/t-1470970.html 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 error on the top Buffer I/O errors up vote 0 down vote favorite I notice that when I unmount my external HDD I sometimes getting messages in my logs which saying: Buffer I/O error on device sdX, logical block XX Where the X stands for the device for example: sdc. How I seriously do I have to take these messages since the device only spewing this messages when I unmount it, when error on device I mount and use it I don't get any messages and the device works fine at this point as far I can see. mount external-hdd share|improve this question asked Nov 18 '14 at 1:39 Allard 1616 Hard to know without more information. I suggest you run fsck on the partition(s) and use smartmontools smartctl -a /dev/sda or smartctl -H /dev/sda change sda to your hard drive –bodhi.zazen Nov 18 '14 at 2:10 I have 2 external HDD's. One was able to give me info about the smart. dropbox.com/s/81nndc10yqy5ux8/smart%20first%20hdd.txt?dl=0 –Allard Nov 18 '14 at 12:58 The one that is giving the messages ? Is it healthy ? –bodhi.zazen Nov 18 '14 at 13:00 Those results look alright, see thomas-krenn.com/en/wiki/SMART_tests_with_smartctl –bodhi.zazen Nov 18 '14 at 13:08 The second drive I had to use in Windows and check with CrystalDiskInfo for the smart status. Note that this is a Seagate Disk. dropbox.com/s/v6bj2x4l1epao9z/smart%20hdd%202.png?dl=0 –Allard Nov 18 '14 at 13:10 | show 2 more comments 3 Answers 3 active oldest votes up vote 0 down vote Typically, this buffer issues can be indicative of a pending HDD failure. However, it is best to test the drive and verify and see where exactly t
days ago, I only started getting this problem today. After a very short amount of time being logged in, 2 of my hard drives stop working. I have 5 750GB hard drives, 1 has / and swap on it, the others are for data, but I am only using the first to at the moment. Nautilus shows no files in these 2 hard drives, but the other 2 are fine, as is the system disk. Here's what I'm getting in dmesg over and over again... [ 2377.833672] end_request: I/O error, dev sdb, sector 4007 [ 2377.833689] sd 9:0:0:0: [sdb] Unhandled error code [ 2377.833695] sd 9:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [ 2377.833708] sd 9:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 0f a7 00 00 08 00 [ 2377.833745] end_request: I/O error, dev sdb, sector 4007 [ 2377.833767] sd 9:0:0:0: [sdb] Unhandled error code [ 2377.833774] sd 9:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [ 2377.833784] sd 9:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 0f a7 00 00 08 00 [ 2377.833820] end_request: I/O error, dev sdb, sector 4007 [ 2414.775081] sd 9:0:0:0: [sdb] Unhandled error code [ 2414.775083] sd 9:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [ 2414.775086] sd 9:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 41 00 00 02 00 I have tried unmounting and remounting the drives, but I cannot remount: mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so and in dmesg: [ 2840.396365] sd 10:0:0:0: [sdc] Unhandled error code [ 2840.396367] sd 10:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [ 2840.396369] sd 10:0:0:0: [sdc] CDB: Read(10): 28 00 00 00 00 41 00 00 02 00 [ 2840.396375] end_request: I/O error, dev sdc, sector 65 [ 2840.396381] EXT3-fs: unable to read superblock I'm running 64-bit 10.04 with Core 2 Quad @ 2.66GHz, 4GB memeory, nVidia (yes, I know) motherboard. These drives have a lot of data on them, any help would be greatly appreciated. Thanks. EDIT: Kernel is 2.6.32-21-generic. Will try with an earli