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

Deploying image with errors, not able to boot to Windows after image deployment

Scheduled Pinned Locked Moved
FOG Problems
2
2
363
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.
  • T
    tramirez
    last edited by tramirez Jan 26, 2022, 6:21 PM Jan 26, 2022, 11:30 PM

    I am still new to FOG, but I have my lab environment setup for it and have tested and successfully deployed just base windows 10 to both virtual and physical PCs. I am having issues when trying to deploy a new Windows 10 image to physical PCs. I think this might be a legacy/uefi issue, but I’m not entirely sure.
    So, I have a SSD(UEFI) that has windows imaged onto it along with programs that are needed for production, when you boot from it on a PC it just prompts windows installer, etc, and once finished it has all the apps loaded onto it already. I put that into a spare laptop(Dell Latitude 5580) that has both legacy and UEFI, added the host to FOG, and captured the image with no issues. I then took out that SSD and put in the original HDD and tried deploying the image to this. During the install I got two messages(I would upload pics but it says error when trying to upload)

    During deployment: Buffer I/O error on dev sda3, logical block <insert numbers here>, lost async page write
    At the end of the deployment it said: a warning has been detected! Image failed to restore and exited with exit code 1(writeimage)

    After this I try booting legacy and uefi via hdd and windows boot manager, however they both don’t work and ask for a windows installation media. I have not tried another physical PC as we do not have any more spares I can use at the moment.
    Any help would be appreciated.

    Q 1 Reply Last reply Jan 27, 2022, 3:41 PM Reply Quote 0
    • Q
      Quazz Moderator @tramirez
      last edited by Jan 27, 2022, 3:41 PM

      @tramirez Try using a different hard drive to deploy to, so we can rule out hardware issues.

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

      181

      Online

      12.1k

      Users

      17.3k

      Topics

      155.3k

      Posts
      Copyright © 2012-2024 FOG Project