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

Issues with MBR images and disk guid

Scheduled Pinned Locked Moved Solved
FOG Problems
2
5
534
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
    jemerson93
    last edited by May 10, 2019, 3:42 PM

    Hello all,

    So images that are created in MBR partitions (legacy) are receiving Unable to load Windows and please re-install Windows error. I found this to be common with Windows Server 2016, Windows 10 and Windows 7. Upon some further searching, I find “Inserting Extended Partitions” are failing and if I redeploy the failed image, I receive the following Disk Guid error. Any input would be appreciated.

    1d6bc52d-d39b-4edb-b7f2-e5c8a77ab43c-image.png

    FOG Version: 1.5.6
    bzImage Version: 4.19.36
    bzImage32 Version: 4.19.36

    J 1 Reply Last reply May 10, 2019, 7:45 PM Reply Quote 0
    • J
      Junkhacker Developer @jemerson93
      last edited by Junkhacker May 10, 2019, 1:45 PM May 10, 2019, 7:45 PM

      @jemerson93 there was a bug that was in the initial 1.5.6 release. it has been fixed. if you rerun the installer it will update the init files and solve the problem, or you can update the init files manually to the new version.

      signature:
      Junkhacker
      We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

      J 1 Reply Last reply May 10, 2019, 8:02 PM Reply Quote 0
      • J
        jemerson93 @Junkhacker
        last edited by May 10, 2019, 8:02 PM

        @Junkhacker said in Issues with MBR images and disk guid:

        @jemerson93 there was a bug that was in the initial 1.5.6 release. it has been fixed. if you rerun the installer it will update the init files and solve the problem, or you can update the init files manually to the new version.

        I saw another post regarding this after I posted it. I downloaded the inits posted and moved them over. I also changed the KERNEL RAMDISK SIZE that I saw as well. Testing now but is that what you were mentioning?

        J 1 Reply Last reply May 10, 2019, 8:13 PM Reply Quote 0
        • J
          Junkhacker Developer @jemerson93
          last edited by May 10, 2019, 8:13 PM

          @jemerson93 there shouldn’t be a need to adjust the ramdisk size for the current release init files. the installer downloads the init files specified for the release during the install. we updated the inits that are downloaded for the 1.5.6 release so that anyone running the installer now gets the init files with this issue fixed.

          signature:
          Junkhacker
          We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

          1 Reply Last reply Reply Quote 0
          • J
            jemerson93
            last edited by May 14, 2019, 8:26 PM

            @Junkhacker

            Thank you for the assistance. This issue was resolved. I’m not sure how to mark this as resolved though.

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

            317

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project