USB drive going offline

[Sunny Jaisinghani]

Hello all,

I have a USB drive mounted on a linux RHEL 4 server which goes offline every now n then.

Here are some logs :
---------------------------------------------
[root@host ~]# lsusb
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 006: ID 0bc2:3101 Seagate RSS LLC
Bus 001 Device 002: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub"
Bus 001 Device 001: ID 0000:0000


Jul 4 18:40:02 host kernel: Device sde not ready.
Jul 4 18:40:02 host kernel: end_request: I/O error, dev sde, sector 12847
Jul 4 18:40:02 host kernel: EXT3-fs error (device sde1): ext3_find_entry: reading directory #2 offset 0
Jul 4 19:38:06 host kernel: Buffer I/O error on device sde, logical block 14
Jul 4 19:38:06 host kernel: Buffer I/O error on device sde, logical block 15
Jul 4 19:38:06 host kernel: Device sde not ready.
Jul 4 19:38:06 host kernel: end_request: I/O error, dev sde, sector 0
Jul 4 19:38:06 host kernel: Buffer I/O error on device sde, logical block 0

Device sde not ready.
end_request: I/O error, dev sde, sector 13711
Buffer I/O error on device sde1, logical block 1706
lost page write due to I/O error on sde1
Aborting journal on device sde1.
Device sde not ready.

Device sde not ready.
end_request: I/O error, dev sde, sector 12847
EXT3-fs error (device sde1): ext3_readdir: directory #2 contains a hole at offset 0
EXT3-fs warning (device sde1): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
EXT3-fs warning (device sde1): ext3_clear_journal_err: Marking fs in need of filesystem check.
EXT3 FS on sde1, internal journal
SELinux: initialized (dev sde1, type ext3), uses xattr

EXT3-fs error (device sde1) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device sde1) in ext3_dirty_inode: IO failure
EXT3-fs error (device sde1): ext3_journal_start_sb: Detected aborted journal

end_request: I/O error, dev sde, sector 12847
EXT3-fs error (device sde1): ext3_readdir: directory #2 contains a hole at offset 0

EXT3-fs error (device sde1): ext3_get_inode_loc: unable to read inode block - inode=4210689, block=8421378
Aborting journal on device sde1.


[root@host ~]# sfdisk -l /dev/sde

Disk /dev/sde: 121601 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/sde1 0+ 121600 121601- 976760001 83 Linux
/dev/sde2 0 - 0 0 0 Empty
/dev/sde3 0 - 0 0 0 Empty
/dev/sde4 0 - 0 0 0 Empty
[root@host ~]# fdisk -l /dev/sde

Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sde1 1 121601 976760001 83 Linux
[root@host ~]# fdisk -l /dev/sde1

Disk /dev/sde1: 1000.2 GB, 1000202241024 bytes
64 heads, 32 sectors/track, 953867 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sde1p1 1 953867 976759792 83 Linux
[root@host ~]#

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

I haven't tried anything yet. But planning to run a fsck and dd on this drive.

Will post the results.

Thanks

Sunny

[AnthonySN]

>>ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure

seems like it was ejected cleanly during the last mount

does the usb work fine in any windows box

[AnthonySN]

typo
not ejected cleanly

[Sunny Jaisinghani]

I don't think that the drive was removed in the recent past.
Haven't tested inserting into a windows box yet.
The drive is online now. but it goes offline very frequently.

I have a dd command runnning on the whole disk. Since it is a 1000GB disk, it is taking time to give me the results.

[Sunny Jaisinghani]

dd did not reveal any errors

# nohup dd if=/dev/sde of=/dev/null bs=1024k &

953869+1 records in
953869+1 records out

[Sunny Jaisinghani]

Tried fsck.....

What does the output mean

# fsck -pv /dev/sde1
fsck 1.35 (28-Feb-2004)
/dev/sde1: recovering journal
/dev/sde1 contains a file system with errors, check forced.
1297672 inodes used (1%)
9594 non-contiguous inodes (0.7%)
# of inodes with ind/dind/tind blocks: 86372/1832/4
68330390 blocks used (27%)
0 bad blocks
8 large files

1217621 regular files
79707 directories
0 character device files
0 block device files
0 fifos
1 link
335 symbolic links (334 fast symbolic links)
0 sockets

[Sunny Jaisinghani]

Syslog:


Jul 7 01:12:23 host kernel: kjournald starting. Commit interval 5 seconds
Jul 7 01:12:23 host kernel: EXT3 FS on sde1, internal journal
Jul 7 01:12:23 host kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 7 01:12:23 host kernel: SELinux: initialized (dev sde1, type ext3), uses xattr

[Sunny Jaisinghani]

Any help would be appreciated