Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
You use sda1 because even if it's labelled as sda, it still has a partition on it and you mount filesystems found on partitions. You could repartition it and have two (or more) partitions and then these would be labelled as sda1 and sda2.
To get back to the topic: "how to unmount a device you can't find?"
-> use mount to determine the mounted filesystems:
Code:
mount
That should list every mounted filesystem. Then simply use umount to unmount the desired filesystem; if the device you're looking for is not in the list (like sda1), then it's probably not mounted.
This thread seems to have turned into "how to mount" rather than "how to umount"..
My apology as I am coming from Windoze/dos environment, but is this sort of correct?
Ubuntu identified the device and "assigned" it to sda (but it is still not mounted), then the mount command did in fact mount it at sda1 within (or on top of or associated with) sda. i.e., sort of like a subfolder (sda1) under folder sda?
Please correct any misunderstanding or give better analogy as I do want to learn how to do this sort of stuff on my own in future. thanks.
Wooopsie! Just tried to unmount the device before removing it and got:
Error: mount point /mnt/flash is not below /media/
Help!
Bouncer, just saw yours as it posted while I was writing mine above. Thanks for yours and technically you are doubtless correct, but surely it should not be an issue when the obvious answer to the question is to solve another problem first. Then the original issue either then becomes moot, or as in this case, we are now back to the original question.
I used the command:
odyssey@ubuntu:/mnt/flash$ umount sda1 /mnt/flash
umount: sda1 is not mounted (according to mtab)
but it is still mounted, so still can't unmount
Last edited by Odyssey1942; 07-25-2006 at 02:28 PM.
This is beginning to seem like the never-ending saga. Results:
odyssey@ubuntu:/mnt/flash$ sudo umount /mnt/flash
Password:
umount: /mnt/flash: device is busy
umount: /mnt/flash: device is busy
odyssey@ubuntu:/mnt/flash$ sudo umount /dev/sda1
umount: /mnt/flash: device is busy
umount: /mnt/flash: device is busy
Looks like both would have worked if Ubuntu didn't think that the "device is busy" (which AFAIAC, it is not as it has been sitting undisturbed for the last 24 hours.
ran fdisk -l and got
Disk /dev/sda: 64 MB, 64487424 bytes
4 heads, 32 sectors/track, 984 cylinders
Units = cylinders of 128 * 512 = 65536 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 983 62896 6 FAT16
This particular USB drive is a Jumpdrive "Secure" meaning it has some sort of encryption feature (which I have never used), but maybe the "secure" feature runs an application which is constantly polling for input to the drive and marks it for encryption or whatever. This is speculative and maybe irrelevant, but since it is a USB device, it probably runs Linux for any intelligence it needs to provide.
Can anyone suggest a way to determine what is going on that results in the message "device is busy"?
Even more. I mounted a second USB drive (without encryption features to create issues) and went to unmount it. Being lazy, I copied the prior command ( sudo umount /dev/sda1 ) and pasted it onto the command line, intending to change the sda1 to sdb1, but apparently the copy picked up the Enter command that was given in the earlier entry and so the command ocurred before I could make the change.
Anyway, much to my surprise, it instantly unmounted the first USB device. Surprising because before the same command resulted in the message in the previous post, but this time it worked.
I then gave the command: "sudo umount /dev/sdb1" and it unmounted the second drive.
So maybe all is OK, but there was some weirdness in that last bit! Anyone have any thoughts on this?
Edit: jstephens, we cross posted. Any additional comments would be welcome.
Last edited by Odyssey1942; 07-26-2006 at 05:12 PM.
odyssey@ubuntu:/mnt/flash$ sudo umount /mnt/flash
Password:
umount: /mnt/flash: device is busy
umount: /mnt/flash: device is busy
The device is busy as you're in the folder that the filesystem is mounted to (presumably you have none of the files open). If you change to another directory and try to unmount, it should work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.