mounting /images failed: Connection timed out

[sjensen]

@george1421 address of the fog server is static. The way I have the network setup, i have a separate VLAN just for imaging. The fog server (static ip) and client (DHCP) both get an IP address from the same subnet.

[Tom Elliott]

@sjensen Is the IP Address of the FOG Server 192.168.28.18

[sjensen]

@sjensen

[Tom Elliott]

@sjensen So the picture from the NFS issue appears to be showing the IP as 192.168.28.18 or 192.168.28.18.16 (I can’t tell the picture get’s too pixelated).

Please either try getting a better picture of the message or tell us what IP it’s looking at for NFS?

[george1421]

@sjensen OK now that we confirmed the IP address is 192.168.28.10 its inline with the error message on the screen shot you posted. Its difficult to see in the picture if the last digit is an 8 or a 0, lets assume its 0.

now from the fog server command prompt lets connect to your nfs share.

mount -t nfs 192.168.28.10:/images /mnt

Then check the content of that mount

ls /mnt that should give you the same response as ls /images

If they are the same then you can nfs mount your fog server by your fog server.

You need to unmount that share to avoid conflicts in the future.

umount /mnt

[sjensen]

@george1421 The result was the same after that was mounted.

[sjensen]

@Tom-Elliott The ip is 192.168. 28.10

[Tom Elliott]

@sjensen What’s the permissions of the /images and /images/dev directories?

[sjensen]

@Tom-Elliott

[Tom Elliott]

Are both set to fsid=1?

But that’s not permissions either.

[george1421]

@sjensen ls -la /images and ls -la /images/dev

[sjensen]

@george1421

[Tom Elliott]

@sjensen THen my other question, what is the exact output of cat /etc/exports

Please don’t screen shot and leave a “part” of it out this time?

[george1421]

@Tom-Elliott for reference this is what my fog server has (note the fsid is different for each export [share]):

pi@pi01:~ $ cat /etc/exports 
/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

[sjensen]

@george1421 What does that affect? Should I change it?

[Tom Elliott]

@sjensen I need to see it.

/images should have FSID of 0
/images/dev should have FSID of 1.

If you must change these values for other reasons, they cannot be the same, and they should be “iterative”

[george1421]

@sjensen said in mounting /images failed: Connection timed out:

@george1421 What does that affect? Should I change it?

In a word, please show us your cards first. Then we will tell you if you won or not.

[sjensen]

@george1421

[Tom Elliott]

Please give a shot at changing the fsid’s so they are in order:
/images with fsid 0
/images/dev with fsid 1.

Also, please give a try at:

sudo touch /images/.mntcheck
sudo touch /images/dev/.mntcheck
sudo chown -R fog:root /images
sudo chmod -R 777 /images
sudo exportfs -a
sudo service nfs-kernel-server restart
sudo service ufw disable

[sjensen]

@Tom-Elliott Ok I did what you asked. Should I try to upload an image again?