What's new

RT-AC68R EXT4-FS Error Logs? Drive won't wake up.

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

ezflrouting

Occasional Visitor
Running Merlin 3.0.0.4.374.39. Have a USB 3.0 WD My PassPort drive connected to the USB 3.0 port.

After so many hours (a day?), the router believes that the HD is asleep, and it can no longer be accessed from other devices on the network. Furthermore, the Network Map shows no HD connected, and the USB 3.0 light on the front of the router is no longer illuminated.

If I reboot the router, it appears again and functions.

I've updated the WD HD to its most recent firmware and also ran the WD Drive Utility to "disable" sleep mode.

In the router:

Wireless->Advanced->Reducing USB 3.0 interference is Disabled.
Tools->Other Settings->Disk Spindown = 0
....Exclude the following drives from spinning down [all unchecked]
...........I've even tried the "exclude spindown" with all three drives checked.

Here are some logs from the router, I am guessing that this is when the error occurs.

Any ideas? :confused::confused::confused:

Feb 19 10:06:44 kernel: usb 1-1: USB disconnect, address 2
Feb 19 10:06:45 rc_service: hotplug 13027:notify_rc restart_nasapps
Feb 19 10:06:45 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #106627073: comm hotplug: reading directory lblock 0
Feb 19 10:06:45 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:45 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #106627073: comm sh: reading directory lblock 0
Feb 19 10:06:45 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:45 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #106627076: comm sh: reading directory lblock 0
Feb 19 10:06:45 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:45 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #106627073: comm sh: reading directory lblock 0
Feb 19 10:06:46 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:46 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #172425218: block 172425218: comm minidlna: unable to read itable block
Feb 19 10:06:46 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 19 10:06:46 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:46 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:46 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #172425218: block 172425218: comm minidlna: unable to read itable block
Feb 19 10:06:46 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 19 10:06:46 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:46 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2004: IO failure
Feb 19 10:06:46 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:46 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:46 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #172425218: block 172425218: comm minidlna: unable to read itable block
Feb 19 10:06:46 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Feb 19 10:06:46 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:47 kernel: end_request: I/O error, dev sda, sector 61584
Feb 19 10:06:47 kernel: Aborting journal on device sda1-8.
Feb 19 10:06:47 kernel: JBD2: I/O error detected when updating journal superblock for sda1-8.
Feb 19 10:06:47 kernel: journal commit I/O error
Feb 19 10:06:47 kernel: EXT4-fs error (device sda1): ext4_discard_preallocations:3804: comm minidlna: Error loading buddy information for 3254
Feb 19 10:06:47 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:47 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #106627076: comm sh: reading directory lblock 0
Feb 19 10:06:47 iTunes: daemon is stoped
Feb 19 10:06:47 FTP Server: daemon is stoped
Feb 19 10:06:48 kernel: EXT4-fs error (device sda1): ext4_discard_preallocations:3804: comm hotplug: Error loading buddy information for 3254
Feb 19 10:06:48 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:48 kernel: EXT4-fs error (device sda1): ext4_put_super:720: Couldn't clean up the journal
Feb 19 10:06:48 kernel: EXT4-fs (sda1): Remounting filesystem read-only
Feb 19 10:06:48 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Feb 19 10:06:48 hotplug[13028]: USB partition unmounted from /tmp/mnt/WD_1TB
Feb 19 10:06:48 rc_service: hotplug 13028:notify_rc restart_nasapps
Feb 19 10:06:48 rc_service: waitting "restart_nasapps" via ...
Feb 19 10:06:49 Samba Server: smb daemon is stoped
Feb 19 10:06:49 kernel: gro disabled
Feb 19 10:06:49 Timemachine: daemon is stoped
Feb 19 10:06:49 kernel: gro enabled with interval 2
Feb 19 10:06:50 Samba Server: daemon is started
Feb 19 10:06:51 iTunes: daemon is stoped
Feb 19 10:06:51 FTP Server: daemon is stoped
Feb 19 10:06:53 Samba Server: smb daemon is stoped
Feb 19 10:06:53 kernel: gro disabled
Feb 19 10:06:53 Timemachine: daemon is stoped
Feb 19 10:06:53 kernel: gro enabled with interval 2
 
Last edited:
Similar threads

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top