What's new

WD 2TB HDD disconnects every week

  • 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!

Algimantas

Occasional Visitor
Hello,

I have 2TB WD External desktop HDD. The file system that i'm using is EXT2.
On this HDD i run transmission daemon and store media files.
The problem is that every week 7-8days it becomes red in the UI (Says that it wasn't cleanly unmounted) and remounts as sdb1. I ran e2fsck multiple times but it always says that it's clean. I even forced the check but nothing changed
System log show this kind of magic
Code:
Oct 27 15:22:45 kernel: xhci_hcd 0000:00:0b.0: WARN: Stalled endpoint
Oct 27 15:22:48 kernel: xhci_hcd 0000:00:0b.0: ERROR: unexpected command completion code 0x11.
Oct 27 15:22:48 kernel: xhci_hcd 0000:00:0b.0: ERROR: unexpected command completion code 0x11.
Oct 27 15:22:49 kernel: usb 1-1: device not accepting address 2, error -22
Oct 27 15:22:49 kernel: xhci_hcd 0000:00:0b.0: ERROR: unexpected command completion code 0x11.
Oct 27 15:22:49 kernel: xhci_hcd 0000:00:0b.0: ERROR: unexpected command completion code 0x11.
Oct 27 15:22:49 kernel: usb 1-1: device not accepting address 2, error -22
Oct 27 15:22:49 kernel: xhci_hcd 0000:00:0b.0: ERROR: unexpected command completion code 0x11.
Oct 27 15:22:50 kernel: xhci_hcd 0000:00:0b.0: ERROR: unexpected command completion code 0x11.
Oct 27 15:22:50 kernel: usb 1-1: device not accepting address 2, error -22
Oct 27 15:22:50 kernel: xhci_hcd 0000:00:0b.0: ERROR: unexpected command completion code 0x11.
Oct 27 15:22:50 kernel: xhci_hcd 0000:00:0b.0: ERROR: unexpected command completion code 0x11.
Oct 27 15:22:50 kernel: usb 1-1: device not accepting address 2, error -22
Oct 27 15:22:50 kernel: usb 1-1: USB disconnect, address 2
Oct 27 15:22:50 kernel: sd 1:0:0:0: [sda] Unhandled error code
Oct 27 15:22:50 kernel: sd 1:0:0:0: [sda]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Oct 27 15:22:50 kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 27 80 18 10 00 00 08 00
Oct 27 15:22:50 kernel: end_request: I/O error, dev sda, sector 662706192
Oct 27 15:22:50 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #20709377: comm transmission-da: reading directory lblock 0
Oct 27 15:22:50 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:50 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #20709377: comm transmission-da: reading directory lblock 0
Oct 27 15:22:50 kernel: usb 1-1: new SuperSpeed USB device using xhci_hcd and address 2
Oct 27 15:22:50 kernel: xhci_hcd 0000:00:0b.0: WARN: short transfer on control ep
Oct 27 15:22:50 kernel: xhci_hcd 0000:00:0b.0: WARN: short transfer on control ep
Oct 27 15:22:50 kernel: xhci_hcd 0000:00:0b.0: WARN: short transfer on control ep
Oct 27 15:22:50 kernel: xhci_hcd 0000:00:0b.0: WARN: short transfer on control ep
Oct 27 15:22:50 kernel: force burst = 0.
Oct 27 15:22:50 kernel: xhci_hcd 0000:00:0b.0: WARN no SS endpoint bMaxBurst
Oct 27 15:22:50 kernel: scsi2 : usb-storage 1-1:1.0
Oct 27 15:22:50 rc_service: hotplug 6414:notify_rc restart_nasapps
Oct 27 15:22:50 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:51 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #83443713: comm hotplug: reading directory lblock 0
Oct 27 15:22:51 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:51 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #20709379: block 82837506: comm minidlna: unable to read itable block
Oct 27 15:22:51 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Oct 27 15:22:51 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:51 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:51 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #20709379: block 82837506: comm minidlna: unable to read itable block
Oct 27 15:22:51 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Oct 27 15:22:51 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:51 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:51 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #20709379: block 82837506: comm bdi-default: unable to read itable block
Oct 27 15:22:51 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:51 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #20709378: comm minidlna: reading directory lblock 0
Oct 27 15:22:51 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:51 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #20709379: block 82837506: comm minidlna: unable to read itable block
Oct 27 15:22:51 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Oct 27 15:22:51 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:51 kernel: EXT4-fs error (device sda1): ext4_read_block_bitmap:349: comm minidlna: Cannot read block bitmap - block_group = 0, block_bitmap = 1025
Oct 27 15:22:51 kernel: EXT4-fs error (device sda1): ext4_discard_preallocations:3811: comm minidlna: Error reading block bitmap for 0
Oct 27 15:22:51 kernel: scsi 2:0:0:0: Direct-Access     WD       Elements 107C    1065 PQ: 0 ANSI: 6
Oct 27 15:22:51 kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0
Oct 27 15:22:51 kernel: sd 2:0:0:0: [sdb] 3906963456 512-byte logical blocks: (2.00 TB/1.81 TiB)
Oct 27 15:22:51 kernel: xhci_hcd 0000:00:0b.0: WARN: Stalled endpoint
Oct 27 15:22:51 kernel: sd 2:0:0:0: [sdb] Write Protect is off
Oct 27 15:22:52 kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
Oct 27 15:22:52 kernel: xhci_hcd 0000:00:0b.0: WARN: Stalled endpoint
Oct 27 15:22:52 kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
Oct 27 15:22:52 iTunes: daemon is stopped
Oct 27 15:22:52 kernel:  sdb: sdb1
Oct 27 15:22:52 kernel: xhci_hcd 0000:00:0b.0: WARN: Stalled endpoint
Oct 27 15:22:52 kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
Oct 27 15:22:52 kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
Oct 27 15:22:52 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:52 hotplug[6415]: USB partition unmounted from /tmp/mnt/sda1 fail. (return -1, Device or resource busy)
Oct 27 15:22:52 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #20709379: block 82837506: comm bdi-default: unable to read itable block
Oct 27 15:22:53 FTP Server: daemon is stopped
Oct 27 15:22:53 Samba Server: smb daemon is stopped
Oct 27 15:22:53 kernel: gro disabled
Oct 27 15:22:53 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:53 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #83443713: comm sh: reading directory lblock 0
Oct 27 15:22:53 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:53 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #83443716: comm sh: reading directory lblock 0
Oct 27 15:22:53 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:22:53 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #83443713: comm sh: reading directory lblock 0
Oct 27 15:22:53 Timemachine: daemon is stopped
Oct 27 15:22:53 rc_service: hotplug 6415:notify_rc stop_nasapps
Oct 27 15:22:53 rc_service: waiting "restart_nasapps" via  ...
Oct 27 15:23:23 rc_service: skip the event: stop_nasapps.
Oct 27 15:23:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:23:23 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #83443716: comm sh: reading directory lblock 0
Oct 27 15:23:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:23:23 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #20709378: comm rm: reading directory lblock 0
Oct 27 15:23:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Oct 27 15:23:23 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #20709378: comm rm: reading directory lblock 0
Oct 27 15:23:24 syslog: USB partition unmounted from /tmp/mnt/sda1 fail. (return -1, Device or resource busy)
(20 more likes this log)
busy)
Oct 27 15:23:59 syslog: USB partition busy - will unmount ASAP from /tmp/mnt/sda1
Oct 27 15:23:59 rc_service: hotplug 6415:notify_rc restart_nasapps
Oct 27 15:23:59 iTunes: daemon is stopped
Oct 27 15:23:59 kernel: EXT4-fs (sdb1): warning: mounting unchecked fs, running e2fsck is recommended
Oct 27 15:23:59 hotplug[6452]: USB ext4 fs at /dev/sdb1 mounted on /tmp/mnt/sdb1
Oct 27 15:23:59 kernel: EXT4-fs (sdb1): mounted filesystem without journal. Opts: user_xattr
Oct 27 15:24:00 FTP Server: daemon is stopped
Oct 27 15:24:00 Samba Server: smb daemon is stopped
Oct 27 15:24:00 kernel: gro disabled
Oct 27 15:24:00 hotplug[6452]: USB partition unmounted from /tmp/mnt/sdb1
Oct 27 15:24:00 Timemachine: daemon is stopped
Oct 27 15:41:32 kernel: EXT4-fs (sdb1): warning: mounting unchecked fs, running e2fsck is recommended
Oct 27 15:41:32 hotplug[6452]: USB ext4 fs at /dev/sdb1 mounted on /tmp/mnt/sdb1
Oct 27 15:41:32 kernel: EXT4-fs (sdb1): mounted filesystem without journal. Opts: user_xattr
Oct 27 15:41:34 admin:  sh /opt/S95transmission.1 start
Oct 27 15:41:34 rc_service: hotplug 6452:notify_rc restart_nasapps
Oct 27 15:41:34 iTunes: daemon is stopped
Oct 27 15:41:34 FTP Server: daemon is stopped
Oct 27 15:41:34 Samba Server: smb daemon is stopped
Oct 27 15:41:34 kernel: gro disabled
Oct 27 15:41:34 Timemachine: daemon is stopped

Does anyone know what is going on and how can I solve it?

Thanks
 
Try a different USB cable. If it still fails, try running a full surface scan of the disk to ensure it's not defective. I see a lot of read errors in that log.
 
Try a different USB cable. If it still fails, try running a full surface scan of the disk to ensure it's not defective. I see a lot of read errors in that log.
Ok so I did the surface scan with Hdtune software. The disk is completely fine, no bad blocks detected. So I guess it has something to do with the router itself.
In my previous post I forgot to mention that i'm using johns fork as my router fw

Sent from my D6503 using Tapatalk
 

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