What's new

RT-AC66U 3TB USB Disk Problem

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

CCatz

New Around Here
I am attempting to use a 3TB hard-drive as storage on an AC66U router, but it always fails to work. The drive+enclosure fails in both MBR and GPT types with any partition layout (or lack thereof) on the router, but works fine on Windows 7 and Arch Linux.
I've also tried an 80 GB hard drive in the same enclosure; it seems to work fine.
From what I've read, this router should support large disks (even more so on Merlin firmware), so I'm not quite sure what's wrong. Any help would be appreciated.
The router is running ASUS Merlin 380.57_0. The HDD is a Seagate ST3000DM001 inside a MediaSonic HD6-SU3-BK (FEB13).
3 TB log (problem):
Code:
Feb 27 14:11:26 kernel: usb 1-1.2: new high speed USB device using ehci_hcd and address 7
Feb 27 14:11:26 kernel: usb 1-1.2: configuration #1 chosen from 1 choice
Feb 27 14:11:26 kernel: scsi4 : SCSI emulation for USB Mass Storage devices
Feb 27 14:11:36 kernel: scsi 4:0:0:0: Direct-Access  ST3000DM 001-1CH166  CC27 PQ: 0 ANSI: 2
Feb 27 14:11:36 kernel: sd 4:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
Feb 27 14:11:36 kernel: sd 4:0:0:0: [sda] 5860533165 512-byte hardware sectors (3000593 MB)
Feb 27 14:11:36 kernel: sd 4:0:0:0: [sda] Write Protect is off
Feb 27 14:11:36 kernel: sd 4:0:0:0: [sda] Assuming drive cache: write through
Feb 27 14:11:36 kernel: sd 4:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
Feb 27 14:11:36 kernel: sd 4:0:0:0: [sda] Assuming drive cache: write through
Feb 27 14:12:06 kernel:  sda:<6>usb 1-1.2: reset high speed USB device using ehci_hcd and address 7
Feb 27 14:12:38 kernel: usb 1-1.2: reset high speed USB device using ehci_hcd and address 7
Feb 27 14:13:09 kernel: usb 1-1.2: reset high speed USB device using ehci_hcd and address 7
Feb 27 14:13:41 kernel: usb 1-1.2: reset high speed USB device using ehci_hcd and address 7
Feb 27 14:14:12 kernel: usb 1-1.2: reset high speed USB device using ehci_hcd and address 7
Feb 27 14:14:43 kernel: usb 1-1.2: reset high speed USB device using ehci_hcd and address 7
Feb 27 14:14:45 kernel: sd 4:0:0:0: [sda] Result: hostbyte=0x05 driverbyte=0x00
Feb 27 14:14:45 kernel: end_request: I/O error, dev sda, sector 0
Feb 27 14:14:45 kernel: printk: 286 messages suppressed.
Feb 27 14:14:45 kernel: Buffer I/O error on device sda, logical block 0
Feb 27 14:14:45 kernel: Buffer I/O error on device sda, logical block 1
Feb 27 14:14:45 kernel: Buffer I/O error on device sda, logical block 2
Feb 27 14:14:45 kernel: Buffer I/O error on device sda, logical block 3
Feb 27 14:14:45 kernel: Buffer I/O error on device sda, logical block 4
Feb 27 14:14:45 kernel: Buffer I/O error on device sda, logical block 5
Feb 27 14:14:45 kernel: Buffer I/O error on device sda, logical block 6
Feb 27 14:14:45 kernel: Buffer I/O error on device sda, logical block 7
Feb 27 14:15:15 kernel: usb 1-1.2: reset high speed USB device using ehci_hcd and address 7
Feb 27 14:15:35 kernel: sd 4:0:0:0: [sda] Result: hostbyte=0x07 driverbyte=0x00
Feb 27 14:15:35 kernel: end_request: I/O error, dev sda, sector 0
Feb 27 14:15:35 kernel: Buffer I/O error on device sda, logical block 0
Feb 27 14:15:35 kernel: Buffer I/O error on device sda, logical block 1
Feb 27 14:15:35 kernel: Buffer I/O error on device sda, logical block 2
Feb 27 14:15:35 kernel: Buffer I/O error on device sda, logical block 3
Feb 27 14:15:35 kernel: Buffer I/O error on device sda, logical block 4
Feb 27 14:15:35 kernel: Buffer I/O error on device sda, logical block 5
Feb 27 14:15:35 kernel: Buffer I/O error on device sda, logical block 6
Feb 27 14:15:35 kernel: Buffer I/O error on device sda, logical block 7
Feb 27 14:15:35 kernel: usb 1-1.2: USB disconnect, address 7
Feb 27 14:15:35 kernel: sd 4:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
Feb 27 14:15:35 kernel: end_request: I/O error, dev sda, sector 0
Feb 27 14:15:35 kernel: Buffer I/O error on device sda, logical block 0
Feb 27 14:15:35 kernel: Buffer I/O error on device sda, logical block 1
Feb 27 14:15:35 kernel:  unable to read partition table
Feb 27 14:15:35 kernel: sd 4:0:0:0: [sda] Attached SCSI disk
Feb 27 14:15:35 kernel: sd 4:0:0:0: Attached scsi generic sg0 type 0
Feb 27 14:15:35 kernel: sd 4:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
Feb 27 14:15:35 kernel: end_request: I/O error, dev sda, sector 0
Feb 27 14:15:35 kernel: sd 4:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
Feb 27 14:15:35 kernel: end_request: I/O error, dev sda, sector 128
Feb 27 14:15:35 kernel: sd 4:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
Feb 27 14:15:35 kernel: end_request: I/O error, dev sda, sector 0
Feb 27 14:15:35 kernel: sd 4:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
Feb 27 14:15:35 kernel: end_request: I/O error, dev sda, sector 0
At around 14:11:50, traffic targeting the router (web-config, SSH) stops responding; other traffic through the router continues fine.
At around 14:15:25, all traffic through the router stops responding.
The hard-drive is unplugged at 14:15:35, at which point all traffic immediately resumes working as normal.


