External USB drive keeps on disconnecting randomly

djgruby · 02-22-2014, 07:02 AM

Hello Linux users!

I have just registered on this forum seeking help for my problem with an external USB disk drive. Hopefully somebody would be able to assist me with troubleshooting and resolving the following issue.

I have just installed Fedora 20 on my brand new Dell XPS 13. Unfortunately, my external USB disk drive constantly disconnects and reconnects. Now, what is important, is that disconnection might happen both during a data transfer and when drive is idle.

Here are my device details as well as some basic info (if you need more information, please tell me what kind of data could be valuable):

Code:

# smartctl -i /dev/sdc
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.3-201.fc20.x86_64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus SpinPoint M8 (AF)
Device Model:     ST1000LM024 HN-M101MBB
Serial Number:    S2S6J9DD220733
LU WWN Device Id: 5 0004cf 209b1af87
Firmware Version: 2AR10001
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sat Feb 22 13:56:32 2014 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

# uname -a
Linux localhost.localdomain 3.13.3-201.fc20.x86_64 #1 SMP Fri Feb 14 19:08:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Here is an example output of a disconnection as encountered in the /var/log/messages file:

Code:

Feb 22 11:44:22 localhost kernel: [ 6283.144884] usb 3-2: USB disconnect, device number 9
Feb 22 11:44:27 localhost kernel: [ 6287.784334] usb 3-2: Disable of device-initiated U1 failed.
Feb 22 11:44:27 localhost kernel: [ 6288.287999] usb 3-2: device not accepting address 9, error -22
Feb 22 11:44:27 localhost kernel: [ 6288.345028] sd 11:0:0:0: [sdb] Unhandled error code
Feb 22 11:44:27 localhost kernel: [ 6288.345033] sd 11:0:0:0: [sdb]  
Feb 22 11:44:27 localhost kernel: [ 6288.345035] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Feb 22 11:44:27 localhost kernel: [ 6288.345038] sd 11:0:0:0: [sdb] CDB: 
Feb 22 11:44:27 localhost kernel: [ 6288.345039] Write(10): 2a 00 57 ea c2 c6 00 00 f0 00
Feb 22 11:44:27 localhost kernel: [ 6288.345048] end_request: I/O error, dev sdb, sector 1475003078
Feb 22 11:44:27 localhost kernel: [ 6288.345108] sd 11:0:0:0: [sdb] Unhandled error code
Feb 22 11:44:27 localhost kernel: [ 6288.345110] sd 11:0:0:0: [sdb]  
Feb 22 11:44:27 localhost kernel: [ 6288.345111] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Feb 22 11:44:27 localhost kernel: [ 6288.345113] sd 11:0:0:0: [sdb] CDB: 
Feb 22 11:44:27 localhost kernel: [ 6288.345114] Write(10): 2a 00 57 ea c3 b6 00 00 10 00
Feb 22 11:44:27 localhost kernel: [ 6288.345121] end_request: I/O error, dev sdb, sector 1475003318
Feb 22 11:44:27 localhost kernel: [ 6288.345132] quiet_error: 446 callbacks suppressed
Feb 22 11:44:27 localhost kernel: [ 6288.345134] Buffer I/O error on device dm-3, logical block 204
Feb 22 11:44:27 localhost kernel: [ 6288.345136] lost page write due to I/O error on dm-3
Feb 22 11:44:27 localhost kernel: [ 6288.345140] Buffer I/O error on device dm-3, logical block 205
Feb 22 11:44:27 localhost kernel: [ 6288.345141] lost page write due to I/O error on dm-3
Feb 22 11:44:27 localhost kernel: [ 6288.345459] Aborting journal on device dm-4-8.
Feb 22 11:44:27 localhost kernel: [ 6288.345460] Aborting journal on device dm-3-8.
Feb 22 11:44:27 localhost kernel: [ 6288.345473] Buffer I/O error on device dm-3, logical block 97656833
Feb 22 11:44:27 localhost kernel: [ 6288.345475] lost page write due to I/O error on dm-3
Feb 22 11:44:27 localhost kernel: [ 6288.345480] JBD2: Error -5 detected when updating journal superblock for dm-3-8.
Feb 22 11:44:27 localhost kernel: [ 6288.345496] Buffer I/O error on device dm-4, logical block 24395776
Feb 22 11:44:27 localhost kernel: [ 6288.345498] lost page write due to I/O error on dm-4
Feb 22 11:44:27 localhost kernel: [ 6288.345505] JBD2: Error -5 detected when updating journal superblock for dm-4-8.
Feb 22 11:44:27 localhost kernel: [ 6288.346628] sd 11:0:0:0: [sdb] Synchronizing SCSI cache
Feb 22 11:44:27 localhost kernel: [ 6288.346686] sd 11:0:0:0: [sdb]  
Feb 22 11:44:27 localhost kernel: [ 6288.346689] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Feb 22 11:44:27 localhost kernel: [ 6288.346764] EXT4-fs error (device dm-4) in ext4_init_inode_table:1299: IO failure
Feb 22 11:44:27 localhost kernel: [ 6288.346787] Buffer I/O error on device dm-4, logical block 0
Feb 22 11:44:27 localhost kernel: [ 6288.346789] lost page write due to I/O error on dm-4
Feb 22 11:44:27 localhost kernel: [ 6288.346941] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88021127ce00
Feb 22 11:44:27 localhost kernel: [ 6288.346948] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88021127ce40
Feb 22 11:44:27 localhost kernel: [ 6288.668132] usb 3-2: new SuperSpeed USB device number 10 using xhci_hcd
Feb 22 11:44:27 localhost kernel: [ 6288.679391] usb 3-2: New USB device found, idVendor=174c, idProduct=5106
Feb 22 11:44:27 localhost kernel: [ 6288.679395] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Feb 22 11:44:27 localhost kernel: [ 6288.679397] usb 3-2: Product: StoreJet Transcend
Feb 22 11:44:27 localhost kernel: [ 6288.679399] usb 3-2: Manufacturer: StoreJet Transcend
Feb 22 11:44:27 localhost kernel: [ 6288.679400] usb 3-2: SerialNumber: S2S6J9DD220733      
Feb 22 11:44:27 localhost kernel: [ 6288.681301] usb-storage 3-2:1.0: USB Mass Storage device detected
Feb 22 11:44:27 localhost kernel: [ 6288.682127] scsi12 : usb-storage 3-2:1.0
Feb 22 11:44:27 localhost mtp-probe: checking bus 3, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
Feb 22 11:44:27 localhost mtp-probe: bus: 3, device: 10 was not an MTP device
Feb 22 11:44:28 localhost kernel: [ 6289.683623] scsi 12:0:0:0: Direct-Access     StoreJet Transcend        0    PQ: 0 ANSI: 6
Feb 22 11:44:28 localhost kernel: [ 6289.684063] sd 12:0:0:0: Attached scsi generic sg1 type 0
Feb 22 11:44:28 localhost kernel: [ 6289.684887] sd 12:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 22 11:44:28 localhost kernel: [ 6289.685136] sd 12:0:0:0: [sdd] Write Protect is off
Feb 22 11:44:28 localhost kernel: [ 6289.685374] sd 12:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 22 11:44:29 localhost kernel: [ 6290.333235]  sdd: sdd1 sdd2 sdd3 sdd4 < sdd5 sdd6 sdd7 >
Feb 22 11:44:29 localhost kernel: [ 6290.334802] sd 12:0:0:0: [sdd] Attached SCSI disk
Feb 22 11:44:30 localhost kernel: [ 6290.949631] EXT4-fs error (device dm-1): __ext4_get_inode_loc:3909: inode #8126465: block 32505888: comm audacious: unable to read itable block
Feb 22 11:44:30 localhost kernel: [ 6290.949662] Buffer I/O error on device dm-1, logical block 0
Feb 22 11:44:30 localhost kernel: [ 6290.949664] lost page write due to I/O error on dm-1
Feb 22 11:44:30 localhost kernel: [ 6290.949797] EXT4-fs error (device dm-1): __ext4_get_inode_loc:3909: inode #8126465: block 32505888: comm audacious: unable to read itable block
Feb 22 11:44:30 localhost kernel: [ 6290.949800] EXT4-fs (dm-1): previous I/O error to superblock detected
Feb 22 11:44:30 localhost kernel: [ 6290.949816] Buffer I/O error on device dm-1, logical block 0
Feb 22 11:44:30 localhost kernel: [ 6290.949818] lost page write due to I/O error on dm-1
Feb 22 11:44:30 localhost kernel: [ 6290.949976] EXT4-fs error (device dm-1): __ext4_get_inode_loc:3909: inode #8126465: block 32505888: comm audacious: unable to read itable block
Feb 22 11:44:30 localhost kernel: [ 6290.949994] EXT4-fs (dm-1): previous I/O error to superblock detected
Feb 22 11:44:30 localhost kernel: [ 6290.950011] Buffer I/O error on device dm-1, logical block 0
Feb 22 11:44:30 localhost kernel: [ 6290.950013] lost page write due to I/O error on dm-1
Feb 22 11:44:30 localhost kernel: [ 6290.990778] EXT4-fs warning (device dm-1): __ext4_read_dirblock:1372: error reading directory block (ino 8388609, block 4)
Feb 22 11:44:30 localhost kernel: [ 6291.035726] EXT4-fs error (device dm-1): ext4_find_entry:1309: inode #131189: comm audacious: reading directory lblock 0
Feb 22 11:44:30 localhost kernel: [ 6291.035732] EXT4-fs (dm-1): previous I/O error to superblock detected
Feb 22 11:44:30 localhost kernel: [ 6291.035756] Buffer I/O error on device dm-1, logical block 0
Feb 22 11:44:30 localhost kernel: [ 6291.035758] lost page write due to I/O error on dm-1
Feb 22 11:44:30 localhost kernel: [ 6291.035820] EXT4-fs warning (device dm-1): __ext4_read_dirblock:908: error reading directory block (ino 131189, block 0)
Feb 22 11:44:30 localhost kernel: [ 6291.056463] EXT4-fs error (device dm-1): __ext4_get_inode_loc:3909: inode #4194305: block 16777248: comm audacious: unable to read itable block
Feb 22 11:44:30 localhost kernel: [ 6291.056469] EXT4-fs (dm-1): previous I/O error to superblock detected
Feb 22 11:44:30 localhost kernel: [ 6291.056492] Buffer I/O error on device dm-1, logical block 0
Feb 22 11:44:30 localhost kernel: [ 6291.056494] lost page write due to I/O error on dm-1
Feb 22 11:44:30 localhost kernel: [ 6291.056937] EXT4-fs error (device dm-1): __ext4_get_inode_loc:3909: inode #4194305: block 16777248: comm audacious: unable to read itable block
Feb 22 11:44:30 localhost kernel: [ 6291.056940] EXT4-fs (dm-1): previous I/O error to superblock detected
Feb 22 11:44:30 localhost kernel: [ 6291.089272] EXT4-fs error (device dm-1): __ext4_get_inode_loc:3909: inode #4194305: block 16777248: comm audacious: unable to read itable block
Feb 22 11:44:30 localhost kernel: [ 6291.089279] EXT4-fs (dm-1): previous I/O error to superblock detected
Feb 22 11:44:30 localhost kernel: [ 6291.144286] EXT4-fs error (device dm-1): __ext4_get_inode_loc:3909: inode #2883585: block 11534368: comm audacious: unable to read itable block
Feb 22 11:44:30 localhost kernel: [ 6291.144292] EXT4-fs (dm-1): previous I/O error to superblock detected
Feb 22 11:44:30 localhost kernel: [ 6291.144636] EXT4-fs error (device dm-1): __ext4_get_inode_loc:3909: inode #2883585: block 11534368: comm audacious: unable to read itable block
Feb 22 11:44:30 localhost kernel: [ 6291.144640] EXT4-fs (dm-1): previous I/O error to superblock detected
Feb 22 11:44:30 localhost kernel: [ 6291.150254] EXT4-fs error (device dm-1): __ext4_get_inode_loc:3909: inode #2883585: block 11534368: comm audacious: unable to read itable block
Feb 22 11:44:30 localhost kernel: [ 6291.150259] EXT4-fs (dm-1): previous I/O error to superblock detected
Feb 22 11:44:30 localhost kernel: [ 6291.163885] EXT4-fs (dm-1): previous I/O error to superblock detected
Feb 22 11:44:30 localhost kernel: [ 6291.189790] EXT4-fs warning (device dm-1): __ext4_read_dirblock:1372: error reading directory block (ino 8388609, block 4)
Feb 22 11:44:35 localhost kernel: [ 6296.250760] Aborting journal on device dm-1-8.
Feb 22 11:44:35 localhost kernel: [ 6296.250787] quiet_error: 17 callbacks suppressed
Feb 22 11:44:35 localhost kernel: [ 6296.250790] Buffer I/O error on device dm-1, logical block 24150016
Feb 22 11:44:35 localhost kernel: [ 6296.250792] lost page write due to I/O error on dm-1
Feb 22 11:44:35 localhost kernel: [ 6296.250818] JBD2: Error -5 detected when updating journal superblock for dm-1-8.

