You are not logged in.
Hello,
So I'm plugging in an external NTFS 1TB HDD into my USB2.0 ports on my Leneovo T520 laptop. I see the device detected using
journalctl -xe
, I see the device under
lsusb (-v)
, but it is not being automounted, nor can I find it using
fdisk -l
, nor does it appear under
/proc/partitions
.
I'm testing with a 1GB flash drive (FAT).
Output of lspci -nn for my USB controller:
00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)
Output from my journalctl:
Aug 22 17:33:49 MiniWarden kernel: usb 2-1.1: new high-speed USB device number 8 using ehci-pci
Don't know if this helps, the Device Quailifer from the lsusb -v:
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
can't get debug descriptor: Resource temporarily unavailable
cannot read device status, Resource temporarily unavailable (11)
And it's appearing as Bus 002 Device 009 under lsusb
The device does not appear under /proc/partition, other than sr0 (can't say I know what that is), I did install ntfs-3g but there's no device to mount!
Thank you for any assistance, I am new and want to learn as much as possible, apologizes if I missed something obvious.
Last edited by Maclu (2017-08-22 23:25:58)
Offline
Offline
Yuuup
....Thanks....
Offline
I would not necessarily expect it to automount. When you connect it, post the entire tail of the journal starting from the MiniWarden kernel: usb 2-1.1: new high-speed USB device number 8 using ehci-pci
line.
Also, post your dmesg output while the USB is attached. While in that state, also post the output of lsblk
slithery is concerned that the kernel you are running is not the kernel that is installed; as am I. Post the output of uname -a and of pacman -Q linux (assuming you are using the stock kernel. If you are not, choose the correct package name)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Please include details of how you solved your issue: https://wiki.archlinux.org/index.php/Co … way_street
Offline
Actually, I now think Yuuup means "no, but yes that was the problem"
Last edited by ewaller (2017-08-23 02:56:50)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I had the same issue and was glad to find this solution. As I switch off my computer every day, I normally don't reboot after a kernel upgrade. But probably that's not such a good idea, as I often need usb automount, and there's also some other cases where I've encountered the need to reboot for things to function properly.
Can somebody explain WHY exactly USB automount stops functioning after a kernel upgrade?
Offline
On kernel updates the module folder for your old (running) kernel is removed (because a new kernel with a new modules folder is installed). If you plug in new hardware that requires the kernel to load a module, it will not find its modules anymore and hence be unable to mount the drive.
Last edited by V1del (2018-03-07 13:14:41)
Online
@v1del Thanks for your clear answer.
Offline