EDGY RC, USB storage devices no longer mounted

gvs@bobby:~$ id
uid=1002(gvs) gid=1002(home) groups=4(adm),24(cdrom),25(floppy),29(audio),44(video),46(plugdev),105(scanner),106(admin),117(fuse),1001(netusers),1002(home),1004(media),1005(bobbyadmin),1006(ras)
gvs@bobby:~$ id hal
id: hal: No such user
gvs@bobby:~$ id haldaemon
uid=116(haldaemon) gid=116(haldaemon) groups=116(haldaemon),24(cdrom),25(floppy),46(plugdev)
gvs@bobby:~$ uname -a
Linux bobby 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686 GNU/Linux
gvs@bobby:~$

Hey guys. Just updated from Dapper Main, and I have the same basic problem. I'm using and amd 64.

here's the strange thing a 'dmesg | grep usb' picks it up
[ 31.820531] usbcore: registered new driver usbfs
[ 31.820552] usbcore: registered new driver hub
[ 31.821754] usb usb1: configuration #1 chosen from 1 choice
[ 31.926135] usb usb2: configuration #1 chosen from 1 choice
[ 32.033820] usb usb3: configuration #1 chosen from 1 choice
[ 32.141614] usb usb4: configuration #1 chosen from 1 choice
[ 32.169178] usb 1-1: new full speed USB device using uhci_hcd and address 2
[ 32.256163] usb usb5: configuration #1 chosen from 1 choice
[ 32.704157] usb 1-1: device not accepting address 2, error -71
[ 33.897869] usb 5-1: new high speed USB device using ehci_hcd and address 2
[ 34.034573] usb 5-1: configuration #1 chosen from 1 choice
[ 34.221311] usbcore: registered new driver libusual
[ 34.460800] usb 1-2: new low speed USB device using uhci_hcd and address 4
[ 34.640530] usb 1-2: configuration #1 chosen from 1 choice
[ 34.643976] usb-storage: device found at 2
[ 34.643978] usb-storage: waiting for device to settle before scanning
[ 34.643988] usbcore: registered new driver usb-storage
[ 34.650600] usbcore: registered new driver hiddev
[ 34.669662] input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:10.0-2
[ 34.669674] usbcore: registered new driver usbhid
[ 34.669678] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[ 39.635514] usb-storage: device scan complete
[ 2477.273207] usb 5-1: USB disconnect, address 2
[ 2480.782534] usb 5-1: new high speed USB device using ehci_hcd and address 4
[ 2480.915225] usb 5-1: configuration #1 chosen from 1 choice
[ 2480.915461] usb-storage: device found at 4
[ 2480.915462] usb-storage: waiting for device to settle before scanning
[ 2485.905274] usb-storage: device scan complete
[ 2501.922434] usb 5-1: USB disconnect, address 4
[ 2508.953081] usb 5-1: new high speed USB device using ehci_hcd and address 5
[ 2509.085685] usb 5-1: configuration #1 chosen from 1 choice
[ 2509.085921] usb-storage: device found at 5
[ 2509.085923] usb-storage: waiting for device to settle before scanning
[ 2514.075853] usb-storage: device scan complete

then even stranger is a 'dmesg | sda' sees it as well
[ 52.239634] SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
[ 52.240772] sda: Write Protect is off
[ 52.240776] sda: Mode Sense: 33 00 00 00
[ 52.240778] sda: assuming drive cache: write through
[ 52.241845] SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
[ 52.245956] sda: Write Protect is off
[ 52.245961] sda: Mode Sense: 33 00 00 00
[ 52.245963] sda: assuming drive cache: write through
[ 52.245970] sda: sda1
[ 52.255861] sd 2:0:0:0: Attached scsi disk sda

I guess I can manually add it to my fstab, but I feel like I'm back in '02.

I tried a full reinstall, same result.

USB devices are detected for a local (non-ldap user) though, so it is not caused by the udev process that starts at boot.

