Did you try "fuser" (as root) to see what process was using the mount point?
# fuser /dev/whatever
If it reports a processid, then
ps -ef | grep that-process-id
to investigate what it is.
Exit the process if you have control of it. Otherise kill -9 that-process-id will put a bullet in its head.
Usually when I can't umount a drive its because I changed to the mount point directory in another window and forgot that I had done so. -- nohup rm -fr /&
I don't know what to replace "whatever" with. I've tried a wildcard but it returns about 25, 4 digit numbers. I've tried /sdcard but get "fuser: can't stat '/dev/sdcard': No such file or directory".
The "sdcard -> /storage/sdcard1" means that "sdcard" is a symbolic link to /storage/sdcard1" The letter "L" at the beginnng of the permissions confirms that.
Try "fuser /storage/sdcard1" and see what it yields. (Hopefully one or more process id numbers.) -- nohup rm -fr /&
reply to sempergoofy Apparently this is all related to Google changing the way it deals with usb connection. With the new Android 4.+ (Jellybean) they've gone to MTP which is why I couldn't see the device from nautilus in Ubuntu. When I ran a ROM based on Android 2.7 (Gingerbread) my Ubuntu nautilus could view it.
Apparently this is all related to Google changing the way it deals with usb connection. With the new Android 4.+ (Jellybean) they've gone to MTP which is why I couldn't see the device from nautilus in Ubuntu. When I ran a ROM based on Android 2.7 (Gingerbread) my Ubuntu nautilus could view it.
The third sentence in the above link refers to a very good explanation with a comment from a google engineer as to why the switch.
That is a very good read, and explains a lot of the confusion I had been having about why I could not switch off of MTP. -- "Padre, nobody said war was fun now bowl!" - Sherman T Potter
·