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

An Error detected, fails capture

Scheduled Pinned Locked Moved Solved
Linux Problems
3
14
385
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.
  • A
    adam1972
    last edited by adam1972 Sep 9, 2024, 9:56 AM Sep 9, 2024, 3:55 PM

    Hello everyon😎😁
    FOG Server is running on an Ubuntu 22.04 server…
    I have an Ubuntu VM I want to capture. (Not too long ago I did this using proxmox on an identical VM that also used a dynamic disk and it worked splendidly). I am now using hyper-V and have a VM of Ubuntu 22.04. It’s an EFI bios and nothing else special or out of the ordinary, just a vanilla Ubuntu, 8 GB RAM and a vhdx hard drive. It’s currently 18.6 GB in size with a 50GB ceiling.
    If I try and create a “Single Disk - resizeable” it will fail the attempt at capturing on VSphere (It worked when using ProxMox).
    If I use Multiple Partition image - Single Disk (Not Resizable), it works.
    When the capture fails, this is the error:
    2b86bb37-e75d-44c5-b8a3-4d45da9b68f9-FOG error on server at DDS (Hyper-V).png
    5fcf6ebd-a9f3-4e8a-8059-4e4c31d548e3-FOG error on server at DDS (Hyper-V)_FOG Settings.png

    Anyone have any ideas? or is there something I missed somewhere?
    ANY help would be greatly appreciated! 😁😎

    T A 2 Replies Last reply Sep 9, 2024, 5:53 PM Reply Quote 0
    • T
      Tom Elliott @adam1972
      last edited by Sep 12, 2024, 6:35 PM

      @adam1972 With the task in debug now, that you’ve done the e2fsck:
      Now run fog from the blue prompt and it should run though the normal process just pausing as it goes along.

      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 Sep 12, 2024, 10:57 PM Reply Quote 0
      • T
        Tom Elliott @adam1972
        last edited by Sep 9, 2024, 5:53 PM

        @adam1972 have you tried running this capture in debug mode and attempt the e2fsck -f /dev/sda2 as suggested?

        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 Sep 9, 2024, 7:33 PM Reply Quote 0
        • A
          adam1972 @adam1972
          last edited by Sep 9, 2024, 7:31 PM

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • A
            adam1972 @Tom Elliott
            last edited by Sep 9, 2024, 7:33 PM

            @Tom-Elliott @adam1972 Thank you so much for getting back to me…
            the efsck shows clean…
            eec58d98-e562-4921-8972-c0f4c2eb4e31-image.png

            Debug mode? This is what I see… I used the FOG menu item.
            d83fc3cb-58e8-4b74-8cd9-0bc7c0941429-image.png

            d1a81ac8-b701-4d9d-833e-6a7b2d9f5d05-image.png

            Should I be using a different option?

            J 1 Reply Last reply Sep 10, 2024, 9:18 PM Reply Quote 0
            • J
              JJ Fullmer Testers @adam1972
              last edited by Sep 10, 2024, 9:18 PM

              @adam1972 that is the debug shell, you can try the efsck command in debug mode then use the command ‘fog’ to step through the capture process

              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

              A 1 Reply Last reply Sep 11, 2024, 3:18 PM Reply Quote 0
              • A
                adam1972
                last edited by Sep 11, 2024, 2:31 PM

                Hello eveyone 😁
                Anyone have any idea or suggestions?
                I would prefer to have it shrunken than the full size if possible 😕

                1 Reply Last reply Reply Quote 0
                • A
                  adam1972 @JJ Fullmer
                  last edited by adam1972 Sep 11, 2024, 9:20 AM Sep 11, 2024, 3:18 PM

                  @JJ-Fullmer Thank you for trying to help 😁😎

                  If you notice the third image --> 8461840f-6c04-42da-9242-10fc7dfd3c0e-image.png
                  I did, The blue colored prompt at the bottom of the image was the only thing that would happen after i had chopsen the “fog” option.

                  I also did the efsck before hand (1st image)–> ad47d6bd-ab80-4eb4-b75a-aa7a9d4a405f-image.png

                  T 1 Reply Last reply Sep 11, 2024, 6:21 PM Reply Quote 0
                  • T
                    Tom Elliott @adam1972
                    last edited by Sep 11, 2024, 6:21 PM

                    @adam1972 you should run the e2fsck command FROM the blue window

                    and you should reschedule your task, but with the debug option.

                    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 2 Replies Last reply Sep 12, 2024, 3:44 PM Reply Quote 0
                    • A
                      adam1972 @Tom Elliott
                      last edited by adam1972 Sep 12, 2024, 9:45 AM Sep 12, 2024, 3:44 PM

                      @Tom-Elliott What do you mean from the “Blue Window”? I ran it from an external usb as /dev/sda2 is mounted with system files (and it was the only way I could find to do it with many many online searches).

                      I did reschedule the tak, I created one specifically with the debug --> 42a746c1-d8a3-4bbf-8bd6-50f7af1be3e7-image.png

                      That is what i got… i chose the Fog option and it gave me a “Variable dump” from FOG… It states "Press [Enter] key to continue… which I did and all I get is a blue prompt…

                      1 Reply Last reply Reply Quote 0
                      • A
                        adam1972 @Tom Elliott
                        last edited by Sep 12, 2024, 5:09 PM

                        @Tom-Elliott You mean like this?
                        e54902ec-e876-412c-912c-84664c64501e-image.png
                        This is the debug capture… with the FOG option selected…

                        T 1 Reply Last reply Sep 12, 2024, 6:35 PM Reply Quote 0
                        • T
                          Tom Elliott @adam1972
                          last edited by Sep 12, 2024, 6:35 PM

                          @adam1972 With the task in debug now, that you’ve done the e2fsck:
                          Now run fog from the blue prompt and it should run though the normal process just pausing as it goes along.

                          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 Sep 12, 2024, 10:57 PM Reply Quote 0
                          • A
                            adam1972 @Tom Elliott
                            last edited by Sep 12, 2024, 10:57 PM

                            @Tom-Elliott I did it before your response… I saw it was the same results as I had done through root using an external boot device… Oddly though, once it completed I restarted the job normally and it actually COMPLETED!!! THANK YOU SO MUCH!!! 😎🔥🔥🔥💯

                            J 1 Reply Last reply Sep 13, 2024, 1:03 PM Reply Quote 1
                            • J
                              JJ Fullmer Testers @adam1972
                              last edited by Sep 13, 2024, 1:03 PM

                              @adam1972 So when you’re in a debug mode, or in a fog task in general, you’re booted into FOS (Fog Operating System) which is the same idea as booting from an external disc/drive. The idea being you’re not mounting and booting from your disks that you are capturing/deploying from/to. So after the efsck came back as clean from where FOS could see, it makes sense that it would work as expected right after.
                              This probably won’t happen every time you capture, if it does then there’s something you’re doing in preparing the image that is causing the dirty bit to be flagged on the disk, there is likely a way around that, I don’t know off the top of my head for Linux what that might be. But we can figure it out if the problem recurs.

                              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

                              A 1 Reply Last reply Sep 13, 2024, 3:02 PM Reply Quote 0
                              • [[undefined-on, A adam1972, Sep 13, 2024, 3:00 PM]]
                              • A
                                adam1972 @JJ Fullmer
                                last edited by Sep 13, 2024, 3:02 PM

                                @JJ-Fullmer Good to know, thank you so much 😎💯

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

                                284

                                Online

                                12.0k

                                Users

                                17.3k

                                Topics

                                155.2k

                                Posts
                                Copyright © 2012-2024 FOG Project