USB devices not mounting

Orion

In the last few days USB storage devices won't mount on my Intrepid system. I've tried a 16Gb usb stick, a 250GB passport drive and my Cowon S9 on two different ports. These all worked last week. At the weekend I did an update to my system - there were a lot of updates (hadn't updated in a while) and upgraded OO.o to v3. They are the only changes made to the system since these devices last worked. See below for log extracts and other relevant info. Any ideas?

n.b. lsusb run with the device unplugged - I'm in work now and won't be able to try anything til this evening.

~$ lsusb
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 004: ID 046d:c049 Logitech, Inc. G5 Laser Mouse
Bus 004 Device 005: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

~$ uname -a
Linux Sethanon 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux

tail /var/log/syslog -n 20
Feb 25 07:46:02 Sethanon kernel: [86044.588047] usb 5-2: new full speed USB device using uhci_hcd and address 22
Feb 25 07:46:02 Sethanon kernel: [86044.712032] usb 5-2: device descriptor read/64, error -71
Feb 25 07:46:03 Sethanon kernel: [86044.940025] usb 5-2: device descriptor read/64, error -71
Feb 25 07:46:03 Sethanon kernel: [86045.156025] usb 5-2: new full speed USB device using uhci_hcd and address 23
Feb 25 07:46:03 Sethanon kernel: [86045.280028] usb 5-2: device descriptor read/64, error -71
Feb 25 07:46:03 Sethanon kernel: [86045.508031] usb 5-2: device descriptor read/64, error -71
Feb 25 07:46:03 Sethanon kernel: [86045.724030] usb 5-2: new full speed USB device using uhci_hcd and address 24
Feb 25 07:46:04 Sethanon kernel: [86046.132016] usb 5-2: device not accepting address 24, error -71
Feb 25 07:46:04 Sethanon kernel: [86046.244025] usb 5-2: new full speed USB device using uhci_hcd and address 25
Feb 25 07:46:04 Sethanon kernel: [86046.652025] usb 5-2: device not accepting address 25, error -71
Feb 25 07:46:04 Sethanon kernel: [86046.652231] hub 5-0:1.0: unable to enumerate USB device on port 2
Feb 25 07:46:49 Sethanon gnome-screensaver-dialog: pam_sm_authenticate: Called 
Feb 25 07:46:49 Sethanon Gnome-screensaver-dialog:pam_sm_authenticate: username = [xxxxxx]
Feb 25 07:46:49 Sethanon gnome-screensaver-dialog: Error attempting to parse .ecryptfsrc file; rc = [-5]
Feb 25 07:46:49 Sethanon gnome-screensaver-dialog: Unable to read salt value from user's .ecryptfsrc file; using default
Feb 25 07:46:50 Sethanon gnome-screensaver-dialog: Passphrase key already in keyring
Feb 25 07:46:50 Sethanon gnome-screensaver-dialog: Error attempting to add passphrase key to user session keyring; rc = [1]
Feb 25 07:46:50 Sethanon gnome-screensaver-dialog: There is already a key in the user session keyring for the given passphrase.

$ dmesg | tail
[86044.712032] usb 5-2: device descriptor read/64, error -71
[86044.940025] usb 5-2: device descriptor read/64, error -71
[86045.156025] usb 5-2: new full speed USB device using uhci_hcd and address 23
[86045.280028] usb 5-2: device descriptor read/64, error -71
[86045.508031] usb 5-2: device descriptor read/64, error -71
[86045.724030] usb 5-2: new full speed USB device using uhci_hcd and address 24
[86046.132016] usb 5-2: device not accepting address 24, error -71
[86046.244025] usb 5-2: new full speed USB device using uhci_hcd and address 25
[86046.652025] usb 5-2: device not accepting address 25, error -71
[86046.652231] hub 5-0:1.0: unable to enumerate USB device on port 2

Khannie

Man....troubleshooting USB not automounting is a huge pain in the hole and that dmesg output is worrying tbh. Did your update include a new kernel perchance? See if you can boot into the old kernel and if your stuff automounts then. I'll keep an eye on the thread.

Orion

It did include a new kernel - how do I boot to a different kernel?

An Fear Aniar

Can you select an earlier kernel in your grub boot menu? Otherwise, I guess you could install an earlier kernel using Synaptic, which would then show up in the boot menu.


.

Orion

hmmm - seems it is directly related to the new kernel. Found a couple of articles on launchpad.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285006

One suggested workaround is to run lsusb - after runnint it the usb device automounts! Very strange. I'll try that this evening to see. I am using a hub (tried two different ones) so I'll try it directly into the mobo too - luckily I just freed up a port by getting a network printer

I'll post back here this evening after I've tried these.

Khannie

Grub should have your old kernel as a boot option alright.

Orion

Just checked menu.lst - it does. Previous kernel was 2.6.27-7-generic - now it's 2.6.27-11-generic. I'll try that too this evening.

Orion

UPDATE
Tried the previous kernel (2.6.27-9-generic) and it was the same. There is another kernel in grub - 2.6.27-7-generic - which I haven't tried yet. Running lsusb as suggested on the ubuntuforums thread didn't let it mount.

However it does mount if I plug it directly into the motherboard. So it's only hubs that are affected. Very strange. I'll pick up a cheap usb extension cable tomorrow to get me by until they resolve this bug unless anyone has any other ideas?

Khannie

Check the hub on another box. You never know.....

Orion

Both hubs worked last week and neither work now. And this seems to be a widespread issue in Ubuntu after a kernel update.

Besides:

~$ lsusb
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 004: ID 046d:c049 Logitech, Inc. G5 Laser Mouse
Bus 004 Device 005: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I'll try one of them but I'd be fairly confident it'll work.

TBH Next time I rebuild I'm choosing a different distro. All too often there's crappy little bugs like this in Ubuntu and it's starting to piss me off. Might go to standard Debian or FC10.

Offy

Im running Ubuntu and I had that problem a few weeks ago. I use a 3G usb modem and I had to do a bit of playing around with it, it was seeing it as a storage device and had to be told it was a modem. Before the problem it picked it up fine, new kernal came along and it saw nothing on any usb port. http://www.boards.ie/vbulletin/showthread.php?t=2055439131
gives the modem solution and once I got that running the usb kicked back in again. Its probably something different with your system though.

I really miss Red Hat.