Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok, so the USB drive isn't found under Devices (when using blkid command) but it is showing up as a connected device USB (when using lsusb command).
Looking at the output of dmesg:
[945968.895128] usb 2-2: Product: External USB 3.0
[945968.895132] usb 2-2: Manufacturer: TOSHIBA
[945968.896050] usb-storage 2-2:1.0: USB Mass Storage device detected
[945968.896180] scsi18 : usb-storage 2-2:1.0
[945991.107826] usb 2-2: Disable of device-initiated U1 failed.
[945991.111326] usb 2-2: Disable of device-initiated U2 failed.
[945991.276781] usb 2-2: reset SuperSpeed USB device number 7 using xhci_hcd
[945991.295715] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b84d3640
[945991.295717] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b84d3688
I'm confused, I've been trying to find out what is wrong with it but it works in Windows, and it appears to connect fine but then I'm thinking the output above means it gets disabled for some reason? I'm running OpenMediaVault 3.0 (which runs on Debian Jessie 8.10). It's frustrating as I just cleaned up this 2TB drive to back up some of my server, and now it's not working directly with linux
It's potentially related, but I only seem to get USB 2.0 speeds with my external drives, although it appears my flash drive at the back is connected with USB 3.0. I'm not absolutely sure I connected the USB cables inside correctly and haven't checked yet, but just wondering if there is a driver support issue?
It's potentially related, but I only seem to get USB 2.0 speeds with my external drives, although it appears my flash drive at the back is connected with USB 3.0. I'm not absolutely sure I connected the USB cables inside correctly and haven't checked yet, but just wondering if there is a driver support issue?
Please post the output of:
Code:
$ lspci | grep USB
It may be the USB3 controller on your motherboard. I had an Asus board where the USB3 controller was made by ASMedia and it would not work under linux but worked under windows. After a little googling revealed the ASMedia controller was simply not supported under linux and was not likely to be in the future, I gave up and bought an addin USB3 card that was supported. Similar to you, USB3 devices would either not work or only work at USB2 speeds. The output of the above command should reveal if this is a potential problem.
Intel should be fine but you should have more than one line of output if you have both USB3 and USB2 ports. Mine reads:
Code:
$ lspci | grep USB
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller
00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
You can check your bios/UEFI and make sure USB3 is activated. On some boards you have to do that or the USB3 port will run at USB2 speeds.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
It might be that the OS isn't automounting the device. Then it could be listed in lsusb but not df -h. Plug it in and try
Code:
$ ls /dev/sd*
and see if there's a device node. Each drive on the system gets sda, sdb, sdc, etc. And each partition on each drive adds a number to the end of those.
It should show up in /proc/partitions or blkid if it is mountable.
$ cat /proc/partitions
$ sudo blkid
I normally cat /proc/partitions before I insert the device and after, then I note the difference. If it's the last thing you changed the tail end of dmesg should have some information to about it's /dev/... name. If it doesn't show up in any of those things, then you have issues. Not enough power to the device, or driver/kernel issues. I have a couple usb 3 spinning rust drives that get quirky if it's connected via a usb 2 extension, or if the powered hub is connected via a usb 2 extension. At least when it's connected to a low power arm device like a pocket chip. But on the short leash it works just fine.
I have a failed usb3 sandisk 32gb stick that shows up in most things, but if I try to mount it, it'll take a bit, and fails. Normally with something about cannot find device or some such. It does show up under /proc/partitions. I was using it as a live system and playing a game when my computer just unexpectedly shut off. Then it was in that state.
No biggie, I opened the packaging for a new one, stuck it in my other computer to install linux under linux $(debootstrap) and was booted up again in less than fifteen minutes, and gaming again in less than an hour. It probably could have been less than half an hour, but it failed to a non-read-only state so I had spent some time checking out my backups and trying to use the failed device. I figured it was faster to start fresh than to try and bring my arch stick up to date.
Well that's odd. Have you tried with the most recent stable kernel?
The xhci stuff is for usb 3 iirc and seem to be puking a bit with your previous output. ehci for usb 2. Perhaps an extension cable to convert it to usb 2? Or a powered hub, I have a couple toshiba 500GB usb3 drives and they are power hungry. Even on a powered hub, I had to pull the usb to ethernet adapter and the rtl sdr dongle leaving just the drive and keyboard on that hub for mine to work.
I still think you should check your bios/UEFi. On my Asus board you go to Advanced Mode and tick the Advanced tab. Then select USB Configuration and check what you have for "Intel xHCI Mode". It should be set to either "Smart Auto" or "Enabled". If it is set to "Disabled", your USB3 ports will run in USB2 mode which appears to be what you have going on. Also, in USB2 mode, USB3 external hard drives will malfunction since they can't draw enough power from a USB2 port.
As suggested above, it might also be a kernel issue since your board is relatively new and you're running Debian 8.1. You can try running a linux livecd with a more recent kernel and see how your external hard drive works in that environment. If it works OK, it's most likely a kernel issue and you need to run a more up to date kernel that fully supports your board.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.