Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: ubuntu, RHAS, and other unmentionables
Posts: 372
Rep:
no I did mean umount -l which is...
-l Lazy unmount. Detach the filesystem from the filesystem hierar-
chy now, and cleanup all references to the filesystem as soon as
it is not busy anymore. (Requires kernel 2.4.11 or later.)
Code:
(u)mount version-2.12r
works great for problematic USB mass-storage. Not sure about this one though
I've been experiancing simular problems but I know what's causing it. I've still got a program accessing the CDROM for some reason. SentralOrigin, to find out which application is interfering with the ejection, type this command:
Which means that kdeinit is interfering with the CDROM. Now I don't know how to properly fix this. So in the mean time, I've been killing the offending application just prior to ejecting:
kill 5852
The number will change each time, hence you have to use the fuser command to determine the proper ProccessID (PID) before using the kill command.
But this is not a pretty way of doing things. Is there a fix to this?
PS: This is only on my Debian box.
Last edited by Spankin Partier; 10-30-2005 at 03:12 PM.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,521
Rep:
Here's the thing:
mount /dev/hdd /media/drive
cd /media/drive
now you are in the filesystem you mounted. That means the file system is busy. If you:
cd /
then you will be in the root, and out of the mounted file system in /media. So, do that, and then issue umount /dev/hdd.
And use the same terminal window. You can't do:
cd /
in a different terminal window. It has to be the same one you cd'ed into the file system with. Ok, now after you get OUT of the file system you want to umount:
umount /dev/hdd
and it won't be busy anymore. Even if you have a file manager, like Konquerer, showing that file system, it will not umount.
I just had this problem today. I had so many terminals open I forgot what was going on. I wanted to umount a loopback device and one of my terminals was still in it. I was sure I was out of it, but low and behold, I looked at every terminal window and I was still inside it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.