Cannot Connect to New External Disk Drive
by arubin from LinuxQuestions.org on (#54J74)
This problem might be solved but I would like some advice on this.
I have a new Seagate External Drive. This is a 4TB "Backup Plus Hub"
I was getting the following error on connecting
Quote:
Googling I found this https://www.suse.com/support/kb/doc/?id=000016942 which advises
Quote:
The hot fix works. I don;t quite understand what is going on and I am not sure what effect the permanent fix will have on other devices.
Is it safe to use the permanent fix?
Could the fix be made specific to this drive.
Update to above. After reformatting the large sdc2 partition to ext4 and rebooting the drive seems to connect without any need for the fix


I have a new Seagate External Drive. This is a 4TB "Backup Plus Hub"
I was getting the following error on connecting
Quote:
[ 48.949109] usb 5-2: device descriptor read/64, error -71 [ 49.204030] usb 5-2: new full-speed USB device number 5 using xhci_hcd [ 49.206415] usb 5-2: Device not responding to setup address. [ 49.409423] usb 5-2: Device not responding to setup address. [ 49.610046] usb 5-2: device not accepting address 5, error -71 [ 49.764058] usb 5-2: new full-speed USB device number 6 using xhci_hcd [ 49.766502] usb 5-2: Device not responding to setup address. [ 49.969446] usb 5-2: Device not responding to setup address. [ 50.170044] usb 5-2: device not accepting address 6, error -71 [ 50.170090] usb usb5-port2: unable to enumerate USB device |
Quote:
hot fix Before implementing the permanent fix, it is suggested that you test it first. Unplug your USB device, and then run, echo -1> /sys/module/usbcore/parameters/autosuspend Plug your USB device in. If it is detected then continue on to the permenant fix. permanent fix The autosuspend setting can be set at the loading of the USB module. The control of device parameters can be found in /etc/modprobe.conf, /etc/modprobe.conf.local and /etc/modprobe.d. Create a file in /etc/modprobe.d called usbcore Populate the file with the following options usbcore autosuspend=-1 Save the file Run "mkinitrd" (If you are sure that no USB device modules are loaded via the initrd, then you can skip this step) Reboot |
Is it safe to use the permanent fix?
Could the fix be made specific to this drive.
Update to above. After reformatting the large sdc2 partition to ext4 and rebooting the drive seems to connect without any need for the fix