HI everybody, this is my first post, even though it's almost 2 years since I started using Arch.
I am usually able to solve the issues that I encountered, but this particular one seems to be not so easy to overcome.
In short, my USB devices cannot be mounted after some time.
At startup everything seems fine, and when I plug in a usb device I am able to mount it and use it normally.
After a couple of hours of uptime, though, I cannot mount USB devices anymore. The laptop behaves as if nothing is plugged to the pc.
Trying to mount the device manually does not help, because mount cannot see the device.
If you were able to help me, I would really appreciate it.
Last edited by ichfarbstift (2013-02-13 15:13:38)
When you say it cannot see the device, how/where are you looking for it? Are you using `ls /dev/sd*` or `lsblk` to check? If not, try those to see if the block device(s) are even created.
Also check dmesg (or dmesg | grep usb) for any relevant messages.
I usually just run a 'mount' in terminal to see whether the device was recognized or not. I am not too experienced in managing devices.
If I run `ls /dev/sd*` or `lsblk` I can't see any useful information, it seems that the block device is not created.
However, running 'dmesg | grep usb' I get the following output:
[ 0.717372] ACPI: bus type usb registered [ 0.717404] usbcore: registered new interface driver usbfs [ 0.717412] usbcore: registered new interface driver hub [ 0.717878] usbcore: registered new device driver usb [ 1.035714] usb 1-1: new high-speed USB device number 2 using ehci_hcd [ 1.265424] usb 4-1: new high-speed USB device number 2 using ehci_hcd [ 1.468699] usb 1-1.5: new high-speed USB device number 3 using ehci_hcd [ 1.631859] usb 1-1.6: new high-speed USB device number 4 using ehci_hcd [ 1.831484] usb 1-1.5.5: new full-speed USB device number 5 using ehci_hcd [ 2.262399] input: Integrated Camera as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input6 [ 2.262779] usbcore: registered new interface driver usbhid [ 2.262782] usbhid: USB HID core driver [ 2.263670] usbcore: registered new interface driver uvcvideo [ 2.295138] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1a.0-1.5.5/input2 [ 2.299059] input: Logitech Unifying Device. Wireless PID:1028 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.5/1-1.5.5:1.2/0003:046D:C52B.0003/input/input7 [ 2.299220] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1028] on usb-0000:00:1a.0-1.5.5:1 [ 2.300789] input: Logitech Unifying Device. Wireless PID:4002 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.5/1-1.5.5:1.2/0003:046D:C52B.0003/input/input8 [ 2.301070] logitech-djdevice 0003:046D:C52B.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:4002] on usb-0000:00:1a.0-1.5.5:2 [ 8962.843812] usb 1-1.5.6: new high-speed USB device number 6 using ehci_hcd [ 9118.859314] usb 1-1.5.6: USB disconnect, device number 6 [ 9276.803184] usb 1-1.5.6: new high-speed USB device number 7 using ehci_hcd
The last three lines refer to the device; I plugged it in, then removed, then plugged it in again.
I hope you have omse suggestions regarding what to do, I am lost.
Thanks for your help, and sorry for the late reply, I was waiting for the issue to reappear.
This is outside my expertise - I basically just know enough to suspect that those responses you provided will have important information for those who have the relevant expertise.
One check I didn't previously mention was whether there were kernel upgrades. In your initial description, it didn't sound like the time frame (couple hours after each boot) fit this possible explanation - but in your second post it does seem more likely. The results you are getting are expected if you install a kernel upgrade but have not rebooted into it. The decisive test for this is to compare the version number in the output of `pacman -Q linux` and `uname -r`.
Last edited by Trilby (2013-02-13 11:48:09)
EDIT: I'm like Trilby in that this is beyond my expertise, but just wanted to suggest a way of making sure all the information is obtained.
It might be worth piping the dmesg output to less and jumping to those lines, to make sure there's nothing of use around them that doesn't contain "usb".
should do the jump (you probably knew that).
Incidentally, try using findmnt to look at mounts, instead of just mount.
is quite nice.
Last edited by skanky (2013-02-13 11:53:16)
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Firstly, thank you skanky for the tips, I did not know them!
Secondly, it could be that the problem is caused by kernel upgrades.
Yesterday I did not upgrade and I did not encounter the problem, but today I did upgrade and the issue was there. I never realized that.
I will remember to pay attention during the next kernel upgrade to see whether the problem is really caused by that or not.
For the moment I will mark the topic as solved, and change it back if it turns out that kernel upgrades are not the reason.
I am experiencing same problem. ichfarbstift did you solve it?
I can confirm that downgrading to linux-3.8.6 solved it for me.
With linux-3.8.7, I cannot mount any usb devices. They simply are not even recognized. The lights flash briefly, then nothing.