4TB Seagate Expansion

[fwfreak]

I have a quick question about my external USB 4TB Seagate Expansion disk.

I'm running Merlin's latest build 374.41 stable, on an ASUS RT-68U. The external drive I have works fine on all machines I plug it into.

The weird thing is that when I first plug it into the router, I get these errors:

Apr 28 14:37:32 kernel: usb 3-1: new full speed USB device using ohci_hcd and address 35
Apr 28 14:37:32 kernel: usb 3-1: device descriptor read/64, error -62
Apr 28 14:37:32 rc_service: hotplug 13117:notify_rc restart_nasapps
Apr 28 14:37:32 rc_service: waitting "restart_nasapps" via  ...
Apr 28 14:37:32 iTunes: daemon is stoped
Apr 28 14:37:32 FTP Server: daemon is stoped
Apr 28 14:37:32 kernel: usb 3-1: device descriptor read/64, error -62
Apr 28 14:37:32 kernel: usb 3-1: new full speed USB device using ohci_hcd and address 36
Apr 28 14:37:33 kernel: usb 3-1: device descriptor read/64, error -62
Apr 28 14:37:33 kernel: usb 3-1: device descriptor read/64, error -62
Apr 28 14:37:33 kernel: usb 3-1: new full speed USB device using ohci_hcd and address 37
Apr 28 14:37:33 kernel: usb 3-1: device not accepting address 37, error -62

The USB 3.0 light does not come on and the router obviously doesn't see the drive and the log alternates between usb: 2-1 and usb: 3-1, but after several attempts and timing it just right it will finally read the drive and log this:

Apr 28 14:37:52 kernel: usb 1-1: new SuperSpeed USB device using xhci_hcd and address 2
Apr 28 14:37:52 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 28 14:37:52 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 28 14:37:52 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 28 14:37:52 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 28 14:37:52 kernel: force burst = 0.
Apr 28 14:37:52 kernel: xhci_hcd 0000:00:0c.0: WARN no SS endpoint bMaxBurst
Apr 28 14:37:52 kernel: scsi4 : usb-storage 1-1:1.0
Apr 28 14:37:53 kernel: scsi 4:0:0:0: Direct-Access     Seagate  Expansion Desk   0739 PQ: 0 ANSI: 6
Apr 28 14:37:53 kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0
Apr 28 14:37:53 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 28 14:37:53 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 28 14:37:53 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 28 14:37:58 kernel: sd 4:0:0:0: [sdb] Spinning up disk...
Apr 28 14:37:58 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 28 14:37:59 kernel: .ready
Apr 28 14:37:59 kernel: sd 4:0:0:0: [sdb] 976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
Apr 28 14:37:59 kernel: sd 4:0:0:0: [sdb] Write Protect is off
Apr 28 14:37:59 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Apr 28 14:37:59 kernel: sd 4:0:0:0: [sdb] 976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
Apr 28 14:37:59 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Apr 28 14:37:59 kernel:  sdb: sdb1 sdb2
Apr 28 14:37:59 kernel: sd 4:0:0:0: [sdb] 976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
Apr 28 14:37:59 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Apr 28 14:37:59 kernel: sd 4:0:0:0: [sdb] Attached SCSI disk
Apr 28 14:37:59 hotplug[13372]: USB /dev/sdb2(ntfs) failed to mount at the first try!
Apr 28 14:38:02 kernel: ufsd: sdb2 is mounted as NTFS (without journal)
Apr 28 14:38:02 hotplug[13372]: USB ntfs fs at /dev/sdb2 mounted on /tmp/mnt/######

Is this a weird spin up timing issue? It looks like its having a hard time deciding which hcd to use ohci (full speed in first box) or xhci (super speed above).

I have a small usb stick in the usb 2.0 port for traffic logs and this drive plugged into the usb 3.0 port. I've tried the obvious stuff like reformatting into ext3, ntfs, repartitioning, etc. . . it shows this behavior no matter the file system format.

This will be a major PITA to deal with on every router reboot.
Any way to remedy this?

Thanks.

 

[RMerlin]

Make sure you don't have the "Reducing USB 3.0 interference" option enabled under Wireless -> Professional (under the 2.4 GHz band).

If you still have issues, try a different USB cable.

 

[JEWBSV]

Connect multiple cables USB 3.0, HDD connected to another router AC68U. The result is zero. USB 3.0 interference disabled. 3TB HDD using Seagete
http://www.seagate.com/ca/en/extern...hard-drives/backup-plus-desk-mac-thunderbolt/

 

[fwfreak]

Make sure you don't have the "Reducing USB 3.0 interference" option enabled under Wireless -> Professional (under the 2.4 GHz band).

If you still have issues, try a different USB cable.

Yeah I do have that disabled under the 2.4Ghz wireless. It has done this with it enabled and disabled. I highly doubt it's the cable because it is brand new and it works fine on all other computers, besides I don't have any others with that unique connector on the enclosure side.

 

[RMerlin]

I don't know if it's also the case for this specific product, but I've had many bad experiences with Seagate's external drives with my customers (and internal as well, but for different reasons). One customer had his Seagate HDD constantly dropping from his server during backups (replaced it with a Vantec enclosure), and another had to plug his Seagate HDD at the back of his PC because the front connectors would also be unstable.

The cable provided by Seagate with these two HDD seemed to be very poorly shielded when I examined them.

Personally, I recommend looking either at WD, or using a Vantec enclosure with a standard WD hard disk in it. Those are what gave me the most stable results.

 