the gvm log says:
manager.c/2020: mounting /org/freedesktop/Hal/devices/volume_uuid_2EAE_1336...
manager.c/2170: mount queued for /org/freedesktop/Hal/devices/volume_uuid_2EAE_1336

nothing happens after that? What does 'mount' show after this happens?

What does 'pmount-hal /dev/sda1' do, does it mount the device manually?

Nothing happens indeed.

mount does not show the device mounted (output is identical to the output before the device was connected).

 pmount-hal /dev/sda1
Error: given UDI is not a mountable volume

I tried several USB sticks, all of them work on my dapper machine and all of them work on this machine when logged in with a full local user.

Hey guys, figured this one out a little while ago, so I don't have detailed
output, but the problem is in lvm2. I had used a FAT fs for my usb stuff,
but in truth FAT is not supposed to handle big filesystems, so now edgy
doesn't. I just backed it up onto a dapper install, reformatted to ext3,
and all was well. Woulda been nice had they warned us though.

On 12/13/06, Guy Van Sanden <email address hidden> wrote:
>
> Nothing happens indeed.
>
> mount does not show the device mounted (output is identical to the
> output before the device was connected).
>
> pmount-hal /dev/sda1
> Error: given UDI is not a mountable volume
>
> I tried several USB sticks, all of them work on my dapper machine and
> all of them work on this machine when logged in with a full local user.
>
> --
> EDGY RC, USB storage devices no longer mounted
> https://launchpad.net/bugs/67307
>

I doubt that lvm is the culprit.

In any case, I tried with a ext3 formatted USB disc and it shows the same problem.

Any news on this issue yet?

I hope it will be resolved soon, so I can move my laptop to Edgy too.

It's strange though that CD's are supported perfectly (CDROM, DVD, CDR) while USB does not work.

This bug is still around in Feisty (and the Tribe 4 Gutsy I tried). Local machine users mount USB storage device sticks fine, LDAP users do not. Sometimes the device will appear under computer:/// not mounted and give a permissions error when double clicking, other times will not.

dmesg | grep usb :

[ 4330.314577] usb-storage: device found at 103
[ 4330.314581] usb-storage: waiting for device to settle before scanning
[ 4335.309419] usb-storage: device scan complete

Any work around for this? I have an entire primary school on feisty without USB stick support atm - Fedora 7 doesn't have this problem. Perhaps a udev rule?

I think the problem is hald-based. I've read reports that hald only reads group memberships from /etc/group on startup and will only accept those users listed in the plugdev group there. Group permissions assigned by LDAP are not considered. I've got a whole lab of computers experiencing this same problem. With users being added on a daily basis, maintaining local /etc/group would be a complete nightmare.

If I manually enter an LDAP user into plugdev in the /etc/group file and log in as an ldap user from cold start, I get no usb stick appearing in Computer:// under gnome.

However, If I log in as a local user to access the stick, then log out and log in as an ldap user, I can access the USB device without any problem.

So I'm still missing a part of the puzzle to use this as a workaround for staff users on their own classroom machines. Namely the part that will access and mount the stick initially for the locally defined ldap user.

I did look into trying to get the /etc/group file to symlink to a central network share location for easy update to all clients but had no joy there. Best case I can see is to use ssh and a bash script to deploy it to all clients.

"However, If I log in as a local user to access the stick, then log out and log in as an ldap user, I can access the USB device without any problem."

to clarify this line refers to an ldap user I have explicitly added to plugdev in /etc/group file.

This is a major problem - USB device mounting is apparently a life-and-death situation for some of our students here. Just a "me too" post, I guess. I'd appreciate a status update.

Thanks!

I was beaten by this same bug, the solution is "USB needs more power". Now, I dunno if the new driver (or the version used by Ubuntu kernels have something to do)

In my case, I just plugged the device in the USB ports behind my computer (not in front) and everything just worked.

Good luck

On 9/19/07 6:39 AM, LuisM wrote:
> I was beaten by this same bug, the solution is "USB needs more power".
> Now, I dunno if the new driver (or the version used by Ubuntu kernels
> have something to do)
>
> In my case, I just plugged the device in the USB ports behind my
> computer (not in front) and everything just worked.
>

