Network similarities are as follows
Same network same switch same router

differences are as follows
motherboard
Bios
network adapter
CPU
(everything)
its a uefi bios

the network adapter

I have 4 different PC models scattered about the place and get different results on them all some boot and mount the nfs others time out

@george1421 i did further testing it seems to be end point related not server i turned the vm into a dual core machine and 2GB of ram and the PC i was running it on at the time imaged with no problems, worked fine, turns out the PC i used was the key .

so to update problem still exists can’t mount filesystem on one PC but can on another

both booting via ipv4

i found the problem single core VM added a extra core and mounts work fine

some heavy searching and came across this

https://forums.fogproject.org/topic/11389/nfs-mount-options-needed/10

looks like editing the init image might resolve it

hi can any one help fog seems to be unable to mount the image in the deploy or image process, I however can access the nfs shares fine from my ubuntu laptop so the fog server is certainly listening and responding on the nfs ports.

I have tried to manually mount the nfs from debug boot but i get connection timed out same error the fog console shows when deploying an image

I have followed the nfs troubleshoting guide, its not firewall, its not vlans, its not the fact nfs isnt listening

the output of showmount -e on the server is

root@fogserver:/home/fogproject# showmount -e
Export list for fogserver:
/home/fogproject/images/dev *
/home/fogproject/images *
root@fogserver:/home/fogproject#

tried a few manual mount commands i’ve found in the forum but nothing works from the fog boot image

if i run uname -r on the debug image i get 4.19.48

some one must be able to point me at what i’ve missed

here are the folder permissions and the mntcheck files

the server is on ubuntu 19.04