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

FOG 1.5.9-RC2 incompatible with Windows 10 v2004 Partition Structure

Scheduled Pinned Locked Moved
FOG Problems
5
27
4.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
    sudburr
    last edited by Jul 7, 2020, 8:24 PM

    Sigh … cold vs warm boot is not it.

    New VMs today, and just to spite me, it failed on the warm reboot test. It worked after resetting to the checkpoint prior to the initial capture attempt. So it worked on a cold boot.

    This is definitely the indicator that the capture will be bad.

    blkid: error: /dev/sda4: No such file or directory
    

    If I see this, I shut the VM down, revert the checkpoint and try again.

    [ Standing in between extinction in the cold and explosive radiating growth ]

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Jul 8, 2020, 3:28 PM

      @sudburr This is a mystery to me. Why would it find four partitions to begin with but then the device node file is one?!?

      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

      1 Reply Last reply Reply Quote 0
      • S
        sudburr
        last edited by Jul 9, 2020, 11:04 PM

        And it appears to be totally random whether it throws that error, cold boot, warm boot, reset, whatever. If blkid: error comes up I just keep resetting the vm until it goes away .

        [ Standing in between extinction in the cold and explosive radiating growth ]

        1 Reply Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Sebastian Roth Jul 10, 2020, 1:21 AM Jul 10, 2020, 7:20 AM

          @sudburr Is the partition layout still fine when you see this blkid: error: /dev/sda4 thing on subsequent tries?

          May I ask you to do the following: Let it try to capture a few times more. Every time you save a copy of the /images/dev/aabbccddeeff/d1.partitions (this aabb… is the MAC address of the host without colons) file to another location for us to compare those afterwards. Whenever you see the blkid... error you name it d1.partitions_fail_X (put in numbers instead of X) and if you don’t see the error you name it d1.partitions_ok_X.sfdiskPartitionFileName

          What kind of VM do you use? I am wondering if I am able to replicate the issue using the same setup?!

          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 Jul 16, 2020, 1:40 PM Reply Quote 0
          • S
            sudburr
            last edited by Jul 14, 2020, 2:37 PM

            I’ll get back to ya on this. I’ve finished my image refresh for the new year and am digging deep into something else now.

            I built them in Hyper-V on Windows 10v2004 .

            It was a coin toss on whether I witnessed the problem on over three dozen VMs, but I was able to overcome it on every one.

            [ Standing in between extinction in the cold and explosive radiating growth ]

            1 Reply Last reply Reply Quote 0
            • F
              Fog_Newb @Sebastian Roth
              last edited by Jul 16, 2020, 1:40 PM

              @Sebastian-Roth

              Not sure if this has been resolved or if this helps -

              I’ve created a Win 10 UEFI VM using the 2004 ISO. VMware® Workstation 15 Pro 15.5.6 build-16341506. All the settings were default except I went up tp 8GB of RAM. I installed it, ran all the updates, activated it while waiting for updates, rebooted twice then captured the image with FOG dev-branch version: 1.5.9-RC2.11 running on Ubuntu 20.04 LTS

              It deployed fine to a similar VM.

              1 Reply Last reply Reply Quote 1
              • P
                ProfDrSir
                last edited by Jul 17, 2020, 10:24 PM

                My workaround that has worked so far was to make the source image drive small, 28GB in my case, and it seems to always work now so long as the target drive is bigger, a complication with the last partition not wanting to be any closer to the beginning of the drive as it was on the source disk (i think), but it can be further away with no issues:

                https://forums.fogproject.org/topic/14571/imaging-windows-10-v2004-with-uefi-gpt-partitions-onto-31gb-or-smaller-drive-and-failing/3

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

                143

                Online

                12.1k

                Users

                17.3k

                Topics

                155.3k

                Posts
                Copyright © 2012-2024 FOG Project