Errors in syslog since 384.10_2 upgrade

[Nick McCulloch]

I have the RT-AC5300 router and have just upgraded to latest firmware.
The log has the following errors that I havent seen before:

Jan 31 10:12:19 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #524290: block 8388640: comm minidlna: unable to read itable block
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #524290: block 8388640: comm minidlna: unable to read itable block
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2004: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #524290: block 8388640: comm minidlna: unable to read itable block
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #524289: comm minidlna: reading directory lblock 0
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #524291: block 8388640: comm minidlna: unable to read itable block
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #524290: block 8388640: comm minidlna: unable to read itable block
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #524290: block 8388640: comm minidlna: unable to read itable block
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2004: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #524290: block 8388640: comm minidlna: unable to read itable block
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #524290: block 8388640: comm minidlna: unable to read itable block
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #524290: block 8388640: comm minidlna: unable to read itable block
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2004: IO failure
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #524290: block 8388640: comm minidlna: unable to read itable block
Jan 31 10:12:19 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Jan 31 10:12:20 kernel: journal commit I/O error
Jan 31 10:12:20 kernel: EXT4-fs error (device sda1): ext4_put_super:720: Couldn't clean up the journal
Jan 31 10:12:20 kernel: EXT4-fs (sda1): Remounting filesystem read-only
May 5 06:05:25 Mastiff: init
May 5 06:05:27 Mastiff: init
May 5 06:05:25 Mastiff: init
May 5 06:05:28 Mastiff: init


Should I be concerned? Is there something I should do?

Nick

 

[L&LD]

Do you have a USB drive attached to the router's USB port?

 

[Nick McCulloch]

No nothing is attached . There "was" a USB disc attached a while ago , but I had to remove it. Would that be the cause? If so, how do I remove these errors etc?

 

[dave14305]

No nothing is attached . There "was" a USB disc attached a while ago , but I had to remove it. Would that be the cause? If so, how do I remove these errors etc?

A while ago as in January? Those log messages are old.

 

[Nick McCulloch]

Oops .. so they are !! Just shows how often I check my logs !!!

 

[corgan2222]

did you find a solution? im on the same problem.
https://www.snbforums.com/threads/remote-logging-sometimes-broken.56361/