DebianThis forum is for the discussion of Debian 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.
I cannot find a hint of what is wrong by searching the Web. All of
the hits are for slightly different symptoms or the solutions are
things I have already done. But, of course, I may have missed
something ....
When I last saw this effect (in another context), it was because the
network or device had gone AWOL in service. I have looked at every
option I can find on the device, MTP is on, USB debugging is on, etc.
etc. Any ideas would be appreciated!
Thanks.
wheeler#ls -ld /media/nexus7
drwx------ 2 root root 4096 Mar 23 10:20 /media/nexus7
wheeler#jmtpfs /media/nexus7wheeler#ls -ld /media/nexus7
drwx------ 2 root root 4096 Mar 23 10:20 /media/nexus7
wheeler#jmtpfs /media/nexus7
Unable to open ~/.mtpz-data for reading, MTPZ disabled.
Device 0 (VID=18d1 and PID=4ee2) is a Google Inc (for LG Electronics/Samsung) Nexus 4/5/7/10 (MTP+ADB).
Android device detected, assigning default bug flags
wheeler#mount | grep jmtpfs
jmtpfs on /media/nexus7 type fuse.jmtpfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
wheeler#ls -ld /media/nexus7
ls: cannot access /media/nexus7: Input/output error
wheeler#ls -l /media
ls: cannot access /media/nexus7: Input/output error
total 12
lrwxrwxrwx 1 root root 6 Apr 25 2016 cdrom -> cdrom0
drwx------ 2 root root 4096 Apr 25 2016 cdrom0
drwx------ 2 root root 4096 Mar 23 10:30 cdrom0.LOCAL
d????????? ? ? ? ? ? nexus7
drwx------ 2 root root 4096 Mar 23 10:20 nexus7.LOCAL
ut error
total 12
lrwxrwxrwx 1 root root 6 Apr 25 2016 cdrom -> cdrom0
drwx------ 2 root root 4096 Apr 25 2016 cdrom0
drwx------ 2 root root 4096 Mar 23 10:30 cdrom0.LOCAL
d????????? ? ? ? ? ? nexus7
drwx------ 2 root root 4096 Mar 23 10:20 nexus7.LOCAL
Last edited by nmm1; 03-23-2019 at 01:16 PM.
Reason: Another wheel mouse problem I had missed!
To eliminate any issues with permissions when mounting your Android, create a directory somewhere in your home folder, i.e. don’t mount it under /media or /media/USER/. Try disconnecting it, then reconnect and run the first two commands below as root, then the next two as user:
Thanks very much, but no joy. I had already tried lots of games with permissions, and (after a
hint elsewhere) running it unprivileged, but even your commands make no difference. mtp-detect and most other low-level commands work, and show the device correctly, and I can get on using 'adb shell/push/pull', but mounting fails half-way through. It's not visible by df, has that broken state, but DOES unmount using fusermount.
Given the pile of cards that is remote mounting in Unices, before even we get onto fuser and the
android link, I really can't think of what to try next.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.