Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Can not mount the device to '/Volumes/X' & Disappearing Mount Folder #66

Open
andreysamode opened this issue Oct 30, 2018 · 2 comments

Comments

@andreysamode
Copy link

andreysamode commented Oct 30, 2018

I'm running simple-mtpfs on OS X with homebrew and while attempting to mount the device with "simple-mtpfs -v /Volumes/X", I get the following error:
"Error: Can not mount the device to '/Volumes/X'."

I see the device in the list—"1: VariousViewpia DR/bq Kepler", /Volumes/X exists. There's nothing in system log.

When I try to run it with sudo, the output says "Connected", but the /Volumes/X simply disappears. I can't see it or cd into it.

df shows this:
simple-mtpfs@osxfuse0 56623656 2070184 54553472 4% 0 0 100% /Volumes/X

After "sudo umount /Volumes/X", the X folder is still gone.

Any ideas?
Thanks.

@andreysamode andreysamode changed the title Error: Can not mount the device to '/Volumes/X'. Error: Can not mount the device to '/Volumes/X' & Disappearing Mount Folder Oct 30, 2018
@andreysamode
Copy link
Author

andreysamode commented Oct 30, 2018

UPDATE: Got it to mount using the following command:
sudo simple-mtpfs -o allow_other,rw -v /Volumes/X

The folder is still automatically deleted afterward, though.

UPDATE 2: If the folder is not in /Volumes, it seems to not be deleted afterwards.

@cpcallen
Copy link

If the folder is not in /Volumes, it seems to not be deleted afterwards.

That is the normal behaviour for unix mount: you have to create the directory (typically but not necessarily empty) before you can mount something on top of it, and when you unmount then the directory remains and whatever was in it (if anything) becomes accessible again.

It's macOS's /Volumes/ which behaves weirdly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants