fooby |
09-08-2012 10:35 AM |
Buffer I/O Error
Afternoon gentleman.
I have come across and issue that I've not previously experienced. I would love to say it was after I updated and rebooted, but I'm going to assume its when I first noticed it.
Very simple, I randomly (once it happens system requires a reboot) loose the ability to read/write to my mounted devices (all hdd's via ntfs-3g) with Buffer i/o error.
dmesg shows the following (a snapshot)
Code:
[ 396.884424] sd 1:0:1:0: [sdd] CDB: Write(10): 2a 00 00 00 08 10 00 00 08 00
[ 396.884433] end_request: I/O error, dev sdd, sector 2064
[ 396.884526] quiet_error: 37378 callbacks suppressed
[ 396.884529] Buffer I/O error on device sdd1, logical block 2
[ 396.884620] lost page write due to I/O error on sdd1
[ 396.884634] sd 1:0:1:0: [sdd] Unhandled error code
[ 396.884636] sd 1:0:1:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 396.884640] sd 1:0:1:0: [sdd] CDB: Write(10): 2a 00 00 00 0a a8 00 00 10 00
[ 396.884647] end_request: I/O error, dev sdd, sector 2728
[ 396.884738] Buffer I/O error on device sdd1, logical block 85
[ 396.884829] lost page write due to I/O error on sdd1
[ 396.884833] Buffer I/O error on device sdd1, logical block 86
[ 396.884924] lost page write due to I/O error on sdd1
[ 396.884932] sd 1:0:1:0: [sdd] Unhandled error code
[ 396.884934] sd 1:0:1:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 396.884938] sd 1:0:1:0: [sdd] CDB: Write(10): 2a 00 0e 8e 14 e0 00 00 08 00
[ 396.884946] end_request: I/O error, dev sdd, sector 244192480
[ 396.885037] Buffer I/O error on device sdd1, logical block 30523804
[ 396.885130] lost page write due to I/O error on sdd1
[ 396.885144] sd 1:0:1:0: [sdd] Unhandled error code
[ 396.885146] sd 1:0:1:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 396.885150] sd 1:0:1:0: [sdd] CDB: Write(10): 2a 00 0e 8e 5c c0 00 00 08 00
[ 396.885157] end_request: I/O error, dev sdd, sector 244210880
[ 396.885250] Buffer I/O error on device sdd1, logical block 30526104
[ 396.885343] lost page write due to I/O error on sdd1
[ 396.885358] sd 1:0:1:0: [sdd] Unhandled error code
[ 396.885361] sd 1:0:1:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 396.885364] sd 1:0:1:0: [sdd] CDB: Write(10): 2a 00 23 eb fe f8 00 04 00 00
[ 396.885372] end_request: I/O error, dev sdd, sector 602668792
[ 396.885464] Buffer I/O error on device sdd1, logical block 75333343
[ 396.885557] lost page write due to I/O error on sdd1
[ 396.885560] Buffer I/O error on device sdd1, logical block 75333344
[ 396.885653] lost page write due to I/O error on sdd1
[ 396.885657] Buffer I/O error on device sdd1, logical block 75333345
[ 396.885749] lost page write due to I/O error on sdd1
[ 396.885752] Buffer I/O error on device sdd1, logical block 75333346
[ 396.885845] lost page write due to I/O error on sdd1
[ 396.885848] Buffer I/O error on device sdd1, logical block 75333347
[ 396.885941] lost page write due to I/O error on sdd1
[ 396.886025] sd 1:0:1:0: [sdd] Unhandled error code
[ 396.886027] sd 1:0:1:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 396.886031] sd 1:0:1:0: [sdd] CDB: Write(10): 2a 00 23 ec 02 f8 00 04 00 00
[ 396.886038] end_request: I/O error, dev sdd, sector 602669816
[ 396.886207] sd 1:0:1:0: [sdd] Unhandled error code
[ 396.886210] sd 1:0:1:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 396.886213] sd 1:0:1:0: [sdd] CDB: Write(10): 2a 00 23 ec 06 f8 00 01 08 00
[ 396.886221] end_request: I/O error, dev sdd, sector 602670840
At first I thought my drive was knackered and was all prepared to throw it in the bin, but I ran smartctl and it appears to be happy with itself, then it started happening to my other mounted drives. Especially weird since I've not experienced a problem with any of my drives before.
I did some googleing and there is a bugreport for my kernel version mounting ext4 drives and getting buffer i/o, but it appears to only apply to XEN, which i don't run (nor am I running ext4). I couldn't really find anything related to my issue and the ntfs-3g package.
Does anyone have any suggestions on where i can go looking to resolve this problem? I'm merely an average user, but i'm willing to learn and investigation on my own.
Some more system information that's hopefully relevant below
Code:
adam@tronlegacy:~$ sudo tail -f /var/log/messages
Sep 8 15:00:25 tronlegacy kernel: [ 396.885653] lost page write due to I/O error on sdd1
Sep 8 15:00:25 tronlegacy kernel: [ 396.885749] lost page write due to I/O error on sdd1
Sep 8 15:00:25 tronlegacy kernel: [ 396.885845] lost page write due to I/O error on sdd1
Sep 8 15:00:25 tronlegacy kernel: [ 396.885941] lost page write due to I/O error on sdd1
Sep 8 15:00:25 tronlegacy kernel: [ 396.886025] sd 1:0:1:0: [sdd] Unhandled error code
Sep 8 15:00:25 tronlegacy kernel: [ 396.886027] sd 1:0:1:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 8 15:00:25 tronlegacy kernel: [ 396.886031] sd 1:0:1:0: [sdd] CDB: Write(10): 2a 00 23 ec 02 f8 00 04 00 00
Sep 8 15:00:25 tronlegacy kernel: [ 396.886207] sd 1:0:1:0: [sdd] Unhandled error code
Sep 8 15:00:25 tronlegacy kernel: [ 396.886210] sd 1:0:1:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 8 15:00:25 tronlegacy kernel: [ 396.886213] sd 1:0:1:0: [sdd] CDB: Write(10): 2a 00 23 ec 06 f8 00 01 08 00
Code:
adam@tronlegacy:~$ uname -a && cat /proc/version
Linux tronlegacy 3.0.0-1-amd64 #1 SMP Sat Aug 27 16:21:11 UTC 2011 x86_64 GNU/Linux
Linux version 3.0.0-1-amd64 (Debian 3.0.0-3) (ben@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011
Code:
adam@tronlegacy:~$ cat /proc/cpuinfo | grep "model name"
model name : Intel(R) Xeon(R) CPU 3065 @ 2.33GHz
model name : Intel(R) Xeon(R) CPU 3065 @ 2.33GHz
Code:
adam@tronlegacy:~$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 110G 63G 41G 61% /
udev 10M 0 10M 0% /dev
tmpfs 101M 880K 100M 1% /run
/dev/disk/by-uuid/937a39f4-e7fb-4c5c-bca4-b3a813d6fbcb 110G 63G 41G 61% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 379M 0 379M 0% /run/shm
/dev/sdb1 699G 665G 35G 96% /media/sdb1
/dev/sdc1 699G 688G 11G 99% /media/sdc1
/dev/sdd1 932G 171G 761G 19% /media/sdd1
Code:
adam@tronlegacy:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=937a39f4-e7fb-4c5c-bca4-b3a813d6fbcb / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=1e0d0c9e-8f6f-49f3-98f2-a4ce2f4395ef none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
/dev/sdb1 /media/sdb1 ntfs-3g,auto rw,user 0 0
/dev/sdc1 /media/sdc1 ntfs-3g,auto rw,user 0 0
/dev/sdd1 /media/sdd1 ntfs-3g,auto rw,user 0 0
|