Adding NAS (NFS) - storage to FOG

[boeleke]

Hi there all,

i’m working already a couple of weeks with FOG , but i’m making a couple of changes now.
In stead of local storage , i want to use our QNAP - nas to save / upload our images.

The problem is , i get some errors while doing it.
First i tried to add the nas directly to the storage node , but it didn’t work. The graph wasn’t showing up.
So i tried it an other way. I mounted my nas-storage first with NFS , then with CIFS then with FTP on a map /mnt/nfs/images/ & in the GUI i just made an storage node with this path.

I see all the things from my nas over there , but when i want to upload an image i get the next error

** Mounting 172.16.0.201:/mnt/nfs/images/dev on /images failed : permission denied

Fatal error : Failed to mount NFS volume - computer will reboot in 1 minute .**

I gave the 172.16.0.201 - address the rights to work with NFS on my QNAP-nas but i don’t get it work.
Its really frustrating , can someone help?

Greetings,
Tom

Ps: They got the .mntcheck files

[Sebastian Roth]

@boeleke Re-exporting a mounted NFS share is not going to work. See here and numerous other information on the internet. Has been asked in the FOG forums a couple of times as well.

[boeleke]

@Sebastian-Roth
I did search a lot about this problem but i didn’t found any solution.
I’m not working with 3 systems like in your topic. I’m just working with a QNAP that is mounted on the ubuntu fog server. & when i add this storage in the gui , i find it. But once i want to upload an image , it fails.

I hope you can help me further.
I’m not that familiar with linux.

Greetings

[Sebastian Roth]

@boeleke You might want to read through this post and we also have an article in the wiki (FreeNAS not QNAP).

Edit: And maybe try searching the forums for QNAP as well.

[boeleke]

@Sebastian-Roth
I did read both of the articles already & tried it.
But still nothing.

The must be a possibility to add it , i’m searching already 2 days for it but i didn’t find it yet…

[Wayne Workman]

@boeleke said:

@Sebastian-Roth
I did read both of the articles already & tried it.
But still nothing.

Read closer. I promise your QNAP nas can be a storage node. It’s just a matter of setting up NFS and FTP on it. If you have some time, maybe I can help you via teamviewer so that we can figure it out, and I can later document what we found.

[boeleke]

@Wayne-Workman

Hi there.
I would be gratefull.
I think i got some mistakes with my QNAP. I’m not sure what settings …
See pictures.

[ch3i]

@boeleke Hi, If your NAS is mounted on your FOG server via NFS you can’t re-export it as NFS via FOG server. You have to create a node storage with IP of NAS ans specify NFS and FTP path in the node settings. Before you have to create a user “fog” in your NAS with the same password of the “fog” user of the FOG server.

When you’ll upload/download image on that node (Your NAS) the fog client will connect directly on your NAS not via your FOG server.

[boeleke]

@ch3i

Hi there ch3i,

thanks for your answer.
that was the first thing i tried. I added a user ‘fog’ with the same password on the QNAP.
Then i added a storage node. But it failed. (See pictures)

LINK FOR BETTER IMAGE : http://i65.tinypic.com/5yucyd.png

[ch3i]

@boeleke FTP and NFS path or the sames on your NAS ?

[boeleke]

@ch3i

hi there!
I’m not sure , i’m not that familiar with all the NAS-settings.
I can acces my NAS on windows with :

ftp://172.16.0.17/images

& i use the same path for my nfs , isn’t it?

Sorry , i’m just a beginner :).

[ch3i]

@boeleke For QNAP the NFS path seem to be : /share/your_nfs_share but for the ftp access it’s /your_nfs_share. In FOG trunk (https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk) you can differentiate NFS and FTP path. In your version FTP and NFS path must be the same !

[boeleke]

@ch3i

hi there.
Thank you for the help. I’m working in a school environment & we can’t work with unstable releases.
If we want to use it every week , it need to be stable.
Is there not another option?

Thanks for the help!

[ch3i]

@boeleke I’m working in a School and use Trunk version Trunk versions of FOG are “stable”.

[Wayne Workman]

@ch3i I too am a systems admin at a school, and I’ve been using FOG Trunk for over a year now. It’s much more stable than it used to be. Others here in the corporate world also use FOG Trunk.

I would recommend that you setup FOG Trunk on a VM though, and take snapshots before each update - just so you have a safety net.

[boeleke]

@Wayne-Workman & @ch3i ,

Hi there guys,

you both convinced me to do this. So i upgraded to Fog Trunk (i can Revert anyway with a snapshot).
But now i need your guys help to add this storage node. You got a lot more settings :
I’m not sure if its correct now. I mean , the snapin path – must that be a map on the QNAP also?

When i use this settings , i get next mistake

while upgrading trunk , he said : (Setting up and starting VSFTP server : Failed! )

Can you guys help me further?

Sorry for my bad english.

Greetings,
Tom

[ch3i]

@boeleke Hi, it’s normal, because your NAS is not a “FOG Storage Node”. A real FOG Storage Node is an installation of FOG on another server with “Node Installation”. You NAS have not the FOG installation. It’s not a problem to upload/download.
Tip : If you use multicast your NAS storage node can’t be the master of the group storage.

@Tom-Elliott It’s possible to check if the hw.php is present and display a message to indicate that it’s not a normal node ?

[boeleke]

@ch3i

Hi Ch3i,
eumh wait. With Multicast you mean , imaging more computer at once? So for example 100 computer with 1 image?
So i need to make a new storage GROUP and link the image with this group?
But how can i image more computers at once then? Just not set it as master node?

I’ll try an upload in a couple of minutes then.

[boeleke]

@ch3i :

i tried to upload an image now.
But still , i get an error :
Could not mount images folder (/bin/fog.upload)
Args Passed.

[raice]

I didn’t test it. But I would say, mount it via linux (ssh into the fog server) and make sure it got the right permissions.