LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 05-24-2018, 04:02 PM   #1
dzongos
LQ Newbie
 
Registered: May 2018
Posts: 5

Rep: Reputation: Disabled
Buffer I/O error


Sorry to bump an old thread but I am having similar issues and this is the only place I found someone who fixed this issue.
Any help would be greatly appreciated.

When I try to mount a hard drive externally this is what I get:

Code:
blk_update_request: critical medium error, dev sdb, sector 27265040
blk_update_request: critical medium error, dev sdb, sector 27265040
Buffer I/O error on dev sdb2, logical block 2, async page read
Here is the output from /var/log/syslog:

Code:
15:13:45 kernel: [  346.984789] sd 3:0:0:0: [sdb] Attached SCSI disk
15:13:45 tpvmlpd2[3553]: device type not supported
15:13:45 tpvmlpd2[968]: aborting
15:13:45 kernel: [  378.903632] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
15:13:45 kernel: [  378.903635] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
15:13:45 kernel: [  378.903637] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
15:13:45 kernel: [  378.903639] sd 3:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 a0 08 10 00 00 08 00
15:13:45 kernel: [  378.903641] blk_update_request: critical medium error, dev sdb, sector 27265040
15:13:50 kernel: [  383.722992] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
15:13:50 kernel: [  383.722995] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
15:13:50 kernel: [  383.722997] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
15:13:50 kernel: [  383.722999] sd 3:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 a0 08 10 00 00 08 00
15:13:50 kernel: [  383.723001] blk_update_request: critical medium error, dev sdb, sector 27265040
15:13:50 kernel: [  383.723466] Buffer I/O error on dev sdb2, logical block 2, async page read
15:14:25 kernel: [  418.614138] usb 2-1: reset high-speed USB device number 6 using ehci-pci
15:14:29 systemd-udevd[239]: seq 3717 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb1' is taking a long time
15:14:29 systemd-udevd[239]: seq 3718 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb2' is taking a long time
15:14:29 systemd-udevd[239]: seq 3719 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb3' is taking a long time
15:14:58 kernel: [  451.506974] usb 2-1: reset high-speed USB device number 6 using ehci-pci
15:15:30 kernel: [  484.434120] usb 2-1: reset high-speed USB device number 6 using ehci-pci
15:16:03 kernel: [  517.328068] usb 2-1: reset high-speed USB device number 6 using ehci-pci
15:16:29 systemd-udevd[239]: seq 3717 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb1' killed
15:16:29 systemd-udevd[239]: seq 3719 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb3' killed
15:16:29 systemd-udevd[239]: seq 3718 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb2' killed
15:16:32 kernel: [  546.064366] usb 2-1: USB disconnect, device number 6
15:16:32 systemd-udevd[239]: worker [3551] terminated by signal 9 (Killed)
15:16:32 kernel: [  546.088981] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
15:16:32 kernel: [  546.088987] sd 3:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 09 10 00 00 f0 00
15:16:32 kernel: [  546.088990] blk_update_request: I/O error, dev sdb, sector 2320
15:16:32 kernel: [  546.089531] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
15:16:32 kernel: [  546.089533] sd 3:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 a3 38 00 00 00 08 00
15:16:32 kernel: [  546.089534] blk_update_request: I/O error, dev sdb, sector 27473920
15:16:32 systemd-udevd[239]: worker [3551] failed while handling '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb1'
15:16:32 systemd-udevd[239]: worker [3567] terminated by signal 9 (Killed)
15:16:32 systemd-udevd[239]: worker [3567] failed while handling '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb2'
15:16:32 systemd-udevd[239]: worker [3568] terminated by signal 9 (Killed)
15:16:32 systemd-udevd[239]: worker [3568] failed while handling '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb3'
15:17:01 CRON[3640]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
15:20:41 kernel: [  796.355245] usb 2-1: new high-speed USB device number 7 using ehci-pci
15:20:41 kernel: [  796.700283] usb 2-1: New USB device found, idVendor=174c, idProduct=1153
15:20:41 kernel: [  796.700286] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
15:20:41 kernel: [  796.700287] usb 2-1: Product: AS2115
15:20:41 kernel: [  796.700288] usb 2-1: Manufacturer: ASMedia
15:20:41 kernel: [  796.700289] usb 2-1: SerialNumber: 00000000000000000000
15:20:41 kernel: [  796.703617] usb-storage 2-1:1.0: USB Mass Storage device detected
15:20:41 kernel: [  796.703760] scsi host3: usb-storage 2-1:1.0
15:20:41 mtp-probe: checking bus 2, device 7: "/sys/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1"
15:20:41 mtp-probe: bus: 2, device: 7 was not an MTP device
15:20:42 kernel: [  797.737157] scsi 3:0:0:0: Direct-Access     ASMT     2115             0    PQ: 0 ANSI: 6
15:20:42 kernel: [  797.738498] sd 3:0:0:0: Attached scsi generic sg2 type 0
15:20:42 kernel: [  797.759212] sd 3:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB)
15:20:42 kernel: [  797.779798] sd 3:0:0:0: [sdb] Write Protect is off
15:20:42 kernel: [  797.779801] sd 3:0:0:0: [sdb] Mode Sense: 43 00 00 00
15:20:42 kernel: [  797.799267] sd 3:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
15:20:42 kernel: [  797.908991]  sdb: sdb1 sdb2 sdb3
15:20:44 kernel: [  799.734374] sd 3:0:0:0: [sdb] Attached SCSI disk
15:21:23 kernel: [  838.840037] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
15:21:23 kernel: [  838.840041] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
15:21:23 kernel: [  838.840042] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
15:21:23 kernel: [  838.840045] sd 3:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 a0 08 10 00 00 08 00
15:21:23 kernel: [  838.840047] blk_update_request: critical medium error, dev sdb, sector 27265040
15:21:56 kernel: [  871.162084] usb 2-1: reset high-speed USB device number 7 using ehci-pci
15:21:59 systemd-udevd[239]: seq 3747 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb1' is taking a long time
15:21:59 systemd-udevd[239]: seq 3748 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb2' is taking a long time
Here is the output from this command "smartctl -a /dev/sdb":

