My RN102 (just upgraded to OS 6.1.1) has two internal 1TB drives and one 2TB USB3 external drive formatted with NTFS.
If I plug in the external drive it is immediately recognized, device (sdc) created, and mounted. But when I reboot the RN102 with the USB drive still connected, it is not mounted even though it is connected and was mounted before the reboot. After such a reboot, if I briefly unplug the external drive and plug it in again, it mounts right up.
I see in dmesg.log [the timestamps are meaningless] during boot, right before finding the SATA drives:
[Mon Aug 26 15:32:44 2013] usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd [Mon Aug 26 15:32:44 2013] scsi4 : usb-storage 4-2:1.0
so it is creating the scsi4 device but not the sdX, and the drive is not mounted at this time. Then later in the boot I see:
[Mon Aug 26 15:32:44 2013] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd [Mon Aug 26 15:32:44 2013] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd [Mon Aug 26 15:32:44 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep d49a8ae0 [Mon Aug 26 15:32:44 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep d49a8b0c [Mon Aug 26 15:32:44 2013] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd [Mon Aug 26 15:32:44 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep d49a8ae0 [Mon Aug 26 15:32:44 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep d49a8b0c [Mon Aug 26 15:32:44 2013] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd [Mon Aug 26 15:32:44 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep d49a8ae0 [Mon Aug 26 15:32:44 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep d49a8b0c
and still nothing useful happens. Then, hours later, when I unplug the drive:
[Mon Aug 26 15:32:44 2013] usb 4-2: USB disconnect, device number 2
and then when I plug it in:
[Mon Aug 26 15:32:44 2013] usb 4-2: new SuperSpeed USB device number 3 using xhci_hcd [Mon Aug 26 15:32:44 2013] scsi5 : usb-storage 4-2:1.0 [Mon Aug 26 15:32:44 2013] scsi 5:0:0:0: Direct-Access Seagate GoFlex Desk 0D16 PQ: 0 ANSI: 5 [Mon Aug 26 15:32:44 2013] sd 5:0:0:0: [sdc] 3907029167 512-byte logical blocks: (2.00 TB/1.81 TiB)
... and then it mounts and is fine.
Others seeing this behavior? I am not seeing it listed as a known issue.
can you please post /run/setup_usb_storage.dbg-sdd1 for us? --enable SSH access in Dashboard(use admin passwor to log in shell) --cd /run --ls (check file name) --cat setup_usb_storage.dbg-sdd1(USB device name might not be the same as this)
I checked /run/setup_usb_storate.dbg-sdc1 and it contains only stuff written after I unplugged/replugged hours after the reboot - at which time as I said, it mounted up fine. (the boot was around 15:34, and I replugged the drive at 22:09). Contents of that file are pasted below. Judging from the logs posted previously it seems more likely it was not seen in the usb scan at boot. Unless anyone has some other ideas, I will find another chance to reboot and check this debug file again after that.
root@nas:/run# cat setup_usb_storage.dbg-sdc1
Mon Aug 26 22:09:21 2013 Setting up external storage device: sdc1 Getting UID for device sdc1 Returning WWN as UID: 5000C50037B7D6DC Got filesystem UUID: 74A89BF8A89BB6D8 Returning UID 5000C50037B7D6DC-74A89BF8A89BB6D83 Got description: Seagate ST2000DL003-9VT166 FS type from env is ntfs for sdc1 Trying ufsd mount of sdc1 with options -o noatime,nls=utf8,umask=0 Executing: mount -o noatime,nls=utf8,umask=0 -t ufsd /dev/sdc1 '/media/USB_HDD_1' Executing: mount -o noatime,nls=utf8,umask=0 -t ufsd /dev/sdc1 '/media/USB_HDD_1' mount_output= /dev/sdc1 on /media/USB_HDD_1 type ufsd (rw,noatime,nls=utf8,fmask=0,dmask=0)
Updating /etc/frontview/usb/storage.conf Adding 5000C50037B7D6DC-74A89BF8A89BB6D83!!USB_HDD_1!!Seagate ST2000DL003-9VT166!!3907029167!!1!!/dev/sdc1!!!!5000!!3:4 REMOVER = /var/run/usb/sdc1 Executing auxiliary scripts Updating backup LED status
3) the dmesg.log has these lines that seem relevant to the USB device:
[Thu Sep 12 22:31:53 2013] usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd [Thu Sep 12 22:31:53 2013] scsi4 : usb-storage 4-2:1.0
... then the SATA disks are discovered and raids come up etc ...
[Thu Sep 12 22:31:53 2013] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd [Thu Sep 12 22:31:53 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep c3058ae0 [Thu Sep 12 22:31:53 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep c3058b0c [Thu Sep 12 22:31:53 2013] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd [Thu Sep 12 22:31:53 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep c3058ae0 [Thu Sep 12 22:31:53 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep c3058b0c [Thu Sep 12 22:31:53 2013] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd [Thu Sep 12 22:31:53 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep c3058ae0 [Thu Sep 12 22:31:53 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep c3058b0c [Thu Sep 12 22:31:53 2013] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd [Thu Sep 12 22:31:53 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep c3058ae0 [Thu Sep 12 22:31:53 2013] xhci_hcd 0000:01:01.0: xHCI xhci_drop_endpoint called with disabled ep c3058b0c
Then, after I unplug and replug the USB3 cable, it is discovered and mounted as last time.
I have captured a full set of logfiles from after the reboot but before replugging, so let me know if there would be anything else interesting to look for.
Thanks for the update!can you please try front USB 2.0 port to see if the same issue will happen again? Base on the logs you provided,I searched it on Google and found a explaination
When you connect a USB device the kernel provides a 10ms delay for the device to initialize, then the kernel begins sending commands to the device.
The delay is hard coded into the kernel for USB2.0 devices, but for 3.0 devices the value is configurable and is provided by the device.
If the device does not provide the latency value for the kernel, the kernel will never send commands to the drive because it will wait forever.
The only way to fix this is to either get a different drive enclosure (yours is broken) or patch the kernel to use the default latency in USB3.0, which would be very difficult and possibly also break other things.
