Buffer I/o Error On Device Sdb Logical Block 0 Usb
Contents |
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 the company Business Learn buffer i/o error on device sdb logical block 0 linux more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges
Buffer Io Error On Device Sdb Logical Block 0
Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a buffer i o error on device sr0 logical block 0 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 Buffer I/O errors up vote 0 down vote favorite I notice that when
Buffer I/o Error On Device Logical Block
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 I mount and use it I don't get any messages and the device works fine at this point as far I can see. buffer i/o error on device sda logical block 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 the error lay. Please run e2fsck -fv /dev/sdX. If it runs without error, then there must be something else wrong. If it has any errors or mentions moving sectors, backup immediately and prepare to replace the drive. I recommend replacing it sooner rather than later in that
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
Buffer I/o Error On Device Dm-0
About Us Learn more about Stack Overflow the company Business Learn more about hiring
Buffer I O Error On Device Sdb Logical Block
developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a buffer i/o error on device logical block 0 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 question Anybody can answer The best answers http://askubuntu.com/questions/550840/buffer-i-o-errors are voted up 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 http://serverfault.com/questions/613249/buffer-i-o-error-on-device-sata-drive own (very limited tw_cli utility). [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
2012-06-05 Posts: 674 Buffer I/O error on device... I get this error sometimes with my external usb drives. At first i thought that it was because my old WD (ext4) was dying https://bbs.archlinux.org/viewtopic.php?id=177447 or something but it gives me the same in a brand new drive (ntfs) that i moved my files on.Any ideas what can be the cause? Offline #2 2014-02-21 15:35:48 Awebb Member Registered: https://www.raspberrypi.org/forums/viewtopic.php?t=20684&p=200707 2010-05-06 Posts: 4,553 Re: Buffer I/O error on device... Such errors are often caused by the lack of logfiles posted in help threads.Try a non-ntfs file system and see if the error error on persists. Offline #3 2014-02-21 15:42:56 89c51 Member Registered: 2012-06-05 Posts: 674 Re: Buffer I/O error on device... The thing is that i saw this on my ext4 external drive also. Is there a possibility to be something related to the USB port?Also is it possible to be related to the udisk2 update? Last edited by 89c51 (2014-02-21 15:46:29) Offline #4 2014-02-21 17:36:09 x33a Forum Moderator error on device Registered: 2009-08-15 Posts: 3,430 Website Re: Buffer I/O error on device... 89c51 wrote:The thing is that i saw this on my ext4 external drive also. Is there a possibility to be something related to the USB port?Also is it possible to be related to the udisk2 update?It could be caused by any number of reasons. If you want something other than speculation, post your logs as Awebb said. blog | github Offline #5 2014-02-21 21:43:05 89c51 Member Registered: 2012-06-05 Posts: 674 Re: Buffer I/O error on device... Sorry. I read his post fast and under the influence of wine. With the new disc.Feb 21 09:59:25 mainland systemd[1]: Mounted FUSE Control File System. Feb 21 09:59:25 mainland ntfs-3g[1112]: Version 2013.1.13 external FUSE 29 Feb 21 09:59:25 mainland ntfs-3g[1112]: Mounted /dev/sdb1 (Read-Write, label "TOSHIBA EXT", NTFS 3.1) Feb 21 09:59:25 mainland ntfs-3g[1112]: Cmdline options: rw,nodev,nosuid,uid=1000,gid=100,dmask=0077,fmask=0177,uid=1000,uhelper=udisks2 Feb 21 09:59:25 mainland ntfs-3g[1112]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdb1,blkdev,blksize=4096 Feb 21 09:59:25 mainland ntfs-3g[1112]: Global ownership and permissions enforced, configuration type 7 Feb 21 09:59:25 mainland udisksd[453]: Mounted /dev/sdb1 at /run/media/toliz/TOSHIBA EXT on behalf of uid 1000 Feb 21 10:03:04 mainland kernel: usb 4-2: USB disconnect, device number 2 Feb 21 10
» Mon Oct 22, 2012 7:44 am Hi all,I have a 32gb patriot class 10 SD card I was using with the pi.It worked great for about 2 weeks...i then was installing chromium and open office when the pi froze. After about half an hour of nothing happening (clock was stuck on the same time too) I decided to unplug the power and reset it.It would then not start up again.I thought I would try with a different SD card and sure enough as soon as I put in an sd card with a new image on it it booted up straight away. The pi seems to be working fine as far as I can tell.I have since tried the 32gb card in my phone, pc, etc and it is recognised as being there but shows no other signs of life - will not be formatted by phone, not assigned a drive letter by computer. Is there anyway to get this back to life or is it completely dead?And my other question is - is there a way to avoid this happening again? Should I disable swap on the pi? Any other tips?Thanks in advance Support The MagPi by purchasing printed copies from one of our retailers - http://themagpi.com/en/buyPlease share with anyone who is interested! Posts: 106Joined: Wed Oct 03, 2012 3:36 am by shawaj » Tue Oct 23, 2012 1:07 pm any ideas? Support The MagPi by purchasing printed copies from one of our retailers - http://themagpi.com/en/buyPlease share with anyone who is interested! Posts: 106Joined: Wed Oct 03, 2012 3:36 am by malakai » Tue Oct 23, 2012 1:10 pm Sounds like a freak accident haven't seen a whole lot of people considering the numbers sold complaining about this. If you can't get a drive letter not sure what you can do.All I can think of is there is a protected area on SD Cards yours probably got written to.Either that or you need an updated driver on your computerCheck this site for infohttps://www.sdcard.org/downloads/formatter_3/ http://www.raspians.com - always looking for content feel free to ask to have it posted. Or sign up and message me to become a contributor to the site. Raspians is not affiliated with the Raspberry Pi Foundation. (RPi's + You = Raspians) Posts: 1383Joined: Sat Sep 15, 2012 10:35 am by Nr90 » Tue Oct 23, 2012 2:07 pm Just checking, you haven't flipped the lock switch?Can you safely eject / unmount the drive and then reinsert?Sometimes helps for me.It might be worth trying a linux PC to see if this picks it up, because of the EXT4 partition.If you do not have access to a PC with linux you could try booting your PC from a live USB drive (see ubuntu.org for example)Not sure if