I have tried asking the same question on Fedora Forums one week ago, but no luck so far (nobody has even bothered to respond, so it might be a though one to tackle).

Please note that the drive works perfectly fine on my older laptop running Fedora 17, so I can instantly eliminate all suspicions about drive or cable defect. It must be something related to a USB 3.0 or a newer Kernel drivers, but I honestly have no clue where and what to look for.

Any ideas what is going on there? I would very much appreciate any help from you!

Many thanks in advance!

metaschima · 02-22-2014, 10:37 AM

First thing I would do is run a 'short' and 'conveyance' test on it using 'smartctl -t short' and 'smartctl -t conveyance'. Wait for each to finish and post 'smartctl -a /dev/sdd'. Running a 'long' test takes forever on external drives, so don't bother.

Is this drive USB 2.0 or 3.0 ? Does the older laptop use 2.0 ? Does the newer computer use 3.0 ?

Try pulling it into the black 2.0 ports on the newer computer, to try and eliminate controller driver issues.

harryhaller · 02-22-2014, 10:38 AM

do you have a USB 2.0 socket you can try it with?

djgruby · 02-22-2014, 11:59 AM

Thank you very much for your response.

Quote:

Is this drive USB 2.0 or 3.0 ? Does the older laptop use 2.0 ? Does the newer computer use 3.0 ?

