OpenWrt Forum Archive

Topic: Ubiquiti RouterStation [AR71xx] USB errors

The content of this topic has been archived on 21 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

I already posted this on the Ubiquiti forum, but since it's OpenWRT, maybe someone here knows help too.

Original post:

---------------------------------------------------------------------------------------------------------------------


Hi,


Just got the RouterStation.

I flashed http://www.ubnt.com/downloads/RS/RSx.ar7100.OpenWRT.bin to it. Also tried the latest openwrt snapshot, with similar problems, but the log is from the ubnt.com image!

What I did:

I attached a 16GB Sandisk flashdrive to the USB-Port. The drive contains a ext3 FS and first everything seems fine (its been detected with right size etc.). Im able to mount the drive to /mnt/usb using the mount -t ext3 /dev/sda /mnt/usb command. I can see the lost+found dir there and did a 'touch test'

Shortly after that first errors came up (see log). So even small writing operations cause it to freeze/crash. Also tried to transfer a huge file over sftp ... but it stalled instantly.

Is this problem known? Any ideas how to fix it? Anyone is succesfully using USB, whats your setup?

Thanks in advance,

Freezer


The Log:


usb 1-1: new high speed USB device using ar71xx-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 0:0:0:0: Direct-Access SanDisk Cruzer 8.02 PQ: 0 ANSI: 0 CCS
sd 0:0:0:0: [sda] 31301631 512-byte hardware sectors (16026 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 45 00 00 08
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 31301631 512-byte hardware sectors (16026 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 45 00 00 08
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: unknown partition table
sd 0:0:0:0: [sda] Attached SCSI removable disk
scsi 0:0:0:1: CD-ROM SanDisk Cruzer 8.02 PQ: 0 ANSI: 0
usb-storage: device scan complete
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
usb 1-1: reset high speed USB device using ar71xx-ehci and address 2
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/64, error -145
usb 1-1: reset high speed USB device using ar71xx-ehci and address 2
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/64, error -145
usb 1-1: reset high speed USB device using ar71xx-ehci and address 2
usb 1-1: device descriptor read/8, error -145
usb 1-1: device descriptor read/8, error -145
usb 1-1: reset high speed USB device using ar71xx-ehci and address 2
usb 1-1: device descriptor read/8, error -145
usb 1-1: device descriptor read/8, error -145
sd 0:0:0:0: Device offlined - not ready after error recovery
sd 0:0:0:0: [sda] Result: hostbyte=0x05 driverbyte=0x00
end_request: I/O error, dev sda, sector 8
Buffer I/O error on device sda, logical block 1
lost page write due to I/O error on sda
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
Buffer I/O error on device sda, logical block 1469
lost page write due to I/O error on sda
sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sda, sector 7664
Buffer I/O error on device sda, logical block 958
lost page write due to I/O error on sda
Buffer I/O error on device sda, logical block 959
lost page write due to I/O error on sda
usb 1-1: USB disconnect, address 2
usb 1-1: new high speed USB device using ar71xx-ehci and address 3
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/64, error -145
usb 1-1: new high speed USB device using ar71xx-ehci and address 4
EXT3-fs error (device sda): ext3_get_inode_loc: unable to read inode block - inode=2, block=959
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT3-fs error (device sda) in ext3_reserve_inode_write: IO failure
------------[ cut here ]------------
WARNING: at fs/buffer.c:1186 ()
Modules linked in: fuse pl2303 ark3116 gpio_buttons input_polldev usb_storage usbserial snd_usb_audio snd_usb_lib ohci_hcd ath_pci wlan_xauth wlan_wep wlan_tkip wlan_ccmp wlan_acl ath_rate_minstrel ath_hal(P) wlan_scan_sta wlan_scan_ap wlan input_core ip6t_REJECT ip6t_LOG ip6t_IMQ ip6t_HL ip6t_rt ip6t_hbh ip6t_mh ip6t_ipv6header ip6t_hl ip6t_frag ip6t_eui64 ip6t_ah ip6table_raw ip6table_mangle ip6table_filter ip6_tables nf_conntrack_ipv6 ebt_vlan ebt_ulog ebt_stp ebt_snat ebt_redirect ebt_pkttype ebt_nflog ebt_mark_m ebt_mark ebt_log ebt_limit ebt_ip ebt_dnat ebt_arpreply ebt_arp ebt_among ebt_802_3 ebtable_nat ebtable_filter ebtable_broute ebtables nf_nat_snmp_basic nf_nat_sip nf_conntrack_sip nf_nat_rtsp nf_conntrack_rtsp nf_nat_pptp nf_conntrack_pptp nf_nat_h323 nf_conntrack_h323 nf_nat_proto_gre nf_conntrack_proto_gre nf_nat_tftp nf_conntrack_tftp nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_policy xt_esp ipt_ah ipt_TTL xt_MARK ipt_ECN xt_CLASSIFY ipt_ttl xt_time ipt_time xt_tcpmss xt_statistic xt_mark xt_length ipt_ecn xt_DSCP xt_dscp ipt_IMQ imq xt_string xt_layer7 ipt_ipp2p ipt_MASQUERADE iptable_nat nf_nat xt_NOTRACK xt_CONNMARK ipt_recent xt_helper xt_conntrack xt_connmark xt_connbytes xt_state nf_conntrack_ipv4 nf_conntrack ehci_hcd sd_mod ipt_REJECT xt_TCPMSS ipt_LOG xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables gpio_dev bonding sit ip6_tunnel ppp_mppe tunnel6 tunnel4 tun snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device snd_hwdep snd_page_alloc snd soundcore ppp_async ppp_generic slhc vfat fat ntfs hfsplus ext3 jbd ext2 ath9k nls_utf8 nls_koi8_r nls_iso8859_2 nls_iso8859_15 nls_iso8859_1 nls_cp850 nls_cp437 nls_cp1251 nls_cp1250 usbcore scsi_mod nls_base mac80211 cfg80211 ipv6 crc_ccitt sha1_generic md5 hmac des_generic arc4 aes_generic deflate ecb cbc crypto_hash cryptomgr crypto_blkcipher aead crypto_algapi
Call Trace:[<80066b24>][<80066b24>][<8007f444>][<80180e2c>][<8014ab8c>][<80180e2c>][<8017aa38>][<800abfd0>][<8007c5c4>][<80079438>][<80079438>][<8017fe6c>][<800794fc>][<8007c5c4>][<8007f5f0>][<802274a4>][<8007fbdc>][<800da050>][<8007bf38>][<80080234>][<8022764c>][<800f6620>][<800f2a40>][<c01f1894>][<c01f1878>][<80080268>][<c01f2678>][<c01f265c>][<c01f2524>][<8008028c>][<c01e7fd0>][<c01e7fc0>][<c01f25f0>][<c01f25c0>][<800da050>][<c01e80dc>][<c01e8074>][<800d40e8>][<c01e812c>][<800da050>][<c015f188>][<c01e5794>][<c01ebf3c>][<800edde8>][<800e2fcc>][<800da43c>][<800da418>][<800da050>][<800da4ec>][<800cdc48>][<800bde18>][<80068304>]
---[ end trace 49dcdf8557ef9fd4 ]---
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT3-fs error (device sda): ext3_get_inode_loc: unable to read inode block - inode=2, block=959
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT3-fs error (device sda) in ext3_reserve_inode_write: IO failure
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT3-fs error (device sda): ext3_get_inode_loc: unable to read inode block - inode=2, block=959
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT3-fs error (device sda) in ext3_reserve_inode_write: IO failure
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT3-fs error (device sda): ext3_get_inode_loc: unable to read inode block - inode=2, block=959
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT3-fs error (device sda) in ext3_reserve_inode_write: IO failure
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
Buffer I/O error on device sda, logical block 1901063
lost page write due to I/O error on sda
Aborting journal on device sda.
Buffer I/O error on device sda, logical block 1901056
lost page write due to I/O error on sda
usb 1-1: device descriptor read/64, error -145
ext3_abort called.
EXT3-fs error (device sda): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
usb 1-1: device descriptor read/64, error -145
usb 1-1: new high speed USB device using ar71xx-ehci and address 5
usb 1-1: device descriptor read/8, error -145
usb 1-1: device descriptor read/8, error -145
usb 1-1: new high speed USB device using ar71xx-ehci and address 6
usb 1-1: device descriptor read/8, error -145
usb 1-1: device descriptor read/8, error -145
hub 1-0:1.0: unable to enumerate USB device on port 1
usb 2-1: new full speed USB device using ar71xx-ohci and address 2
usb 2-1: device descriptor read/64, error -145
usb 2-1: device descriptor read/64, error -145
usb 2-1: new full speed USB device using ar71xx-ohci and address 3
Buffer I/O error on device sda, logical block 1901056
lost page write due to I/O error on sda
scsi 0:0:0:0: rejecting I/O to dead device
usb 2-1: device descriptor read/64, error -145
usb 2-1: device descriptor read/64, error -145
usb 2-1: new full speed USB device using ar71xx-ohci and address 4
usb 2-1: device descriptor read/8, error -145
usb 2-1: device descriptor read/8, error -145
usb 2-1: new full speed USB device using ar71xx-ohci and address 5
usb 2-1: device descriptor read/8, error -145
usb 2-1: device descriptor read/8, error -62
hub 2-0:1.0: unable to enumerate USB device on port 1
usb 1-1: new high speed USB device using ar71xx-ehci and address 7
usb 1-1: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 7
usb-storage: waiting for device to settle before scanning
scsi 1:0:0:0: Direct-Access SanDisk Cruzer 8.02 PQ: 0 ANSI: 0 CCS
sd 1:0:0:0: [sda] 31301631 512-byte hardware sectors (16026 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 45 00 00 08
sd 1:0:0:0: [sda] Assuming drive cache: write through
sd 1:0:0:0: [sda] 31301631 512-byte hardware sectors (16026 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 45 00 00 08
sd 1:0:0:0: [sda] Assuming drive cache: write through
sda: unknown partition table
sd 1:0:0:0: [sda] Attached SCSI removable disk
scsi 1:0:0:1: CD-ROM SanDisk Cruzer 8.02 PQ: 0 ANSI: 0
usb-storage: device scan complete
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
usb 1-1: reset high speed USB device using ar71xx-ehci and address 7
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/64, error -145
usb 1-1: reset high speed USB device using ar71xx-ehci and address 7

Just tested a 512MB stick with vfat.


It's interesting, it seems to work better, but still errors. I was able to read over 100MB from the stick and had only some reset errors (see log).

Then i was able to write about 20MB, and then got several resets in row again and directly after that a lot of more i/o errors.

But it seems to be a lot better than the 16GB stick anyway...how can that be?


Here the log for the 512MB:


usb 1-1: new high speed USB device using ar71xx-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 0:0:0:0: Direct-Access SanDisk Cruzer Mini 0.2 PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
usb-storage: device scan complete
yaffs: dev is 8388609 name is "sda1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.1, "sda1"
yaffs: dev is 8388609 name is "sda1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.1, "sda1"
usb 1-1: reset high speed USB device using ar71xx-ehci and address 2
usb 1-1: reset high speed USB device using ar71xx-ehci and address 2
usb 1-1: reset high speed USB device using ar71xx-ehci and address 2
usb 1-1: reset high speed USB device using ar71xx-ehci and address 2
usb 1-1: reset high speed USB device using ar71xx-ehci and address 2
usb 1-1: reset high speed USB device using ar71xx-ehci and address 2
usb 1-1: reset high speed USB device using ar71xx-ehci and address 2
sd 0:0:0:0: Device offlined - not ready after error recovery
sd 0:0:0:0: [sda] Result: hostbyte=0x05 driverbyte=0x00
end_request: I/O error, dev sda, sector 387663
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
sd 0:0:0:0: rejecting I/O to offline device
Buffer I/O error on device sda1, logical block 100
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 101
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 102
lost page write due to I/O error on sda1
sd 0:0:0:0: rejecting I/O to offline device
Buffer I/O error on device sda1, logical block 345
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 346
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 347
lost page write due to I/O error on sda1
sd 0:0:0:0: rejecting I/O to offline device
Buffer I/O error on device sda1, logical block 501
lost page write due to I/O error on sda1
sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sda, sector 387903
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 102)
sd 0:0:0:0: rejecting I/O to offline device
FAT: FAT read failed (blocknr 100)
sd 0:0:0:0: rejecting I/O to offline device
FAT: unable to read inode block for updating (i_pos 8028)

I made an very interesting observation:


I removed the kmod-usb2 and now using kmod-usb-ohci only (USB1.1).


Now I'm able to write/read large files, even with the 16GB stick without problems! So the problem seems to be with USB2 only.

I am on a Netgear WNDR3700 (also a AR71xx router) and was getting this same error.  Removing kmod-usb2 also worked to eliminate i/o errors when copying files.

Some configs may be running a bad max_sectors value for certain usb sticks.  I use a usb hard drive, which got a speed tweak when I maxed it out to 1024, but you may need to lower it for a usb stick, depending on its driver.  Then maybe you can do kmod-usb2 which gives you faster speeds than ohci.

If you need to commit the value for every reboot, you can add this line to /etc/sysctl.conf and reboot or run sysctl -p.
/sys/block/sda/device/max_sectors=xxxx (where xxxx is the value you find that works)


http://www.linux-usb.org/FAQ.html#i5
Q: What is max_sectors and how should I use it?

A:For USB Mass Storage devices (that is, devices which use the usb-storage driver) max_sectors controls the maximum amount of data that will be transferred to or from the device in a single command. As the name implies this transfer length is measured in sectors, where a sector is 512 bytes (that's a logical sector size, not necessarily the same as the size of a physical sector on the device). Thus for example, max_sectors = 240 means that a single command will not transfer more than 120 KB of data.

Linux 2.6 gives you the ability to see and to change the max_sectors value for each USB storage device, independently. Assuming you have a sysfs filesystem mounted on /sys and assuming /dev/sdb is a USB drive, you can see the max_sectors value for /dev/sdb simply by running:

        cat /sys/block/sdb/device/max_sectors

and you can set max_sectors to 64 by running (as root):

        echo 64 >/sys/block/sdb/device/max_sectors

Values should be positive multiples of 8 (16 on the Alpha and other 64-bit platforms). There is no upper limit, but you probably shouldn't make max_sectors much bigger than 2048 (corresponding to 1 MB, which is quite a lot).

In general, increasing max_sectors will improve throughput since it means that larger amounts of data can be transferred in a single command with no need for being split up among multiple commands. Of course this is subject to diminishing returns when max_sectors is very big. More importantly, it's true only up to a point. Many devices have limits on the amount of data they can transfer, and if you try to exceed that limit you will most likely crash the device.

The default value of 240 works well with most devices. If you're not running at USB 2.0's high speed (480 Mb/s) there's no reason to increase max_sectors. If you are running at high speed and your device can take it, feel free to go as high as you like. Note that with many devices there isn't much penalty for using a smaller-than-optimum value unless you set max_sectors to something really low! Go ahead and experiment to find what value works best with your hardware.

Some devices can only transfer 64 KB or less at a time. The most notable example is the suite of USB-IDE adapters made by Genesys Logic. According to their technical support staff transfers should be limited to 32 KB (max_sectors = 64), and usb-storage automatically sets max_sectors to this value when it detects a Genesys Logic device. However people have had no trouble using 64 KB transfers (max_sectors = 128), and that's what Windows uses. You can always increase the value above 64 using sysfs, but don't go beyond 128 as Genesys Logic devices are known to fail when transferring more than 64 KB.

(Last edited by robnitro on 20 Feb 2011, 20:56)

The discussion might have continued from here.