[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: problems with USB disk

lee wrote:

Hi,

I´m having trouble copying files for backup purposes to an USB disk
with rsync. Copying the files sometimes fails with "Input/output error
(5)", and I´m getting messages in the syslog like these:


[128625.090339] sd 11:0:0:0: [sdf] Unhandled sense code
[128625.090342] sd 11:0:0:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08
[128625.090345] sd 11:0:0:0: [sdf] Sense Key : 0x3 [current] [128625.090348] sd 11:0:0:0: [sdf] ASC=0x11 ASCQ=0x0 
[128625.090350] sd 11:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 67 d0 99 65 00 00 10 00
[128625.090354] end_request: I/O error, dev sdf, sector 1741724005
[128627.397801] sd 11:0:0:0: [sdf] Unhandled sense code
[128627.397811] sd 11:0:0:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08
[128627.397821] sd 11:0:0:0: [sdf] Sense Key : 0x3 [current] [128627.397830] sd 11:0:0:0: [sdf] ASC=0x11 ASCQ=0x0 
[128627.397839] sd 11:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 67 d0 99 6d 00 00 08 00
[128627.397858] end_request: I/O error, dev sdf, sector 1741724013
[128627.397894] EXT4-fs error (device sdf3): __ext4_get_inode_loc: unable to read inode block - inode=52298807, block=209191011
[128629.945331] sd 11:0:0:0: [sdf] Unhandled sense code
[128629.945340] sd 11:0:0:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08
[128629.945349] sd 11:0:0:0: [sdf] Sense Key : 0x3 [current] [128629.945359] sd 11:0:0:0: [sdf] ASC=0x11 ASCQ=0x0 
[128629.945367] sd 11:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 67 d0 99 65 00 00 10 00
[128629.945386] end_request: I/O error, dev sdf, sector 1741724005
[128632.219655] sd 11:0:0:0: [sdf] Unhandled sense code
[128632.219664] sd 11:0:0:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08
[128632.219673] sd 11:0:0:0: [sdf] Sense Key : 0x3 [current] [128632.219682] sd 11:0:0:0: [sdf] ASC=0x11 ASCQ=0x0 
[128632.219690] sd 11:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 67 d0 99 6d 00 00 08 00
[128632.219708] end_request: I/O error, dev sdf, sector 1741724013


If this wasn´t an USB disk, I would assume that the disk has
failed. But with USB, I´m not so sure: can this be some sort of
problem with USB, like a connection problem?

Sometimes copying the files works just fine, sometimes not. If the
disk was actually broken, I´d rather expect the copying to fail every
time. What might be going on here?
When you say 'USB disk' I presume you mean an exterior harddrive, either SATA or IDE, connected via USB cable.
I have 2 of those, one IDE and one SATA and I never ever see error messages like that: IMO the disk is bad. 

With

smartctl -d sat /dev/sda --all -T permissive

I can test the IDE USB disk but not the SATA one.

Hugo
Reply to: