In my continued attempt to connect to my media player via NFS (http://lime-technology.com/forum/index.php?topic=4208.0, seeing how many have been successful...), I reviewed my syslog (attached) and discovered this:

 

Nov 11 11:58:49 Tower exportfs[1606]: invalid netmask `' for 192.168.0.112:

 

I'm completely puzzled; I've checked all router settings, and unRAID server settings as well:

 

From router:

 

LAN

 

MAC Address : --------------

IP Address : 192.168.0.1 

Subnet Mask : 255.255.255.0 

 

 

From Putty:

 

root@Tower:~# ifconfig

eth0   root@Tower:~# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:25:11:35:b9:42

          inet addr:192.168.0.112  Bcast:192.168.0.255  Mask:255.255.255.0

          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1473 errors:0 dropped:0 overruns:0 frame:0

          TX packets:961 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:142507 (139.1 KiB)  TX bytes:758740 (740.9 KiB)

          Interrupt:29 Base address:0xe000

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:408 errors:0 dropped:0 overruns:0 frame:0

          TX packets:408 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:48447 (47.3 KiB)  TX bytes:48447 (47.3 KiB)

 

root@Tower:~# exportfs eth0

exportfs: invalid netmask `' for 192.168.0.112:

root@Tower:~#

 

 

I can't see where the issue may lie.  I'm not a networking guru by any stretch of the imagination but everything looks right to me.  Any help would be greatly appreciated.

 

Thanks,

 

Y

 

shcmd (44): echo \"/mnt/user/tvixhd1\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=100' '192.168.0.112:/ mnt/user/tvixhd1' >>/etc/exports

 

I'm not a networking guru either, especially in connection with NFS, but I noticed the above in your syslog.  The part in red has an embedded space, just before mnt, that almost certainly should not be there.  I imagine the space is causing it to look like 2 parameters instead of 1, with the first an IP address, and the second a netmask, which of course it is not.

Thanks for the reply, RobJ, and the correction.  I implemented the change (not sure how that crept in, but thanks for catching it).  It now appears I have some kind of syntax error (new full syslog attached as well):

 

Nov 11 22:49:53 Tower emhttp: shcmd (195): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Nov 11 22:49:53 Tower emhttp: shcmd (196): cp /etc/exports- /etc/exports

Nov 11 22:49:53 Tower emhttp: shcmd (197): echo \"/mnt/disk1\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash' '*(ro)' >>/etc/exports

Nov 11 22:49:53 Tower emhttp: shcmd (198): echo \"/mnt/disk2\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash' '*(ro)' >>/etc/exports

Nov 11 22:49:53 Tower emhttp: shcmd (199): echo \"/mnt/disk3\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash' '*(ro)' >>/etc/exports

Nov 11 22:49:53 Tower emhttp: shcmd (200): echo \"/mnt/disk4\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash' '*(ro)' >>/etc/exports

Nov 11 22:49:53 Tower emhttp: shcmd (201): echo \"/mnt/disk5\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash' '*(ro)' >>/etc/exports

Nov 11 22:49:53 Tower emhttp: shcmd (202): echo \"/mnt/disk6\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash' '*(ro)' >>/etc/exports

Nov 11 22:49:53 Tower emhttp: shcmd (203): echo \"/mnt/disk7\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash' '*(ro)' >>/etc/exports

Nov 11 22:49:53 Tower emhttp: shcmd (204): echo \"/mnt/user/tvixhd1\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=100' '*(ro):/mnt/user/tvixhd1' >>/etc/exports

Nov 11 22:49:53 Tower emhttp: shcmd (205): killall -HUP smbd

Nov 11 22:49:53 Tower emhttp: shcmd (206): /etc/rc.d/rc.nfsd restart | logger

Nov 11 22:49:53 Tower mountd[4673]: Caught signal 15, un-registering and exiting.

Nov 11 22:49:54 Tower kernel: nfsd: last server has exited, flushing export cache

Nov 11 22:49:55 Tower logger: Starting NFS server daemons:

Nov 11 22:49:55 Tower logger: /usr/sbin/exportfs -r

Nov 11 22:49:55 Tower exportfs[4726]: /etc/exports:9: syntax error: bad option list

Nov 11 22:49:55 Tower logger: /usr/sbin/rpc.nfsd 8

Nov 11 22:49:55 Tower logger: /usr/sbin/rpc.mountd

 

Y

The "/etc/exports:9: syntax error" would lead me to check the syntax of line 9 of the /etc/exports file.  I'm not familiar with that file though, to provide any help.

 

In the past, we have found that some settings changes involving the security or User Share system required a reboot, before they actually 'took'.

Thanks again, RobJ.

 

I've rebooted a couple times and no change; "exportfs eth0" still produces a syntax error.

 

Though my knowledge of linux has tripled in the last 24 hours, I'm still a novice.  Will keep reading and post but help from the greater community would be greatly appreciated.

 

Thanks much,

 

Y

Below is the /etc/exports file:

 

[/img]

 

Can anyone see something that I'm not?

 

Thanks,

 

Y