You are not logged in. Please login or register.
chumbysphere forum → Software → chumby NFS
I'm having trouble getting chumby to mount an NFS share.
I do the following:
chumby:/mnt# mount -o nolock -t nfs 192.168.1.69:/home/ubuntu/share /mnt/share
mount: mounting 192.168.1.69:/home/ubuntu/share on /mnt/share failedThe host is accessible because I'm connecting from it to the chumby and I know the NFS share works because I can mount it from itself with the exact same mount command.
Any ideas?
robert
Do you have a firewall configured on that box? It might be allowing local connections but blocking external connections.
make sure that the filesystem on the server is exported to hosts other than itself. you can do this via
the following command:
showmount -e $NFS_HOST
where $NFS_HOST is the hostname or ip.address of the NFS server
if you need help with exporting the NFS filesystem, let us know
/mdkail
Did you create the /mnt/share directory first? The NFS mount will fail if the destination directory (/mnt/share in your case) does not exist.
chumby:~# mount -o nolock -t nfs 192.168.1.100:/root /mnt/share
mount: mounting 192.168.1.100:/root on /mnt/share failed
chumby:~# mkdir /mnt/share
chumby:~# mount -o nolock -t nfs 192.168.1.100:/root /mnt/share
chumby:~#Also, please note that NFS mounting was broken on chumby software version 1.1 and has been fixed in 1.2. Please apply the update if you have not done so already.
That was it. I updated to 1.2 yesterday and now it works. Thanks!
I can confirm this. As was said above:
1. Make sure you are running version 1.2 of the Chumby firmware
2. make sure to have created the folder you are trying to mount to
Does chumby support/provide an NFS server as opposed to a client?
Not at the moment, because there really isn't anything to serve.
However, I'm sure one could build a server for it, perhaps to server content off a USB drive.
We can't put *everything* into the device.
Duane, point well taken. I guess I had envisioned hanging ai big USB drive off of Chumby (say, 500 Gb), and using the Chumby as wireless network attached storage. Obviously you can't include everything under the sun... I just figured I'd ask 
I'm getting this error, too.
I have server2003 with SFU 3.5 unix tools installed. I shared a folder (G:\My Music) using NFS with the name "ChumbyMusic"
I then ran:
chumby# mkdir /mnt/nfs
chumby# mount -o nolock -t nfs 192.168.1.1:/ChumbyMusic /mnt/nfs
and got the following error:
mount: mounting 192.168.1.1:/ChumbyMusic on /mnt/nfs failed
and ran dmesg and got:
portmap: server localhost not responding, timed out
RPC: failed to contact portmap (errno -5).
I checked the NFS log on my server, and it's reporting:
03-13-2008 12:57:46 MOUNT SUCCESS 192.168.1.10 G:\My Music
i also ran showmount -e 192.168.1.1 from the server, and it says:
Export list on 192.168.1.1:
/ChumbyMusic All Machines
showmount -a gives me:
All mount points on 192.168.1.1:
192.168.1.10 : G:\My Music
any help would be greatly appreciated. (192.168.1.1 = NFS server, 192.168.1.10 = Chumby)
I'm getting this error, too.
I have server2003 with SFU 3.5 unix tools installed. I shared a folder (G:\My Music) using NFS with the name "ChumbyMusic"
I then ran:chumby# mkdir /mnt/nfs
chumby# mount -o nolock -t nfs 192.168.1.1:/ChumbyMusic /mnt/nfsand got the following error:
mount: mounting 192.168.1.1:/ChumbyMusic on /mnt/nfs failed
and ran dmesg and got:
portmap: server localhost not responding, timed out
RPC: failed to contact portmap (errno -5).I checked the NFS log on my server, and it's reporting:
03-13-2008 12:57:46 MOUNT SUCCESS 192.168.1.10 G:\My Music
i also ran showmount -e 192.168.1.1 from the server, and it says:
Export list on 192.168.1.1:
/ChumbyMusic All Machinesshowmount -a gives me:
All mount points on 192.168.1.1:
192.168.1.10 : G:\My Musicany help would be greatly appreciated. (192.168.1.1 = NFS server, 192.168.1.10 = Chumby)
I fixed the problem. You have to synchronize the passwd and group file from the chumby (copy to windows server) with the windows server, and link the administrator user with the root user on the chumby.
You can set up automatic synchronization through the NFS service manager so that in the future, if for any reason the passwd or group id's ever change, upon startup will automatically pull the information back to the server.
mount the drive, voila!
Does the chumby support nfs v3? I use NFS all over my network and am very familiar with configuring it. However, when I try to mount a share on one of my boxes, I get an error. I don't see anything helpful in dmesg output either. My only guess is that it might not support nfs v3?
Here's how I'm mounting it:
chumby:/sbin# mount -t nfs -o nolock 192.168.1.102:/usr/local/media2/music /mnt/nfs
mount: mounting 192.168.1.102:/usr/local/media2/music on /mnt/nfs failed
And on the server, the fs is exported...
nikita ~ # exportfs
/usr/local/media2/music
chumby
And yes, the "chumby" hostname maps to the correct IP address of my chumby. Also, I do not have a firewall between the two boxes.
I'm an idiot... I forgot to create /mnt/nfs. So yes, the chumby does support NFS v3 as it's working now.
Alright so I can now mount nfs shares, but I can't figure out how to get my infocast to check my mountpoint. What's the trick with that?
Additionally how do I get the chumby to automatically mount my nfs share on startup?
chumbysphere forum → Software → chumby NFS
Powered by PunBB, supported by Informer Technologies, Inc.