Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a ASUS laptop with Fedora 13. My problem is that any USB storage I connect does not automount. I have other computer with Fedora 13 which does not have the problem.

I have not be able to find any difference in configuration between my laptop and other computers that work.

So to try to trace down the problem I started to looomk for documentation on how it was supposed to work. I have looked at udev, devkit, hal , dbus, polkit, gnome and others.

I want to know which events, logs, config files and monitor programs that I can use to track down the events that takes place from when I attach an USB stick and until i have a window up and running in GNOME.

So far I have traced that udev detects the disk and creates /dev/sdb (and /dev/sdb1 for partition 1) and that event about device added is sent as messages on dbus. I am able to mount the disk manually with udisks but not with gnome-disk-utility (palmiset).

There is many different applications involved to automount a disk, I want to find out where in the chain of events does it fail.

share|improve this question
up vote 0 down vote accepted

HAL posts a D-Bus system message when a new volume comes up. It is up to a D-Bus client (usually nautilus) to listen for that message and request via D-Bus that HAL mount the volume.

share|improve this answer
OK, how can I monitor or verify if nautilus receives this message? Is there a log or a monitor program that I can run? – pablaasmo Sep 4 '10 at 19:26
dbus-monitor will allow you to monitor D-Bus signals. D-Feet will allow you to introspect D-Bus interfaces. – Ignacio Vazquez-Abrams Sep 4 '10 at 23:28
Thanks, but that just shows that the message is issued on the dbus? How do I know if is picked up by Nautilus? Also, how do I know what messages to look for? – pablaasmo Sep 5 '10 at 9:40
According to [this] (…) the chain of events/programs is: kernel -> udev -> dbus -> hal -> gnome-vfs/nautilus (mount). The last step does not seem to work for me and I am wondering why. Also I believe that HAL is partly replaced by devkit/udisks in Gnome 2.30? – pablaasmo Sep 5 '10 at 9:57
I just found the reason it did not mount. I had a leftover file from earlier udev version. File 60-persistent-storage.rules existed in both /etc/udev/rules.d and in /lib/udev/rules.d . The former overruled the last one. When removing the one in /etc/udev/rules.d the USB drives mounted correctly again. – pablaasmo Sep 5 '10 at 11:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .