[SOLVED] Fatal Error: Failed to mount NFS Volume
Hi Fog Community,
As i say in the title, i can’t upload any image on my shared storage i just created.
I mounted a shared directory on /srv/cfs/SRVADM/images on my server, connected by domain admin account; on my FOG server, i’m able to create a directory with mkdir or a file asked for the problem like:
The two files appears in the directory; but when i try tu upload an image from a computer, iPXE say in “Mouting File System” step: "mount: mounting 10.1.11.170:/srv/cifs/SRVADM/images/dev on /images failed: Permission denied
root@SRVFOG ls -l /srv/cifs/SRVADM returns
drwxr-xr-x 2 fog fog 0 mars 10 18:18 images
On the storage node defined on fog webui, the credentials are id: “fog” and pass “password” exactly like “defaultStorageNode”
Thank you for ur help and sorry for my English…
Ok, thanks for your precisions, i’ll work on NFS storage later.
Is there a simple way to externalize the fog storage … ?
Yes, you can use any number of NAS products and it’s possible to use Windows server as well.
without using NFS because its look very hard.
How FOG users store their images on a Windows Server?
The general idea is outlined in the article that Sebastian posted.
are they forced to use the NFS ?
They fianlly use linux or local fog storage ?
Some give up and decide to go the easy route and use linux.
@arnaudrigole What I said was “It’s not officially supported but …” - meaning that you can setup your Windows server as a storage node for FOG - we just don’t provide any kind of automatic installer script (like we do for linux). But we’ll still try to help you setting it up here in the forums. I don’t have access to a windows server so I can’t go into updating the article. Maybe we can work together. You try things as noted in the article and let us know what works and what we should change…
Why did u say "but you should be able to setup FOG as a storage node on your windows server."
its the opposite , no ? I want to setup my Windows server as a storage node for FOG.
@Wayne-Workman Is there a simple way to externalize the fog storage … ? without using NFS because its look very hard. How FOG users store their images on a Windows Server? are they forced to use the NFS ? They fianlly use linux or local fog storage ?
I’d like to try to review that wiki article and update it - but it’s a lower priority in the scope of things. We have a perfectly working storage node system designed for Linux.
@arnaudrigole Again, please read through this wiki article: https://wiki.fogproject.org/wiki/index.php/Windows_Storage_Node
It’s not officially supported but you should be able to setup FOG as a storage node on your windows server.
Thanks for your reply, but i really think that its not a complicated problem like that… :/
I just never setup a NFS share between unix and Windows and i think i dont setup credentials as i should.
•NFS share (windows) <-> NFS share (linux) <-> FOG client: does not work!
Maybe my problem is here!?
So whats the better solution to export images of fog server on a external storage ?
@Quazz Good catch! As well @arnaudrigole you might want to look into the article on the same blog explaining the UID mapping a little closer: http://blogs.msdn.com/b/sfu/archive/2007/04/19/sharing-folders-over-nfs.aspx
And you might want to try the ‘nolock’ option that we use with FOG usually:
mount -t nfs -o nolock 10.1.11.64:/FOG /srv/nfs/SRVADM/Images
But reading your initial post again I suppose I need to tell you that even if you are able to mount the NFS share from your Linux server you won’t be able to send your images to that NFS share from your FOG client. Re-exporting NFS shares is not possible!
- NFS share (linux) <-> FOG client: works!
- NFS share (windows) <-> FOG client: works!
- NFS share (windows) <-> NFS share (linux) <-> FOG client: does not work!
So when you get the permissions correct you still need to setup both NFS share in windows correctly (default /images and /images/dev) and/or configure storage management within the web gui accordingly! Please read this as well: https://wiki.fogproject.org/wiki/index.php/Windows_Storage_Node
@arnaudrigole I’m not experienced with AD, so I had to use some googlefu and it seems like this is an issue with AD mapping unix users.
Check out this link on what to try: http://blogs.msdn.com/b/sfu/archive/2007/04/19/mounting-nfs-share-on-nfs-client.aspx
Ok i did
umount /srv/nfs/SRVADM/Images then
mount -t nfs 10.1.11.64:/FOG /srv/nfs/SRVADM/Images -> command seems to be ok but…
cd /srv/nfs/SRVADM/Images -> -bash: cd: /srv/nfs/SRVADM/Images/: Input/Output error
showmount -e 10.1.11.64
Export list for 10.1.11.64:
you right, the nfs share on Windows server is defined only on /FOG, but it still the same … :/
@arnaudrigole Seems like you don’t have an export for /FOG/Images only for /FOG. Can you mount /FOG over NFS?
It returns me “Export list for 10.1.11.64: /FOG (everyone)”
@arnaudrigole Do this on your linux machine:
showmount -e 10.1.11.64
I’m not sure if that works with windows server, but if it does, it should basically give you the answer.
FOG directory is located physically on E:\informatique\Service_info\FOG\Images but the NFS share is setup on FOG so nfs assistant told me the way is : \SRVADM\FOG , so i have to set:
mount -t nfs 10.1.11.64:/E:/informatique/Service_info/FOG/Images ??
@arnaudrigole Is the FOG directory located at the root of that server? Because you need the full path!
Ok so, the mount cmd i type is exactly this : mount -t nfs 10.1.11.64:/FOG/Images /srv/nfs/SRVADM/Images
"FOG" directory is the one shared by NFS on the server, give full rw rights for “anybody” -> nothing returned by the cmd, seems to be OK, but when i type : cd /srv/nfs/SRVADM/images -> input/output error
i did apt-get install nfs-common too
i’m sorry but it look so complicated to mount any Windows shared directory on a linux VM… :(
// is only used for SAMBA/CIFS paths and won’t work for other methods of connecting.
I agree, we are dealing with a unix system not windows. NFS requires unix style syntax for drive mapping required here.
@Tom-Elliott Right you are.
@Quazz I’m only aware of CIFS using
//as the leader.