LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices

Reply
 
Search this Thread
Old 09-08-2012, 10:35 AM   #1
fooby
LQ Newbie
 
Registered: Apr 2006
Posts: 7

Rep: Reputation: 0
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
 
Old 09-09-2012, 10:29 PM   #2
td3201
Member
 
Registered: Jan 2002
Location: Omaha, NE US
Distribution: Red Hat/CentOS
Posts: 224

Rep: Reputation: 30
I am assuming this is a dual-booted machine? Did you try running an fsck within windows against these drives? If that's not the case, please describe the physical layout, distribution, and ntfs-3g version.
 
Old 09-10-2012, 04:57 AM   #3
fooby
LQ Newbie
 
Registered: Apr 2006
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by td3201 View Post
I am assuming this is a dual-booted machine? Did you try running an fsck within windows against these drives? If that's not the case, please describe the physical layout, distribution, and ntfs-3g version.
Hi td3201.

No this isn't a dual booted machine. The disks were in my home PC (which was dual booted) but the motherboard since broke, so I moved them into an HP Proliant server.

These are just normal disks plugged in to the motherboard via sata (not raided, not plugged into the raid controller).

I've done more investigation since my first post, most results for these sorts of errors point to hardware failure. Which, I'll accept if I have too, just odd that 2x HDD's go at the same time (different make/models/ages)

I've changed the SATA cables on the 2 effected drives and made sure the contacts are clean, just in case this was an issue.

I have performed a smartctl long test on both drives. Below is my smartctl output on both devices.

NTFS-3G Version: ntfs-3g 2012.1.15AR.5 external FUSE 29

Code:
root@tronlegacy:~# smartctl --all /dev/sdc
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.0.0-1-amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Blue Serial ATA
Device Model:     WDC WD7500AAKS-00RBA0
Serial Number:    WD-WCAPT0747564
LU WWN Device Id: 5 0014ee 20116d3b6
Firmware Version: 30.04G30
User Capacity:    750,156,374,016 bytes [750 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Sun Sep  9 20:40:06 2012 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 121) The previous self-test completed having
                                        the read element of the test failed.
Total time to complete Offline
data collection:                (16800) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 207) minutes.
Conveyance self-test routine
recommended polling time:        (   6) minutes.
SCT capabilities:              (0x303f) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0003   197   045   021    Pre-fail  Always       -       7116
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       635
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000e   200   200   051    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   064   064   000    Old_age   Always       -       26451
 10 Spin_Retry_Count        0x0012   100   100   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0012   100   100   051    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       555
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       349
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       641
194 Temperature_Celsius     0x0022   117   104   000    Old_age   Always       -       35
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0010   200   200   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       2
200 Multi_Zone_Error_Rate   0x0008   200   200   051    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%     26448         27856418

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Code:
root@tronlegacy:~# smartctl --all /dev/sdd
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.0.0-1-amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital RE4 Serial ATA
Device Model:     WDC WD1003FBYX-50Y7B0
Serial Number:    WD-WCAW30797925
LU WWN Device Id: 5 0014ee 2b021aff1
Firmware Version: 01.01V02
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Sun Sep  9 20:39:07 2012 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (16560) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 171) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x303f) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   175   172   021    Pre-fail  Always       -       4250
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       42
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -       10737
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       40
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       35
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       6
194 Temperature_Celsius     0x0022   113   107   000    Old_age   Always       -       34
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       18
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     10737         -
# 2  Extended offline    Aborted by host               90%     10734         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Last edited by fooby; 09-10-2012 at 05:02 AM.
 
Old 09-10-2012, 05:10 AM   #4
td3201
Member
 
Registered: Jan 2002
Location: Omaha, NE US
Distribution: Red Hat/CentOS
Posts: 224

Rep: Reputation: 30
Try plugging them into a windows box and running the fsck to see what happens.
 
Old 09-10-2012, 01:21 PM   #5
fooby
LQ Newbie
 
Registered: Apr 2006
Posts: 7

Original Poster
Rep: Reputation: 0
indeedy, few bad secords and the MFT was broken on /dev/sdc

/dev/sda just sayins MFT is b0rked and cannot fixed, so looks like they are both actually on their way out!! really odd. But thanks for making sure I wasn't doing something wrong.

New HDD & chkdsk /R time and hope it lasts long enough to copy my data off.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
buffer i/o error kaustubhdatar Linux - Newbie 1 09-02-2008 07:01 PM
Buffer IO error raybakh Linux - Hardware 0 10-02-2006 03:24 AM
What is the difference between the free buffer and buffer in the buffer hash queue? Swagata Linux - Enterprise 0 05-25-2006 11:57 PM
Buffer I/O error linuxhippy Fedora 4 07-15-2005 05:25 AM
mnt error--buffer I/O error, dev fd0 elempoimen Linux - Hardware 0 06-10-2005 10:51 PM


All times are GMT -5. The time now is 08:40 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration