Red Hat Bugzilla – Bug 182048
HAL assigns different mount point names to USB devices if device attached at boot time.
Last modified: 2013-03-13 00:49:56 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/20060210 Fedora/184.108.40.206-3 Firefox/220.127.116.11
Description of problem:
If a USB device is attached at boot time, its mount point name is based on some variation of "disk", but if the device is hot plugged, the mount point name is based on the volumne name. This is inconsistent.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Attach USB devices to a running system. Note names of mount points in /media
2. Reboot system leaving devices attached
3. Observe mount point names after reboot
Actual Results: Devices are named according to a different scheme. No longer uses volume names for basis of mount point names.
Expected Results: A consistent naming scheme should be used.
Upon further examination, I see this is only observed in Nautilus. If a device
is present at start up, it has the "disk" style naming, but once it is unmounted
and re-mounted by Nautilus it assumes the volume name style naming. In KDE this
does not happen - it always has "disk" style naming. That being said, this does
not apply to ext3 formatted file systems that are on removable devices. They
always have volume name style mount points. Very inconsistent and confusing.
I can't reproduce this on my system. Maybe you have old entries in /etc/fstab;
care to paste the output of /etc/fstab?
[bshotts@twin7 ~]$ cat /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/boot1 /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
LABEL=/home /home ext3 defaults 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
LABEL=SWAP-hda3 swap swap defaults 0 0
This looks like a gnome-volume-manager issue so I'm reassigning..
1. log in to GNOME
2. unmount your USB device via nautilus
3. open a terminal
4. do a 'gnome-session-remove gnome-volume-manager'
5. do 'gnome-volume-manager --sm-disable --no-daemon'
Post the output from 5. For me I get this line
manager.c/2699: mount_all: mounting /dev/sda1
manager.c/774: executing command: /usr/bin/gnome-mount --no-ui
Is your device mounted in the right location?
[bshotts@twin7 ~]$ gnome-volume-manager --sm-disable --no-daemon
manager.c/583: setting: bool: autobrowse = 1
manager.c/583: setting: bool: autoburn = 0
manager.c/578: setting: string: autoburn_audio_cd_command = nautilus
manager.c/578: setting: string: autoburn_data_cd_command = nautilus
manager.c/583: setting: bool: autoipod = 0
manager.c/578: setting: string: autoipod_command =
manager.c/583: setting: bool: autokeyboard = 0
manager.c/578: setting: string: autokeyboard_command =
manager.c/583: setting: bool: automount_drives = 1
manager.c/583: setting: bool: automount_media = 1
manager.c/583: setting: bool: automouse = 0
manager.c/578: setting: string: automouse_command =
manager.c/583: setting: bool: autophoto = 0
manager.c/578: setting: string: autophoto_command = gthumb-import %h
manager.c/583: setting: bool: autopalmsync = 0
manager.c/578: setting: string: autopalmsync_command = gpilotd-control-applet
manager.c/583: setting: bool: autoplay_cda = 1
manager.c/578: setting: string: autoplay_cda_command = totem %d
manager.c/583: setting: bool: autoplay_dvd = 1
manager.c/578: setting: string: autoplay_dvd_command = totem %d
manager.c/583: setting: bool: autoplay_vcd = 1
manager.c/578: setting: string: autoplay_vcd_command = totem %d
manager.c/583: setting: bool: autopocketpc = 0
manager.c/578: setting: string: autopocketpc_command = multisync
manager.c/583: setting: bool: autoprinter = 0
manager.c/578: setting: string: autoprinter_command =
manager.c/583: setting: bool: autorun = 0
manager.c/578: setting: string: autorun_path = .autorun:autorun:autorun.sh
manager.c/583: setting: bool: autotablet = 0
manager.c/578: setting: string: autotablet_command =
manager.c/2365: mount_all: mounting /dev/sda1
manager.c/1298: mounting /org/freedesktop/Hal/devices/volume_uuid_2C12_B46D...
manager.c/717: executing command: /usr/bin/gnome-mount --no-ui
manager.c/2082: Mounted: /org/freedesktop/Hal/devices/volume_uuid_2C12_B46D
In response to comment 5: is your device mounted in the right location?
I think I see what the problem is now. This makes my head hurt. Ok, from the
I am normally a KDE user but look at GNOME sometimes while testing, so I switch
back and forth a lot.
I a bunch of different USB device for testing but for this test I am limiting it
to a vfat formatted 8Gb disk drive in a USB 2.0 enclosure.
If I attach the drive while KDE is running, it mounts it on /media/disk.
If I attach the drive while GNOME is running, it mounts it on /media/NEW VOLUME.
That's bug number one - they are not consistent.
If I leave the drive attached and log out of either KDE or GNOME, the drive
remains mounted. I think those are bugs and have filed them separately.
If I attatch the drive in KDE, log out and log into GNOME, GNOME shows the drive
and the mount point remains /media/disk as KDE created it, but if I unmount the
drive in GNOME and then remount it, the mount point changes to /media/NEW
VOLUME. So that's why it appears to change. KDE and GNOME are using different
names for the mount points and the drives remain mounted after the attaching
user has logged off.
> KDE and GNOME are using different names for the mount points
Not a bug.
> and the drives remain mounted after the attaching user has logged off.
Not a bug in GNOME at least.
Closing as NOTABUG. Thanks for your input anyway.