Cannot unmount volume error

Bug #268356 reported by Christian Stöveken
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-mount (Ubuntu)
Invalid
Low
Unassigned

Bug Description

I always get this error "Cannot unmount volume" when I unmount an SD card from the right-click menu.
I don't know if it matters that I use an USB SD card-reader "ID 058f:6331 Alcor Micro Corp.".

The thing is that it gets unmounted correctly afaik (no more "disk" folder in /media).

Running "sudo umount /media/disk/" works without the error.

I've seen some bug reports regarding this error message for Hardy Heron but none for
Intrepid Ibex.

lsb_release -rd
Description: Ubuntu intrepid (development branch)
Release: 8.10

Revision history for this message
Christian Stöveken (excogitation) wrote :
Revision history for this message
Luke Faraone (lfaraone) wrote :

Triage recommendation: Low

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Could you run gnome-mount -b -v -u -d /dev/device? where device is the device you try to unmount and copy the log to the bug?

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Christian Stöveken (excogitation) wrote :

Hope this is what you're asking for (if not please clarify):

$ gnome-mount -b -v -u -d /dev/sdb1
gnome-mount 0.8
** (gnome-mount:789): DEBUG: Unmounting /org/freedesktop/Hal/devices/volume_uuid_48DF_D6D7
** (gnome-mount:789): DEBUG: Setting up 750ms timer for Flushing Cache dialog
** (gnome-mount:789): DEBUG: in unmount_done : user_data = 0x0
** Message: Unmount failed for /org/freedesktop/Hal/devices/volume_uuid_48DF_D6D7: org.freedesktop.Hal.Device.Volume.UnknownFailure : Cannot remove directory

Revision history for this message
Sebastien Bacher (seb128) wrote :

gnome-mount doesn't unmount it either, reassign the bug to it rather

Changed in nautilus:
assignee: desktop-bugs → nobody
status: Incomplete → New
Revision history for this message
Martin Pitt (pitti) wrote :

Please mount it, and then copy&paste the output of

  mount
  ls -l /media

Changed in gnome-mount:
status: New → Incomplete
Revision history for this message
Christian Stöveken (excogitation) wrote :

SD-card with 2 partitions:
$ ls -l /media
total 7
lrwxrwxrwx 1 root root 6 2008-03-12 12:46 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 2008-05-07 15:31 cdrom0
drwx------ 4 excogitation root 1536 1970-01-01 01:00 disk
drwxr-xr-x 17 root root 1024 2008-06-21 11:58 disk-1

I played around with it a bit more and I think the error (now?) only occurs on SD-cards with multiple partitions.
$ gnome-mount -b -v -u -d /dev/sdb1
gnome-mount 0.8
** (gnome-mount:24678): DEBUG: Unmounting /org/freedesktop/Hal/devices/volume_uuid_481F_CDCE
** (gnome-mount:24678): DEBUG: Setting up 750ms timer for Flushing Cache dialog
** (gnome-mount:24678): DEBUG: in unmount_done : user_data = 0x0
** Message: Unmount failed for /org/freedesktop/Hal/devices/volume_uuid_481F_CDCE: org.freedesktop.Hal.Device.Volume.UnknownFailure : Cannot remove directory

 -> error

$ gnome-mount -b -v -u -d /dev/sdb2
gnome-mount 0.8
** (gnome-mount:24691): DEBUG: Unmounting /org/freedesktop/Hal/devices/volume_uuid_1f44940d_4650_40d0_ae8e_afd45da8814d
** (gnome-mount:24691): DEBUG: Setting up 750ms timer for Flushing Cache dialog
** (gnome-mount:24691): DEBUG: in unmount_done : user_data = 0x0
** Message: Unmount failed for /org/freedesktop/Hal/devices/volume_uuid_1f44940d_4650_40d0_ae8e_afd45da8814d: org.freedesktop.Hal.Device.Volume.UnknownFailure : Cannot remove directory

 -> error

Standard SD-card:$ ls -l /media (named 0151024EUR5)
total 20
drwx------ 5 excogitation root 16384 1970-01-01 01:00 0151024EUR5
lrwxrwxrwx 1 root root 6 2008-03-12 12:46 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 2008-05-07 15:31 cdrom0

$ gnome-mount -b -v -u -d /dev/sdb
gnome-mount 0.8
** (gnome-mount:22768): DEBUG: Unmounting /org/freedesktop/Hal/devices/volume_uuid_CC76_8152
** (gnome-mount:22768): DEBUG: Setting up 750ms timer for Flushing Cache dialog
** (gnome-mount:22768): DEBUG: in unmount_done : user_data = 0x0
Unmounted /dev/sdb

-> no errors (works as it should)

$ gnome-mount -b -v -u -d /dev/sdb
gnome-mount 0.8
** (gnome-mount:22780): DEBUG: Unmounting /org/freedesktop/Hal/devices/volume_uuid_CC76_8152
** (gnome-mount:22780): DEBUG: Setting up 750ms timer for Flushing Cache dialog
** (gnome-mount:22780): DEBUG: in unmount_done : user_data = 0x0
** Message: Unmount failed for /org/freedesktop/Hal/devices/volume_uuid_CC76_8152: org.freedesktop.Hal.Device.Volume.NotMounted : According to HAL, the volume is not mounted