Code:
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-6-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Scorpio Blue Serial ATA
Device Model:     WDC WD5000BEVT-22A0RT0
Serial Number:    WD-WXD1A90T6298
LU WWN Device Id: 5 0014ee 6ab2e345b
Firmware Version: 01.01A01
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Thu May 24 15:24:46 2018 CDT
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:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
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:                (13200) 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:        ( 154) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x7037) SCT Status 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   185   153   021    Pre-fail  Always       -       1725
  4 Start_Stop_Count        0x0032   089   089   000    Old_age   Always       -       11948
  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   089   089   000    Old_age   Always       -       8577
 10 Spin_Retry_Count        0x0032   100   100   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   092   092   000    Old_age   Always       -       8940
191 G-Sense_Error_Rate      0x0032   001   001   000    Old_age   Always       -       793
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       113
193 Load_Cycle_Count        0x0032   170   170   000    Old_age   Always       -       90679
194 Temperature_Celsius     0x0022   114   100   000    Old_age   Always       -       33
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   193   193   000    Old_age   Always       -       630
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   051    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.
 
Old 05-24-2018, 08:44 PM   #2
jsbjsb001
Senior Member
 
Registered: Mar 2009
Location: Somewhere on earth? Maybe I'm a figment of your imagination?
Distribution: A number of them over the years...
Posts: 1,521

Rep: Reputation: 735Reputation: 735Reputation: 735Reputation: 735Reputation: 735Reputation: 735Reputation: 735
While it maybe a similar issue, you should have started you're own thread rather than hijacking someone else's. I've reported this to be split off into it's own thread. Next time, start you're own thread for you're own question.

You also don't explain what (if anything) you have even tried to resolve this.

EDIT:

On closer look;

I'm not sure that the problem being referred to in your kernel log is actually the drive you mention in your smartctl output. As your smartctl output refers to a SATA drive, not a USB drive.

If you're referring to the lines below:

