Remote mount from mfsBSD

For NFS no packages needed. (iSCSI either)
Setup remote drive machine as NFS server with desired remote drive directory as export.
Setup mfsBSD as NFS client.
Code: 
#
### NFS Client ####
nfs_client_enable="YES"
nfs_client_flags="-n 4"
rpc_lockd_enable="YES"
rpc_statd_enable="YES"
#

Set mfsBSD /etc/fstab to mount remote NFS Server export at bootup.
You will want to use the the failok flag for the remote mount.
That way if it can't find the remote drive it will not crash the client machine.
 
Phishfry said:
For NFS no packages needed. (iSCSI either)
Setup remote drive machine as NFS server with desired remote drive directory as export.
Setup mfsBSD as NFS client.
Code: 
#
### NFS Client ####
nfs_client_enable="YES"
nfs_client_flags="-n 4"
rpc_lockd_enable="YES"
rpc_statd_enable="YES"
#

Set mfsBSD /etc/fstab to mount remote NFS Server export at bootup.
You will want to use the the failok flag for the remote mount.
That way if it can't find the remote drive it will not crash the client machine.
Click to expand...
Not sure what you mean.... I'm using an mfsBSD iso. When I try to mount an NFS share I get:-

tcp: Netconfig database not found

which suggest that something is missing from the mfsBSD image.
It would be nice to know should be included to make this work.
 
forums.freebsd.org

tcp: Netconfig database not found

I'm trying to mount an NFS share when PXE booting mfsBSD. Any idea what's missing? I do realise that mfsBSD is a minimal installation of FreeBSD, but if I knew what was required to run an NFS client, maybe I could add it.
forums.freebsd.org forums.freebsd.org
You will have to rebuild the kernel with these options and copy over the mfbsd image.
 
Alain De Vos said:
forums.freebsd.org

tcp: Netconfig database not found

I'm trying to mount an NFS share when PXE booting mfsBSD. Any idea what's missing? I do realise that mfsBSD is a minimal installation of FreeBSD, but if I knew what was required to run an NFS client, maybe I could add it.
forums.freebsd.org forums.freebsd.org
You will have to rebuild the kernel with these options and copy over the mfbsd image.
Click to expand...
Looks like I've been trying to figure this out for a while, but couldn't figure out how to add the required options to build mfsBSD.
 
I wonder why NFS is not in the kernel of mfbsd ? Where is the location of the configuration of that ?
Do you have a custom KERNCONF on your system ?
 
In case of NFS there is no package to install or configuration needed to mount a share.

balanga, I just checked it: cloned git repository, build image (13.1-RELEASE), boot mfsbsd (in VirtualBox in my case), mount NFS share from a 13.1-RELEASE server:

mount -o nfsv4 <nfs-server-ip>:/ /mnt/d1
mount <nfs-server-ip>:/dir /mnt/d1

If there is an mount error, then it's probably an issue on the server side.

Can you ping the server? If it's a NFSv3 server, what does showmount -e <nfs-server-ip> show? How does on the server the /etc/exports file look (eventually redact domain names and/or IP's)?
 
Alain De Vos said:
I already had the impression mfsbsd uses the default kernel which normally has NFS.
T-deamon you have the file /etc/netconfig ?
Click to expand...
It is present.

Regular 13.1-RELEASE
Code: 
% ls /etc/net*
/etc/netconfig        /etc/netstart        /etc/network.subr    /etc/networks

mfsbsd 13.1
mfsbsd.png
 
This suggest Balanga has a mis-configuration. Which can happen to anyone.
According to my analysis mfsbsd uses the DEFAULT or GENERIC kernel.
 
T-Daemon said:
It is present.

Regular 13.1-RELEASE
Code: 
% ls /etc/net*
/etc/netconfig        /etc/netstart        /etc/network.subr    /etc/networks

mfsbsd 13.1
View attachment 14947
Click to expand...
I tried to PXE boot mfsbsd-mini-13.1-RELEASE-amd64.iso but I get numerous errors which I'm unable to capture, although most mention various 'screen*' files. mini-12.2 works fine using the same PXE entry.
 
You must log in or register to reply here.
Back
Top