FOG: 1.5.4 -> How to setup NAS - Synology DiskStation as Master Node

[jeremyvdv]

it makes me crazy … I still have data from the image created …

And I can not download … the capture spot turns in a loop …

[george1421]

@jeremyvdv Well I guess we have 2 things.

1. 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.

2. 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.

[jeremyvdv]

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.

[george1421]

@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.

1. Schedule a capture task with a target computer, but before you hit the submit button check the debug check box then submit the task.
2. pxe boot the target computer.
3. on the target computer press enter to clear the several screens of text to end up a the FOS Linux command prompt.
4. key in ip addr show to get the IP address of the target computer.
5. key in passwd and reset root’s password to something simple like hello (no worries the password will be reset when you next reboot the target computer).
6. 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 root with the password you set in step 5.

That will prep us for a debugging session.

[george1421]

@george1421 After having a chat session with @jeremyvdv which we had to cut short I discovered somethings.

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/dev but 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 /volume1/images2

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.

[george1421]

@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

[jeremyvdv]

Hello George

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]

@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?

[jeremyvdv]

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

[george1421]

@jeremyvdv Ah, OK I missed in the screen shot the type=down.

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).

[jeremyvdv]

ok I try max client on fog a 0 and on the nas a 10 … I keep you informed.
Thank you

[jeremyvdv]

Hello
so I check the parameters but I still have the same problem.

[jeremyvdv]

Hello

Do you have an idea @george1421 Georges for my problem?

Thank you

[george1421]

@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.

[loadedmind]

@Alex78 What do we need to do to gain access to the images? When clicking any of the links, I get “Not Found”.