CentOS

Hey guys we're running CentOS Linux release 7.7.1908 (Core) and our external USB drives disconnect and get I/O errors after a few hours - a day or so at most. (depending on traffic????) The only solution is to fall back to: CentOS Linux (3.10.0-957.27.2.el7.x86_64) 7 (Core). Could this possibly be a hardware issue?


Dec 3 02:00:02 c5 kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc:4247: inode #236453889: block 1891631136: comm rsync: unable to read itable block
Dec 3 02:00:02 c5 kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc:4247: inode #236453889: block 1891631136: comm rsync: unable to read itable block
Dec 3 02:00:02 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 02:00:02 c5 kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc:4247: inode #236453889: block 1891631136: comm rsync: unable to read itable block
Dec 3 02:00:02 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 02:00:02 c5 kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc:4247: inode #236453889: block 1891631136: comm rsync: unable to read itable block
Dec 3 02:00:02 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 02:00:03 c5 kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc:4247: inode #236453889: block 1891631136: comm rsync: unable to read itable block
Dec 3 02:00:03 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 03:47:13 c5 kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc:4247: inode #236453889: block 1891631136: comm updatedb: unable to read itable block
Dec 3 03:47:13 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 03:47:13 c5 kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc:4247: inode #33226753: block 265814048: comm updatedb: unable to read itable block
Dec 3 03:47:13 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 03:47:13 c5 kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc:4247: inode #55640065: block 445120544: comm updatedb: unable to read itable block
Dec 3 03:47:13 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 03:47:13 c5 kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc:4247: inode #75104257: block 600834080: comm updatedb: unable to read itable block
Dec 3 03:47:13 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 03:47:13 c5 kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc:4247: inode #11: block 1989: comm updatedb: unable to read itable block
Dec 3 03:47:13 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 03:47:14 c5 kernel: EXT4-fs error (device sdb1): ext4_find_entry inode #125042699: comm updatedb: reading directory lblock 0
Dec 3 03:47:14 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 03:47:14 c5 kernel: EXT4-fs warning (device sdb1): __ext4_read_dirblock:903: error reading directory block (ino 133169985, block 0)
Dec 3 03:47:14 c5 kernel: EXT4-fs error (device sdb1): ext4_find_entry inode #125042699: comm updatedb: reading directory lblock 0
Dec 3 03:47:14 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 03:47:14 c5 kernel: EXT4-fs error (device sdb1): ext4_find_entry inode #125109373: comm updatedb: reading directory lblock 0
Dec 3 03:47:14 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 03:47:14 c5 kernel: EXT4-fs error (device sdb1): ext4_find_entry inode #125109373: comm updatedb: reading directory lblock 0
Dec 3 03:47:14 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 03:47:14 c5 kernel: EXT4-fs error (device sdb1): ext4_find_entry inode #125109373: comm updatedb: reading directory lblock 0
Dec 3 03:47:14 c5 kernel: EXT4-fs (sdb1): previous I/O error to superblock detected
Dec 3 03:47:14 c5 kernel: EXT4-fs warning (device sdb1): __ext4_read_dirblock:903: error reading directory block (ino 125239342, block 0)
Dec 3 03:47:14 c5 kernel: EXT4-fs warning (device sdb1): __ext4_read_dirblock:903: error reading directory block (ino 125239374, block 0)
Dec 3 03:47:14 c5 kernel: EXT4-fs warning (device sdb1): __ext4_read_dirblock:903: error reading directory block (ino 125239379, block 0)
Dec 3 08:21:25 c5 kernel: EXT4-fs (sdd1): warning: maximal mount count reached, running e2fsck is recommended
Dec 3 08:21:25 c5 kernel: EXT4-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
Dec 3 08:21:25 c5 kernel: EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: acl
Dec 3 08:21:25 c5 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: acl
Dec 3 08:21:26 c5 kernel: EXT4-fs (sdc1): recovery complete
Dec 3 08:21:26 c5 kernel: EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: acl

Have you checked the S.M.A.R.T. details of the drive to see if you are seeing any problems there?

Believe you can install the smartmontools and be able to view those details. That might be a good start to see whether you are having a possible hard drive failure.

Can USBs actually deal with traffic like that without developing "memory leaks" due to the read/edits/writes? (I don't know - hence the question).

Are you saying that it doesn't do this on the earlier kernel?

i always have problems with long USB connections and externals HDs

i don´t like it