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

Unable to Capture Using Single Disk - Resizable

Scheduled Pinned Locked Moved Solved
FOG Problems
3
21
2.1k
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.
  • S
    shatchett0
    last edited by Sep 16, 2024, 4:22 PM

    Moved to a new Alma install. Used the git install. I could not register an Ubuntu 20.04 host. I then diid a clean install of Alma and used the latest tar for FOG. Was able to register a host but could not capture single disk resizable. Posting this pic of the error. Curious if anyone sees anything obvious. Thanks for any input.

    fog.jpg

    1 Reply Last reply Reply Quote 0
    • S
      shatchett0 @JJ Fullmer
      last edited by Sep 16, 2024, 6:00 PM

      @JJ-Fullmer Sorry JJ. I’ve been checking for replies but today is the first I’m seeing this. It was working on an old z840 with 1 TB of storage. I’ve not moved to a Dell Server with 120 TB and I posted an image of the error I’m seeing in my latest update dated 9/16/2024.

      1 Reply Last reply Reply Quote 0
      • S
        shatchett0 @JJ Fullmer
        last edited by Sep 16, 2024, 6:50 PM

        @JJ-Fullmer “boot the host to the pxe menu, and use the check compatibility option”

        Hey JJ. what are the steps to do this?

        J 1 Reply Last reply Sep 18, 2024, 1:46 AM Reply Quote 0
        • J
          JJ Fullmer Testers @shatchett0
          last edited by Sep 18, 2024, 1:46 AM

          @shatchett0 you would cancel the capture task and then boot the host to pxe and you should see a compatibility check in the fog boot menu.
          The error also looks like an issue with ext4 thinking it’s a dirty filesystem being captured. If you schedule the capture task with debug checked you can try running the file system check tools interactively. This looks like a problem with this specific host and the image being captured more than a fog server issue.

          Have you tried the FogApi powershell module? It's pretty cool IMHO
          https://github.com/darksidemilk/FogApi
          https://fogapi.readthedocs.io/en/latest/
          https://www.powershellgallery.com/packages/FogApi
          https://forums.fogproject.org/topic/12026/powershell-api-module

          S 2 Replies Last reply Sep 19, 2024, 3:51 PM Reply Quote 0
          • S
            shatchett0 @JJ Fullmer
            last edited by Sep 19, 2024, 3:51 PM

            @JJ-Fullmer That is helpful. I’ll run those.

            1 Reply Last reply Reply Quote 0
            • S
              shatchett0 @JJ Fullmer
              last edited by Oct 1, 2024, 4:07 PM

              @JJ-Fullmer It looks like one of my problems was that I was runnning two network interfaces. One was going to our production network, the other to the fog network. I deleted the production interface and that eliminated the random errors I was getting. I was getting one consistent error during capture “Could not mount images folder (/bin/fog.upload) Args passed: Reason: mount: 192.168.7.184:/images/dev/ on /images failed: No such file or directory”

              I had a 125 TB raid for internal storage (images) and a separate system drive for the OS and fog. So I installed the OS and fog on my raid. I can now consistently capture images with no problem. Deploying is the problem now. I’ve attached a pic. If anybody sees anything in the error please feel free to chime in.

              BTW I have been using the compatibility feature to ensure the hardware passes muster.

              Thanks!

              fig.jpg

              J 1 Reply Last reply Oct 2, 2024, 3:24 PM Reply Quote 0
              • J
                JJ Fullmer Testers @shatchett0
                last edited by Oct 2, 2024, 3:24 PM

                @shatchett0

                Glad to hear it’s working for capture now. You should be able to mount /images on a separate disk without issue, but having it all in the same place is fine too.

                I’m not 100% sure what that error is saying. At least not with enough detail to be helpful right off the bat.

                First thing that comes to mind is a sector mismatch. If your image was captured from a disk with 512e sectors and you try to deploy to a 4kn disk (or vice versa) you’ll get errors when it tries to align the partition table because the sector sizes can’t align. It’s a limitation in disk alignment at a lower hardware level. I have some notes on when I was debugging such an issue in this post https://forums.fogproject.org/topic/17112/surface-go-4-incompatible

                It could also be a simpler issue of the image doesn’t fit on the new disk. In most cases the resizable takes care of it, but if the image’s min size is bigger than the disk, not much can be done. But it looks like it’s an all disk or all partition image?

                Have you tried the FogApi powershell module? It's pretty cool IMHO
                https://github.com/darksidemilk/FogApi
                https://fogapi.readthedocs.io/en/latest/
                https://www.powershellgallery.com/packages/FogApi
                https://forums.fogproject.org/topic/12026/powershell-api-module

                S 3 Replies Last reply Oct 9, 2024, 7:00 PM Reply Quote 0
                • S
                  shatchett0 @JJ Fullmer
                  last edited by Oct 9, 2024, 7:00 PM

                  @JJ-Fullmer Hey, I’ll check out the notes you posted. I’m back at it after dealing with other issues.

                  1 Reply Last reply Reply Quote 0
                  • S
                    shatchett0 @JJ Fullmer
                    last edited by Oct 18, 2024, 1:47 PM

                    @JJ-Fullmer I think you’re right. It’s a matter of disk size. I have to be more conscious of the source disk size in relation to the destination disk size. I am capturing consistently now and deploying more reliably.

                    So my problems really amounted to network issues (I had two interfaces that confused my fog server) and the other was not paying more attention to my disk sizes.

                    Thanks for all your help and patience with this.

                    Steve

                    1 Reply Last reply Reply Quote 1
                    • S
                      shatchett0 @JJ Fullmer
                      last edited by Oct 22, 2024, 3:34 PM

                      @JJ-Fullmer I would mark this one as solved. I didn’t see a way for me to do it. Thanks, again

                      1 Reply Last reply Reply Quote 1
                      • [[undefined-on, J JJ Fullmer, Oct 22, 2024, 4:33 PM]]
                      • 1
                      • 2
                      • 2 / 2
                      • First post
                        Last post

                      223

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project