This is a USB 3.0 drive. The older laptop used USB 2.0. The newer computer uses USB 3.0.

Quote:

Try pulling it into the black 2.0 ports on the newer computer, to try and eliminate controller driver issues.

Unfortunately, there are no USB 2.0 slots in this new computer, only two USB 3.0 slots.

Here we go with smart tests...

Code:

# smartctl -t short /dev/sdc
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.3-201.fc20.x86_64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 2 minutes for test to complete.
Test will complete after Sat Feb 22 18:48:49 2014

Use smartctl -X to abort test.

# smartctl -t conveyance /dev/sdc
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.3-201.fc20.x86_64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Conveyance Self-test functions not supported

Sending command: "Execute SMART Conveyance self-test routine immediately in off-line mode".
Command "Execute SMART Conveyance self-test routine immediately in off-line mode" failed: scsi error aborted command

# smartctl -a /dev/sdc
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.3-201.fc20.x86_64] (local build)                                                               
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org                                                                     

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus SpinPoint M8 (AF)
Device Model:     ST1000LM024 HN-M101MBB
Serial Number:    S2S6J9DD220733
LU WWN Device Id: 5 0004cf 209b1af87
Firmware Version: 2AR10001
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sat Feb 22 18:52:20 2014 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (13200) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 220) minutes.
SCT capabilities:              (0x003f) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   086   077   025    Pre-fail  Always       -       4452
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       762
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       1663
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       8
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       399
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       1
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   064   053   000    Old_age   Always       -       32 (Min/Max 17/47)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       223
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       8
225 Load_Cycle_Count        0x0032   097   097   000    Old_age   Always       -       36978

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      1663         -

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed [00% left] (0-65535)
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Does it give any hint about a problem?

