What's new

External HDD mounting issues

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

utamav

Regular Contributor
I recently lost an external HDD during a router upgrade. So I bought another drive to replace it. My previous drive was Seagate 3TB with external power. I also have a 4TB WD (older model) with external power. Since WD was working flawlessly my replacement drive is 4TB WD (newer model) with external power.

Now the newer 4TB WD won't mount in either port.

These are the syslogs:

Jul 23 21:58:13 kernel: usb 2-2: new high speed USB device using ehci_hcd and address 4
Jul 23 21:58:13 kernel: scsi4 : usb-storage 2-2:1.0
Jul 23 21:58:14 kernel: scsi 4:0:0:0: Direct-Access WD My Book 25EE 4004 PQ: 0 ANSI: 6
Jul 23 21:58:14 kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0
Jul 23 21:58:14 kernel: scsi 4:0:0:1: Enclosure WD SES Device 4004 PQ: 0 ANSI: 6
Jul 23 21:58:14 kernel: sd 4:0:0:0: [sdb] Spinning up disk...
Jul 23 21:58:14 kernel: scsi 4:0:0:1: Attached scsi generic sg3 type 13
Jul 23 21:58:21 kernel: .......ready
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] 7814035456 512-byte logical blocks: (4.00 TB/3.63 TiB)
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] 4096-byte physical blocks
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] Write Protect is off
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Jul 23 21:58:21 kernel: sdb: sdb1
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] Attached SCSI disk
Jul 23 21:58:21 hotplug[17854]: USB /dev/sdb1(unknown) failed to mount at the first try!
Jul 23 21:58:21 usb: USB /dev/sdb1(unknown) failed to mount At the first try!
Jul 23 21:58:21 kernel: tfat: fail_safe is enabled
Jul 23 21:58:21 kernel: tntfs info (device sdb1, pid 17862): ntfs_fill_super(): fail_safe is enabled​

Does this mean that the device is too big?
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
 
Does this mean that the device is too big?
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
That message does not indicate a problem. You can see that the disk is attached:
Jul 23 21:58:21 kernel: sd 4:0:0:0: [sdb] Attached SCSI disk

Try reformatting the drive as it looks to be having trouble mounting it. There seems to be a problem with some drives, if possible use ext4 instead of NTFS.

https://www.snbforums.com/threads/p...on-rt-ac68u-with-asuswrt-merlin-380-59.33217/
 
All my drives were working fine until now. The one connected to the USB 2.0 port is not being detected by the router. I've tried rebooting the router and also re-plugging the drive. Following is the log:

Sep 10 07:39:43 kernel: usb 2-2: new high speed USB device using ehci_hcd and address 2
Sep 10 07:39:43 kernel: scsi1 : usb-storage 2-2:1.0
Sep 10 07:39:44 kernel: scsi 1:0:0:0: Direct-Access WD My Book 1230 1065 PQ: 0 ANSI: 6
Sep 10 07:39:44 kernel: sd 1:0:0:0: Attached scsi generic sg2 type 0
Sep 10 07:39:44 kernel: scsi 1:0:0:1: Enclosure WD SES Device 1065 PQ: 0 ANSI: 6
Sep 10 07:39:44 kernel: scsi 1:0:0:1: Attached scsi generic sg3 type 13
Sep 10 07:42:44 kernel: sd 1:0:0:0: timing out command, waited 180s
Sep 10 07:43:01 rc_service: httpd 481:notify_rc restart_ftpsamba
Sep 10 07:43:01 FTP_Server: daemon is stopped
Sep 10 07:43:02 Samba_Server: smb daemon is stopped
Sep 10 07:43:02 kernel: gro disabled​

Then I keep getting this message:

Sep 10 07:45:44 kernel: sd 1:0:0:0: timing out command, waited 180s​
 
FYI, after previous issues, I formatted both my HDD as EXT4. Both my HDD are 4TB WD with external power source.
 
Some more logs:

Sep 10 07:57:44 kernel: sd 1:0:0:0: [sdb] READ CAPACITY failed
Sep 10 07:57:44 kernel: sd 1:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 10 07:57:44 kernel: sd 1:0:0:0: [sdb] Sense Key : Hardware Error [current]
Sep 10 07:57:44 kernel: sd 1:0:0:0: [sdb] ASC=0x30 <<vendor>> ASCQ=0x89
Sep 10 08:00:45 kernel: sd 1:0:0:0: timing out command, waited 180s
Sep 10 08:00:45 kernel: sd 1:0:0:0: [sdb] Test WP failed, assume Write Enabled
Sep 10 08:00:45 kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Sep 10 08:00:49 disk_monitor: Got SIGALRM...

I'm going to remove the drive from the port for now.
 
Your disk isn't responding properly to command. There could be a number of causes:

1) Bad sector causing the HDD to stall/ freeze for an extended period of time
2) Bad USB cable
3) If it's a bus-powered HDD that draws its power from the USB port, these can be very touchy, and seem to become worse over time. Best to use an HDD that has its own power supply.

I'd started first by doing a surface scan of the disk from a PC, and replacing the USB cable.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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