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

    Unit nfs.service could not be found

    Scheduled Pinned Locked Moved
    Linux Problems
    4
    6
    3.5k
    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
      threeonesix
      last edited by Sebastian Roth

      CentOS 8
      FOG 1.5.9
      New install

      Following the installation instructions at https://wiki.fogproject.org/wiki/index.php?title=CentOS_7
      When I get to ./installfog.sh it works fine until it gets to “Setting up and starting NFS Server” and that fails with the error messages:

      “Unit nfs-kernel-server.service could not be found.”
      “Failed to enable unit: Unit file nfs.service does not exist.”
      “Failed to stop nfs.service: Unit nfs.service not loaded.”
      “Failed to start nfs.service: Unit nfs.service not found.”
      “Unit nfs.service could not be found.”

      I am far, far from a Linux n00b, even, I literally haven’t touched Linux in at least a decade. I’ve followed the exact installation instructions for FOG. What am I missing?

      T 2 Replies Last reply Reply Quote 0
      • T
        threeonesix @threeonesix
        last edited by

        I should mention that I am trying to setup FOG in a VMware ESXi 5.5 free edition with the VM hard drives (3) setup via iSCSI to a Lenovo NAS. I want the FOG software running on sda, the images of client computers stored on sdb, which I have mounted to /home/images, and the snap-ins stored on sdc, which I have mounted to /home/snapins.

        1 Reply Last reply Reply Quote 0
        • T
          threeonesix @threeonesix
          last edited by

          Funny, I meant “far, far from a Linux expert”!

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by

            @threeonesix Sounds like NFS was not installed?! Please run rpm -qa | grep nfs and post output here.

            … the images of client computers stored on sdb, which I have mounted to /home/images, and the snap-ins stored on sdc, which I have mounted to /home/snapins.

            I wouldn’t advice you to split off and move the images and snapins directories if you are a Linux beginner. Keep things in FOG default so you don’t have to mess with it.

            If you want to have images on a different partition that’s easy enough by just mounting sdb in /images and FOG will work just as usual.

            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

            Tom ElliottT 1 Reply Last reply Reply Quote 0
            • Tom ElliottT
              Tom Elliott @Sebastian Roth
              last edited by

              @threeonesix As @sebastian-roth suggests, leave the locations default. /home/images /home/snapins is changing the default locations.

              FOG defaults to put images on /images and snapins on /opt fog/snapins

              If you are a beginner, why state where you want these things mounted instead of saying, I would like images on /dev/sdb and snapins on /dev/sdc. You have admitted to not knowing much about linux.

              To understand:

              /dev/sdb = /images
              /dev/sdc = /opt/fog/snapins

              That would get you where you need to be, all you need to learn is how to tell your server to mount /images and /opt/fog/snapins.

              First things first, did you make sdb a single partition using all available space for the partition? How are you formatting the partition? xfs, ext2, ext3, ext4, ntfs, btrfs?

              Same questions for sdc

              The following instructions assume you are going to use /images and /opt/fog/snapins as the installer defaults to. It assumes the partition is formatted on both disks as ext4. Adjust as necessary.

              sudo -i #enter sudo password
              
              mkdir /images #creates /images if it does not exist already
              mkdir -p /opt/fog/snapins #creates /opt/fog/snapins if it does not exist already
              
              echo "/dev/sdb1 /images ext4 defaults 0 0" >> /etc/fstab # appends the quoted line into the /etc/fstab file
              echo "/dev/sdc1 /opt/fog/snapins ext4 defaults 0 0" >> /etc/fstab # appends the quoted line into the /etc/fstab file
              
              mount -a #attempts to mount /dev/sdb1 to /images and /dev/sdc1 to /opt/fog/snapins
              

              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

              george1421G 1 Reply Last reply Reply Quote 2
              • george1421G
                george1421 Moderator @Tom Elliott
                last edited by george1421

                @tom-elliott said in Unit nfs.service could not be found:

                To understand:
                /dev/sdb = /images
                /dev/sdc = /opt/fog/snapins

                I 100% agree with this route AND to add create the partitions on the disk as standard partitions and not LVM volumes. If they are standard partitions you can expand them easier than a LVM volume (debatable) if you are running the fog server on a V and need to grow your storage.

                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!

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                • First post
                  Last post

                280

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project