[Armadillo:08001] Armadillo-440でUSBメモリ使用時に読込み専用となってしまう

[Kotaro MORI]

お世話になります森と申します。

Armadillo-440とUSBメモリを使って
随時データの保存を行なっています、
USBメモリは起動時に自動マウントを行い、
起動時にはrw属性でマウントを行なっています。

運用中にUSBメモリがリードオンリーとなってしまい困っています。

USBの構成は以下の通りです。
　USB2.0ポート：USBメモリ（バスパワーを使用）
　USB1.1ポート：USB機器（セルフパワー）

USBメモリは複数パーティションに分割し、
ext3でフォーマットを行なっています。

またUSBメモリの接続には延長ケーブルを使用しています。

ログの示す内容や今回の現象の原因等、
わかりましたらご教授頂けないでしょうか。
よろしくお願いいたします。

実行ログは次の通りです。
========================================
[email@hidden (ttyp1) /media/config]# dmesg
 block 0
RAMDISK: Loading 40960KiB [1 disk] into ram disk... done.
scsi 0:0:0:0: Direct-Access     Corsair  Voyager GT 3.0   0.00 PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 126162944 512-byte hardware sectors (64595 MB)
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 128K
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 126162944 512-byte hardware sectors (64595 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15 >
sd 0:0:0:0: [sda] Attached SCSI removable disk
usb-storage: device scan complete
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda10, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda11, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda13, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3 FS on sda14, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda12, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda15, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3 FS on sda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda9, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
fec: PHY @ 0x0, ID 0x0007c0f1 -- LAN8720
eth0: link down
eth0: link up, 100Mbps, full-duplex
########## (以下エラーログ) ##########
attempt to access beyond end of device
sda15: rw=17, want=825389808, limit=6150112
Buffer I/O error on device sda15, logical block 640044637
lost page write due to I/O error on sda15
Aborting journal on device sda15.
EXT3-fs error (device sda15) in ext3_reserve_inode_write: Journal has 
aborted
EXT3-fs error (device sda15) in ext3_dirty_inode: Journal has aborted
ext3_abort called.
EXT3-fs error (device sda15): ext3_journal_start_sb: Detected aborted 
journal
Remounting filesystem read-only
========================================