[fwfreak]

I don't know if it's also the case for this specific product, but I've had many bad experiences with Seagate's external drives with my customers (and internal as well, but for different reasons). One customer had his Seagate HDD constantly dropping from his server during backups (replaced it with a Vantec enclosure), and another had to plug his Seagate HDD at the back of his PC because the front connectors would also be unstable.

The cable provided by Seagate with these two HDD seemed to be very poorly shielded when I examined them.

Personally, I recommend looking either at WD, or using a Vantec enclosure with a standard WD hard disk in it. Those are what gave me the most stable results.

For what its worth I did find a different cable to try that came with a wd passport I had that I forgot was usb 3.0. It worked flawlessly the first time I plugged it in, but upon unmount and reattach it did the same thing. Its got to be something weird with the enclosure or something then. I may pull the physical drive out of the seagate enclosure and put it in something else if possible.

Thanks for the feedback Merlin.

 

[Il Anso]

I got my AC-68 last Sep. Have never been able to successfully connect to usb 3.0. I am now on 3.0.0.4.378.50_0. My interference option says "disable". Tried a 320 GB drive in a Sabrent sleeve and a 1 TB one in a StarTech sleeve; both unsuccessful with 2 different cables. Works (in 2.0 mode) when plugging a USB 2 cable in the USB 3 port of the router or when plugging the 3.0 cable in the USB 2 port. Both sleeves are independently powered.
The log says:
~~~~~~~~~~~~~~~~~~~~
Mar 18 17:27:22 kernel: usb 2-1: new high speed USB device using ehci_hcd and address 10
Mar 18 17:27:38 kernel: usb 2-1: device descriptor read/64, error -110
Mar 18 17:27:53 kernel: usb 2-1: device descriptor read/64, error -110
Mar 18 17:27:53 kernel: usb 2-1: new high speed USB device using ehci_hcd and address 11
Mar 18 17:28:08 kernel: usb 2-1: device descriptor read/64, error -110
Mar 18 17:28:23 kernel: usb 2-1: device descriptor read/64, error -110
Mar 18 17:28:24 kernel: usb 2-1: new high speed USB device using ehci_hcd and address 12
Mar 18 17:28:34 kernel: usb 2-1: device not accepting address 12, error -110
Mar 18 17:28:34 kernel: usb 2-1: new high speed USB device using ehci_hcd and address 13
Mar 18 17:28:45 kernel: usb 2-1: device not accepting address 13, error -110
Mar 18 17:28:45 kernel: hub 2-0:1.0: unable to enumerate USB device on port 1
Mar 18 17:28:45 kernel: usb 3-1: new full speed USB device using ohci_hcd and address 10
Mar 18 17:29:00 kernel: usb 3-1: device descriptor read/64, error -110
Mar 18 17:29:15 kernel: usb 3-1: device descriptor read/64, error -110
Mar 18 17:29:16 kernel: usb 3-1: new full speed USB device using ohci_hcd and address 11
Mar 18 17:29:31 kernel: usb 3-1: device descriptor read/64, error -110
Mar 18 17:29:46 kernel: usb 3-1: device descriptor read/64, error -110
Mar 18 17:29:46 kernel: usb 3-1: new full speed USB device using ohci_hcd and address 12
Mar 18 17:29:57 kernel: usb 3-1: device not accepting address 12, error -110
Mar 18 17:29:57 kernel: usb 3-1: new full speed USB device using ohci_hcd and address 13
Mar 18 17:30:07 kernel: usb 3-1: device not accepting address 13, error -110
Mar 18 17:30:07 kernel: hub 3-0:1.0: unable to enumerate USB device on port 1
~~~~~~~~~~~~~~~~~~~~
When it works (in USB 2 mode), I get:
~~~~~~~~~~~~~~~~~~~~~
Mar 18 18:31:59 kernel: tntfs info: NTFS volume name 'ASUS_NASp', version 3.1 (cluster_size 4096, PAGE_CACHE_SIZE 4096).
Mar 18 18:32:00 syslog: USB ntfs fs at /dev/sda1 mounted on /tmp/mnt/ASUS_NAS
~~~~~~~~~~~~~~~~~~~~~
There was only one instance when I briefly got:
~~~~~~~~~~~~~~~~~~~~~~
Mar 18 16:33:58 kernel: usb 1-1: new SuperSpeed USB device using xhci_hcd and address 2
Mar 18 16:33:59 kernel: scsi 4:0:0:0: Direct-Access WDC WD32 00AAJS-41VWA0 58.0 PQ: 0 ANSI: 0
Mar 18 16:35:05 kernel: ohci_hcd 0000:00:0b.0: USB bus 3 deregistered
Mar 18 16:35:06 kernel: xhci_hcd 0000:00:0c.0: xHCI Host Controller
Mar 18 16:35:06 kernel: xhci_hcd 0000:00:0c.0: new USB bus registered, assigned bus number 1
Mar 18 16:35:06 kernel: xhci_hcd 0000:00:0c.0: irq 112, io mem 0x18023000
Mar 18 16:35:06 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
Mar 18 16:35:06 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Mar 18 16:35:06 kernel: usb usb1: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values
~~~~~~~~~~~~~~~~~~~~~~
but the connection broke in seconds.
Any ideas?
Thanks in advance

 

[MRxROBOT]

I appear to be having more or less the same issue Il Anso

Did you find a fix?