Announcement

**Snowhog** · Jul 25, 2015, 10:59 AM

Those a LARGE drives, and USB Bus speeds are slower than internally connected HDDs. You just need to wait until the indexing on those drives is completed.

**bmaring** · Jul 25, 2015, 12:05 PM

Originally posted by Snowhog View Post

Those a LARGE drives, and USB Bus speeds are slower than internally connected HDDs. You just need to wait until the indexing on those drives is completed.

I suspected that, so I let it try to connect over night. No help. I always wait for thee activity light on the drive to go out. By the way, thumb drives do connect with no problems.

**oshunluvr** · Jul 30, 2015, 06:56 AM

Those errors seem related to UAS support. Could be a kernel issue, which might explain why it works under 14.04.

I wonder if you tried a vanilla kernel or a different kernel version if you'd get different results.

Another option I've read about is to prevent the Seagate from using the UAS module. To do that:

First, create a file named/etc/modprobe.d/ignore_uas.conf containing the following*:

Code:

options usb-storage quirks=Vendor_ID:Product_ID:u

*(substitute your actual Vendor_ID and Product_ID obtained from lsusb).

Next, regenerate your initial ramdisk:

Code:

sudo update-initramfs -u -v -k `uname -r`

Then reboot. Although this is not a solution to broken uas, at least it may let you use your drive as before.

**DISCLAIMER** I have not attempted this as I don't have this problem. To reverse this change, delete /etc/modprobe.d/ignore_uas.conf and re-run the update-initramfs command and reboot.

**Snowhog** · Jul 30, 2015, 09:50 AM

You didn't state, and I don't want to imply, so I'll ask: Is 15.04 installed on the same PC that 14.04 is/was on? Do the USB HDDs receive power separately; have a power cord; or through the USB connector? If the latter, then the USB HDDs are (almost certainly) USB 3.0 (data and power) and would have to be connected to a USB 3.0 port.

**bmaring** · Jul 30, 2015, 11:20 AM

Originally posted by oshunluvr View Post

Those errors seem related to UAS support. Could be a kernel issue, which might explain why it works under 14.04.

I wonder if you tried a vanilla kernel or a different kernel version if you'd get different results.

Another option I've read about is to prevent the Seagate from using the UAS module. To do that:

First, create a file named/etc/modprobe.d/ignore_uas.conf containing the following*:

Code:

options usb-storage quirks=Vendor_ID:Product_ID:u

*(substitute your actual Vendor_ID and Product_ID obtained from lsusb).

Next, regenerate your initial ramdisk:

Code:

sudo update-initramfs -u -v -k `uname -r`

Then reboot. Although this is not a solution to broken uas, at least it may let you use your drive as before.

**DISCLAIMER** I have not attempted this as I don't have this problem. To reverse this change, delete /etc/modprobe.d/ignore_uas.conf and re-run the update-initramfs command and reboot.

I reformatted the drive and it still wouldn't mount. Something it didn't like about the ntfs specification. I bought a new harddrive the works fine. I will use the old drive on windows.

Thanks for attention. I will save this in case I come down this road again.

Announcement

15.04 Doesn't mount USB harddrive

[KDE] 15.04 Doesn't mount USB harddrive

Comment

Comment

Comment

Comment

Comment