FOG: 1.5.4 -> How to setup NAS - Synology DiskStation as Master Node
Follow this tutorial step by step, and you will have everything configured, I spent a lot of hours to understand where my mistakes were and I make this tutorial to help the maximum number of people.
To begin, let’s configure the NAS - Synology DiskStation:
First, go to --> Control Panel --> File services --> SMB/AFP/NFS, scroll down:
-Check “Activer NFS” = “Enable NFS”.
-Check “Activer la prise en charge de NFSv4.1” = “Enable support for NFSv4.1”.
Go to --> Control Panel --> File services --> FTP:
-Check “Activer le service FTP (pas de chiffrage)” = “Enable FTP service (no encryption)”.
-Check “Utiliser la plage de ports par défaut (55536-55567)” = “Use the default port range (55536-55567)”
Go to Control Panel --> User --> Select the advanced window:
-Check “Activer le service d’accueil de l’utilisateur” = “Enable the user’s home service”.
-Let’s create the folders to share.
-Go to Control Panel --> shared folders --> create and follow the pictures below:
-Click “Suivant” = “Next”.
-Click “Suivant” = “Next”.
-Click “Suivant” = “Next”.
-Click “Appliquer” = “Apply”.
Create two more shared folders with the name “tftpboot” and “snapins”, with the same configuration as the shared folder that we create together "images"
Go to --> Control Panel --> File services – TFTP:
-Check “Activer le service TFTP” = “Enable TFTP Service”.
-Dossier racine TFTP = “TFTP root folder” : tftpboot (choose the tftpboot folder you created).
After doing that, you have to create a user.
-Go to Control Panel --> User --> Create and follow the pictures below:
-Here the username = userFOG and password = FOGuser.
-Check --> “Ne pas autoriser l’utilisateur à changer le mot de passe du compte” = “Do not allow the user to change the password of the account”.
-Check only --> users.
-Folder “images” --> Reading/writing.
-Folder “snapins” --> Reading/writing.
-Folder “tftpboot” --> Reading/writing.
Go to Control Panel --> Shared folders --> select the folder “images” you created before --> Right click on folder --> edit --> NFS permissions --> “Créer” = “Create”:
-Squash: no mapping
-Check “Activer le mode asynchrone” = “Enable asynchronous mode”.
-Check “Permettre à des utilisateurs d’accéder aux sous-dossiers montés” = “Allow users to access mounted subfolders”.
DO THE SAME THINGS ON THE OTHER TWO FOLDERS: “tftpboot” and “snapins”.
DO NOT ACTIVATE THIS IN FOLDERS:
NAS is now configured.
Let’s move on the FOG server. (I host the server fog on ubuntu):
CREATE THE SAME USER THAT WE CREATED ON THE NAS ON THE FOG SERVER
Connect to your FOG server and open the terminal and enter these lines:
sudo -s mount -t nfs "Your_NAS_IP":/volume1/images /mnt mkdir /mnt/dev touch /mnt/.mntcheck umount /mnt
mount -t nfs <syno_nas_ip>:/volume1/images/dev /mnt touch /mnt/.mntcheck umount /mnt
mount -t nfs <syno_nas_ip>:/volume1/snapins /mnt mkdir /mnt/ssl cp -R /opt/fog/ssl/* /mnt/ssl umount /mnt
mount -t nfs <syno_nas_ip>:/volume1/tftpboot /mnt cp -R /tftpboot/* /mnt umount /mnt
When you have done that, you have nothing to do on the FOG server.
Go to the FOG Management GUI, select Storage --> Add storage Node:
-Management Username it’s the user we created before on NAS.
-Management Password it’s the same password of the user we created on the NAS.
-Check master node.
-Storage Group: default.
-Click on ADD.
Go to Storage --> All storage nodes --> Click on DefaultMember:
-Uncheck “Master Node”.
Now create a new image and try to capture a image:
Go to hosts --> List all hosts --> Click on your host:
And now capture the image:
YOU CAN DEPLOY IMAGE TOO
There is already a very good tutorial on this subject, but I wanted to enhance it with images that it is more understandable.
@jeremyvdv I’m sorry I don’t have a good answer for you. With the fog server max clients at 0 and other nodes greater than 0, the code should use the available storage nodes and not the FOG server for image delivery.
Do you have an idea @george1421 Georges for my problem?
so I check the parameters but I still have the same problem.
ok I try max client on fog a 0 and on the nas a 10 … I keep you informed.
@jeremyvdv Ah, OK I missed in the screen shot the
Then what its doing is picking the FOG server as the download node. If you go into the storage configuration and pick the default storage node (the fog server) change the max clients field to 0. Make sure the max clients field on the NAS is set to something higher than 0 (10 is default).
I did not change anything at the storage level …
And I have never tested the download of an image since I have never been able to create until now
@jeremyvdv But this part worked before. This is the NFS side. The image was getting to the NAS but it was failing to move to the /images2 directory. That was/is an FTP issue. Now its failing to upload the image, which is an nfs issue.
Ah, I see it. From my notes I have your nas at IP 10.1.5.8 your storeIP is 10.16.3.129 your fog server. Did you change the storage node configuration? Your nas server needs to be the master in the storage group. Here is the kernel line you collected from the debug session I saved.
cat /proc/cmdline loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://10.16.3.129/fog/ consoleblank=0 rootfstype=ext4 mac=30:8d:99:14:a4:e6 ftp=10.1.5.8 storage=10.1.5.8:/volume1/images2/dev/ storageip=10.1.5.8 osid=5 irqpoll hostname=LP0045 chkdsk=0 img=test10 imgType=n imgPartitionType=all imgid=5 imgFormat=5 PIGZ_COMP=-10 hostearly=1 pct=5 ignorepg=1 isdebug=yes type=up
See how it differs from the picture you posted?
Actually it was the path in ftp Path.
My image capture works. and I thank you very much.
now I meet the problem attached when downloading the image : - /
@george1421 After thinking about this I looked at my tutorial on setting up a synology nas as a storage node and my guess in the previous post was correct, the FTP path should just be /images as seen in this post: https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node/28
I asked him to post the output of the kernel parameters from a debug session.
cat /proc/cmdline loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://10.16.3.129/fog/ consoleblank=0 rootfstype=ext4 mac=00:00:00:00:00:00 ftp=10.1.5.8 storage=10.1.5.8:/volume1/images2/dev/ storageip=10.1.5.8 osid=5 irqpoll hostname=LP0045 chkdsk=0 img=test10 imgType=n imgPartitionType=all imgid=5 imgFormat=5 PIGZ_COMP=-10 hostearly=1 pct=5 ignorepg=1 isdebug=yes type=up
Where we can see the storage path for NFS is
10.1.5.8:/volume1/images2/devbut looking on the nas via FTP there is no reference to /volume1/images2 its just /images2, yet there is data in /images2/dev/<mac_address> directory. So NFS is working and FTP is not.
If we looked at what he posted as a screen shot of the nas storage node
We can see that he is clearly calling out
When he connected via ftp to the nas the path was /images2/dev/<mac_address> like we see from the top picture here.
So what I’m thinking is that we leave storage path at /volume1/images2 and set the FTP path to /images2 then it should work. I think NFS is looking at it form the filesystem view where ftp is looking at the path from a logical view. They technically point to the same location, just how they get there is via two different paths.
@jeremyvdv If you are ready now, I am. We can switch over to FOG IM (look for the bubble in the upper right corner of this forum) to send the details of teamviewer connection.
What I will need you to do before we connect to make things go quicker.
- Schedule a capture task with a target computer, but before you hit the submit button check the debug check box then submit the task.
- pxe boot the target computer.
- on the target computer press enter to clear the several screens of text to end up a the FOS Linux command prompt.
- key in
ip addr showto get the IP address of the target computer.
- key in
passwdand reset root’s password to something simple like hello (no worries the password will be reset when you next reboot the target computer).
- Now from your teamviewer host computer use putty and ssh into the target computer using the IP address you collected in step 4 and the user
rootwith the password you set in step 5.
That will prep us for a debugging session.
yes we can do a team viewer.
Can you set a date and time if you can?
IF you can I give you a clear diagram of my install.
@jeremyvdv Well I guess we have 2 things.
While this is not a fix, you can save the failed upload by manually moving the folder /volume1/Images2/dev/<mac_address> to /volume1/Images2/<image_name> . Understand this is not a fix only a work around.
Do you have teamviewer capabilities? I would like to see what you are seeing, because its impossible to happen the way you say it does. Understand I am not doubting you, only don’t understand how its possible.
it makes me crazy … I still have data from the image created …
And I can not download … the capture spot turns in a loop …
yes i have disabled the id mode on the stoarge default.
but I do not know what to do concretely …
Min image is created well and the tahce resten loop
@jeremyvdv Then I don’t understand how this picture was created in this post: https://forums.fogproject.org/topic/12168/fog-1-5-4-how-to-setup-nas-synology-diskstation-as-master-node/26 The path clearly states /images/dev/<mac_address>. I can understand if the FTP Path is different than your Image Path in the host definition, but that is not the case in your picture of the storage node configuration here: https://forums.fogproject.org/topic/12168/fog-1-5-4-how-to-setup-nas-synology-diskstation-as-master-node/28
Did you by chance on the default node (real fog server) uncheck the box that says Is Master Node ? You can only have one master node in each storage group. You can have more than one storage group, but each storage group can only have one master.
Yes that’s right.
on the nas the files are well in volume1 \ images2 \ dev <mac adress>
can someone help me?
^ thank you
Are you telling me the that the storage node configuration you have is still creating the error message
ftp_put(/images/dev/308...)because the storage node configuration clearly states /volume1/images2 fro the FTP path. This should not happen. Do you happen to have more than the one storage node configuration for this nas? I can’t explain why it says /volume1/images2 yet the error message is still defult?
When you look on the NAS the files are for sure in
I can not understand.
When I capture the image … the files are well stored in the synlogy. But I can not find the way from the fog …