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

    Deploy 512 Image to 4K Drive - Sector Size Issue

    Scheduled Pinned Locked Moved Hardware Compatibility
    4 Posts 2 Posters 8 Views
    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.
    • J
      JCS-RVK
      last edited by

      Hi all,
      I’m struggling to get an image captured from a 512-byte sector size disk to deploy to a 4K sector size disk. I’ve read through a variety of forum posts and have not had much luck yet. Wondering if anyone has other suggestions for things to try?

      FOG Version 1.5.10
      Image captured as Single Disk - Resizable

      This image was created on a VM in VMware Workstation Pro. It has been deployed successfully to the following devices:
      HP Pro x360 Fortis 11 inch G9
      HP Fortis Flip G1i 11
      It will not deploy to the following:
      HP Pro x360 Fortis 11 inch G11

      The G11 series devices have a 4k sector size, whereas the G9 and G1i have 512 sector size.

      I have modified the values in d1.partitions, d1.minimum.partitions and d1.shrunken.partitions by dividing by 8, which did not get the image to deploy. I eventually copied d1.mbr from another image that did deploy to the G11 series last summer which got the new image to partially deploy but threw an error during partition 4 deployment (WinRE) and the Windows instance won’t boot - it throws a BSOD for UMOUNTABLE_BOOT_VOLUME (0xED).

      W11-25H2-Base (captured image, 512 sectors)
      d1.partitions

      label: gpt
label-id: 86F191F2-2CAE-480E-B10E-A0DD33576DD0
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 134217694
sector-size: 512

/dev/nvme0n1p1 : start=        2048, size=      409600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=9F86984D-60A5-4836-B346-F8AC8E17AA4F, name="Basic data partition", attrs="GUID:63"
/dev/nvme0n1p2 : start=      411648, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=8434A6C2-7386-41F4-9176-96B9B391C711, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=      444416, size=   132143104, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=B6295B36-726D-4F69-A568-10750A329149, name="Basic data partition"
/dev/nvme0n1p4 : start=   132587520, size=     1626112, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=736D6E93-5F7D-4CF2-B6C0-48B55A4F9943, attrs="RequiredPartition GUID:63"

      d1.minimum.partitions

      label: gpt
label-id: 86F191F2-2CAE-480E-B10E-A0DD33576DD0
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 134217694
sector-size: 512

/dev/nvme0n1p1 : start=        2048, size=      409600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=9F86984D-60A5-4836-B346-F8AC8E17AA4F, name="Basic data partition", attrs="GUID:63"
/dev/nvme0n1p2 : start=      411648, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=8434A6C2-7386-41F4-9176-96B9B391C711, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=      444416, size=    34036750, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=B6295B36-726D-4F69-A568-10750A329149, name="Basic data partition"
/dev/nvme0n1p4 : start=    34481664, size=     1626112, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=736D6E93-5F7D-4CF2-B6C0-48B55A4F9943, attrs="RequiredPartition GUID:63"

      d1.shrunken.partitions

      label: gpt
label-id: 86F191F2-2CAE-480E-B10E-A0DD33576DD0
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 134217694
sector-size: 512

/dev/nvme0n1p1 : start=        2048, size=      409600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=9F86984D-60A5-4836-B346-F8AC8E17AA4F, name="Basic data partition", attrs="GUID:63"
/dev/nvme0n1p2 : start=      411648, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=8434A6C2-7386-41F4-9176-96B9B391C711, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=      444416, size=    34036750, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=B6295B36-726D-4F69-A568-10750A329149, name="Basic data partition"
/dev/nvme0n1p4 : start=   132587520, size=     1626112, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=736D6E93-5F7D-4CF2-B6C0-48B55A4F9943, attrs="RequiredPartition GUID:63"

      W11-25H2-Base-4k (I copied the image for testing purposes)
      d1.partitions

      label: gpt
label-id: 86F191F2-2CAE-480E-B10E-A0DD33576DD0
device: /dev/nvme0n1
unit: sectors
first-lba: 6
last-lba: 31246330
sector-size: 4096

