Alright, I got this figured out. Everything was configured correctly on the FOG end, it ended up being a setting on the Synology NAS that I needed to change. I had to enable SFTP. Once that was enabled, everything began working correctly.

Alright, I got this figured out. Everything was configured correctly on the FOG end, it ended up being a setting on the Synology NAS that I needed to change. I had to enable SFTP. Once that was enabled, everything began working correctly.

@Wayne-Workman said:

@Chris-Bosman said:

Wayne,

Going into the folder where my images are to be stored on the NAS via the command line and running pwd, the path I get is “/volume1/Workstation_Images”. The lowest directory I can get to on the NAS simply displays as “/”.

To me, this would suggest that “/volume1/Workstation_Images” is the proper path? Am I correct in assuming that? Because I’ve attempted using that path and still receive the error.

For FTP credentials, I am using the same user name and credentials in the following locations. This has been the case since the start:

• On the Synology NAS box, which as read/write privileges over the Workstation_Images folder
• Under Management Username & Management Password for the storage node.
• Under FOG_TFTP_FTP_USERNAME/FOG_TFT_FTP_PASSWORD
• For the FOG Server’s “fog” user
• In the file /opt/fog/.fogsettings under storageftpuser/storageftppass

So close.

On a windows machine at a command prompt, you can FTP into your FOG box.

Like this:

There are more details here: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP#Try_to_get_a_file_with_Windows:

So, the path you found was the disk path, via CLI on the server itself. I’m asking you to figure out your “FTP Path”

Wayne,

Following the instructions in the linked Troubleshooting document does not work with the instructions provided. Most commands using Windows Command Line give me an error of “500 PORT/EPRT (Active Mode/Extended Active Mode) is not supported. Use PASV/EPSV instead of this”. This includes attempting to use “ls” to list any directory or using “cd”. Using “pwd” to list the directory gives me an answer of “‘/’ is current directory.”

I did, however, find the Workstation_Images folder by randomly inputting some cd commands. Getting into that folder and requesting the filepath gave me “‘/Workstation_Images’ is current directory”. This would be helpful, except I’ve already attempted using both “/Workstation_Images” and "Workstation_Images’ (without the leading /) as my FTP Path.

Any advice on where to go from here?

• Chris

Wayne,

Going into the folder where my images are to be stored on the NAS via the command line and running pwd, the path I get is “/volume1/Workstation_Images”. The lowest directory I can get to on the NAS simply displays as “/”.

To me, this would suggest that “/volume1/Workstation_Images” is the proper path? Am I correct in assuming that? Because I’ve attempted using that path and still receive the error.

For FTP credentials, I am using the same user name and credentials in the following locations. This has been the case since the start:

• On the Synology NAS box, which as read/write privileges over the Workstation_Images folder
• Under Management Username & Management Password for the storage node.
• Under FOG_TFTP_FTP_USERNAME/FOG_TFT_FTP_PASSWORD
• For the FOG Server’s “fog” user
• In the file /opt/fog/.fogsettings under storageftpuser/storageftppass

Tom,

I have tried “/Workstation_Images” and simply “Workstation_Images” as the ftp path and have had no luck. The images still end up in the /[NFS path]/dev/[MAC address] folder.

What does it need to be changed to?

To be specific, my Image Path is /volume1/Workstation_Images, as is my FTP path.

Hello,

I posted originally in an older topic but am now creating a new topic for this issue, as I am just finding time to come back around to it.

I am attempting to use a Synology NAS for the storage of my FOG server’s images. I am able to successfully upload images to the NAS, however I am unable to then deploy those images, receiving the error “You must first upload an image to create a download task.”

I am using FOG Trunk Git version 4660 on Ubuntu 15.04.

My pertinent storage node information is as followed:

Storage Node Name: [NAME]
IP Address: [NAS IP Address]
Web root [NAS IP Address] (Is this correct?)
Image Path: [NFS path to Images folder on the NAS]
FTP Path: [Identical to Image Path] (Is this correct?)
Management Username: fog
Management Password: [password for fog user on the NAS]

Per the documentation at https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP#Credentials_.2F_Passwords, all passwords mentioned on that page are identical. Additionally, the fog user on the NAS also has that same password.

I am able to successfully FTP from the FOG server to the NAS using the fog user credentials and both upload and download a test text file to the Images folder. Permissions when I do so appear appropriately, and when I do FTP into the NAS from the FOG server using the fog user, I do end up in the Images folder.

Ultimately, once I upload the image, said image ends up in the /[Images NFS path]/dev/[Machine’s MAC address] folder, which if I’m remembering correctly indicates some failure of FTP.

Any assistance would be appreciated.

Thank you,
Chris Bosman

@Wayne-Workman Case is confirmed correct and the .mntcheck files have been moved there. Uploading works fine. I set the permissions recursively but still cannot set up a download task. I get the error:

“Download task failed to create for [COMPUTER] with image [IMAGE NAME]
To setup download task, you must first upload an image”

@Wayne-Workman Hey, thanks for the reply. I’m back in to the office and working on this issue.

I was able to confirm that FTP is working in general on the NAS via Windows.

So my problem is twofold:

The first is I was/am having the same specific issue as @szecca1 where after uploading an image, the image does not properly get FTP’d to the folder for images that I have set up and instead stays in the dev folder under the MAC address. I am assuming this has to do with the FTP issue that @Tom-Elliott described and suggested the symbolic links. I was able to eventually properly put up the symbolic links. I haven’t been able to test yet, but I think that any new upload will be able to be used properly.

But that’s where my second issue comes in. I have an upload that I need quickly downloaded that ended up in a /dev/[MACADDRESS] folder. I manually moved the image to a folder named appropriately for said image but I’m still not able to create a download task. It’s like the image within FOG is not associated with the folder I created. I am not sure how to forge this association so I can start the download task. This is a large image file and I do not necessarily have time to upload it again. Any suggestions would be appreciated. Thank you.

I have gone through this thread because I too was trying to add a Synology NAS share as additional storage for my FOG server. Everything in this post was very helpful…

Until I got to the end. How did the FTP issue get resolved, step-by-step? I attempted to perform a symbolic link on the NAS as instructed in the final developer post, however this did not seem to resolve my issue.

Any further help would be greatly appreciated.

Any other suggestions? I already have a couple images saved to the server and would rather not start from scratch, but if I can’t figure this out, I guess that’ll have to be my solution.