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

Error when deploying image - Checking Mounted File System... Failed

Scheduled Pinned Locked Moved Solved
FOG Problems
2
3
184
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.
  • F
    Fog_Newb
    last edited by Fog_Newb Aug 5, 2024, 10:43 AM Aug 5, 2024, 3:34 PM

    I’ve been able to capture and deploy images just fine. Until… mounting a 2nd hard drive as /images and upgrading to FOG 1.5.10.48 from the previous dev version. .mntcheck exits under /images/dev

    I thought I had the permission set correctly since I can still capture… anyways, I’m not sure what to do.

    The error message is attached

    20240805_112211.jpg

    What do?

    Thanks

    update: SOLVED

    T 1 Reply Last reply Aug 5, 2024, 3:44 PM Reply Quote 0
    • F
      Fog_Newb @Tom Elliott
      last edited by Fog_Newb Aug 5, 2024, 8:44 PM Aug 5, 2024, 4:12 PM

      @Tom-Elliott

      Thanks Tom, that fixed it right up. I guess I overlooked that file when copying everything from the original /images.

      Yeah, that fdrive number… 🙂 It is the serial number of the drive.

      The NVME drives initialize differently each time during boot. I guess that is a thing, so nvme0 would sometimes be nvme1. It was a mess. Then I learned drive size could be used to differentiate between drives under Host Primary Disk. Now that both of my NVME drives are the same size, I have to use the drive serial number.

      1 Reply Last reply Reply Quote 1
      • T
        Tom Elliott @Fog_Newb
        last edited by Aug 5, 2024, 3:44 PM

        @Fog_Newb That’s an interesting fdrive you got there

        Not sure how that would work but to your actual question:

        Please try:

        touch /images/.mntcheck
        

        As that error is indicating that the /images mount (for deploy points) is missing that file.

        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

        F 1 Reply Last reply Aug 5, 2024, 4:12 PM Reply Quote 1
        • F
          Fog_Newb @Tom Elliott
          last edited by Fog_Newb Aug 5, 2024, 8:44 PM Aug 5, 2024, 4:12 PM

          @Tom-Elliott

          Thanks Tom, that fixed it right up. I guess I overlooked that file when copying everything from the original /images.

          Yeah, that fdrive number… 🙂 It is the serial number of the drive.

          The NVME drives initialize differently each time during boot. I guess that is a thing, so nvme0 would sometimes be nvme1. It was a mess. Then I learned drive size could be used to differentiate between drives under Host Primary Disk. Now that both of my NVME drives are the same size, I have to use the drive serial number.

          1 Reply Last reply Reply Quote 1
          • [[undefined-on, T Tom Elliott, Aug 5, 2024, 5:08 PM]]
          • 1 / 1
          1 / 1
          • First post
            1/3
            Last post

          242

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project