Code:
15:14:29 systemd-udevd[239]: seq 3717 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb1' is taking a long time
15:14:29 systemd-udevd[239]: seq 3718 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb2' is taking a long time
15:14:29 systemd-udevd[239]: seq 3719 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb3' is taking a long time
...
15:16:29 systemd-udevd[239]: seq 3717 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb1' killed
15:16:29 systemd-udevd[239]: seq 3719 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb3' killed
15:16:29 systemd-udevd[239]: seq 3718 '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb2' killed
As the above is referring to a USB device of some description. I'm not sure this is related to the same issue in the thread you decided to bump.

Last edited by jsbjsb001; 05-24-2018 at 09:02 PM. Reason: additions
 
Old 05-24-2018, 10:08 PM   #3
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 16,656

Rep: Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454
Me, I would say the disk is dead.
Is this a "portable" drive - i.e. sold in a case with USB cable ?. If so might not be much you can do. If it is a "normal" SATA drive you have mounted using a caddy or adaptor, try mounting it in the case of a desktop machine using a SATA cable to the motherboard. You might be lucky that it's just a USB problem.
I wouldn't be relying on that though, it looks dead.
 
Old 05-24-2018, 11:24 PM   #4
dzongos
LQ Newbie
 
Registered: May 2018
Posts: 5

Original Poster
Rep: Reputation: Disabled
Thanks for the replies...

This is actually a sata drive from a laptop.
I took it out of the laptop and put it into a sata to usb adapter.
It attempts to mount but times out.
I tried to mount it manually with no luck.

It contains some family pictures and a few other things I would like to recover if possible.
I thought maybe I could clone it to a file and then run some sort of file recovery software on it.

I am not sure the best way to clone the drive to file though.

I am trying to figure out exactly what I need to do before loading the drive back up because I am sure it is about to completely fail.
 
Old 05-25-2018, 12:44 AM   #5
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 16,656

Rep: Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454
The best tool to create the image is ddrescue - the manual is here - take the time to read it.

As I mentioned, you should mount the drive with a SATA cable - USB is too flaky for this; and it will take forever. Once you have the image, use photorec on it to attempt to recover your files.
 
Old 05-25-2018, 12:54 AM   #6
dzongos
LQ Newbie
 
Registered: May 2018
Posts: 5

Original Poster
Rep: Reputation: Disabled
Okay. I will try this and post back my results.

Thank you!
 
Old 05-26-2018, 01:01 AM   #7
AwesomeMachine
LQ Guru
 
Registered: Jan 2005
Location: USA and Italy
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,029

Rep: Reputation: 906Reputation: 906Reputation: 906Reputation: 906Reputation: 906Reputation: 906Reputation: 906Reputation: 906
I would say it could be the drive, enclosure or cable. But the drive looks pretty good in smartctl. Drives in a USB enclosure still show up as SATA in smartctl.
 
Old 05-26-2018, 01:12 AM   #8
AwesomeMachine
LQ Guru
 
Registered: Jan 2005
Location: USA and Italy
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,029

Rep: Reputation: 906Reputation: 906Reputation: 906Reputation: 906Reputation: 906Reputation: 906Reputation: 906Reputation: 906
This is a nice ddrescue tutorial: https://www.technibble.com/guide-usi...-recover-data/
 
Old 05-26-2018, 01:15 AM   #9
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 16,656

Rep: Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454Reputation: 2454
A high Current_Pending_Sector count is ok ?.
 
Old 05-26-2018, 01:43 PM   #10
dzongos
LQ Newbie
 
Registered: May 2018
Posts: 5

Original Poster
Rep: Reputation: Disabled
I am going to try ddrescue this afternoon.

Thanks for all the replies.
 
Old 05-28-2018, 01:39 AM   #11
dzongos
LQ Newbie
 
Registered: May 2018
Posts: 5

Original Poster
Rep: Reputation: Disabled
I just wanted to say thanks again.

ddrescue is working great so far.

It has a few more gigs left and I will try to recover the files tomorrow.
 
  


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

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 09:39 PM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration