@habu what I’m saying is its copying data that should not be there. Modifying core files only works around the issue. What I’m suggest will fix the issue permanently for you.

@Tom-Elliott, @Sebastian-Roth all working! 🙂 🙂 🙂
The image already is deploying!

Thank you guys!
Solved!

@Wayne-Workman said:

I really doubt it’s the unmanaged switches fault, and I’m willing to lay 99% odds it’s a cable.

While I totally agree on what you said and fully trust in your network knowledge (I mean that!) this is not a cable issue from my point of view - not this time at least:
http://www.viktorious.nl/2013/11/05/cisco-sg200-08-nfs/
https://supportforums.cisco.com/discussion/11755791/sg200-08-firmware-issue

Other than that I found this as well: http://serverfault.com/questions/367107/cant-mount-nfs-share-over-tcp

Turns out there was a “security” feature enabled on our PowerConnect switch that took offense to NFS SYN packets with source ports < 1024 (dos-control tcpflag). Suffice it to say, disabling the feature solved the issue.

Reading this again I think this is actually the case here. Why? Because I made Miguel try telnet <fog-server-ip> 56557 (the actual NFS data port) and it worked - as telnet is not using a high source port I suppose.

@Miguel-Palacios
I think fog 1.2 is not totally compatible with synology nas because synology use two different path to access data over NFS & FTP (/volume1/images & /images)
and on fog storage node interface you can only set one path.
(Fog does the rename job with the ftp account.)
you need to go with a newer fog version to have the “ftp path” option.

I put the FOG server on a VM, and then have storage on my NAS.

Most NAS’ can function as a storage node if you configure it correctly, I normally use FreeNAS.