Mounting File System Failed



  • Hi,

    I’m receiving an error when attempting to upload a new image from a computer workstation. It states ‘Mounting file system failed. %windows storage node IP address%:/images/ on /images failed: no such file or directory’.

    My FOG Server is utilising the Ubuntu 14.04.2 Server x64 platform. My FOG Server is version 1.2.0. My FOG Server resides within a VMware vSphere 5.5 Hypervisor. I had issues utilising the local storage node. I created a thread specific to this problem. Since this thread as suggested I created a new FOG Server instance on a CentOS platform. Unfortunately I had difficulty during the FOG Server installation; with the additional server components that the system require – specifically MySQL, and the outdated repository sources.
    https://forums.fogproject.org/topic/5171/vmware-vsphere-ide-hdd-image-store

    I conducted more research and have since decided to continue with Ubuntu, while utilising a Windows NFS server as the FOG Server Storage Node. I have been utilising the documentation below as a reference.
    https://wiki.fogproject.org/wiki/index.php/Windows_Storage_Node
    https://wiki.fogproject.org/wiki/index.php/FOGUserGuide#Separate_NFS_Server

    Take note the errors stated above and specifically related to this new implementation of Windows.

    I guess my issue is related to the computer workstation not being able to write to the NFS Server, I would assume it’s probably more inclined to be due to not being able to locate the appropriate NFS images path.

    Is there any way I can navigate to the NFS storage node from the CLI of Ubuntu? Sorry for my ignorance, I’m not really a Linux sys admin.

    Any ideas or suggestions would be greatly appreciated.

    Cheers



  • This thread can now be flagged as resolved.

    I ended up moving over to FOG Trunk due to the OS platform version being not supported.

    Everything is now working. Huuuuuge thank you to Wayne, & everyone else for your assistance; it’s very much appreciated!


  • Moderator

    Was able to help with this via Team Viewer.

    CentOS 7 was being used with 1.2.0 - which likely would have issues. Moved to FOG Trunk and everything worked fine. Added a 2nd HDD for additional space without any issues.


  • Moderator

    @no1bossman I’d recommend continuing with CentOS.

    Some things to check with CentOS is SELinux, and make sure firewall is off.
    After those two things, run through this:
    https://wiki.fogproject.org/wiki/index.php/Troubleshoot_NFS



  • So I’ve completed more testing. I’ve logged into the FTP server on the Storage Node successfully with the default FOG Server account. To re-confirm that I have write access I created a directory.

    So I’m not sure what else I can do here, without any further suggestions.

    Remote system type is UNIX.
    ftp> ls
    200 Port command successful
    150 Opening data channel for directory listing of “/”
    -rw-r–r-- 1 ftp ftp 0 Jun 30 11:45 .mntcheck
    drwxr-xr-x 1 ftp ftp 0 Jun 30 12:08 dev
    226 Successfully transferred "/"
    ftp> mkdir test
    257 “/test” created successfully
    ftp>

    I tried one more time with CentOS. I already knew about MariaDB when I did my research of CentOS. So with a little more research this time round of MariaDB I completed a successful install of FOG Server on CentOS 7.
    https://wiki.fogproject.org/wiki/index.php/Installation_on_CentOS_7#Mariadb_.28optional.29

    Unfortunately my hosts are not able to connect to the internal storage node.
    Mounting File System:…mount: mounting %FOG Server IP Address%:/images/dev/ on images failed: Connection refused
    Fatal Error: Failed to mount NFS Volume.

    I haven’t performed any research specific to this new problem with CentOS. But I thought I would mention it just in case an answer is posted before I find it myself.

    Again, thanks in advance.


  • Moderator

    @no1bossman Take a look at this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

    But, try to execute the test commands against your windows NFS server where the images reside.

    Also, if you can figure out where they are, look at your FTP settings and see if you can set the FTP root directory to the images directory.



  • Thank you very much for the quick replies; much appreciated!

    I ended up discovering my problem was with the NFS server. I hadn’t set the share correctly on the Windows server.

    The problem I now have is with FTP & the uploading of a image. I can only assume I shouldn’t have to manually create the image directory for the specific host. Even so for kicks I created the image folder called FGASupervisor, which resulted in the same log as shown below from the FTP server.

    What confuses me is that the log states file not found.

    I simply registered a host. Created a image. Linked the image to the host, and then created a task to upload the image. Take note the FTP user account has full permissions to the file system for read, write & so on.

    I’m not sure what other information I can provide to assist with the configuration, without including too much unnecessary information. Other than to re-clarify that I uterlised the following document to complete the configuration.
    https://wiki.fogproject.org/wiki/index.php/Windows_Storage_Node

    Thanks in advance, cheers.

    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> 230 Logged on
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> PASV
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> 227 Entering Passive Mode (10,0,0,24,212,240)
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> DELE /images/FGASupervisor
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> 550 File not found
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> RMD /images/FGASupervisor
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> 550 Directory not found
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> TYPE A
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> 200 Type set to A
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> NLST /images/FGASupervisor
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> 550 Directory not found.
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> PASV
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> 227 Entering Passive Mode (10,0,0,24,248,170)
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> NLST /images/dev/74e6e2db8fa4
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> 550 Directory not found.
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> QUIT
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> 221 Goodbye
    (000003)30/06/2015 15:29:48 PM - fog (10.0.0.20)> disconnected.


  • Moderator

    @no1bossman said:

    problem. Since this thread as suggested I created a new FOG Server instance on a CentOS platform. Unfortunately I had difficulty during the FOG Server installation; with the additional server components that the system require – specifically MySQL, and the outdated repository sources.
    https://forums.fogproject.org/topic/5171/vmware-vsphere-ide-hdd-image-store

    I conducted more research and have since decided to continue with Ubuntu, while utilising a Windows

    FOG 1.2.0 would have difficulty installing on the latest CentOS, the latest Ubuntu, the latest Debian, etc.

    MySQL has been depreciated in favor of MariaDB. If you were to install mariadb, mariadb-server before running the installation, it’s likely to succeed.

    However, these issues are resolved in FOG Trunk.

    If you have some time and are willing, I could try to help via Team Viewer, just chat me up.

    Oh and you can find examples of NFS mounting here: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_NFS


  • Moderator

    @no1bossman
    Hi,

    to view NFS shares of a server you can (from a linux client) use that :

    showmount -e your_fog_server_ip
    

    below an example :

    showmount -e xxx.xxx.xxx.xxx
    Export list for xxx.xxx.xxx.xxx:
    /fogimages/dev *
    /fogimages     *
    

Log in to reply
 

372
Online

38976
Users

10712
Topics

101675
Posts

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