Buffer I/o Error On Device Sdc Logical Block Usb
Contents |
HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - General [SOLVED] Problem mounting, checking or reading partition (probably a physical buffer i/o error on device sdb logical block damage) User Name Remember Me? Password Linux - General This Linux forum buffer i/o error on device sdb logical block 0 is for general Linux questions and discussion. If it is Linux Related and doesn't seem to fit in any buffer i/o error on device sdb logical block 0 linux other forum then this is the place. Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will
Buffer Io Error On Device Sdb Logical Block
have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site buffer i/o error on device logical block FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 03-21-2010, 01:21 PM #1 scmbg Member Registered: Oct 2008 Loca
Support Search GitHub This repository Watch 545 Star 3,190 Fork 1,767 raspberrypi/linux buffer i/o error on device sda logical block Code Issues 190 Pull requests 26 Projects 0 Wiki
Buffer I/o Error On Device Dm-0
Pulse Graphs New issue external USB drive: blk_update_request: I/O error and the USB drive gets
Buffer I/o Error On Device Logical Block 0
another /dev/sd node #777 Open f18m opened this Issue Jan 31, 2015 · 41 comments Projects None yet Labels None yet Milestone No milestone Assignees http://www.linuxquestions.org/questions/linux-general-1/problem-mounting-checking-or-reading-partition-probably-a-physical-damage-796892/ P33M 20 participants f18m commented Jan 31, 2015 Hi, I found a quite-reproducible problem (happens quite often!) with the following setup: HW: Raspberry model B+, powered by its own 5V, 2A power supply USB HUB 3.0 (Trascend TS-HUB3K), powered by its own 12V, 1.5A power supply (15W) 2 external hard https://github.com/raspberrypi/linux/issues/777 disks (the problem happens also with just 1 hard disk!) root@rasptorrent:~# cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)" NAME="Raspbian GNU/Linux" VERSION_ID="7" VERSION="7 (wheezy)" ID=raspbian ID_LIKE=debian ANSI_COLOR="1;31" HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" root@rasptorrent:~# uname -a Linux rasptorrent 3.18.5+ #744 PREEMPT Fri Jan 30 18:19:07 GMT 2015 armv6l GNU/Linux (did "rpi-update" on Jan 31 2015) HOW TO REPRODUCE: just producing traffic on the USB external drives at some point produces: [ 1116.317108] sd 1:0:0:0: [sdb] [ 1116.317199] Result: hostbyte=0x07 driverbyte=0x00 [ 1116.317220] sd 1:0:0:0: [sdb] CDB: [ 1116.317233] cdb[0]=0x28: 28 00 13 7b 13 08 00 00 f0 00 [ 1116.317297] blk_update_request: I/O error, dev sdb, sector 326832904 (several times, for different sectors) and the USB device (e.g., /dev/sdb1) is destroyed and a new dev node is created (e.g., /dev/sdc1). The dwc_otg driver seems latest one: root@rasptorrent:~# dmesg | grep dwc_otg [ 0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708.boardrev=0x10 bcm2708.serial=0xee394e21 sm
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 or something but https://bbs.archlinux.org/viewtopic.php?id=177447 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: 2010-05-06 Posts: 4,553 https://www.redhat.com/archives/ext3-users/2015-May/msg00000.html 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 persists. Offline #3 2014-02-21 15:42:56 error on 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 Registered: 2009-08-15 Posts: 3,430 Website Re: Buffer I/O error on device 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:03:04 mainland udisksd[453]: Cleaning up mount point /run/media/toliz/TOSHIBA EXT (device 8:17 no longer exist) Feb
Subject: fsck failing to notice that the block device was pulled out from under it? Date: Mon, 25 May 2015 23:59:44 +0200 Hello, tl;dr: it seems like fsck fails to notice when the block device disappears from under it. I have the following setup: * external USB disk * a partition with LUKS in it * ext4 filesystem inside the LUKS block device While doing backups to it I noticed that after some time backups would fail with an error (failed to write, ). In the following log I'm attaching the disk, enabling LUKS and mounting the disk and then starting the backup, which will fail after a while: May 25 11:39:18 hier kernel: [76241.727367] usb 4-1.1: new high-speed USB device number 6 using ehci-pci May 25 11:39:19 hier kernel: [76241.881892] usb 4-1.1: New USB device found, idVendor=0bc2, idProduct=3320 May 25 11:39:19 hier kernel: [76241.881902] usb 4-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 May 25 11:39:19 hier kernel: [76241.881907] usb 4-1.1: Product: Expansion Desk May 25 11:39:19 hier kernel: [76241.881911] usb 4-1.1: Manufacturer: Seagate May 25 11:39:19 hier kernel: [76241.881915] usb 4-1.1: SerialNumber: NA4JDN4N May 25 11:39:19 hier kernel: [76241.882652] usb-storage 4-1.1:1.0: USB Mass Storage device detected May 25 11:39:19 hier kernel: [76241.883007] scsi7 : usb-storage 4-1.1:1.0 May 25 11:39:20 hier kernel: [76242.907527] usb 4-1.1: USB disconnect, device number 6 May 25 11:39:30 hier kernel: [76252.987833] usb 4-1.1: new high-speed USB device number 7 using ehci-pci May 25 11:39:30 hier kernel: [76253.142659] usb 4-1.1: New USB device found, idVendor=0bc2, idProduct=3320 May 25 11:39:30 hier kernel: [76253.142669] usb 4-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 May 25 11:39:30 hier kernel: [76253.142674] usb 4-1.1: Product: Expansion Desk May 25 11:39:30 hier kernel: [76253.142678] usb 4-1.1: Manufacturer: Seagate May 25 11:39:30 hier kernel: [76253.142681] usb 4-1.1: SerialNumber: NA4JDN4N May 25 11:39:30 hier kernel: [76253.143465] usb-storage 4-1.1:1.0: USB Mass Storage device detected May 25 11:39:30 hier kernel: [76253.144285] scsi8 : usb-storage 4-1.1:1.0 May 25 11:39:31 hier kernel: [76254.144816] scsi 8:0:0:0: Direct-Access Seagate Expansion Desk 070B PQ: 0 ANSI: 6 May 25 11:39:31 hier kernel: [76254.145528] sd 8:0:0:0: Attached scsi generic sg1 type 0 May 25 11:39:31 hier kerne