metaschima · 02-22-2014, 12:03 PM

The HDD looks good, so I think it might be a problem with the USB 3.0 controller. Are you sure there are no USB 2.0 ports ? Because that would mean you cannot plug a printer into your new computer. USB 3.0 ports are usually blue, and USB 2.0 ones are black.

djgruby · 02-22-2014, 12:28 PM

Quote:

Originally Posted by metaschima

The HDD looks good, so I think it might be a problem with the USB 3.0 controller. Are you sure there are no USB 2.0 ports ? Because that would mean you cannot plug a printer into your new computer. USB 3.0 ports are usually blue, and USB 2.0 ones are black.

Glad to hear that HDD looks good. Yes, I am positively sure that there is no USB 2.0 port, just two USB 3.0 ports. That's confirmed by a laptop specification too.

metaschima · 02-22-2014, 12:59 PM

One of the ports in 3.0 and one is 2.0. Can you post the output of '/sbin/lspci -k'. This should list controllers and drivers used.

djgruby · 02-22-2014, 01:02 PM

Quote:

Originally Posted by metaschima

One of the ports in 3.0 and one is 2.0. Can you post the output of '/sbin/lspci -k'. This should list controllers and drivers used.

Sure. Here it is:

Code:

# /sbin/lspci -k
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
        Subsystem: Dell Device 060a
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)
        Subsystem: Dell Device 060a
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)
        Subsystem: Dell Device 060a
        Kernel driver in use: snd_hda_intel