That would be a different bug, then :)

This problem is when:
a) you use anything newer than dapper
b) your users aren't local - they're in LDAP.

It's completely reproducible with all USB Mass Storage devices,
regardless whether or not it's a clean edgy/feisty install or an upgrade.

 -Charlie

Just to add a me too on this bug, as far as I can tell USB automounting has been broken since Dapper

I'd not seen this report before I have posted a lot more info in this report: https://bugs.launchpad.net/ubuntu/+bug/130367

I really hope this gets fixed sometime soon.

Child

All is well (for me at least), USB automounting now working properly for both hard-drive and pendrives.

Thankyou Ubuntu Devs

Child

rothchild wrote:
> All is well (for me at least), USB automounting now working properly for
> both hard-drive and pendrives.
>

Are you using LDAP? What version of Ubuntu??

 -Charlie

Hi Charlie
No I'm not using ldap and this is on Gutsy (although I had problems with feisty too) it just started working after todays update.

Child

On 10/1/07 8:12 AM, rothchild wrote:
> Hi Charlie
> No I'm not using ldap and this is on Gutsy (although I had problems with feisty too) it just started working after todays update.
>
> Child
>

Oh..
It has worked all along (for most people) as long as all your users are
"local." The jist of this bug is that it hasn't worked with LDAP users
since Dapper.

 -Charlie

Hi Charlie,