And if it helps, the working 80 GB log:
Code:
Feb 26 18:58:47 kernel: usb 1-1.2: new high speed USB device using ehci_hcd and address 4
Feb 26 18:58:47 kernel: usb 1-1.2: configuration #1 chosen from 1 choice
Feb 26 18:58:47 kernel: scsi11 : SCSI emulation for USB Mass Storage devices
Feb 26 18:58:52 kernel: scsi 11:0:0:0: Direct-Access  ST380013 AS  8.12 PQ: 0 ANSI: 2
Feb 26 18:58:52 kernel: sd 11:0:0:0: [sda] 156249997 512-byte hardware sectors (80000 MB)
Feb 26 18:58:52 kernel: sd 11:0:0:0: [sda] Write Protect is off
Feb 26 18:58:52 kernel: sd 11:0:0:0: [sda] Assuming drive cache: write through
Feb 26 18:58:52 kernel: sd 11:0:0:0: [sda] Assuming drive cache: write through
Feb 26 18:58:52 kernel:  sda: unknown partition table
Feb 26 18:58:52 kernel: sd 11:0:0:0: [sda] Attached SCSI disk
Feb 26 18:58:52 kernel: sd 11:0:0:0: Attached scsi generic sg0 type 0
Feb 26 18:58:52 kernel: kjournald starting.  Commit interval 5 seconds
Feb 26 18:58:52 kernel: EXT3 FS on sda, internal journal
Feb 26 18:58:52 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 26 18:58:52 hotplug[2397]: USB ext3 fs at /dev/sda mounted on /tmp/mnt/sda
Feb 26 18:58:52 usb: USB ext3 fs at /dev/sda mounted on /tmp/mnt/sda.
Feb 26 18:58:52 rc_service: hotplug 2397:notify_rc restart_nasapps
Feb 26 18:58:52 FTP Server: daemon is stopped
Feb 26 18:58:52 Samba Server: smb daemon is stopped
 
Have you tried formatting it with the router?
 
Have you tried formatting it with the router?
I've tried, but cannot. The SSH connection stops responding ~20-30 seconds after I connect the drive, and if I do anything that interfaces with it (`fdisk -l`, I think I tried) it instantly stops responding. This happens even if the drive is unformatted, with no partitions.
 
What filesytem/block size do you have on the 3tb drive, and can you post that log?
 
What filesytem/block size do you have on the 3tb drive, and can you post that log?

It's currently using ext3 with a 4 KiB block size. I've also tried NTFS and a 1GB ext3 (rest unpartitioned) partitions as well, with the same results.

Fdisk list from the Arch install.
Code:
fdisk -l /dev/sdb
Disk /dev/sdb: 2.7 TiB, 3000592980480 bytes, 5860533165 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 94989DAF-A533-48FC-A319-25D7B0E0CBFB

Device    Start        End    Sectors  Size Type
/dev/sdb1  2048 5860532223 5860530176  2.7T Linux filesystem

Ext3 partition log, if it helps: (The clock is wrong; "Jan 4" is today)
Code:
tune2fs -l /dev/sdb1
tune2fs 1.42.13 (17-May-2015)
Filesystem volume name:  backup
Last mounted on:  <not available>
Filesystem UUID:  a2e41375-f2f5-4f3f-b6be-56dcd53f758d
Filesystem magic number:  0xEF53
Filesystem revision #:  1 (dynamic)
Filesystem features:  has_journal ext_attr resize_inode dir_index filetype sparse_super large_file
Filesystem flags:  signed_directory_hash
Default mount options:  user_xattr acl
Filesystem state:  clean
Errors behavior:  Continue
Filesystem OS type:  Linux
Inode count:  183148544
Block count:  732566272
Reserved block count:  36628313
Free blocks:  721019417
Free inodes:  183148533
First block:  0
Block size:  4096
Fragment size:  4096
Reserved GDT blocks:  849
Blocks per group:  32768
Fragments per group:  32768
Inodes per group:  8192
Inode blocks per group:  512
Filesystem created:  Wed Jan  2 23:49:05 2008
Last mount time:  Fri Jan  4 18:14:35 2008
Last write time:  Fri Jan  4 18:41:31 2008
Mount count:  1
Maximum mount count:  -1
Last checked:  Wed Jan  2 23:49:05 2008
Check interval:  0 (<none>)
Lifetime writes:  2964 kB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:    256
Required extra isize:  28
Desired extra isize:  28
Journal inode:  8
Default directory hash:  half_md4
Directory Hash Seed:  f7109371-4395-46c7-af36-b68ac8b2e2d0
Journal backup:  inode blocks
 
I was able to solve this; turns out the HD6-SU3-BK enclosure itself is the problem. I bought another enclosure, and the router recognized it with the HDD no problem and is working fine now.
 

Sign Up For SNBForums Daily Digest

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