usb key is not mounted automaticaly (feisty)

Please do the steps on https://wiki.ubuntu.com/DebuggingRemovableDevices and attach the logs. Thank you!

I have forgotten to says that I use Kubuntu, I don't know if it is the reason why I didn't find any gnome-volume-manager.

id gave :
uid=1000(vince) gid=1000(vince) groupes=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),109(lpadmin),111(scanner),113(admin),1000(vince)

id hal gave :
id: hal: usager inexistant.

id haldaemon gave :
uid=106(haldaemon) gid=110(haldaemon) groupes=110(haldaemon),24(cdrom),25(floppy),46(plugdev),116(powerdev)

uname -a gave :
Linux vince-desktop 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux

Can you give the output of the following command:
$ LANG=C dpkg -l gnome-volume-manager ubuntu-desktop | cat

~$ LANG=C dpkg -l gnome-volume-manager ubuntu-desktop | cat
No packages found matching gnome-volume-manager.
No packages found matching ubuntu-desktop.

I use Kubuntu, that's why there is no ubuntu-desktop.

I can confirm this bug :

id
uid=1000(wattazoum) gid=1000(wattazoum) groupes=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),106(lpadmin),107(scanner),108(admin),1000(wattazoum)
id hal
id: hal: usager inexistant.
id haldaemon
uid=107(haldaemon) gid=114(haldaemon) groupes=114(haldaemon),24(cdrom),25(floppy),46(plugdev),115(powerdev)
uname -a
Linux Ouattazoum 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

I noticed, that after I launched gnome-volume-manager myself, it mounted my disk.

I am seeing similar issue. One note though, I have see the same issue in Edgy as well. Breeze mounted the key properly.
output of #LANG=C dpkg -l gnome-volume-manager ubuntu-desktop | cat

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-====================-===============-===================================================
ii gnome-volume-manager 2.17.0-0ubuntu2 GNOME daemon to auto-mount and manage media devices
ii ubuntu-desktop 1.36 The Ubuntu desktop system

$ uname -a
Linux atriums 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

manual mount works. ie mount /dev/sda /mnt/usb mounts the key properly.

This bug seems still on .

Still for me too. Still does not work.

If you are on feisty, you should not have a /media/.hal-mtab directly after booting, can you confirm? Then, please do the following:

  - boot and log in without the stick attached
  - killall gnome-volume-manager
  - gnome-mount -vbd /dev/sda1

what does the last command print out? Please copy&paste it here

Oops, sorry, ignore my last comment. This should have gone to a different bug.

Ugh:

  block.device = '/dev/sdc1' (string)
  volume.fsusage = 'partitiontable' (string)

This should be 'filesystem'. Can you please get a hal debug output, as described on the second half of https://wiki.ubuntu.com/DebuggingRemovableDevices ?

I currently use a desktop computer. I have tested this problem on a laptop with the desktop CD (with the same usb key) and it still does not work.
It works on dapper, edgy and every other systems.

Here is the file. Thank you.

