• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

NFS volume failed to mount

Scheduled Pinned Locked Moved Solved
FOG Problems
4
24
4.8k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    Tom Elliott
    last edited by Jan 9, 2017, 2:38 PM

    Trying to hit you on chat with more ideas.

    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

    A 1 Reply Last reply Jan 9, 2017, 3:15 PM Reply Quote 0
    • A
      abos_systemax @Tom Elliott
      last edited by Jan 9, 2017, 3:15 PM

      @Tom-Elliott Thanks Tom for the quick help;
      For the others in this topic: Thanks as well,
      The issue has been resolved. Apparently there was a misconfiguration ‘somewhere’ in the server setup.
      I installed FOG 1.2.0 and immediately upgraded to 1.3.1, then configured the SDB harddisk and the images (which were copied from another server), chown-ed and grpch-ed the folders, reconfigured the node and MySQL …

      somewhere some setting went wrong;

      I’ve reinstalled the server and started from scratch with Fog 1.3.1, now everything works as intended.

      W 1 Reply Last reply Jan 9, 2017, 6:15 PM Reply Quote 0
      • W
        Wayne Workman @abos_systemax
        last edited by Jan 9, 2017, 6:15 PM

        @abos_systemax next time please include the bigger story. In this situation, telling us that this was a migration would have caused us to ask different questions.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
        Daily Clean Installation Results:
        https://fogtesting.fogproject.us/
        FOG Reporting:
        https://fog-external-reporting-results.fogproject.us/

        A 1 Reply Last reply Jan 10, 2017, 10:41 AM Reply Quote 0
        • A
          abos_systemax @Wayne Workman
          last edited by Jan 10, 2017, 10:41 AM

          @Wayne-Workman I will. I did not pay much attention to it because I assumed that I installed 1.3… but during our Q&A, i slowly realized that there might be an issue with my initial install, especially when I noticed that the FOG client that loaded was 1.2, not 1.3 (but that skips so darn fast that I noticed only after 3 reboots…)

          1 Reply Last reply Reply Quote 0
          • 1
          • 2
          • 2 / 2
          2 / 2
          • First post
            21/24
            Last post

          220

          Online

          12.2k

          Users

          17.3k

          Topics

          155.5k

          Posts
          Copyright © 2012-2024 FOG Project