I have the same problem under Mandriva 2007.1 Spring x64 :
No mounted USB key for ldap users ;-(

all fine for local one.

Laurent

When I plugged in my USB storage device it was recognized as a USB device but not recognized as a storage device, it was never assigned a device.

I saw messages like:

[ 154.708000] usb 5-3: new high speed USB device using ehci_hcd and address 4
[ 154.852000] usb 5-3: configuration #1 chosen from 1 choice

But it was never assigned a device.

 I rebooted the machine and it now was recognized as a storage device, but not mounted, when attempting to mount it manually I did:

sudo mkdir /media/sdb1
sudo mount -t auto /dev/sdb1 /media/sdb1
mount: you must specify the filesystem type
Then I did
sudo mount -t vfat /dev/sdb1 /media/sdb1
and it mounted normally.

I am a local user on my laptop, it's an IBM T43

If people keep replying with unrelated issues, the devs will ignore this
even longer. At least, it'll make it harder to see at a glance what the
real issue is. Perhaps there's multiple issues in this bug, but _I
believe_ it the majority of the focus is on people who have LDAP users.

It has been over a year.. it's unfortunate that this problem isn't
impacting the single-user experience.

:(

On 10/9/07 9:59 AM, DavidMandala wrote:
> When I plugged in my USB storage device it was recognized as a USB
> device but not recognized as a storage device, it was never assigned a
> device.
>
> I saw messages like:
>
> [ 154.708000] usb 5-3: new high speed USB device using ehci_hcd and address 4
> [ 154.852000] usb 5-3: configuration #1 chosen from 1 choice
>
> But it was never assigned a device.
>
> I rebooted the machine and it now was recognized as a storage device,
> but not mounted, when attempting to mount it manually I did:
>
> sudo mkdir /media/sdb1
> sudo mount -t auto /dev/sdb1 /media/sdb1
> mount: you must specify the filesystem type
> Then I did
> sudo mount -t vfat /dev/sdb1 /media/sdb1
> and it mounted normally.
>
> I am a local user on my laptop, it's an IBM T43
>

I sorry Charlie, where should I have logged this? I'm new onboard and
if I've done something incorrect or stupid, I'll be happy to correct it.

Thanks,

David

Charlie Schluting wrote:
> If people keep replying with unrelated issues, the devs will ignore this
> even longer. At least, it'll make it harder to see at a glance what the
> real issue is. Perhaps there's multiple issues in this bug, but _I
> believe_ it the majority of the focus is on people who have LDAP users.
>
> It has been over a year.. it's unfortunate that this problem isn't
> impacting the single-user experience.
>
> :(
>
> On 10/9/07 9:59 AM, DavidMandala wrote:
>> When I plugged in my USB storage device it was recognized as a USB
>> device but not recognized as a storage device, it was never assigned a
>> device.
>>
>> I saw messages like:
>>
>> [ 154.708000] usb 5-3: new high speed USB device using ehci_hcd and address 4
>> [ 154.852000] usb 5-3: configuration #1 chosen from 1 choice
>>
>> But it was never assigned a device.
>>
>> I rebooted the machine and it now was recognized as a storage device,
>> but not mounted, when attempting to mount it manually I did:
>>
>> sudo mkdir /media/sdb1
>> sudo mount -t auto /dev/sdb1 /media/sdb1
>> mount: you must specify the filesystem type
>> Then I did
>> sudo mount -t vfat /dev/sdb1 /media/sdb1
>> and it mounted normally.
>>
>> I am a local user on my laptop, it's an IBM T43
>>
>

--
David Mandala <davidm at canonical dot com>
http://www.canonical.com/ Public Key id: 45B2D952
Murphy TX, 75094 +1.214.774.2569 O +1.972.693.4007 C

That's not really directed at you.. I'm just pissed that they haven't
fixed this (or even commented).

"This" is specifically about LDAP users not being able to mount USB
devices. I'd guess your issue is a new bug, if it's reproducible with a
fresh install.

 -Charlie

On 10/9/07 10:35 AM, DavidMandala wrote:
> I sorry Charlie, where should I have logged this? I'm new onboard and
> if I've done something incorrect or stupid, I'll be happy to correct it.
>
> Thanks,
>
> David
>
> Charlie Schluting wrote:
>> If people keep replying with unrelated issues, the devs will ignore this
>> even longer. At least, it'll make it harder to see at a glance what the
>> real issue is. Perhaps there's multiple issues in this bug, but _I
>> believe_ it the majority of the focus is on people who have LDAP users.
>>
>> It has been over a year.. it's unfortunate that this problem isn't
>> impacting the single-user experience.
>>
>> :(
>>
>> On 10/9/07 9:59 AM, DavidMandala wrote:
>>> When I plugged in my USB storage device it was recognized as a USB
>>> device but not recognized as a storage device, it was never assigned a
>>> device.
>>>
>>> I saw messages like:
>>>
>>> [ 154.708000] usb 5-3: new high speed USB device using ehci_hcd and address 4
>>> [ 154.852000] usb 5-3: configuration #1 chosen from 1 choice
>>>
>>> But it was never assigned a device.
>>>
>>> I rebooted the machine and it now was recognized as a storage device,
>>> but not mounted, when attempting to mount it manually I did:
>>>
>>> sudo mkdir /media/sdb1
>>> sudo mount -t auto /dev/sdb1 /media/sdb1
>>> mount: you must specify the filesystem type
>>> Then I did
>>> sudo mount -t vfat /dev/sdb1 /media/sdb1
>>> and it mounted normally.
>>>
>>> I am a local user on my laptop, it's an IBM T43
>>>
>
>

Well I just installed this a week ago Tuesday on my laptop and updated
it everyday since. Given how hard it was to install it then, I'm loath
to try that again, I lack a full days time for that trick. The beta
image from last week would not install, I had to install 7.04 and
upgrade, no other way. (That was reported.)

However the bug has changed a bit more. I used the device for something
else so I had to reformat it. I used fdisk and put a fresh partition on
it using the entire device as the first partition, and then formatted it
vfat with mkfs.vfat. Now it attempts to mount the device and fails with:

[10394.360000] usb 5-3: new high speed USB device using ehci_hcd and
address 6
[10394.504000] usb 5-3: configuration #1 chosen from 1 choice
[10394.504000] scsi5 : SCSI emulation for USB Mass Storage devices
[10394.504000] usb-storage: device found at 6
[10394.504000] usb-storage: waiting for device to settle before scanning
[10399.504000] usb-storage: device scan complete
[10399.504000] scsi 5:0:0:0: Direct-Access Memorex TD Classic 003C
 1.04 PQ: 0 ANSI: 0 CCS
[10400.088000] SCSI device sdb: 2007040 512-byte hdwr sectors (1028 MB)
[10400.088000] sdb: Write Protect is off
[10400.088000] sdb: Mode Sense: 23 00 00 00
[10400.088000] sdb: assuming drive cache: write through
[10400.088000] SCSI device sdb: 2007040 512-byte hdwr sectors (1028 MB)
[10400.088000] sdb: Write Protect is off
[10400.088000] sdb: Mode Sense: 23 00 00 00
[10400.088000] sdb: assuming drive cache: write through
[10400.088000] sdb: sdb1
[10400.092000] sd 5:0:0:0: Attached scsi removable disk sdb
[10400.092000] sd 5:0:0:0: Attached scsi generic sg2 type 0
[10400.680000] FAT: Unrecognized mount option "usefree" or missing value

So what is the proper thing to do here? Open a new bug, leave it here.
 I'm not sure what is the correct thing.

Cheers,

David

Charlie Schluting wrote:
> That's not really directed at you.. I'm just pissed that they haven't
> fixed this (or even commented).
>
> "This" is specifically about LDAP users not being able to mount USB
> devices. I'd guess your issue is a new bug, if it's reproducible with a
> fresh install.
>
> -Charlie
>
> On 10/9/07 10:35 AM, DavidMandala wrote:
>> I sorry Charlie, where should I have logged this? I'm new onboard and
>> if I've done something incorrect or stupid, I'll be happy to correct it.
>>
>> Thanks,
>>
>> David
>>
>> Charlie Schluting wrote:
>>> If people keep replying with unrelated issues, the devs will ignore this
>>> even longer. At least, it'll make it harder to see at a glance what the
>>> real issue is. Perhaps there's multiple issues in this bug, but _I
>>> believe_ it the majority of the focus is on people who have LDAP users.
>>>
>>> It has been over a year.. it's unfortunate that this problem isn't
>>> impacting the single-user experience.
>>>
>>> :(
>>>
>>> On 10/9/07 9:59 AM, DavidMandala wrote:
>>>> When I plugged in my USB storage device it was recognized as a USB
>>>> device but not recognized as a storage device, it was never assigned a
>>>> device.
>>>>
>>>> I saw messages like:
>>>>
>>>> [ 154.708000] usb 5-3: new high speed USB device using ehci_hcd and address 4
>>>> [ 154.85...

I have a workaround which I have working under gutsy. I've written a guide which should result in usb working for ldap users here:

http://ubuntuforums.org/showthread.php?p=3668359#post3668359

In a nutshell, check ldap before files in pam and assign an ldap plugdev group. This works where on the fly group assignment doesn't. Still use the on the fly assignment because audio didn't seem to work for me when using an ldap group. using both does.

hope this helps.

I have the same bug here.

LDAP users won't be able to (auto)mount their devices. There are no problems for local users.
The workaround from kesomir is not suitable for me, since i don't have access to the ldap-server.

Most people agree, I'd think. It isn't really acceptable to put 10,000+
users, for example, in a single group and keep it updated.

 -Charlie

Change the order of etc/pam.d/common-session . First pam_unix.so and later pam_ldap.so. Reboot the computer and the automount will work.

For example:

session required pam_mkhomedir.so skel=/etc/skel/ umask=077
session optional pam_mount.so
session required pam_unix.so
session optional pam_ldap.so
session optional pam_foreground.so

No more changes :)

Sorry for my bad english :D

There are several different issues reported here. The "usefree" option isn't used any more, gnome-volume-manager isn't used any more, and you don't need to be in the group "plugdev" any more to mount removable devices, so from my point of view there isn't anything relevant left here. Please open new bug reports against hal if your devices are still not automounted in 8.10.