I can mount it manually, but I have noticed something that might help (I'm not sure, as I'm not a developper, I don't understand all those messages but maybe...).

I was curiose to see what was in that hal.log file, so I searched the line corresponding to my key and I saw this part :

15:59:46.993 [D] hald_dbus.c:2528: udi=/org/freedesktop/Hal/devices/storage_serial_04_01_09_U_storage_24438A3FFE066C08
15:59:46.993 [I] hald_dbus.c:2554: AddonIsReady on udi '/org/freedesktop/Hal/devices/storage_serial_04_01_09_U_storage_24438A3FFE066C08'
[9129]: 15:59:46.996 [D] addon-storage.c:312: **************************************************
[9129]: 15:59:46.996 [D] addon-storage.c:313: Doing addon-storage for /dev/sdc (bus usb) (drive_type disk) (udi /org/freedesktop/Hal/devices/storage_serial_04_01_09_U_storage_24438A3FFE066C08)
[9129]: 15:59:46.996 [D] addon-storage.c:314: **************************************************
15:59:46.996 [W] hald_dbus.c:89: No property storage.disable_volume_handling on device with id /org/freedesktop/Hal/devices/computer
15:59:47.021 [I] osspec.c:226: SEQNUM=2663, ACTION=add, SUBSYSTEM=block, DEVPATH=/sys/block/sdc/sdc1, DEVNAME=/dev/sdc1, IFINDEX=0
15:59:47.021 [E] util.c:170: Cannot open '/sys/block/sdc/sdc1/range'
15:59:47.021 [I] osspec.c:737: hal_util_find_known_parent: '/sys/block/sdc/sdc1'->'/sys/block/sdc'

So, even if I don't understand many things in those messages, I know that my key is usually detected as (on dapper and edgy) "storage_serial_04_01_09_U".
As I saw this "DEVPATH=/sys/block/sdc/sdc1, DEVNAME=/dev/sdc1, IFINDEX=0", I though that I had to write this in a terminal to mount it :

sudo mount -t vfat -o rw,users /dev/sdc1 /home/vince/Desktop/az/

Then I had some error messages (french) :

mount: type erroné de système de fichiers, option erronée, super bloc erroné sur /dev/sdc1,
       codepage manquante ou autre erreur
       (tentez-vous de monter une partition étendue,
       au lieu d'une partition logique à l'intérieur?)
       Dans quelques cas certaines informations sont utiles dans syslog - essayez
       dmesg | tail ou quelque chose du genre

So I did dmesg | tail in a terminal and it answered :

~$ dmesg | tail
[19449.005620] sdc: assuming drive cache: write through
[19449.017569] SCSI device sdc: 512000 512-byte hdwr sectors (262 MB)
[19449.020556] sdc: Write Protect is off
[19449.020560] sdc: Mode Sense: 03 00 00 00
[19449.020563] sdc: assuming drive cache: write through
[19449.020571] sdc: sdc1 < sdc5 >
[19449.032711] sd 6:0:0:0: Attached scsi removable disk sdc
[19449.032780] sd 6:0:0:0: Attached scsi generic sg2 type 0
[19513.917456] FAT: bogus number of reserved sectors
[19513.917467] VFS: Can't find a valid FAT filesystem on dev sdc1.

Finally, I though (and was right) that the correct command was :

sudo mount -t vfat -o rw,users /dev/sdc5 /home/vince/Desktop/az/

So maybe hal detects the wrong device (/dev/sdc1) instead of the correct one (/dev/sdc5)

Hope that helps. I don't know if my way of thinking was logical.

Something else very interesting.

As I wrote just before, I had this in a terminal :

~$ dmesg | tail
 [19449.005620] sdc: assuming drive cache: write through
 [19449.017569] SCSI device sdc: 512000 512-byte hdwr sectors (262 MB)
 [19449.020556] sdc: Write Protect is off
 [19449.020560] sdc: Mode Sense: 03 00 00 00
 [19449.020563] sdc: assuming drive cache: write through
 [19449.020571] sdc: sdc1 < sdc5 >
 [19449.032711] sd 6:0:0:0: Attached scsi removable disk sdc
 [19449.032780] sd 6:0:0:0: Attached scsi generic sg2 type 0
 [19513.917456] FAT: bogus number of reserved sectors
 [19513.917467] VFS: Can't find a valid FAT filesystem on dev sdc1.

So, when I saw this line "[19513.917456] FAT: bogus number of reserved sectors"

I tried to format my usb key and create a new fat16 file system to see if it would change something and miracle (!), everythings working fine now.

However, there is although something strange. It is that my usb key was working on edgy and dapper when I first reported this bug (=> without any formatting). So maybe feisty is more "sensitive" or something.

However, thank you all for your great work.

Vince

Hi. I would like to report I'm also having this bug. I have it installed on a HP zv6000 laptop with an AMD Athlon 64. I followed the procedure for collecting data for debugging removable storage (https://wiki.ubuntu.com/DebuggingRemovableDevices) and I am including the output in a compressed folder. However, in running the procedure, the command "ls /dev/sd*" produces an error on my machine because there are no directories beginning with "sd", so there is no "devices.txt" file included in my report. You should also notice that the command "id hal" returned an error. If you need additional info, just ask.

Same prob here, Vince's fix doesn't apply--I can mount/umount and read/write to the disk manually without a problem.

Me too. :(

Same problem here. (Running Kubuntu)

I've two pc, the first one (an Acer notebook) got a fresh install, and it's working fine. I did an upgrade from Edgy to Feisty on my desktop, and I've this usb problem.

Maybe this bug is related to this one?
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/94119/

Hi. I'm gonna post how I resolved my "problem;" this is also from a thread running in Ubuntu forums in case there is similarity.

I have to post back that my problem with outomounting has been resolved; however it was auto inflicted to begin with. I'll explain what happened in case someone goes through the same (doubtful).

I'm working Ubuntu amd64 Feisty on an HP laptop. Those with one know how pleasant it is getting the embedded ATI accelerator and Broadcom wireless card working.

Well, I got a vanilla kernel b/c ndiswrapper wouldn't work on Edgy 64 bit without one, and installing ndiswrapper the first time in Feisty didn't work. So I got 2.6.20.7 (so it's close to Feisty's (2.6.20-15-generic), recompiled using The Master Kernel Thread and got ndiswrapper working. I then got fglrx working too.

It was a couple of days later that I tried using the USB drive and noticed it wasn't mounting. Thus my posts.

I uninstalled fglrx AND ndiswrapper, and reverted back to the 2.6.20-15-generic kernel and guess what? Automounting. But if that's not enough, ndiswrapper was working too! So I still can use my wireless! Weird!

I have similar problems here, on kubuntu feisty, kernel 2.6.20-12-generic
Only a bit more complex situation, due to my HDD partitioning.

I have an external USB disk with four partitions on it, that almost every time are mounted correctly as:
/dev/sda7 244598656 233698224 10900432 96% /media/disk
/dev/sda5 7052464 32812 6661408 1% /media/disk-1
/dev/sda6 25197220 23341036 576208 98% /media/disk-2
/dev/sda1 15243312 12584064 1884920 87% /media/disk-3

But sometimes only one or two of them are automounted.
If then I unmount it with the "safely remove" option on the HDD desktop icon, then the other partitions are automounted; same if I unplug/replug the USB cable.

That's quite annoying, because on those disks I have audacity and cinelerra projects, that have references to absolute paths. As the drives are mounted from time to time in different /media/disk-x directories I have to manually edit the projects' scripts. Moreover when I connect a second drive it's not so easy to distinguish what is what, as was on dapper with the /media/sdax, /media/sdbx, ... naming convention.

Anyhow, some command outputs:

$ LANG=C dpkg -l gnome-volume-manager ubuntu-desktop | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-====================-===============-===================================================
ii gnome-volume-manager 2.17.0-0ubuntu2 GNOME daemon to auto-mount and manage media devices
ii ubuntu-desktop 1.43 The Ubuntu desktop system

$ uname -a
Linux Gigetto 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux

$ id
uid=1000(manu) gid=1000(manu) groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),110(netdev),111(lpadmin),113(powerdev),114(scanner),117(admin),121(mythtv),1000(manu)

$ id hal
id: hal: No such user

$ id haldaemon
uid=107(haldaemon) gid=112(haldaemon) groups=112(haldaemon),24(cdrom),25(floppy),46(plugdev),113(powerdev)

I atach the files obtained as described in DebuggingRemovableDevices. However, by performing such operations I (up to now) got all the drives automounted.
I don't know if what I do makes fully sense bekause I use kde, so gnome-volume-manager works atop of the kde equivalent (whose name I ignore).

Ciao, Leo

I have a MiniDisc (a new one, but nothing special) that can take 1GB discs. It functions just like a normal, generic, mass storage device, and has worked on every linux system I have ever plugged it in to, except Feisty. I've tried a lot of the suggestions in these bug reports, but still no go. I figure it must be something really simple, but I'm not sure. I have managed to mount it manually, but when I say 'mount' what I mean is - no icon on the desktop, have to go search for /media/disk/, I can see some files, but I cannot write to the disk. At first I thought maybe it was a permission problem, but hal reports that it can't identify filesystem type. The weird thing is, I have more complex usb devices, and they work fine e.g. digital camera, usb key, mouse, scanner, vibrator. Joking about the vibrator.

Does anyone have the same experience?

I have the USB drive set up as two separate partitions. They can be mounted manually, but not automatically.

 /dev/sda2 on /home/me/a type hfsplus (rw)
 /dev/sda3 on /home/me/b type hfsplus (rw)

Even when mounted manually, the system seem to get mounted Read Only rather than Read/Write although that is not the case.

So though they are mounted RW, the system seems to think they are RO and gives this error: "Read-only file system"

KDE Daemon finds them just fine, and asks what should be done. However, regardless of the selection, the result is the same. : no action.

Amarok also seems to find them, but does nothing either.

System info:

 $ uname -a ; cat /etc/lsb-release
 Linux myhost 2.6.20-16-powerpc #3 Thu Jun 7 19:32:55 UTC 2007 ppc GNU/Linux
 DISTRIB_ID=Ubuntu
 DISTRIB_RELEASE=7.04
 DISTRIB_CODENAME=feisty
 DISTRIB_DESCRIPTION="Ubuntu 7.04"

I had the same problem... i've tried to launch my Kubuntu Feisty with kernel
2.6.17-11 and now all works fine... i think it could be a kernel 2.6.20-15issue.

Daniele

2007/6/28, Lars Noodén <email address hidden>:
>
> I have the USB drive set up as two separate partitions. They can be
> mounted manually, but not automatically.
>
> /dev/sda2 on /home/me/a type hfsplus (rw)
> /dev/sda3 on /home/me/b type hfsplus (rw)
>
> Even when mounted manually, the system seem to get mounted Read Only
> rather than Read/Write although that is not the case.
>
> So though they are mounted RW, the system seems to think they are RO and
> gives this error: "Read-only file system"
>
> KDE Daemon finds them just fine, and asks what should be done. However,
> regardless of the selection, the result is the same. : no action.
>
> Amarok also seems to find them, but does nothing either.
>
> System info:
>
> $ uname -a ; cat /etc/lsb-release
> Linux myhost 2.6.20-16-powerpc #3 Thu Jun 7 19:32:55 UTC 2007 ppc
> GNU/Linux
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=7.04
> DISTRIB_CODENAME=feisty
> DISTRIB_DESCRIPTION="Ubuntu 7.04"
>
> --
> usb key is not mounted automaticaly (feisty)
> https://bugs.launchpad.net/bugs/86292
> You received this bug notification because you are a bug contact for hal
> in ubuntu.
>

I tried Fedora Core 6, Mandrake 2007.1 Spring, and Gentoo 2007 and all have the same issue with the MiniDisc 1GB device. What do you know? All the kernels are different, however, the way HAL automounts USB drives is the same, or similar. No one else seems to have a fix for this. Maybe its listed in the bugs for HAL?

Jim

Having problems accessing my SD card after reinstalling. Worked fine when I upgraded but a fresh install screwed it up..

Logs attached.
Linux blackbox 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

[Expired for hal (Ubuntu) because there has been no activity for 60 days.]