nfs mount.nfs4: Host is down when trying to mount nfs share

[ichase]

With the upgrade to SAMBA 4 and pulling my hair out trying to get that to work, Security Breach recommended NFS.

I read the Arch Wiki on NFS, wow, pretty easy. Yeah, for everyone but me. I hate following the wiki and stuff not working.

I have tried numerous things on the /etc/exports file to get this to work but I get the same thing EVERY TIME when trying to mount it on the laptop: mount.nfs4: Host is down

 

My current etc/exports currently looks like this:

# /etc/exports
#
# List of directories exported to NFS clients.  See exports(5).
# Use exportfs -arv to reread.
#
# Example for NFSv2 and NFSv3:
#  /srv/home	   hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
 /srv/nfs4 192.168.0.104/24(rw,sync,fsid=0)
 /srv/nfs4/storage 192.168.0.104/24(rw,sync,nohide)
# Using Kerberos and integrity checking:
#  /srv/nfs4	    gss/krb5i(rw,sync,fsid=0,crossmnt)
#  /srv/nfs4/home   gss/krb5i(rw,sync,nohide)
#

 

Something to note. The server share is sdb1 the 2nd hard drive on the server. It's mounted to /mnt/storage. It has been mounted to the actual target share /srv/nfs4/storage via the mount command:

# mount --bind /mnt/storage /srv/nfs4/storage

 

I have added both to my fstab and checked to make sure that sdb mounts and the target share mounts with a reboot of the server. I have also started and enabled both rpc-idmapd.service and rpc-mountd.service. And I have used exportfs -ra when ever I made a change to /etc/exports.

[securitybreach]

I'm at work till later but when I get home I'll compare it to mine.

[crp]

Firewall cleared? and as always, webmin.com is your friend.

[securitybreach]

Here are my configs:

 

cat /etc/exports
# /etc/exports
#
# List of directories exported to NFS clients. See exports(5).
# Use exportfs -arv to reread.
#
# Example for NFSv2 and NFSv3:
# /srv/home	 hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4	hostname1(rw,sync,fsid=0)
# /srv/nfs4/home hostname1(rw,sync,nohide)
# Using Kerberos and integrity checking:
# /srv/nfs4		gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/home gss/krb5i(rw,sync,nohide)
#

/srv/nfs4/MEDIA 192.168.1.1/24(rw,no_subtree_check,nohide)

 

 

cat /etc/idmapd.conf
[General]

Verbosity = 1
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = 192.168.1.2

[Mapping]

Nobody-User = nobody
Nobody-Group = nobody

[Translation]

Method = nsswitch

 

cat /etc/fstab | grep nfs
# nfs
/MEDIA										 /srv/nfs4/MEDIA none			bind							0 0

[ichase]

Well I was able to get NFS up and running and was able to mount via Linux. Though by using Windows utilities for Unix, you can get Windows to map to the share it was a Royal PITA

So, I re-imaged the server from when I had fixed SAMBA 3 and now all of my computers in the house (Windoz included) are back to being able to use the file server.

 

And I am NOT going to pacman -Syu the server again. LOL It only has the one purpose of being a portal to the files and printer and it does that quite well the way it is.

Edited April 28, 2013 by ichase

[securitybreach]

If you wait too long, just make sure to never update it

 

I still say NFS is better.....