Buffer I/o Error On Device Sd Card
Contents |
Board index The team Delete all board cookies All times are UTC
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
Buffer I O Error On Device Sdc
Us Learn more about Stack Overflow the company Business Learn more about hiring developers buffer i o error on device sdc1 or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question
Ubuntu Buffer I O Error On Device
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 are voted https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=20659 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 own (very limited http://serverfault.com/questions/613249/buffer-i-o-error-on-device-sata-drive 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 sdg, sector 0 Thanks! linux hard-drive share|impr
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://stackoverflow.com/questions/18911932/what-is-the-reason-for-this-mmc-reading-in-linux of this site About Us Learn more about Stack Overflow the company Business https://developer.ridgerun.com/wiki/index.php/Storage_device_USB_or_SD_Card_debugging Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: error on Sign up what is the reason for this mmc reading in linux [closed] up vote 7 down vote favorite what is the reason for this mmc reading problem in linux ..? please help to solve this...? please check my kernel booting log below help me to solve this.. I have enabled the relevant drivers for mmc compiled and booted with with newly created error on device kernel image I am getting the kernel boot loogs as shown below mmc0: card lacks mandatory switch function, performance might suffer. mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new SD card at address b368 mmcblk0: mmc0:b368 SMI-S 8.00 MiB mmcblk0: mmcblk0: retrying using single block read mmcblk0: error -110 transferring data, sector 0, nr 8, card status 0xb00 end_request: I/O error, dev mmcblk0, sector 0 mmcblk0: error -110 sending read/write command, response 0xb00, card status 0x40 end_request: I/O error, dev mmcblk0, sector 1 mmcblk0: error -110 sending read/write command, response 0x400b00, card status 0 end_request: I/O error, dev mmcblk0, sector 2 mmcblk0: error -110 sending read/write command, response 0x400b00, card status 0 end_request: I/O error, dev mmcblk0, sector 3 mmcblk0: error -110 sending read/write command, response 0x400b00, card status 0 end_request: I/O error, dev mmcblk0, sector 4 mmcblk0: error -110 sending read/write command, response 0x400b00, card status 0 end_request: I/O error, dev mmcblk0, sector 5 mmcblk0: error -110 sending read/write command, response 0x400b00, card status 0 end_request: I/O error, dev mmcblk0, sector 6 mmcblk0: error -110 sending read/write command, response
required. The only problem was the host computer kept throwing errors when trying to access the video file. I was asked to dig into the details. Do no harm The first thing I did was copy the raw contents of the entire SD card to a file. That way I can make mistakes on the image file without risking loosing the video file on the SD card. You need to be careful as most host computers will try to mount the file systems on the SD card. I have my Ubuntu box configured so auto-mount is disabled. To find the SD card device file I used dmesg. [3097298.239288] sd 154:0:0:0: [sdi] 15523840 512-byte logical blocks: (7.94 GB/7.40 GiB) As you can see, in my case the device file was /dev/sdi. You may also see devices files like /dev/sdi1 and/dev/sdi2 (try cat /proc/partitions). These device files expose the partition contents. We want to copy the entire SD card, so I used /dev/sdi. Your computer will use a different device filename. My first attempt was to use 'dd to do a raw copy of the entire SD card contents: sudo dd bs=64M if=/dev/sdi of=sd.img I saw errors and the copy stopped before all 8 GB were copied. dd: reading `/dev/sdi': Input/output error 47+1 records in 47+1 records out 3168010240 bytes (3.2 GB) copied, 531.645 s, 6.0 MB/s So, I tried again telling dd to ignore errors and fill the unreadable areas with zeros: sudo dd bs=64M if=/dev/sdi of=sd.img conv=noerror conv=sync with output dd: reading `/dev/sdi': Input/output error 117+2 records in 119+0 records out 7985954816 bytes (8.0 GB) copied, 868.579 s, 9.2 MB/s It is interesting the file size using dd is bigger than expected - 7985954816 bytes in the dd created copy where as the kernel reported the size as 7948206080 (15523840 512-byte logical blocks). I suspect this has to do with the last block being increased to match the 64M boundary of my block size setting. I then used dmesg again to see what type of errors occurred: [3099472.345548] Buffer I/O error on device sdi, logical block 773440 [3099472.345567] Buffer I/O error on device sdi, logical block 773441 [3099472.345575] Buffer I/O error on device sdi, logical block 773442 [3099472.345581] Buffer I/O error on device sdi, logical block 773443 [3099472.345588] Buffer I/O error on device sdi, logical block 773444 [3099472.345595] Buffer I/O error on device sdi, logi