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

    Windows 10 single disk resizable, stuck on BIOS screen after process

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    5
    20
    811
    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
      Sebastian Roth Moderator
      last edited by

      @banana123 said in Windows 10 single disk resizable, stuck on BIOS screen after process:

      I am still at the debug menu after the capture, should I do anything else where I am here?’

      Not right now. Just shut it down (halt). I need a bit more time to look at all the information closely. Will do this as soon as I have a bit more time.

      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
      • Q
        Quazz Moderator @banana123
        last edited by Quazz

        @banana123 Looks like your first partition is incorrectly identified as being resizable, which is likely at the root of your problems.

        Though, it looks like that partition has been altered in some way.

        Currently, FOS uses partition flags to attempt to identify “non-resizable” partitions.

        As far as I can tell, your first partition is missing essential flags (namely System and Active), causing FOS to misidentify the partition as a normal NTFS data partition that should be resized.

        george1421G 1 Reply Last reply Reply Quote 1
        • george1421G
          george1421 Moderator @Quazz
          last edited by george1421

          @Quazz said in Windows 10 single disk resizable, stuck on BIOS screen after process:

          your first partition is missing essential flags (namely System and Active),

          Only adding color commentary here: That is because it (the first partition is neither). The first partition is a recovery partition which isn’t typically bootable. While the partition layout is functionally ok, its not standard or correct. In almost all instances the uefi boot partition should be the first partition on the disk so the uefi firmware can find the boot files. It is possible to update the uefi firmware by creating an entry in the uefi boot manger to look for the uefi files on the second partition, that seems a bit awkward to do that for every system this image is deployed to. Its best to fix the partition table to match the MS standard layout. And again the recovery partition is not typically needed in an enterprise environment.

          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!

          B 1 Reply Last reply Reply Quote 0
          • B
            banana123 @george1421
            last edited by banana123

            @george1421 I am not sure how to fix this partition layout in its current state, since If I delete the recovery partition it won’t be adjacent to extend with my data partition. I looked into some freeware partition tools but it didn’t seem to cover what I need to do.

            I am a bit confused though, since I am seeing other w10 GPT disks with Recovery being on partition 1

            Is my best course of action here just starting a new w10 image?

            B 1 Reply Last reply Reply Quote 0
            • B
              banana123 @banana123
              last edited by

              @banana123

              I installed a fresh W10 and compared the log files and how it handled this partition. I changed the flags on the recovery partition so it matched. I ran these on the Recovery partition from diskpart to get it back to normal. Went to do a resize capture, saw it not resize in log file, but still got stuck on Dell Logo http://prntscr.com/qu632u

              set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001

              label: gpt
label-id: E3756D2D-6EEC-459F-BFA3-B0DCB3D4891D
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/nvme0n1p1 : start=        2048, size=     1083392, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=C0E109E0-E41D-47CB-8798-38C184966E0C, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1085440, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=D8942D98-D71D-4348-8909-A6BC265A8BBB, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=     1290240, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=E9F36812-1E24-4028-873E-83C84B42E9DE, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start=     1323008, size=   498794496, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=C0AECA45-A5CD-4B3C-AB8A-F3102F545114, name="Basic data partition"

              label: gpt
label-id: E3756D2D-6EEC-459F-BFA3-B0DCB3D4891D
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/nvme0n1p1 : start=        2048, size=     1083392, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=B4F54B55-07DE-41E0-932A-9FEC86A30A65, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1085440, size=      202752, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=B7155540-CEA7-4F35-BDDB-E3CEF4D40130, name="EFI system partition"
/dev/nvme0n1p3 : start=     1288192, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=FA93F7E5-982E-476F-93D1-8DBC9E9E6ABC, name="Microsoft reserved partition"
/dev/nvme0n1p4 : start=     1320960, size=    59195110, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=AD6ABD0C-959A-491C-A9A5-FDDD31822B65, name="Basic data partition"
              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by

                @banana123 said in Windows 10 single disk resizable, stuck on BIOS screen after process:

                Went to do a resize capture, saw it not resize in log file, but still got stuck on Dell Logo

                We might need to look into that state a bit more. Any chance you can get some more information on what happens at this point? Does is wait or freeze? Caps lock, Num lock still working? Maybe disable fast boot in the UEFI setup to hopefully get some more hints on what the issue is?!

                While this partition layout might now be standard (George you are absolutely right) I still don’t have a clue why you can capture and deploy as non-resizable but it seems to be doomed when capturing as resizable.

                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 Reply Quote 0
                • B
                  banana123 @Sebastian Roth
                  last edited by

                  @Sebastian-Roth just stuck at Dell logo. I can press caps lock to toggle, I can alt + ctrl + del. If I try to quickly boot into an F Key, it will show a bar but get stuck at 30%. Fast boot set at minimal… .

                  george1421G Q 2 Replies Last reply Reply Quote 0
                  • george1421G
                    george1421 Moderator @banana123
                    last edited by george1421

                    @banana123 As a point of data collection, how did this disk get created in this state? This is not how the M$ installer creates the disk layout.

                    Through MDT its efi, c drive 99% of free, recovery partition 100% of free space.

                    Someone/thing had to create this format structure intentionally.

                    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!

                    1 Reply Last reply Reply Quote 1
                    • Q
                      Quazz Moderator @banana123
                      last edited by Quazz

                      @banana123 I agree with George.

                      The type matches a normal Windows first partition, but it appears to have been heavily modified afterwards to be “recovery”.

                      And it seems your second partition is now getting resized for whatever reason…

                      If you don’t need the recovery partition it seems best to just start over.

                      1 Reply Last reply Reply Quote 0
                      • B
                        banana123
                        last edited by banana123

                        Not sure what happened, I originally created the image on another physical machine.
                        I am going to restart with a new image.

                        Thanks all

                        D 1 Reply Last reply Reply Quote 0
                        • D
                          dclark @banana123
                          last edited by

                          @banana123 Did the new image fix the issue for you? I am having the same issue with the Latitude 3400 model. If it did what changes did you make? Ours was working and then I updated the image with the latest Windows updates and a couple of testing apps needed by the users and now the 3400 exhibits the same behavior as you describe. All other models here are working fine with the latest image. (Windows 10)

                          B 1 Reply Last reply Reply Quote 0
                          • S
                            Sebastian Roth Moderator
                            last edited by

                            @dclark I kind of doubt you are having the exact same issue. While it might look the same at first I am fairly sure your partition layout is differnt and that is playing a big role in this case. Please open a new topic and post all your details so we can help properly: FOG version, Linux OS version, image type (resize or not), contents of d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions…

                            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
                            • B
                              banana123 @dclark
                              last edited by banana123

                              @dclark I ended up just redoing my image for my Latitude 3500s with a clean install of latest W10 from USB. I gave up trying to fix the partitions/issue.

                              No issue with new image and deployed a bunch so far (single disk resizable)

                              1 Reply Last reply Reply Quote 1
                              • 1 / 1
                              • First post
                                Last post

                              307

                              Online

                              11.7k

                              Users

                              17.1k

                              Topics

                              154.7k

                              Posts
                              Copyright © 2012-2024 FOG Project