00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
        Subsystem: Dell Device 060a
        Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 (rev 04)
        Subsystem: Dell Device 060a
        Kernel driver in use: mei_me
00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 04)
        Subsystem: Dell Device 060a
        Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 (rev e4)
        Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 (rev e4)
        Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
        Subsystem: Dell Device 060a
        Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
        Subsystem: Dell Device 060a
        Kernel driver in use: lpc_ich
00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 [AHCI mode] (rev 04)
        Subsystem: Dell Device 060a
        Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
        Subsystem: Dell Device 060a
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
        Subsystem: Intel Corporation Dual Band Wireless-AC 7260
        Kernel driver in use: iwlwifi

metaschima · 02-22-2014, 01:24 PM

Did you try the drive in both ports ? Try another USB cable as well, a high-quality short cable. I know even USB 2.0 HDDs disconnect with longer bad-quality cables. Or you can try a two-headed cable one for power and one for data, which might help.

I think there is only one controller, but it could be a driver issue.

If only there were a way to force it to use USB 2.0 for the HDD. Do you have any other USB 3.0 devices that you use ? You could try blacklisting the xhci driver, but that would prevent USB 3.0 devices from working.

djgruby · 02-22-2014, 01:28 PM

Yes, I have tried the drive in both ports. I will have to buy a high-quality short cable first before trying it.

Two-headed cable wouldn't work here, because both ports are located on the opposed sides of a laptop.

Yes, indeed, I have another USB 3.0 HDD, and this one is working perfectly fine. I absolutely agree that forcing this drive to somehow operate in a 2.0 mode would probably solve the issue. But I have no idea, how to make it.

metaschima · 02-22-2014, 01:50 PM

If the other USB 3.0 HDD works fine, then I don't think it is the controller. Try another cable first.

djgruby · 02-22-2014, 03:18 PM

Alright, now it seems like something interesting is happening. I have removed the other USB 3.0 drive from its slot. The previously disconnecting one is working stable so far. It has been running fine since two hours already. No breaks, no disconnection happened. So... I do not want to announce a success yet, but it seems like either this laptop or this Linux system simply cannot handle having two external disk drives connected and active at the same time. Let me wait a bit more and see if that is actually the case. Thanks!

metaschima · 02-22-2014, 03:39 PM

Sometimes, if you plug an external HDD in, then you plug another one in, the first disconnects. I'm not sure why it happens, but I have observed this. Usually it happens if the two HDDs are the same brand and type.

djgruby · 02-22-2014, 04:03 PM

Unfortunately, it is not that. The drive still disconnects, at least it has just now happened.

metaschima · 02-22-2014, 04:52 PM

Can you switch the cables, from the one that works to the one that disconnects ?