Synology NAS as FOG Storage node
-
@VincentJ Just for clarity the issue I’m working on is the dashboard reporting only works correctly if the storage node is a “real” fog server. If that isn’t a problem then a NAS will work perfectly.
The only caveat to using a NAS as your primary storage is that multicast deployments will not work at all. If you only do unicast imaging then again, there is no problem using a NAS in this manner.
-
hello, I’m trying to use this…and when the sync starts the error I receive is: mirror: Access failed: 550 No such file or directory. (/volume9/fog_images/test01) test01 is the test images I’ve created…
all the other point ar ok as the guide… -
Hello, so…
the sync between the default repository and the synology works.
Now I’ve moved the synology storage on another storage group, because I want to use only it since the default (fog server) has not enough space for my pourpose…
The snapins creation and distribution works fine (i can create snapins only on the synology and deploy them from the synology)
But…trying to capture an image (setted to stay on the synology storage) I receive an error:mounting x.x.x.x:/fog_images/dev on /images failed: Permission denied
have you any suggestions?
-
@brusa.matteo Hmm I didn’t see your post from a few days ago, sorry.
You are getting a permission denied message. This sounds like you don’t have the nfs permissions setup correctly on your NAS.
Specifically in this section
NFS Permission (tab)
Create new Permission
Hostname or IP: *
Privilege: Read/Write
Squash: No mapping
Security: sys
Checked Enable asynchronous
Checked Allow users to access mounted subfolders -
@george1421 thanks for your reply…
it was my fault: I had entered the wrong path in the configuration…
working late at night is not a good idea!!
thaks a lot! -
@george1421 I “cheesed” the dashboard in our FOG by mounting the image folder on the FOG server as NFS from my synology NAS (rather than add another storage node). Using an 815+ here and have been for a while.
-
@KKTwenty101 said in Synology NAS as FOG Storage node:
@george1421 I “cheesed” the dashboard in our FOG by mounting the image folder on the FOG server as NFS from my synology NAS (rather than add another storage node). Using an 815+ here and have been for a while.
^^Please explain this^^
If I understand correctly you have an nfs share on your nas, and you mounted that nfs share over the /images directory on your fog server. And the fog server is sharing out the /images directory on your fog server??
-
@george1421 yes. That way the fog server considers /images local so the “defaultmember” pie chart works just fine.
-
@george1421 Hello, i did all the things you say, but i stay with this error, and i don’t know what this means:
Did someone known this problem ?
-
@alex78 Just be aware that changes in the FOG program make using a NAS as a storage node a bit more difficult.
Did you complete all parts of the tutorial? With synology nas, typically the path would be
/volume1/images/igmWindowsit appears you have missed a setting someplace. -
@george1421
Ok, I am still checking all the steps of your tutorial and I will come back to you, if it not solved the problem or on the contrary if it solved it, thank you for your answer. -
I think it’s working thanks you
-
@alex78 Can you tell us what you had missed originally and what you did to fix it? This could help another user down the road, so always good to share if you can.
-
@tom-elliott I just unchecked “Enable advanced sharing permissions in affected folders”:
-
I would like to appreciate this nice little post, I wish I had stumbled upon this earlier. Last week I tried creating my Synology NAS as a storage node and it worked. Little did I know that was the beginning of my misery. Whole week I struggled in fixing the replication issues.
Had I found this Thread earlier, I wouldn’t have attempted it. -
Hi,
First of all, thanks to george1421 and other users who deliver this solution.
Before i say what is my problem, the existant :
FOG serveur 1.5.4 on a Debian 9.4 with no graphical environment (terminal only) with 100Go disk. This debian is virtual on ESX6.5.0
NAS : Synologie DS116 with plenty of spaceI’m a bit confuse.
All opération discribe here works whell, but when i capture, the image is copied on FOG server. Then, after capture, image is automaticaly copied on NAS. But after copy on NAS was finish, she stay on my FOG server, so after two Win10 capture the server is full.
What i miss out on ?
Is the capture normally do directly on NAS without any write on Server ?Thanks in advance.
-
@Vincent-Caraby First let me say that changes in the fog server makes using a non-fog NAS a problem if you have it configured as you have it now. The FOG replicator will continue to copy the image over and over again to your NAS.
But let me tell you that you can do what I think you want. You must know that you can only capture images to a Master Node in a storage group. So in your settings change it so the NAS is the master node in your storage group, instead of the FOG server. This should make the images to go directly to the NAS and not FOG server.
-
Thanks, i see the red message at top of topic to late.
I test this solution, it seem to be wright but i’m stuck on a permission problem.Setup my NAS storage node to master node. But when i would capture there a message “permission denied” when mounting file system.
I don’t understand who on what give permission ? I suppose it’s my “adminfog” (fog server) to my NAS folders (images, snapins, tftpboot).
Is there a file where i can configure this rigtly ? A bit lost and not linux expert, but i prefer use config files if possible.
Some capture of my configuration :
-
@Vincent-Caraby Well lets see if I can explain this, but the answer is simple and complicated at the same time.
The FOS engine connects to the master node as
rootso the synology nas needs to allowrootto connect to the /volume1/images and /volume1/images/dev as root.Also the FOS engine will use ftp to connect to the NAS using the
adminfoguser and password you defined in the Storage Node configuration to move the files from /images/dev to /images directory. -
G george1421 referenced this topic on
-
G george1421 referenced this topic on
-
G george1421 referenced this topic on
-
G george1421 referenced this topic on
-
G george1421 referenced this topic on
-
@george1421
for those struggling with permissions with dev folder.
nfs creates a root:root with 775 permissions and fog ftpuser isn’t part of that groupJust use setgid feature on filesystem . it will enable inheritance
first change the owner of the folders and make “users” the group , lets say fog is your ftp userchown -R fog:users /volume1/images/
#set inheritance to the dev folder
chmod g+s /volume1/images/dev/
now every new file under dev will have the directory group owner
Regards
