On Fri, Apr 08, 2005 at 05:38:29PM +0200, Martin Pitt wrote: > Diwaker Gupta [2005-02-03 17:27 -0800]: > > > Also, can you unmount the respective device manually? So what happens > > > if you execute 'pumount /dev/yourdevice' while the device is still > > > mounted? If that command fails, please try > > > > Yes, I can unmount the device manually. pumount fails. > > > > # first I ripped out the device > > $ mount > > [snip] > > /dev/sda1 on /mnt/backup type ext3 (rw,noexec,nosuid,nodev,user=diwaker) > > > > # so the entry is still there, while it shouldn't have been > > $ pumount /dev/sda1 > > Error: could not determine real path of the device: No such file or > > directory > > > > # of course, since /dev/sda1 doesn't exist anymore > > > > $ pumount -d /dev/sda1 > > /dev/sda1 cannot be resolved to a proper device node > > Error: could not determine real path of the device: No such file or > > directory > > > > Like I said, this only happens with devices which have entries in > > /etc/fstab. > > Devices that are completely automagically handled by pmount don't give this > > problem. > > pmount does not do automatic unmounting of ripped out devices, this is > done by /etc/dev.d/block/hal-unmount.dev. This doesn't seem to work > for you, I reassign to the hal maintainer. (Hello Sjoerd :-) )
Does pumount -l <your ripped device> work ? If that works, do the same again but use ACTION=remove DEVNAME=<device name> /etc/dev.d/block/hal-unmount.dev That should also unmount the device... If those both work we should track down what's going wrong with udev on your system.. Sjoerd -- It's hard to think of you as the end result of millions of years of evolution. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