-> different errror (also occurs when you doubleclick on the unmount icon in nautilus)

Revision history for this message
Christian Stöveken (excogitation) wrote :

If there is nobody else expierencing this error I have to assume it's an error on my machine and this bug can be closed - if not it should be fixed.

$ ls -l /media/
total 20
lrwxrwxrwx 1 root root 6 2008-03-12 12:46 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 2008-05-07 15:31 cdrom0
drwx------ 4 excogitation root 16384 1970-01-01 01:00 fat16

128MB SD card with a single Fat16 partition (named fat16)

$ gnome-mount -b -v -u -d /dev/sdb1
gnome-mount 0.8
** (gnome-mount:18046): DEBUG: Unmounting /org/freedesktop/Hal/devices/volume_uuid_48F4_46DB
** (gnome-mount:18046): DEBUG: Setting up 750ms timer for Flushing Cache dialog
** (gnome-mount:18046): DEBUG: in unmount_done : user_data = 0x0
** Message: Unmount failed for /org/freedesktop/Hal/devices/volume_uuid_48F4_46DB: org.freedesktop.Hal.Device.Volume.UnknownFailure : Cannot remove directory

->error

The cardreader I use:
$ lsusb
Bus 005 Device 005: ID 05e3:0715 Genesys Logic, Inc. USB 2.0 microSD Reader

Revision history for this message
Christian Stöveken (excogitation) wrote :

Some more data:

[ 7260.190609] usb 5-6: USB disconnect, address 7
[ 7265.504066] usb 5-6: new high speed USB device using ehci_hcd and address 8
[ 7265.686290] usb 5-6: configuration #1 chosen from 1 choice
[ 7265.716075] scsi6 : SCSI emulation for USB Mass Storage devices
[ 7265.721328] usb-storage: device found at 8
[ 7265.721337] usb-storage: waiting for device to settle before scanning
[ 7270.720458] usb-storage: device scan complete
[ 7270.722940] scsi 6:0:0:0: Direct-Access Generic STORAGE DEVICE 9407 PQ: 0 ANSI: 0

e.g. 128MB Card
[ 7270.850152] sd 6:0:0:0: [sdb] 248320 512-byte hardware sectors (127 MB)
[ 7270.851524] sd 6:0:0:0: [sdb] Write Protect is off
[ 7270.851528] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 7270.851531] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 7270.853900] sd 6:0:0:0: [sdb] 248320 512-byte hardware sectors (127 MB)
[ 7270.855270] sd 6:0:0:0: [sdb] Write Protect is off
[ 7270.855274] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 7270.855277] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 7270.855640] sdb: sdb1

e.g. 4GB card
[ 7059.729753] sd 5:0:0:0: [sdb] 7700480 512-byte hardware sectors (3943 MB)
[ 7059.732119] sd 5:0:0:0: [sdb] Write Protect is off
[ 7059.732128] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 7059.732134] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 7059.739644] sd 5:0:0:0: [sdb] 7700480 512-byte hardware sectors (3943 MB)
[ 7059.741873] sd 5:0:0:0: [sdb] Write Protect is off
[ 7059.741882] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 7059.741888] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 7059.744462] sdb: sdb1

Revision history for this message
draco (draco31-fr) wrote :

I've got the same error but I am under Xubuntu 8.10 and using Thunar.
I don't know if gnome-mount is used on my system.

Here is the error on the terminal :
umount /media/panasonic_
/sbin/umount.hal: Unmounting /media/panasonic_ failed: org.freedesktop.Hal.Device.Volume.UnknownFailure: Cannot remove directory

Revision history for this message
Catalin David (c.david) wrote :

Experiencing the same problem. Running Ubuntu 8.10 and problem only appears with a usb stick after i have formatted it using gparted. Though, all the other devices run nicely.

Changed in gnome-mount:
status: Incomplete → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you run "mount" before trying to unmount those and add the log to the bug? could you are strace the gnome-mount call to see what directory it tries to remove?

Revision history for this message
Jorge Silva (jorge-silva) wrote :

Removing (as root) the /media/.hal-mtab and /media/.hal-mtab-lock files solves the problem

Revision history for this message
Christian Stöveken (excogitation) wrote :

I can confirm that removing those two files mentioned by opteron does solve the problem (don't know if it's just temporarily)

@Sebastian Bacher: If you still need that info - I've put it here: http://pastebin.com/m693fd5c9

Revision history for this message
Sebastien Bacher (seb128) wrote :

how do you get those lock added? do you get the issue every time?

Revision history for this message
Christian Stöveken (excogitation) wrote :

Please specify.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the comment was for operon

Revision history for this message
Jorge Silva (jorge-silva) wrote :

not sure, but i think they get created every time you mount something. the issue happens because the files go stale for some reason (perhaps removing a disk without unmounting or a crash that forces you to shut off the comp). I had a couple of electricity outages, so I am blaming it on those

Revision history for this message
draco (draco31-fr) wrote :

Removing the two files solves the problem, but only temporary !
I don't know how those files are created and why the are still present after unmount all drives.
Maybe this the origin af the problem, are maybe only a consequence.

Revision history for this message
Phillip Susi (psusi) wrote :

This package has been removed from Ubuntu. Closing all related bugs.

Changed in gnome-mount (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.