/dev/nvme0n1p1 : start=        256, size=      51200, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=9F86984D-60A5-4836-B346-F8AC8E17AA4F, name="Basic data partition", attrs="GUID:63"
/dev/nvme0n1p2 : start=      51456, size=       4096, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=8434A6C2-7386-41F4-9176-96B9B391C711, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=      55552, size=   16517888, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=B6295B36-726D-4F69-A568-10750A329149, name="Basic data partition"
/dev/nvme0n1p4 : start=   16573440, size=     203264, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=736D6E93-5F7D-4CF2-B6C0-48B55A4F9943, attrs="RequiredPartition GUID:63"

      d1.minimum.partitions

      label: gpt
label-id: 86F191F2-2CAE-480E-B10E-A0DD33576DD0
device: /dev/nvme0n1
unit: sectors
first-lba: 6
last-lba: 31246330
sector-size: 4096

/dev/nvme0n1p1 : start=        256, size=      51200, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=9F86984D-60A5-4836-B346-F8AC8E17AA4F, name="Basic data partition", attrs="GUID:63"
/dev/nvme0n1p2 : start=      51456, size=       4096, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=8434A6C2-7386-41F4-9176-96B9B391C711, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=      55552, size=    4254594, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=B6295B36-726D-4F69-A568-10750A329149, name="Basic data partition"
/dev/nvme0n1p4 : start=    4310208, size=     203264, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=736D6E93-5F7D-4CF2-B6C0-48B55A4F9943, attrs="RequiredPartition GUID:63"

      d1.shrunken.partitions

      label: gpt
label-id: 86F191F2-2CAE-480E-B10E-A0DD33576DD0
device: /dev/nvme0n1
unit: sectors
first-lba: 6
last-lba: 31246330
sector-size: 4096

/dev/nvme0n1p1 : start=        256, size=      51200, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=9F86984D-60A5-4836-B346-F8AC8E17AA4F, name="Basic data partition", attrs="GUID:63"
/dev/nvme0n1p2 : start=      51456, size=       4096, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=8434A6C2-7386-41F4-9176-96B9B391C711, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=      55552, size=    4254594, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=B6295B36-726D-4F69-A568-10750A329149, name="Basic data partition"
/dev/nvme0n1p4 : start=   16573440, size=     203264, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=736D6E93-5F7D-4CF2-B6C0-48B55A4F9943, attrs="RequiredPartition GUID:63"
      Tom ElliottT 1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @JCS-RVK
        last edited by Tom Elliott

        @JCS-RVK I’m assuming by 4k you mean a “native 4k” drive? Meaning, that it cannot except 512e sectors (break out a 4k block by allowing 512 byte emulation)?

        Basically if the drive you’re working on is 4Kn you MUST capture an image from a 4k based machine and deploy. It bites, yes, but there’s no real way to group 8 512 sectors into a single 4k sector without data loss/corruption in some way shape or form.

        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

        J 1 Reply Last reply Reply Quote 0
        • J
          JCS-RVK @Tom Elliott
          last edited by

          @Tom-Elliott
          Pretty sure it’s a 4K native. I did wonder if that was going to be the case, as when I was ‘converting’ the partition files, one of them (p3, I think) didn’t cleanly divide by 8.

          Guess I’ll rebuild on one of the G11 devices instead of a VM and go from there. Don’t think VMware Workstation will do 4Kn virtual disks.

          Thanks!

          Tom ElliottT 1 Reply Last reply Reply Quote 0
          • Tom ElliottT
            Tom Elliott @JCS-RVK
            last edited by

            @JCS-RVK Understood and apologies there’s not a good method around this.

            Thanks for at least understanding. I wonder if some of the similar types of issues we’ve seen historically have a similar style of problem that I’m only coming to realize now-a-days.

            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

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

            81

            Online

            12.7k

            Users

            17.6k

            Topics

            156.6k

            Posts
            Copyright © 2012-2026 FOG Project