Anyone has been able to mount any Window$ share with CIFS Manager?? When I try to do it I give "No such file or directory" error, module is rightly loaded (I checked this with "lsmod")
Also I tried to do with terminal emulator with "mount -t cifs //xxx.xxx.xxx.xxx /mnt/cifs/xxx...." and same in "/sdcard/X" folder, and the same error in all of the cases
Also I'm using the latest couttstech kernel from here and nightly build from Cyanogen (It also was occured same error with older RCs and nightlies)
i looked at these forums and solutions for doing this and none of them worked for me so i'm posting this in case someone knows how to solve this:
I am using nexus 7 2013 with cyanogenmod 10.2.1. i tried both "cifsmanager" and "mount manager" applications to mount my shares (with the right credentials). i also used the following command:
busybox mount -t cifs -o username=[user],password=[password] //192.168.1.91/T /mnt/sdcard/users
all these produce the same error - "mount: invalid argument" when trying to connect to the shared folder.
Have you seen if smbfs rather than cifs works? ( I know smbfs is "old"). There is some relevant info here http://www.netzgewitter.com/2013/10/troubleshoot-cifs-on-android/ on the problems with cifs and Sony Xperia
peterk-1 said:
Have you seen if smbfs rather than cifs works? ( I know smbfs is "old"). There is some relevant info here http://www.netzgewitter.com/2013/10/troubleshoot-cifs-on-android/ on the problems with cifs and Sony Xperia
Click to expand...
Click to collapse
Thanks man!!!!! the "-o unc=" thing soved the issue!
liran corleone said:
Thanks man!!!!! the "-o unc=" thing soved the issue!
Click to expand...
Click to collapse
I guess i was happy too soon - the mount now does work, but i cannot access it with other users. this is how i did the mount:
mount -o unc=\\\\192.168.1.91\\d$,username=developer,password=pass -t cifs none /mnt/cifs/arcade/d
this is the "mount" command output afterwards:
none /mnt/cifs/arcade/d cifs rw,relatime,sec=ntlm,unc=\\192.168.1.91\d$,username=developer,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.91,file_mode=0755,dir_mode=0755,nounix,serverino,rsize=61440,wsize=65536,actimeo=1 0 0
Any idea why/how to solve this?
I've had good luck using the cifs module in the ElementalX kernel along with cifsmanager. You don't need to configure anything other than your shares, and maybe set mount point prefix to /mnt/cifs
If you want to mount shares remotely through ssh port forwarding you can specify the port number that you are forwarding to using port= in options. I'm getting ready for work, so I don't have time right now to get the output showing the mount command that it generates, but I can when I get home.
spiked_mistborn said:
I've had good luck using the cifs module in the ElementalX kernel along with cifsmanager. You don't need to configure anything other than your shares, and maybe set mount point prefix to /mnt/cifs
If you want to mount shares remotely through ssh port forwarding you can specify the port number that you are forwarding to using port= in options. I'm getting ready for work, so I don't have time right now to get the output showing the mount command that it generates, but I can when I get home.
Click to expand...
Click to collapse
i cannot use this kernel since i am using cyanogenmod 10.2.1 (i need the wireless ad-hoc connection mode support) so i will need another solution for this...
Well, I checked in /system/lib/modules to see if cifs.ko was there, but it's not. I was thinking maybe extracting the cifs modules from the ElementalX kernel might be possible, but it must be part of the kernel source and not a separate file. Seems like more people would find cifs support useful, so maybe somebody with development skills will make a kernel module file that's compatible with the N7 2013.
Here's what shows up when I run mount:
//192.168.0.100/Music /mnt/cifs/Music cifs rw,relatime,sec=ntlm,unc=\\192.168.0.100\Music,username=username,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.0.100,file_mode=0755,dir_mode=0755,nounix,serverino,rsize=16384,wsize=131007,actimeo=1 0 0
Nevermind.
mdamaged said:
Nevermind.
Click to expand...
Click to collapse
cifs seems to be supported well by cyanogenmod - the mount process is working fine, but the mounted folders are only visible with root priviledges - not to device's applications like poweramp, pdf reader etc.
liran corleone said:
cifs seems to be supported well by cyanogenmod - the mount process is working fine, but the mounted folders are only visible with root priviledges - not to device's applications like poweramp, pdf reader etc.
Click to expand...
Click to collapse
It's private namespaces that's the issue.
Hi everybody,
I'm trying to mount a nfs at ouya but the ouya refused the mount.
i connect to ouya via adb and try:
mount: mounting 192.168.1.13:/volume1/teste on /sdcard/teste/ failed: Connection refused
my /etc/export file is like that:
/volume1/teste 192.168.1.16(ro,no_root_squash,no_subtree_check)
the ip address of ouya is 192.168.1.16 and the nas server is 192.168.1.13
i create the teste folder at /sdcard to mount the volume there.
i don't know if ouya has support to mount nfs....
i try this command:
[email protected]:/ # find / -name *nfs*
the result is here:
/sys/module/nfs
/sys/module/nfs/parameters/nfs4_disable_idmapping
/proc/sys/fs/nfs
/proc/sys/fs/nfs/nfs_mountpoint_timeout
/proc/sys/fs/nfs/nfs_congestion_kb
/proc/sys/sunrpc/nfs_debug
/proc/sys/sunrpc/nfsd_debug
/proc/fs/nfsfs
/proc/fs/nfsd
so... i think the ouya has nfs support...
someone can help me...
thk very much...
im trying to use this because i installed XBMC at ouya and i would like to use the nfs to share my videos in NAS server....
.....
other information... my nas server is a synology ds212j... on my desktop machine i able to mount the partition, only at ouya i have problems...
excuse-me for my poor english.
NFS Works!
NFS works!
I root the ouya and install busybox.
I use adb connection to mount command that comes with busybox to mount nfs!
the default mount command that comes with ouya dont be able to mount nfs!
i'll make a howto.
Thanks to rootfan I've been able to finally root Shield TV 2017 16GB with NVIDIA Experience Upgrade 8.0.0. (Pie) hoping I'll be able to mount my LAN NAS media content on it. But to make things more complicated my LAN is VLAN segmented due to security reasons. I know KODI and PLEX have NFS mounting capabilities without rooting but all I could see were devices on the same VLAN and of course my media NAS is not part of it and they're primarily media oriented and you might want to expand this focus . Since I've acquired certain knowledge on how to do enable NFS mounting on Shield TV (on "regular" non-VLAN LAN) I'll share all my findings for all of you interested in making this work. Hopefully/Ultimately I'm seeking for any user experience mounting NFS with VLAN enabled LAN, since I'm not Android expert I don't know if it is currently even possible or not.
Anyway long story short here are my findings regarding mounting NFS shares on Android:
I came across this post https://forum.xda-developers.com/shield-tv/help/automount-cifs-nfs-share-write-access-t3783735 and patched Cifsmanager (https://forum.xda-developers.com/showpost.php?p=53760495&postcount=537).
The thing is it requires SuperSU which of course is not an option since Pie is rooted with Magisk. Luckily Magisk comes with su therefore SuperSU isn't needed.
You might come across info you also need SELinuxModeChanger (https://forum.xda-developers.com/showthread.php?t=2524485) - once again if you used rootfan's rooting image you don't need it as rootfan has already preset SELinux to Permissive. You can check it with issuing getselinux command in terminal (I use Termux app for this).
BusyBox needed - I'm also not quite sure it is needed for NFS mounting to work as Magisk BusyBox doesn't contain mount command but Magisk itself does. I've installed Magisk BusyBox module through rootfan's TWRP for Pie (https://drive.google.com/open?id=1934405D1S0lv52jZMqS-Zny62RIzGWSi - link is in the 1st post of https://forum.xda-developers.com/shield-tv/development/kernel-overclock-kernel-2-22-ghz-t3943079; Make sure you don't mix 7.2.3 and 8.0.0) but I'm not quite sure this was necessary as it does not include mount command which is included in Magisk (https://github.com/topjohnwu/Magisk/blob/master/docs/tools.md). I've also wanted to try sideloading BusyBox Pro from GP but didn't see how it would change anything so I haven't done it.
Regarding https://gist.github.com/aldur/4a3f90a111b71662f056 there seems to be an (root) ownership problem when mounting NFS shares. The solutions is to use su -mm -c "mount command". If you take a look at https://github.com/topjohnwu/Magisk/blob/master/docs/tools.md you'll see -mm stands for --mount-master. I personally haven't tried this as I don't have any non-VLAN shares I could mount.
So far this was all I managed to find about NFS mounting on Shield TV, but haven't found anything regarding mounting VLAN segmented NFS shares.
What makes me suspicious about Android's ability to mount/work with VLAN segmented NFS shares is a fact I can ping NFS server from Shield TV but when I try to mount it I get an error 'No such device'. Therefore I'm kindly asking anyone who has any ideas/knowledge to help me out. Thanks.
PS.
Please don't suggest to use CIFS - I want NFS as it is at least as twice as fast as SAMBA/CIFS.
UPDATE:
Caught some time to explore this thing in detail and found out two very important things:
NFS with VLAN(S) is working in KODI without any problems therefore problem is definitely on Android side;
Magisk BusyBox NDK doesn't have/support mount applet/command and seems like even though Magisk itself has it (mount) issuing lsmod | grep nfs returns nothing; Empty response could be cause by the following - When issued mount -t nfs ... the mount command is looking for the filesystem type of nfs. If it doesn't find it, it returns no such device error. If it does find it, it basically hands off the "mount" to the module; Accordingly I came to a conclusion that mounting nfs share on Shield TV via mount command isn't possible with just Magisk and Magisk BusyBox module installed. I'll try installing/sideloading BusyBox (Pro) from Play Store ...
Hey @allidea Thanks for all the information. Did you get anywhere with this? Just ordered a 2019 shield pro, and I was hoping to mount my NFS share on it as well.
Does Cifsmanager work on Android 8.0 with Magisk? (Assuming no Vlan segmentation)
I stopped digging further as I've stated using Kodi which fulfilled all my needs and is definitely a great and free player with lots of plugins. But from what I could tell problem with NFS on Shield TV originates from it's kernel - it simply wasn't compiled with full mount module / NFS support. Obviously Kodi has some custom built in NFS support independent from kernel but I really didn't go into details with it.
BusyBox (Pro) made no difference as it only added a few more commands not present within Magisk BusyBox module and it even skipped installing mount module as it already found it installed.
Therefore cifsmanager doesn't work on 8.0.0 but not because it's incompatible rather due to kernel missing full mount module.
Hope this helped a bit.
I'd like to mount a SMB share on my device so that I can access ROMs on my network share through retroarch.
I've rooted my device, I have Magisk installed, and I was using ADB to try and push the module to places on my device (and having trouble). But I've been barking up the wrong tree since the cifs.ko I have isn't for this kernel. Probably why insmod failed.
This is turning out a lot more complicated than I'd anticipted. I can hook up the share and access via a file browser no problems. I'd anticipated setting up a symlink to an accessible directory, but I read that there was something in the way that android mounts the share that would prevent that from working.
Does anyone have any advice on where to look next? There's no Magisk module I can see that would help me. I'm at a dead end.