Fatal Error: failed to mount NFS volume



  • Hi everyone,

    I’m finally turning to this forum for a solution because I’m all out of ideas. I will try to give you as much information as possible, but don’t hesitate to contact me for more information. Please keep in mind that I’m a newbie in Linux.

    The Setup:

    I have a Ubuntu 12.10 machine with FOG 0.32 installed on it. Everything works fine: computers can boot through PXE and can register themselves in FOG.
    The image storage is located on a Windows 2008 R2 machine. NFS Server is enabled (took me a few days to find out that was a requirement). The folder on the server is shared (with Services for NFS Sharing) as “10.0.0.72:/Belgium”. Anonymous access is allowed and all machines have Read-Write access (ANSI encoding), also root access is allowed.

    The Problem:

    When trying to upload an image to the server I get the following messages:

    • Preparing to send image file to server.
    • Mounting File System … Done
    • Checking Mounted File System …
      ############################################

    An error has been detected !

    ############################################

    Fatal Error: Failed to mount NFS Volume.

    ##############################################

    Information:

    /etc/export contains:
    /images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
    /images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)

    On the windows 2008 machine:
    there is .mntcheck file in the root directory of the share and one in the “dev” directory. I’ve also created a subdirectory called images, with .mntcheck files and “dev” subdirectory.

    The FOG configuration:
    There is only 1 storage node and it has 10.0.0.72 as ip address and /Belgium/ as Image location. It is enabled and is a Master node. It is also assigned to the default storage group.
    There is an image assigned to the host and it is also in the correct group.

    On the FOG Dashboard:
    I can’t pull any information about the storage node’s disk information.

    The Big Question:

    What’s happening here? I assume it’s some kind of a rights problem, but I have almost no knowledge of NFS and security.


  • Developer

    As a quick update I have added this into the wiki “How-To-Guides”
    [url]http://www.fogproject.org/wiki/index.php/Windows_Storage_Node[/url]


  • Senior Developer

    This is an interesting thread to me as it shows the flexibility of FOG. While cumbersome, it CAN be “ported” to run on nearly any OS.


  • Developer

    I tweaked a few more settings with the info you provided and mine is working correctly now also. Images upload on top of each other with out issues and this works perfectly.

    [B]No need for purchased software! I love opensource![/B]



  • Just a quick status update (and closure).

    To answer Wolfbane8653: yes, it was possible. Everything worked.

    I got everything working on the day that FOG released version 1.0.1
    I think I was still high of the sweet victory, when I (later that same day) decided to ditch 0.32 and go for version 1.0.1
    So I got version 0.32 to work and it was fully tested, but it has never been used.

    Instead I deployed version 1.0.1 and started from scratch again (I didn’t have any other option because the update messed up the whole system).
    I ran into some new problems, but fortunatly the error messages in 1.0.1 are a little bit more detailed so I could fix everything. Since yesterday our new (international) FOG environment is ready to deploy. For those interested I will give a summary of our FOG configuration.

    Thank you all for your support. I will try to keep in touch on this forum, and don’t forget to have fun with FOG!

    Our company FOG setup:

    General network: we have multiple locations (in Belgium and The Netherlands) we are all connected in one big network.
    Thanks to FOG we are now able to auto-install any computer on our network, no matter where they are.

    Location: Antwerp. This is our main site. The (one and only) FOG server is hosted here and the PXE boot-service comes from that server. This is a virtual ubuntu 12.10 that runs on VMWare. We also have a Windows 2008 server located here that functions as a storage node. The reason behind this is because of the backup. Backups are made on tape and our tapedrives / software are not supported in Linux.

    Location: Schiphol. This is one of our two main sites in The Netherlands. A Windows 2008 server functions as a storage node. It is equiped with a tapedrive and makes a weekly backup.

    Location: Amsterdam. This is the second main site in The Netherlands and has not yet been configured. This will probably become a virtual windows 2008 server, with backup possibilities on tape.


  • Developer

    Can you upload an image and then reupload on top of it? The case being to update the original image? or is that still untested.


  • Developer

    [quote=“David Van Uffelen, post: 27291, member: 21873”]I’ve found the solution!

    I followed the procedure at this site: [url]http://virtuallyhyper.com/2012/06/configure-windows-2008-nfs-share-vmware-esx/[/url]
    and now everything works.[/quote]

    That’s a nice guide it’s choked full of information! Thanks for sharing this with us!



  • I’ve found the solution!

    I followed the procedure at this site: [url]http://virtuallyhyper.com/2012/06/configure-windows-2008-nfs-share-vmware-esx/[/url]
    and now everything works.



  • Well, I can’t create or change anything in the mounted folder.
    So it seems I’m struggling with a security/sharing/permission setting.

    I’m off to find some more information about NFS and sharing issues between Linux & Windows.


  • Developer

    Open Terminal or SSH into your fog server…
    Then mount the NFS if not done so already.
    cd to the mounted folder. In my example it would be /images2
    Just do a quick [CODE]sudo nano test.txt[/CODE]. Edit the file type in anything and save.
    Then jump on to the windows machine and see if the file exists. Then create a folder using the windows machine.
    See if you can see the folder in linux.

    [B]If you have any issues with this then there is a security/sharing/permissions setting that is incorrect.[/B]



  • Hi,

    I have those security in place, but that didn’t solve the problem
    At this moment I’m stuck at the following stage:

    • Checking Mounted File System … Done
    • Using image blablabla
    • Looking for Hard Disks …Done
    • Using Hard Disk : /dev/sda
    • Preparing bakcup location …Done
      #####################################

    An error has been detected!

    #####################################

    Unable to create /images/001aa0…


  • Developer

    It seems that you don’t have the rights configured. I also forgot one other security setting in the above post.

    [ATTACH=full]756[/ATTACH]

    [ATTACH=full]759[/ATTACH]

    Make sure you do this for C:\images, and C:\images\dev

    I will add for future reference.

    [B][SIZE=14px][FONT=sans-serif][COLOR=#252525]Kerberos[/COLOR][/FONT][/SIZE][/B][SIZE=14px][FONT=sans-serif][COLOR=#252525][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English’][COLOR=#0b0080]/[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]ˈ[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]k[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]ɛər[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]b[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]ər[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]ə[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]s[/COLOR][/URL][URL='http://en.wikipedia.org/wiki/Help:IPA_for_English’][COLOR=#0b0080]/[/COLOR][/URL][/COLOR][/FONT][/SIZE][SIZE=14px][FONT=sans-serif][COLOR=#252525] is a [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Computer_network’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]computer network[/COLOR][/FONT][/SIZE][/URL][URL=‘http://en.wikipedia.org/wiki/Authentication’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]authentication[/COLOR][/FONT][/SIZE][/URL][URL='http://en.wikipedia.org/wiki/Cryptographic_protocol’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]protocol[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525] which works on the basis of ‘tickets’ to allow [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Node_(networking)’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]nodes[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525] communicating over a non-secure network to prove their identity to one another in a secure manner. Its designers aimed it primarily at a [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Client–server’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]client–server[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525] model and it provides [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Mutual_authentication’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]mutual authentication[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525]—both the user and the server verify each other’s identity. Kerberos protocol messages are protected against [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Computer_insecurity#Eavesdropping’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]eavesdropping[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525]and [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Replay_attack’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]replay attacks[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525].[/COLOR][/FONT][/SIZE]
    [SIZE=14px][FONT=sans-serif][COLOR=#252525]~[URL=‘http://en.wikipedia.org/wiki/Kerberos_(protocol)’]Wiki[/URL][/COLOR][/FONT][/SIZE]

    [url="/_imported_xf_attachments/0/756_Security 2.png?:"]Security 2.png[/url][url="/_imported_xf_attachments/0/759_Security 2.png?:"]Security 2.png[/url]



  • Thank you very much for the tip.

    I’ve compared our settings against yours and it helped. Anonymous login was not configured on the server.

    Unfortunately, another error has popped up: unable to create /images/MAC-address.
    Also, I’ve discovered that I’m not able to write anything from the Linux server to the Windows server via NFS. “Permission denied” shows up every time, so I’ll probably have to look into that a little bit further.

    Another difference in our settings was kerberos. We don’t have any mentioning of that on our server. Is that necessary?


  • Developer

    Warning: Most of this information is pulled from this post --> [url]http://fogproject.org/forum/threads/how-to-setup-a-fog-storage-node-without-installing-fog.4294/#post-12035[/url] but the following excludes haneWIN NFS Server. Woot! open source!

    I have set this up and it …was working. Until my resent update to v1.0.0 but thats another post in another discussion. Check these settings against yours.


    Server 2008 R2:

    Install NFS role.

    [ATTACH=full]740[/ATTACH]

    [ATTACH=full]743[/ATTACH]

    [ATTACH=full]758[/ATTACH]

    [ATTACH=full]745[/ATTACH]

    [ATTACH=full]759[/ATTACH]

    Make sure you do this for C:, C:\images, and C:\images\dev


    Filezilla:
    [ATTACH=full]747[/ATTACH]

    Make sure these files $ Directories all have Read, write, delete, append rights
    [ATTACH=full]746[/ATTACH]


    Fog server: (Terminal or ssh)
    Here is the tricky part…You need to copy the hiddent files on your linux server to your windows server. These files are located @:

    /images/.mntcheck --> c:\images
    /images/dev/.mntcheck --> c:\images\dev\

    xxx.xxx.xxx.xxx ==> ip address of the windows server

    I mounted the NFS drive and just did a cp command.
    [CODE]sudo mkdir images2
    sudo chmod 777 images2
    sudo mount xxx.xxx.xxx.xxx:/images /images2
    cp /images/.mntcheck /images2
    cp /images/dev/.mntcheck /images2/dev/
    sudo umount /images2
    [/CODE]


    Fog web interface:

    Then continue by adding a storage node just as you would in the wiki.

    [QUOTE]I Simply added a Storage Node Definition in its own Storage Group independent to the default storage Group, added it’s IP 172.19.102.6 and the path /images/ because it’s the path 172.19.102.6 exports also /images/dev/ like an original FOG node does.

    [IMG]http://i.imgur.com/2cZcI4J.png[/IMG]

    [IMG]http://i.imgur.com/VB2LeZM.png[/IMG]
    [/QUOTE]

    Only issue I have now is when updating the same image it will not overwrite the old image until I delete it or change the rights on that image.

    [url="/_imported_xf_attachments/0/740_NFS Sharing.png?:"]NFS Sharing.png[/url][url="/_imported_xf_attachments/0/743_NFS Permissions.png?:"]NFS Permissions.png[/url][url="/_imported_xf_attachments/0/745_security.png?:"]security.png[/url][url="/_imported_xf_attachments/0/746_File zilla folders.png?:"]File zilla folders.png[/url][url="/_imported_xf_attachments/0/747_File zilla.png?:"]File zilla.png[/url][url="/_imported_xf_attachments/0/758_Security 2.png?:"]Security 2.png[/url]


Log in to reply
 

353
Online

39.3k
Users

11.0k
Topics

104.4k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.