RT-AC68 - System Logs; How to run e2fsck?

[ezflrouting]

RT-AC68R on FW 3.0.0.4.374_4561. Also tried Merlin's latest (non-alpha) build.

My WD 1TB USB 3.0 drive, formatted to EXT4 using MiniTool Home Partition Wizard, keeps being unmounted by the router. The sleep mode has been disabled via WD Drive Utility, HD's firmware is up to date, USB 3.0 Interference is Disabled on router, and even on Merlin's build, the sleep timer was set to 0 as well.

Here are two log snippets. The first is what I encounter from the router-forced unmount, and the bottom are some errors after the router is rebooted and drive becomes usable again.

If I run the disk check utility in Asus firmware, the drive results with the following:
/usr/sbin/app_fsck.sh: eval: line 1: fsck.ext4: not found

I need help troubleshooting, please...



[FIRST SNIPPET]:

Feb 26 23:28:54 rc_service: hotplug 2569:notify_rc restart_nasapps
Feb 26 23:28:54 hotplug[2571]: USB partition unmounted from /tmp/mnt/WD_1TB fail. (return -1, Device or resource busy)
Feb 26 23:28:54 rc_service: hotplug 2571:notify_rc stop_nasapps
Feb 26 23:28:54 rc_service: waitting "restart_nasapps" via ...
Feb 26 23:29:24 rc_service: skip the event: stop_nasapps.
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2004: IO failure
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2004: IO failure
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #106630317: comm minidlna: reading directory lblock 0
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106627074: block 106627074: comm minidlna: unable to read itable block
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:24 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2004: IO failure
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1): ext4_discard_preallocations:3804: comm minidlna: Error loading buddy information for 117
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2004: IO failure
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #106630383: block 106627280: comm minidlna: unable to read itable block
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 iTunes: daemon is stoped
Feb 26 23:29:25 FTP Server: daemon is stoped
Feb 26 23:29:25 kernel: end_request: I/O error, dev sda, sector 66504
Feb 26 23:29:25 kernel: Aborting journal on device sda1-8.
Feb 26 23:29:25 kernel: JBD2: I/O error detected when updating journal superblock for sda1-8.
Feb 26 23:29:25 kernel: journal commit I/O error
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 kernel: EXT4-fs error (device sda1): ext4_put_super:720: Couldn't clean up the journal
Feb 26 23:29:25 kernel: EXT4-fs (sda1): Remounting filesystem read-only
Feb 26 23:29:25 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 26 23:29:25 syslog: USB partition unmounted from /tmp/mnt/WD_1TB
Feb 26 23:29:25 rc_service: hotplug 2571:notify_rc restart_nasapps
Feb 26 23:29:25 rc_service: waitting "restart_nasapps" via ...
Feb 26 23:29:27 Samba Server: smb daemon is stoped
Feb 26 23:29:27 kernel: gro disabled
Feb 26 23:29:27 Timemachine: daemon is stoped
Feb 26 23:29:27 iTunes: daemon is stoped
Feb 26 23:29:27 FTP Server: daemon is stoped
Feb 26 23:29:27 Samba Server: smb daemon is stoped
Feb 26 23:29:27 kernel: gro disabled
Feb 26 23:29:27 Timemachine: daemon is stoped



[SECOND SNIPPET // rebooting shows this]

Dec 31 19:00:15 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Dec 31 19:00:15 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 31 19:00:15 kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Dec 31 19:00:15 kernel: EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
Dec 31 19:00:15 hotplug[536]: USB ext4 fs at /dev/sda1 mounted on /tmp/mnt/WD_1TB
Dec 31 19:00:15 kernel: EXT4-fs (sda1): recovery complete
Dec 31 19:00:15 kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: user_xattr


Thanks in advance.

 

[r00t4rd3d]

I know EXT4 is not compatible with the AC66, not sure about the 68 but can you try EXT3 on the drive and see if it works?

 

[Adamm]

I have my 500GB HDD formatted as EXT4 without issues.

Try in SSH;

umount /dev/sda1
e2fsck /dev/sda1

 

[vapochilled]

Can this issue be related?

http://forums.smallnetbuilder.com/showthread.php?p=113583#post113583