Well… if we didn’t hear from him this morning, that probably means the FOG server stayed up all week. Thread solved.

I’m thinking it was cache related as a refresh got it fixed.

@Tom-Elliott Working with latest update TY

I wanted to respond with a link:

https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

Please bear in mind that at the time of this post, this article is a work in progress - however at this point it does contain a lot of information and links to other information.

@Wayne-Workman Sorry guys, was doing a Core switch replacement at my job. Imaging still works perfectly, in fact just uploaded an image about an hour ago.

@szecca1 said:

@Wayne-Workman Also the test.txt file is in the /images folder on the FOG server but not on the Synology box, just for your information

You should be altering the commands so that you are testing the synology box. The test file should exist on the Synology box.

When the directory successfully mounts via NFS, you shouldn’t get any messages at all.

Have you updated to the latest yet?

Glad to see this is fixed. I helped to the extent of my abilities via forum chat but I came to a dead end basically. And Tom’s post explains why. Good to see a solution is found.

@Chris-Bosman A new feature has been added to FOG Trunk that allows users to specify the FTP path to the image directory for any storage node.

This is exactly what you need in your situation. The relevant thread is here: https://forums.fogproject.org/topic/5333/ftp-path-for-storage-nodes

Here is how you would upgrade to FOG Trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk