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

win 10 deployment / disk size auto-adjusting / recovery mode

Scheduled Pinned Locked Moved Unsolved
FOG Problems
3
18
1.4k
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.
  • B
    Baessens @Sebastian Roth
    last edited by Nov 13, 2018, 9:59 AM

    @Sebastian-Roth Thanks for the reply.
    d1.fixed_size_partitions:
    This is an empty file.
    0_1542102731687_fog3.PNG

    d1.partitions:
    0_1542102603915_fog.PNG

    d1.minimum.partitions:
    0_1542102684608_fog1.PNG

    Disk management of the machine i captured;
    0_1542103075365_fog4.PNG

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Nov 13, 2018, 11:04 AM

      @Baessens Ok, Quazz was definitely on the right track with this. Your partition layout does not seem to be the issue but the Dutch labels are. As of now we still use thise partition labels to discover special Windows partitions like Boot or Recovery partition. In your case our scripts fail.

      Although I wonder about this causing real trouble because the starting point of the partitions are untouched. Nevermind, we’ll try the fix anyway.

      @Quazz Would you find the time to add Door systeem gereserveerd (hope there is no typo!) to the scripts? Not sure from the top of my head but I think there were at least two places. I can push changes and auto-build new init’s then.

      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

      Q 1 Reply Last reply Nov 13, 2018, 2:25 PM Reply Quote 0
      • Q
        Quazz Moderator @Sebastian Roth
        last edited by Quazz Nov 13, 2018, 8:39 AM Nov 13, 2018, 2:25 PM

        @Sebastian-Roth Well, the strange thing, to me, is that the current regex should match the label. It’s the default Dutch label for that partition and it works fine on my images with that exact same label!!!

        Very mysterious…

        Door systeem ge**reserve**erd

        Part between ** should match and in my tests (as well as image captures) it does, so I’m kind of surprised it’s not working for Baessens

        Relevant commit: https://github.com/FOGProject/fos/commit/e6431418022911bef122394c57726f4a879421cf

        All this being said. I don’t recall this ever breaking my windows installs prior to the fix. I’m going to assume there is something else going on.

        @Baessens do you use an unattend.xml file? driver installs/packs? (nothing to do with the resize issue, but might have something to do with the recovery issue)

        B 1 Reply Last reply Nov 13, 2018, 3:56 PM Reply Quote 0
        • B
          Baessens @Quazz
          last edited by Nov 13, 2018, 3:56 PM

          @Quazz
          I do not use any unattend.xml file.
          All I do is install from a win 10 pro 64 bit iso, on my hyper-v which is Windows server 2016.

          Version: Windows 10 Professional, version 1803 (june 2018) - Dutch

          I manually go through the installation process, install office and some other small things (with Ninite); and capture the machine with FOG.
          I do add a legacy network card to be able to boot from network on hyperv. and i use generation 1 as my VM type.

          If i do not chose for the resizable disk, it deploys just fine.

          Thanks for all of the help already!

          Q 1 Reply Last reply Nov 13, 2018, 4:55 PM Reply Quote 0
          • Q
            Quazz Moderator @Baessens
            last edited by Nov 13, 2018, 4:55 PM

            @Baessens @Sebastian-Roth Some googling indicates 0x0000225 has to do with the BCD.

            Given that the start positions of the partitions seem to be correct, I don’t think the resize process is directly responsible for the error.

            Is it possible you’re deploying an MBR (legacy/old BIOS) (assuming, based on your partitions) to a system that’s trying to boot in GPT (new/UEFI) mode?

            Does d1.mbr exist in your image folder?

            1 Reply Last reply Reply Quote 1
            • S
              Sebastian Roth Moderator
              last edited by Sebastian Roth Nov 13, 2018, 11:50 AM Nov 13, 2018, 5:46 PM

              @Quazz You are right, it should match. Seems strange as fixed_size_partition is empty and sda1 is definitily been shrunk… But you are right, it shouldn’t cause the recovery boot. Maybe this is some Win10 fast boot foo?!

              @Baessens Make sure you disable fast boot and shutdown the machine using shutdown -s -t 0 -f in Windows command line.

              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

              B 1 Reply Last reply Nov 14, 2018, 10:01 AM Reply Quote 0
              • B
                Baessens @Sebastian Roth
                last edited by Nov 14, 2018, 10:01 AM

                @Sebastian-Roth @Quazz

                Make sure you disable fast boot and shutdown the machine using shutdown -s -t 0 -f in Windows command line.
                I used the shutdown command. I’ll try disabling fast boot and reimaging.

                Is it possible you’re deploying an MBR (legacy/old BIOS) (assuming, based on your partitions) to a system that’s trying to boot in GPT (new/UEFI) mode?
                It’s possible the VM i made uses MBR. But i’ve enabled Legacy boot on the BIOS and disabled secure boot. Also with the other image(not resizable) i made i have no problems deploying.

                Does d1.mbr exist in your image folder?
                Yes, it does.

                The thing i don’t understand is how i don’t have any problems deploying the other image i made. Which is Not Resizable. I’m deploying on the exact same machine.

                I do have the option legacy boot enabled in the BIOS, and secure boot disabled. I’ve tried using uefi boot but that doesn’t work at all.

                Maybe i have to add some kind of option or parameter in the host options on the FOG UI?

                B 1 Reply Last reply Nov 15, 2018, 3:48 PM Reply Quote 0
                • B
                  Baessens @Baessens
                  last edited by Nov 15, 2018, 3:48 PM

                  @Sebastian-Roth @Quazz

                  I captured a new image of one of the physical machines (not VM). This is a resizable image.
                  I CAN deploy this image to the other machines without the recovery screen error…

                  This machine has been setup by one of my colleagues using windows media creation tool.
                  It’s also a Win 10 pro 64 bit.
                  The Disk management looks a little different tho; (name of OEM partition)

                  0_1542296739071_fog5.jpg

                  Seems like something must be wrong with the VM i set up ?

                  Thanks 😉

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sebastian Roth Moderator
                    last edited by Nov 15, 2018, 4:05 PM

                    @Baessens From the pictures it looks like the hardware client is installed as UEFI (EFI boot partition and probably GPT partition layout) while the VM as legacy BIOS. Usually FOG is able to handle both and I am still at a loss with this.

                    Please do me a favour, deploy that image you took from the VM to a machine. Now don’t let it boot to Windows but shut it down and schedule another task for it again. But this time tick the checkbox for debug. Boot the machine and it should bring you to a shell. Run the following command, take a picture and post here: sfdisk -d /dev/sda

                    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
                      Sebastian Roth Moderator
                      last edited by Nov 15, 2018, 4:07 PM

                      @Baessens Ahhh, I just had one more idea. Please run fdisk -l /dev/sda and post a picture as well. Possibly this is a sector size issue.

                      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
                      • 1 / 1
                      1 / 1
                      • First post
                        18/18
                        Last post

                      203

                      Online

                      12.1k

                      Users

                      17.3k

                      Topics

                      155.3k

                      Posts
                      Copyright © 2012-2024 FOG Project